Re: Cox cable modem and debian **FINALE**
On Thursday 16 August 2001 16:38, dman wrote: > On Thu, Aug 16, 2001 at 04:11:48PM -0700, Jaye Inabnit ke6sls wrote: > Greetz, > > I have been running myself through the ringer trying to get debian to log > onto my new Cox Communications cable modem using @home. I was given a new nic > (Dlink dfe-550tx) that wasn't supported by linux. I found a site and pulled > down source and attempted to build it for use on my 2.2.17 kernel (didn't > happen) then finally pulled down kernel 2.4.7, where it is supported. I can > boot up 2.4.7 and it sees both my nics (realtek and Dlink) and run pump but > it fails every time. > > At this point, I removed my lan from my realtek and started attempting to get > pump to use that card (cat5 connection). It still failed. > > I purged then re-installed pump and tried again using 2.2.17 kernel. > > Finally, I rounded up an old win95 laptop. I had a TRENDnet pcmcia dual-nic > and loaded up windoz drivers for this. What a pain! Anyway, after dozens of > reboots and locating my very old win95 cdrom, was able to get the nic working > in this computer. Finally I loaded up some of the software [EMAIL PROTECTED] > gives > you. It tried and died and would not get online with the cable modem. Huh. . . > > A call to local cable buddy. We ponder the windoz network settings. Should > work. Using Winipcfg, I released all, then renewed all - fails. . . Finally > he asks, what's my Identity setting? I looked at my booklet and told him what > it said. He informs me that isn't right, it has to have at least this many > digits (forgot what number). I look at my reciept and there is a CX number. > Is this required? Yes(!) he reports. > > I set the new identity tab, boot a few more times and it still fails. Then he > asks again what number I was given and then reports, that it is not correct! > . . . Okay, he gets on the telephone and comes back in a minute and says I > had the wrong number and we type in the new number, boot. Bingo, I am now > online with the cable modem with a DHCP'd ip address. > > So, now I KNOW the cable modem works. I can smirf as fast as the old lap top > can go. > > Back to my nics. I rename my computers HOSTNAME to the number and re-run > pump.. It fails. Next I issue the pump command using the -h hostname and -i > interface, and it still fails. > > This is where I am. Sorry about the long post, but wanted to include the > background of where I've been. > > Also note, I have read the cablemodem-howto at linuxdoc.org and not just the > @home entries, but all of them... I'm stumped. > > Any help would be very greatly appreciated. > > thank you > | I just carried over another windoz desktop (wife sure liked seeing this!) > | and fired up win98. The NIC on this box is part of my lan so I removed > | the lan settings from the nic and set them up as I did on the lap top. > | Without shutting off the cable modem, I was able to gain my ip and was on > | the net with it. > | > | I will 'assume' this means the MAC isn't an issue - that the cablemodem > | and @home dont care about the nic in use. So, this means that I can get > | two differnt windoz boxes to work but sadly, not debian at this point. > > At least you aren't pulling your hair out while it is the ISP's fault :-). > > | I am lost in this netherworld at this point. > > I noticed you were using pump to try and get the dynamic IP, etc. How > about trying dhcpcd? I haven't used pump myself, but dhcpcd is > working well on my ADSL connection. > > -D I want to thank those kind beings who helped with good ideas from this list. I was able to download dhcpcd from potato and run it without success. After reading man pages, this command worked for Eureka's [EMAIL PROTECTED] network: ~ tty3> dhcpcd -h CX000-A -D eth0 (as root) Where CX000-A was my supplied 'dns' that the Cox tech wrote on my paper reciept. Note, the original IDENT I was given was not correct. I am lucky to have a friend working for Cox locally and with his assist, he learned my REAL IDENT and gave it to me. Here, it's required to use the -D (note uppercase) aurgument for dhcpcd to nogotiate the link. It is instantanious. I renamed my local hostname to this IDENT - I will learn if it is required when I bring the nets back up next week after I finish remodeling the back of our home. It DOES NOT matter what nic's you use. The nics address will not matter to [EMAIL PROTECTED] servers. You can fire up a laptop and use it, then move it to a desktop and use it. So MAC addresses won't be an issue (this is VERY good). Cox will not supply you with a REAL smtp or pop3 address. You are given a small booklet that tells you to run outlook and IExplorer (evil, so evil!). Then tell you your smtp and pop3 servers are: mail. I talked to a user in Arizona who told me to go on IRC, once I joined the channel, he used my login to learn my domain, which is eureka1.ca.home.com. Once I installed it, mail
Re: Cox cable modem and debian**UPDATE**
On 16 Aug 2001 19:54:53 -0400, Alan Shutko wrote: > Michael Heldebrant <[EMAIL PROTECTED]> writes: > > > I may also go back to dhcpd from pump since pump seems unable to ever > > renew it's lease. > > At least, it can't obtain a new IP if the dhcp server decides to > change yours. I have a url to the bugzilla about that somewhere Mine never changes. I was looking through my syslog and pump says it just can't get a renewal.. Maybe it's a bug in unstable. I won't know until I see it upgraded. --mike
Re: Cox cable modem and debian**UPDATE**
Michael Heldebrant <[EMAIL PROTECTED]> writes: > I may also go back to dhcpd from pump since pump seems unable to ever > renew it's lease. At least, it can't obtain a new IP if the dhcp server decides to change yours. I have a url to the bugzilla about that somewhere -- Alan Shutko <[EMAIL PROTECTED]> - In a variety of flavors! If an experiment works, something has gone wrong.
Re: Cox cable modem and debian**UPDATE**
On 16 Aug 2001 19:38:33 -0400, dman wrote: > On Thu, Aug 16, 2001 at 04:11:48PM -0700, Jaye Inabnit ke6sls wrote: > > | I just carried over another windoz desktop (wife sure liked seeing this!) > and > | fired up win98. The NIC on this box is part of my lan so I removed the lan > | settings from the nic and set them up as I did on the lap top. Without > | shutting off the cable modem, I was able to gain my ip and was on the net > | with it. > | > | I will 'assume' this means the MAC isn't an issue - that the cablemodem and > | @home dont care about the nic in use. So, this means that I can get two > | differnt windoz boxes to work but sadly, not debian at this point. > > At least you aren't pulling your hair out while it is the ISP's fault :-). > > | I am lost in this netherworld at this point. > > I noticed you were using pump to try and get the dynamic IP, etc. How > about trying dhcpcd? I haven't used pump myself, but dhcpcd is > working well on my ADSL connection. I may also go back to dhcpd from pump since pump seems unable to ever renew it's lease. Every six days I fall off the net because of what I think now is pump. I'd give it a shot. --mike
Re: Cox cable modem and debian**UPDATE**
On Thu, Aug 16, 2001 at 04:11:48PM -0700, Jaye Inabnit ke6sls wrote: | I just carried over another windoz desktop (wife sure liked seeing this!) and | fired up win98. The NIC on this box is part of my lan so I removed the lan | settings from the nic and set them up as I did on the lap top. Without | shutting off the cable modem, I was able to gain my ip and was on the net | with it. | | I will 'assume' this means the MAC isn't an issue - that the cablemodem and | @home dont care about the nic in use. So, this means that I can get two | differnt windoz boxes to work but sadly, not debian at this point. At least you aren't pulling your hair out while it is the ISP's fault :-). | I am lost in this netherworld at this point. I noticed you were using pump to try and get the dynamic IP, etc. How about trying dhcpcd? I haven't used pump myself, but dhcpcd is working well on my ADSL connection. -D
Re: Cox cable modem and debian**UPDATE**
On Thursday 16 August 2001 15:31, Jaye Inabnit ke6sls wrote: > On Thursday 16 August 2001 15:14, Michael Heldebrant wrote: > > On 16 Aug 2001 15:10:24 -0700, Jaye Inabnit ke6sls wrote: > > > On Thursday 16 August 2001 14:36, Michael Heldebrant wrote: > > > > On 16 Aug 2001 13:13:32 -0700, Jaye Inabnit ke6sls wrote: > > > > > On Thursday 16 August 2001 12:54, you wrote: > > > > > > On 16 Aug 2001 12:42:29 -0700, Jaye Inabnit ke6sls wrote: > > > > > > > Greetz, > > > > Tale of woe snipped > > > > > > > > Have you tried echo 1 > /proc/sys/net/ipv4/ip_dynaddr and > > > > > > rerunning pump? > > > > > > > > > > > > --mike > > > > > > > > > > Mike, here's the report: > > > > > ~ pts/2> echo 1 > /proc/sys/net/ipv4/ip_dynaddr > > > > > ~ pts/2> > > > > > ~ pts/2> pump -h cx1243895-a -i eth0 > > > > > Operation failed. > > > > > ~ pts/2> > > > > > > > > > > I am using my 2.2.17 kernel at this time. Any other ideas? > > > > > > > > Silly question... You are root right? I don't see the # prompt. > > > > Can we also see parts of /var/log/syslog with pump relevant info? > > > > The output from ifconfig, /etc/network/interfaces and /proc/modules > > > > would be helpfull. Cat /proc/sys/net/ipv4/ip_dynaddr to make sure > > > > it's one now too please. > > > > > > > > --mike > > > > > > Mike, > > > > > > Yes, I was root. I removed most of my prompt for this email but left > > > that so you would understand I was doing this at a command prompt :) > > > I've added an excerpt of my log file. Also, you can see the interfaces > > > file as it now > > > > Do you have any firewall rules at the moment? ipchains -L -v -n output > > may show something. Sorry to be demanding all this input from you, I'm > > still fishing for something that seems wrong. So far everything seems > > ok. > > > > The only other thing that I can think of at the moment would be to try > > and power cycle both the cable modem and the computer. I seem to have a > > problem where my cable modem will not connect no matter what unless I > > reboot. I'm still investigating why. > > > > --mike > > Mike, > > I do have ipchains running: > > YOU ARE ROOT!! on cx1243895-a > ~ pts/2> ipchains -L -v -n > Chain input (policy ACCEPT: 3680 packets, 1560984 bytes): > pkts bytes target prot opttosa tosx ifname mark outsize > source > destination ports > 0 0 DENY udp -- 0xFF 0x00 ppp0 > 0.0.0.0/0 > 0.0.0.0/0 * -> 137 > 0 0 DENY udp -- 0xFF 0x00 ppp0 > 0.0.0.0/0 > 0.0.0.0/0 * -> 138 > 0 0 DENY udp -- 0xFF 0x00 ppp0 > 0.0.0.0/0 > 0.0.0.0/0 * -> 139 > 0 0 DENY tcp -- 0xFF 0x00 ppp0 > 0.0.0.0/0 > 0.0.0.0/0 * -> 137 > 0 0 DENY tcp -- 0xFF 0x00 ppp0 > 0.0.0.0/0 > 0.0.0.0/0 * -> 138 > 0 0 DENY tcp -- 0xFF 0x00 ppp0 > 0.0.0.0/0 > 0.0.0.0/0 * -> 139 > Chain forward (policy ACCEPT: 0 packets, 0 bytes): > Chain output (policy ACCEPT: 3634 packets, 311915 bytes): > YOU ARE ROOT!! on cx1243895-a > ~ pts/2> > > I will try to gain yet another laptop and see if the MAC has anything to do > with this mess. As far as I could find on the cablemodem-howto, @home > doesn't have the mess of the MAC address. as you can also see, I have > changed the name of my computer host (blowing the lan apart for the time > being) to deal with the IDENDINTITY hupla.. I just carried over another windoz desktop (wife sure liked seeing this!) and fired up win98. The NIC on this box is part of my lan so I removed the lan settings from the nic and set them up as I did on the lap top. Without shutting off the cable modem, I was able to gain my ip and was on the net with it. I will 'assume' this means the MAC isn't an issue - that the cablemodem and @home dont care about the nic in use. So, this means that I can get two differnt windoz boxes to work but sadly, not debian at this point. I am lost in this netherworld at this point. -- Jaye Inabnit\ARS ke6sls\/A GNU-Debian linux user \/ http://www.qsl.net/ke6sls If it's stupid, but works, it ain't stupid. SHOUT JUST FOR FUN. Free software, in a free world, for a free spirit. Please Support freedom!
Re: Cox cable modem and debian
On Thursday 16 August 2001 15:14, Michael Heldebrant wrote: > On 16 Aug 2001 15:10:24 -0700, Jaye Inabnit ke6sls wrote: > > On Thursday 16 August 2001 14:36, Michael Heldebrant wrote: > > > On 16 Aug 2001 13:13:32 -0700, Jaye Inabnit ke6sls wrote: > > > > On Thursday 16 August 2001 12:54, you wrote: > > > > > On 16 Aug 2001 12:42:29 -0700, Jaye Inabnit ke6sls wrote: > > > > > > Greetz, > > Tale of woe snipped > > > > > > Have you tried echo 1 > /proc/sys/net/ipv4/ip_dynaddr and rerunning > > > > > pump? > > > > > > > > > > --mike > > > > > > > > Mike, here's the report: > > > > ~ pts/2> echo 1 > /proc/sys/net/ipv4/ip_dynaddr > > > > ~ pts/2> > > > > ~ pts/2> pump -h cx1243895-a -i eth0 > > > > Operation failed. > > > > ~ pts/2> > > > > > > > > I am using my 2.2.17 kernel at this time. Any other ideas? > > > > > > Silly question... You are root right? I don't see the # prompt. Can > > > we also see parts of /var/log/syslog with pump relevant info? The > > > output from ifconfig, /etc/network/interfaces and /proc/modules would > > > be helpfull. Cat /proc/sys/net/ipv4/ip_dynaddr to make sure it's one > > > now too please. > > > > > > --mike > > > > Mike, > > > > Yes, I was root. I removed most of my prompt for this email but left that > > so you would understand I was doing this at a command prompt :) I've > > added an excerpt of my log file. Also, you can see the interfaces file as > > it now > > Do you have any firewall rules at the moment? ipchains -L -v -n output > may show something. Sorry to be demanding all this input from you, I'm > still fishing for something that seems wrong. So far everything seems > ok. > > The only other thing that I can think of at the moment would be to try > and power cycle both the cable modem and the computer. I seem to have a > problem where my cable modem will not connect no matter what unless I > reboot. I'm still investigating why. > > --mike Mike, I do have ipchains running: YOU ARE ROOT!! on cx1243895-a ~ pts/2> ipchains -L -v -n Chain input (policy ACCEPT: 3680 packets, 1560984 bytes): pkts bytes target prot opttosa tosx ifname mark outsize source destination ports 0 0 DENY udp -- 0xFF 0x00 ppp0 0.0.0.0/0 0.0.0.0/0 * -> 137 0 0 DENY udp -- 0xFF 0x00 ppp0 0.0.0.0/0 0.0.0.0/0 * -> 138 0 0 DENY udp -- 0xFF 0x00 ppp0 0.0.0.0/0 0.0.0.0/0 * -> 139 0 0 DENY tcp -- 0xFF 0x00 ppp0 0.0.0.0/0 0.0.0.0/0 * -> 137 0 0 DENY tcp -- 0xFF 0x00 ppp0 0.0.0.0/0 0.0.0.0/0 * -> 138 0 0 DENY tcp -- 0xFF 0x00 ppp0 0.0.0.0/0 0.0.0.0/0 * -> 139 Chain forward (policy ACCEPT: 0 packets, 0 bytes): Chain output (policy ACCEPT: 3634 packets, 311915 bytes): YOU ARE ROOT!! on cx1243895-a ~ pts/2> I will try to gain yet another laptop and see if the MAC has anything to do with this mess. As far as I could find on the cablemodem-howto, @home doesn't have the mess of the MAC address. as you can also see, I have changed the name of my computer host (blowing the lan apart for the time being) to deal with the IDENDINTITY hupla.. --
Re: Cox cable modem and debian
On 16 Aug 2001 15:10:24 -0700, Jaye Inabnit ke6sls wrote: > On Thursday 16 August 2001 14:36, Michael Heldebrant wrote: > > On 16 Aug 2001 13:13:32 -0700, Jaye Inabnit ke6sls wrote: > > > On Thursday 16 August 2001 12:54, you wrote: > > > > On 16 Aug 2001 12:42:29 -0700, Jaye Inabnit ke6sls wrote: > > > > > Greetz, > > > > > Tale of woe snipped > > > > > > > > Have you tried echo 1 > /proc/sys/net/ipv4/ip_dynaddr and rerunning > > > > pump? > > > > > > > > --mike > > > > > > Mike, here's the report: > > > ~ pts/2> echo 1 > /proc/sys/net/ipv4/ip_dynaddr > > > ~ pts/2> > > > ~ pts/2> pump -h cx1243895-a -i eth0 > > > Operation failed. > > > ~ pts/2> > > > > > > I am using my 2.2.17 kernel at this time. Any other ideas? > > > > Silly question... You are root right? I don't see the # prompt. Can > > we also see parts of /var/log/syslog with pump relevant info? The > > output from ifconfig, /etc/network/interfaces and /proc/modules would be > > helpfull. Cat /proc/sys/net/ipv4/ip_dynaddr to make sure it's one now > > too please. > > > > --mike > > Mike, > > Yes, I was root. I removed most of my prompt for this email but left that so > you would understand I was doing this at a command prompt :) I've added an > excerpt of my log file. Also, you can see the interfaces file as it now Do you have any firewall rules at the moment? ipchains -L -v -n output may show something. Sorry to be demanding all this input from you, I'm still fishing for something that seems wrong. So far everything seems ok. The only other thing that I can think of at the moment would be to try and power cycle both the cable modem and the computer. I seem to have a problem where my cable modem will not connect no matter what unless I reboot. I'm still investigating why. --mike
Re: Cox cable modem and debian
On Thursday 16 August 2001 14:36, Michael Heldebrant wrote: > On 16 Aug 2001 13:13:32 -0700, Jaye Inabnit ke6sls wrote: > > On Thursday 16 August 2001 12:54, you wrote: > > > On 16 Aug 2001 12:42:29 -0700, Jaye Inabnit ke6sls wrote: > > > > Greetz, > > > > > > > > I have been running myself through the ringer trying to get debian to > > > > log onto my new Cox Communications cable modem using @home. I was > > > > given a new nic (Dlink dfe-550tx) that wasn't supported by linux. I > > > > found a site and pulled down source and attempted to build it for use > > > > on my 2.2.17 kernel (didn't happen) then finally pulled down kernel > > > > 2.4.7, where it is supported. I can boot up 2.4.7 and it sees both my > > > > nics (realtek and Dlink) and run pump but it fails every time. > > > > > > > > At this point, I removed my lan from my realtek and started > > > > attempting to get pump to use that card (cat5 connection). It still > > > > failed. > > > > > > > > I purged then re-installed pump and tried again using 2.2.17 kernel. > > > > > > > > Finally, I rounded up an old win95 laptop. I had a TRENDnet pcmcia > > > > dual-nic and loaded up windoz drivers for this. What a pain! Anyway, > > > > after dozens of reboots and locating my very old win95 cdrom, was > > > > able to get the nic working in this computer. Finally I loaded up > > > > some of the software [EMAIL PROTECTED] gives you. It tried and died and > > > > would > > > > not get online with the cable modem. Huh. . . > > > > > > > > A call to local cable buddy. We ponder the windoz network settings. > > > > Should work. Using Winipcfg, I released all, then renewed all - > > > > fails. . . Finally he asks, what's my Identity setting? I looked at > > > > my booklet and told him what it said. He informs me that isn't right, > > > > it has to have at least this many digits (forgot what number). I look > > > > at my reciept and there is a CX number. Is this required? Yes(!) he > > > > reports. > > > > > > > > I set the new identity tab, boot a few more times and it still fails. > > > > Then he asks again what number I was given and then reports, that it > > > > is not correct! . . . Okay, he gets on the telephone and comes back > > > > in a minute and says I had the wrong number and we type in the new > > > > number, boot. Bingo, I am now online with the cable modem with a > > > > DHCP'd ip address. > > > > > > > > So, now I KNOW the cable modem works. I can smirf as fast as the old > > > > lap top can go. > > > > > > > > Back to my nics. I rename my computers HOSTNAME to the number and > > > > re-run pump.. It fails. Next I issue the pump command using the -h > > > > hostname and -i interface, and it still fails. > > > > > > > > This is where I am. Sorry about the long post, but wanted to include > > > > the background of where I've been. > > > > > > > > Also note, I have read the cablemodem-howto at linuxdoc.org and not > > > > just the @home entries, but all of them... I'm stumped. > > > > > > > > Any help would be very greatly appreciated. > > > > > > > > thank you > > > > > > Have you tried echo 1 > /proc/sys/net/ipv4/ip_dynaddr and rerunning > > > pump? > > > > > > --mike > > > > Mike, here's the report: > > ~ pts/2> echo 1 > /proc/sys/net/ipv4/ip_dynaddr > > ~ pts/2> > > ~ pts/2> pump -h cx1243895-a -i eth0 > > Operation failed. > > ~ pts/2> > > > > I am using my 2.2.17 kernel at this time. Any other ideas? > > Silly question... You are root right? I don't see the # prompt. Can > we also see parts of /var/log/syslog with pump relevant info? The > output from ifconfig, /etc/network/interfaces and /proc/modules would be > helpfull. Cat /proc/sys/net/ipv4/ip_dynaddr to make sure it's one now > too please. > > --mike Mike, Yes, I was root. I removed most of my prompt for this email but left that so you would understand I was doing this at a command prompt :) I've added an excerpt of my log file. Also, you can see the interfaces file as it now stands.start snip of logfile Aug 16 13:10:16 cx1243895-a pppd[483]: rcvd [LCP EchoRep id=0x94 magic=0x0] Aug 16 13:10:27 cx1243895-a pumpd[849]: PUMP: sending discover Aug 16 13:10:27 cx1243895-a pumpd[849]: breq: opcode: 1 Aug 16 13:10:27 cx1243895-a pumpd[849]: breq: hw: 1 Aug 16 13:10:27 cx1243895-a pumpd[849]: breq: hwlength: 6 Aug 16 13:10:27 cx1243895-a pumpd[849]: breq: hopcount: 0 Aug 16 13:10:27 cx1243895-a pumpd[849]: breq: id: 0x 6b40a98 Aug 16 13:10:27 cx1243895-a pumpd[849]: breq: secs: 0 Aug 16 13:10:27 cx1243895-a pumpd[849]: breq: flags: 0x 0 Aug 16 13:10:27 cx1243895-a pumpd[849]: breq: ciaddr: 0.0.0.0 Aug 16 13:10:27 cx1243895-a pumpd[849]: breq: yiaddr: 0.0.0.0 Aug 16 13:10:27 cx1243895-a pumpd[849]: breq: server_ip: 0.0.0.0 Aug 16 13:10:27 cx1243895-a pumpd[849]: breq: bootp_gw_ip: 0.0.0.0 Aug 16 13:10:27 cx1243895-a pumpd[849]: breq: hwaddr: Aug 16 13:10:27 cx1243895-a pumpd[849]: breq: servername: Aug 16 13:10:27 cx1243895-a pumpd[849]: breq: bootfile: Aug 16 13:10:2
Re: Cox cable modem and debian
Hmm... I can't say this is true for Cox, but it is true for Adelphia. I'm wondering if what they are calling an Identity setting is the MAC address of the NIC? If so, the problem is that the MAC address you give the cable company is the only one that will be able to obtain an IP address using pump. You can obtain your MAC address with ifconfig, the MAC address is the HWaddr and should be in the format of xx:xx:xx:xx:xx:xx Call them and tell them to set your Identity to this address. If you need to hook more than one computer up, either buy a router or set up a box with two nics using NAT. Kent On Thu, Aug 16, 2001 at 12:42:29PM -0700, Jaye Inabnit ke6sls wrote: > > Greetz, > > I have been running myself through the ringer trying to get debian to log > onto my new Cox Communications cable modem using @home. I was given a new nic > (Dlink dfe-550tx) that wasn't supported by linux. I found a site and pulled > down source and attempted to build it for use on my 2.2.17 kernel (didn't > happen) then finally pulled down kernel 2.4.7, where it is supported. I can > boot up 2.4.7 and it sees both my nics (realtek and Dlink) and run pump but > it fails every time. > > At this point, I removed my lan from my realtek and started attempting to get > pump to use that card (cat5 connection). It still failed. > > I purged then re-installed pump and tried again using 2.2.17 kernel. > > Finally, I rounded up an old win95 laptop. I had a TRENDnet pcmcia dual-nic > and loaded up windoz drivers for this. What a pain! Anyway, after dozens of > reboots and locating my very old win95 cdrom, was able to get the nic working > in this computer. Finally I loaded up some of the software [EMAIL PROTECTED] > gives > you. It tried and died and would not get online with the cable modem. Huh. . . > > A call to local cable buddy. We ponder the windoz network settings. Should > work. Using Winipcfg, I released all, then renewed all - fails. . . Finally > he asks, what's my Identity setting? I looked at my booklet and told him what > it said. He informs me that isn't right, it has to have at least this many > digits (forgot what number). I look at my reciept and there is a CX number. > Is this required? Yes(!) he reports. > > I set the new identity tab, boot a few more times and it still fails. Then he > asks again what number I was given and then reports, that it is not correct! > . . . Okay, he gets on the telephone and comes back in a minute and says I > had the wrong number and we type in the new number, boot. Bingo, I am now > online with the cable modem with a DHCP'd ip address. > > So, now I KNOW the cable modem works. I can smirf as fast as the old lap top > can go. > > Back to my nics. I rename my computers HOSTNAME to the number and re-run > pump.. It fails. Next I issue the pump command using the -h hostname and -i > interface, and it still fails. > > This is where I am. Sorry about the long post, but wanted to include the > background of where I've been. > > Also note, I have read the cablemodem-howto at linuxdoc.org and not just the > @home entries, but all of them... I'm stumped. > > Any help would be very greatly appreciated. > > thank you > > > -- > > Jaye Inabnit\ARS ke6sls\/A GNU-Debian linux user \/ http://www.qsl.net/ke6sls > If it's stupid, but works, it ain't stupid. SHOUT JUST FOR FUN. > Free software, in a free world, for a free spirit. Please Support freedom! > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >
Re: Cox cable modem and debian
On 16 Aug 2001 13:13:32 -0700, Jaye Inabnit ke6sls wrote: > On Thursday 16 August 2001 12:54, you wrote: > > On 16 Aug 2001 12:42:29 -0700, Jaye Inabnit ke6sls wrote: > > > Greetz, > > > > > > I have been running myself through the ringer trying to get debian to log > > > onto my new Cox Communications cable modem using @home. I was given a new > > > nic (Dlink dfe-550tx) that wasn't supported by linux. I found a site and > > > pulled down source and attempted to build it for use on my 2.2.17 kernel > > > (didn't happen) then finally pulled down kernel 2.4.7, where it is > > > supported. I can boot up 2.4.7 and it sees both my nics (realtek and > > > Dlink) and run pump but it fails every time. > > > > > > At this point, I removed my lan from my realtek and started attempting to > > > get pump to use that card (cat5 connection). It still failed. > > > > > > I purged then re-installed pump and tried again using 2.2.17 kernel. > > > > > > Finally, I rounded up an old win95 laptop. I had a TRENDnet pcmcia > > > dual-nic and loaded up windoz drivers for this. What a pain! Anyway, > > > after dozens of reboots and locating my very old win95 cdrom, was able to > > > get the nic working in this computer. Finally I loaded up some of the > > > software [EMAIL PROTECTED] gives you. It tried and died and would not get > > > online > > > with the cable modem. Huh. . . > > > > > > A call to local cable buddy. We ponder the windoz network settings. > > > Should work. Using Winipcfg, I released all, then renewed all - fails. . > > > . Finally he asks, what's my Identity setting? I looked at my booklet and > > > told him what it said. He informs me that isn't right, it has to have at > > > least this many digits (forgot what number). I look at my reciept and > > > there is a CX number. Is this required? Yes(!) he reports. > > > > > > I set the new identity tab, boot a few more times and it still fails. > > > Then he asks again what number I was given and then reports, that it is > > > not correct! . . . Okay, he gets on the telephone and comes back in a > > > minute and says I had the wrong number and we type in the new number, > > > boot. Bingo, I am now online with the cable modem with a DHCP'd ip > > > address. > > > > > > So, now I KNOW the cable modem works. I can smirf as fast as the old lap > > > top can go. > > > > > > Back to my nics. I rename my computers HOSTNAME to the number and re-run > > > pump.. It fails. Next I issue the pump command using the -h hostname and > > > -i interface, and it still fails. > > > > > > This is where I am. Sorry about the long post, but wanted to include the > > > background of where I've been. > > > > > > Also note, I have read the cablemodem-howto at linuxdoc.org and not just > > > the @home entries, but all of them... I'm stumped. > > > > > > Any help would be very greatly appreciated. > > > > > > thank you > > > > Have you tried echo 1 > /proc/sys/net/ipv4/ip_dynaddr and rerunning pump? > > > > --mike > > Mike, here's the report: > ~ pts/2> echo 1 > /proc/sys/net/ipv4/ip_dynaddr > ~ pts/2> > ~ pts/2> pump -h cx1243895-a -i eth0 > Operation failed. > ~ pts/2> > > I am using my 2.2.17 kernel at this time. Any other ideas? Silly question... You are root right? I don't see the # prompt. Can we also see parts of /var/log/syslog with pump relevant info? The output from ifconfig, /etc/network/interfaces and /proc/modules would be helpfull. Cat /proc/sys/net/ipv4/ip_dynaddr to make sure it's one now too please. --mike
Re: Cox cable modem and debian
On Thursday 16 August 2001 12:54, you wrote: > On 16 Aug 2001 12:42:29 -0700, Jaye Inabnit ke6sls wrote: > > Greetz, > > > > I have been running myself through the ringer trying to get debian to log > > onto my new Cox Communications cable modem using @home. I was given a new > > nic (Dlink dfe-550tx) that wasn't supported by linux. I found a site and > > pulled down source and attempted to build it for use on my 2.2.17 kernel > > (didn't happen) then finally pulled down kernel 2.4.7, where it is > > supported. I can boot up 2.4.7 and it sees both my nics (realtek and > > Dlink) and run pump but it fails every time. > > > > At this point, I removed my lan from my realtek and started attempting to > > get pump to use that card (cat5 connection). It still failed. > > > > I purged then re-installed pump and tried again using 2.2.17 kernel. > > > > Finally, I rounded up an old win95 laptop. I had a TRENDnet pcmcia > > dual-nic and loaded up windoz drivers for this. What a pain! Anyway, > > after dozens of reboots and locating my very old win95 cdrom, was able to > > get the nic working in this computer. Finally I loaded up some of the > > software [EMAIL PROTECTED] gives you. It tried and died and would not get > > online > > with the cable modem. Huh. . . > > > > A call to local cable buddy. We ponder the windoz network settings. > > Should work. Using Winipcfg, I released all, then renewed all - fails. . > > . Finally he asks, what's my Identity setting? I looked at my booklet and > > told him what it said. He informs me that isn't right, it has to have at > > least this many digits (forgot what number). I look at my reciept and > > there is a CX number. Is this required? Yes(!) he reports. > > > > I set the new identity tab, boot a few more times and it still fails. > > Then he asks again what number I was given and then reports, that it is > > not correct! . . . Okay, he gets on the telephone and comes back in a > > minute and says I had the wrong number and we type in the new number, > > boot. Bingo, I am now online with the cable modem with a DHCP'd ip > > address. > > > > So, now I KNOW the cable modem works. I can smirf as fast as the old lap > > top can go. > > > > Back to my nics. I rename my computers HOSTNAME to the number and re-run > > pump.. It fails. Next I issue the pump command using the -h hostname and > > -i interface, and it still fails. > > > > This is where I am. Sorry about the long post, but wanted to include the > > background of where I've been. > > > > Also note, I have read the cablemodem-howto at linuxdoc.org and not just > > the @home entries, but all of them... I'm stumped. > > > > Any help would be very greatly appreciated. > > > > thank you > > Have you tried echo 1 > /proc/sys/net/ipv4/ip_dynaddr and rerunning pump? > > --mike Mike, here's the report: ~ pts/2> echo 1 > /proc/sys/net/ipv4/ip_dynaddr ~ pts/2> ~ pts/2> pump -h cx1243895-a -i eth0 Operation failed. ~ pts/2> I am using my 2.2.17 kernel at this time. Any other ideas? -- Jaye Inabnit\ARS ke6sls\/A GNU-Debian linux user \/ http://www.qsl.net/ke6sls If it's stupid, but works, it ain't stupid. SHOUT JUST FOR FUN. Free software, in a free world, for a free spirit. Please Support freedom!
Re: Cox cable modem and debian
On 16 Aug 2001 12:42:29 -0700, Jaye Inabnit ke6sls wrote: > > Greetz, > > I have been running myself through the ringer trying to get debian to log > onto my new Cox Communications cable modem using @home. I was given a new nic > (Dlink dfe-550tx) that wasn't supported by linux. I found a site and pulled > down source and attempted to build it for use on my 2.2.17 kernel (didn't > happen) then finally pulled down kernel 2.4.7, where it is supported. I can > boot up 2.4.7 and it sees both my nics (realtek and Dlink) and run pump but > it fails every time. > > At this point, I removed my lan from my realtek and started attempting to get > pump to use that card (cat5 connection). It still failed. > > I purged then re-installed pump and tried again using 2.2.17 kernel. > > Finally, I rounded up an old win95 laptop. I had a TRENDnet pcmcia dual-nic > and loaded up windoz drivers for this. What a pain! Anyway, after dozens of > reboots and locating my very old win95 cdrom, was able to get the nic working > in this computer. Finally I loaded up some of the software [EMAIL PROTECTED] > gives > you. It tried and died and would not get online with the cable modem. Huh. . . > > A call to local cable buddy. We ponder the windoz network settings. Should > work. Using Winipcfg, I released all, then renewed all - fails. . . Finally > he asks, what's my Identity setting? I looked at my booklet and told him what > it said. He informs me that isn't right, it has to have at least this many > digits (forgot what number). I look at my reciept and there is a CX number. > Is this required? Yes(!) he reports. > > I set the new identity tab, boot a few more times and it still fails. Then he > asks again what number I was given and then reports, that it is not correct! > . . . Okay, he gets on the telephone and comes back in a minute and says I > had the wrong number and we type in the new number, boot. Bingo, I am now > online with the cable modem with a DHCP'd ip address. > > So, now I KNOW the cable modem works. I can smirf as fast as the old lap top > can go. > > Back to my nics. I rename my computers HOSTNAME to the number and re-run > pump.. It fails. Next I issue the pump command using the -h hostname and -i > interface, and it still fails. > > This is where I am. Sorry about the long post, but wanted to include the > background of where I've been. > > Also note, I have read the cablemodem-howto at linuxdoc.org and not just the > @home entries, but all of them... I'm stumped. > > Any help would be very greatly appreciated. > > thank you Have you tried echo 1 > /proc/sys/net/ipv4/ip_dynaddr and rerunning pump? --mike
