Topic 'Re: [help] Linux DHCP - can't get an IP with new Sci Atlanta Cab' in forum 'OptimumOnline' - dslreports.com

Re: [help] Linux DHCP - can't get an IP with new Sci Atlanta Cab

Wed, 05 Mar 2008 18:46:32 EDT

Cool6324 posted : Don't get a wrt54g; go for the wrt54gl. It is $10 extra but it has more memory and it runs linux. Very customizable as well. The "g" is crap, not to mention that I'm not a fan of linksys(aka crapsys); but if you have to go there please get the wrt54gl model.
--
OOL Boost running via Airport Extreme Base Station N + Gigagbit Ethernet.

Re: [help] Linux DHCP - can't get an IP with new Sci Atlanta Cab

Mon, 03 Mar 2008 20:12:03 EDT

StreetSpirit posted :

said by ehoffman:

I've tried a few other things, including having my Windows laptop get an IP and trying static IP with the same info (netmask, gateway, etc) and that didn't work. I tried spoofing my linux box's eth0 MAC address to be the same as my Windows machine's; that also didn't work. I've tried every combination of rebooting the machine and the modem - machine then modem, modem then machine, both simultaneously. As I said, when I had the SurfBoard (SBV5120) it worked fine - there was no issue at all, but now on this piece of junk it's not working at all.

Visiting »192.168.100.1/ all I get is

This feature is not enabled.
This feature has not been enabled in your cable modem.

Please contact your data services provider for more information about this feature and its availability on the network.

To exit this page, click on the "Back" button on your browser tool bar to return to the previous page or click on the "System" link above.

I'm gonna go pick up a Linksys WRT54G at Best Buy, if that lets me get up and running then that's what I'll stick with. :-/

The status page is disabled on the Webstar DPX2203 modems.. And only provides cursory info on the DCP2100. It sounds like it could possibly be a bad modem. Try swapping the ethernet cable, but it sure sounds like a bad modem to me.

Re: [help] Linux DHCP - can't get an IP with new Sci Atlanta Cab

Mon, 03 Mar 2008 20:09:08 EDT

StreetSpirit posted : I'm a big fan of ISC dhcp3, though I have a machine running udhcp as well (not sure of the version, but it's recent.) Both have no problems getting/renewing an IP. Curiously I'm using a Webstar DPX2203 at the moment.

Windows XP:

C:\ipv6\bin>ipconfig /release Ethernet adapter WAN:        Connection-specific DNS Suffix  . :       IP Address. . . . . . . . . . . . : 0.0.0.0       Subnet Mask . . . . . . . . . . . : 0.0.0.0       Default Gateway . . . . . . . . . : --C:\ipv6\bin>ipconfig /renewEthernet adapter WAN:         Connection-specific DNS Suffix  . :        IP Address. . . . . . . . . . . . : 24.185.xxx.xxx        Subnet Mask . . . . . . . . . . . : 255.255.240.0        Default Gateway . . . . . . . . . : 24.185.xxx.1

Re: [help] Linux DHCP - can't get an IP with new Sci Atlanta Cab

Mon, 03 Mar 2008 13:25:14 EDT

ehoffman posted : I've tried a few other things, including having my Windows laptop get an IP and trying static IP with the same info (netmask, gateway, etc) and that didn't work. I tried spoofing my linux box's eth0 MAC address to be the same as my Windows machine's; that also didn't work. I've tried every combination of rebooting the machine and the modem - machine then modem, modem then machine, both simultaneously. As I said, when I had the SurfBoard (SBV5120) it worked fine - there was no issue at all, but now on this piece of junk it's not working at all.

Visiting »192.168.100.1/ all I get is

This feature is not enabled.
This feature has not been enabled in your cable modem.

Please contact your data services provider for more information about this feature and its availability on the network.

To exit this page, click on the "Back" button on your browser tool bar to return to the previous page or click on the "System" link above.

I'm gonna go pick up a Linksys WRT54G at Best Buy, if that lets me get up and running then that's what I'll stick with. :-/

Re: [help] Linux DHCP - can't get an IP with new Sci Atlanta Cab

Mon, 03 Mar 2008 11:34:49 EDT

anon posted :

said by ehoffman:

however my "router" is a linux box I've had for about 7 or 8 years and it cannot acquire an IP address, ifup eth0 fails, despite working fine at my last house.[...]
I've tried playing with some of the more obscure options for dhcpcd, like -r to try and use an old protocol, but nothing seems to work.

Does that mean your Linux distro and the dhclient is 7-8 years old ? What make and versions are we talking about here for distro and the dhclient in particular?

There were some dhclient bugs fixed in OpenBSD around 1999 (fixes there tend to trickle slowly back to other compilations and OSs) that showed similar behavior: just can't get an IP, because the client was unable to understand a UNICAST DHCP reply (standard) - it would only understand a broadcast reply: those have long gone down the path of the dinosaurs, at least in cable modem networks.

It's odd that different modem types would make a difference in such a situation though:

- please post your modem's exact type and firmware (see »192.168.100.1)
- please upgrade your dhclient package, try different ones (ISC dhcp3, udhcp, etc.)
- upgrade your Linux distro, if it's really 7-8 years old :)

udhcp(d) is used in a lot of access points (like the DD-WRT code), and works with am amazingly often given its at times unstable operation (saved by the watchdog again, hah!) - and access points use a tiny fraction of your Linux boxes' electric power (my reason to switch, a small 200W box costs more than $20/month to operate) :)

ISC dhcp3 is common in most Debian-based distros, like Ubuntu, and should work under all conditions.

Re: [help] Linux DHCP - can't get an IP with new Sci Atlanta Cab

Mon, 03 Mar 2008 06:57:23 EDT

TheWiseGuy posted : Make sure the Linux Box is connected and powered ON, then power the modem OFF then ON.

The modem remembers the MAC address of the last device connected and in many cases will not recognize a new MAC except on boot.

Or you can clone the old MAC address for use with the Linux box.
--
Warning, If you post nonsense and use misinformation and are here to argue based on those methods, you will be put on ignore.

Re: [help] Linux DHCP - can't get an IP with new Sci Atlanta Cab

Mon, 03 Mar 2008 03:53:48 EDT

StreetSpirit posted : Just the other day I took a basically stock install of Ubuntu 7.10 on a new quad core PC I have yet to do much with.

I had absolutely no problem getting an IP, without any modifications.

The few tweaks I made pertained to the RWIN and were done after the modem synced up.

I gedited /etc/sysctl.conf adding the following:

net.core.rmem_max = 16777216net.core.wmem_max = 16777216net.ipv4.tcp_rmem = 4096 87380 16777216net.ipv4.tcp_wmem = 4096 65536 16777216net.ipv4.tcp_no_metrics_save = 1net.core.netdev_max_backlog = 2500net.ipv4.tcp_timestamps = 0net.ipv4.tcp_sack = 1net.ipv4.tcp_window_scaling = 1

After editing the file and adding the above, I entered the command sudo sysctl -p to apply the changes.

In any case, here's the result of an ifconfig:

IFCONFIG ubuntu@ool-18abcdef:~$ ifconfigeth0 Link encap:Ethernet HWaddr 00:04:E2:08:4A:36inet addr:24.185.xxx.xxx Bcast:255.255.255.255 Mask:255.255.240.0inet6 addr: fe80::204:e2ff:fe08:4a36/64 Scope:LinkUP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1RX packets:26367 errors:0 dropped:0 overruns:0 frame:0TX packets:2097 errors:0 dropped:0 overruns:0 carrier:0collisions:0 txqueuelen:1000RX bytes:2858999 (2.7 MiB) TX bytes:399970 (390.5 KiB)Interrupt:19 Base address:0xde00 lo Link encap:Local Loopbackinet addr:127.0.0.1 Mask:255.255.255.255inet6 addr: ::1/128 Scope:HostUP LOOPBACK RUNNING MTU:16436 Metric:1RX packets:8009 errors:0 dropped:0 overruns:0 frame:0TX packets:8009 errors:0 dropped:0 overruns:0 carrier:0collisions:0 txqueuelen:0RX bytes:730187 (713.0 KiB) TX bytes:730187 (713.0 KiB) Latency: Excellent! ubuntu@ool-18abcdef:~$ ping ftp1.optonline.netPING ftp1.srv.hcvlny.cv.net (167.206.5.41) 56(84) bytes of data.64 bytes from ftp1.srv.hcvlny.cv.net (167.206.5.41): icmp_seq=1 ttl=249 time=8.50 ms64 bytes from ftp1.srv.hcvlny.cv.net (167.206.5.41): icmp_seq=2 ttl=249 time=8.80 ms64 bytes from ftp1.srv.hcvlny.cv.net (167.206.5.41): icmp_seq=3 ttl=249 time=8.65 ms64 bytes from ftp1.srv.hcvlny.cv.net (167.206.5.41): icmp_seq=4 ttl=249 time=8.04 ms64 bytes from ftp1.srv.hcvlny.cv.net (167.206.5.41): icmp_seq=5 ttl=249 time=10.2 ms64 bytes from ftp1.srv.hcvlny.cv.net (167.206.5.41): icmp_seq=6 ttl=249 time=8.55 ms64 bytes from ftp1.srv.hcvlny.cv.net (167.206.5.41): icmp_seq=7 ttl=249 time=8.95 ms

I'm going through a speed issue that I'm working with the techs, but I basically connected the modem to the machine, making sure to power the modem off, then on, once synced, I booted Linux.

Other than a handful of RWIN tweaks, it's a completely stock install.

HTH

--
Regards,
Dave

"Abusive interrogation tactics produce bad intel, and undermine the values we hold dear. Torture's Terrible Toll: Why we must, as a nation, do better." - Senator John McCain. »www.newsweek.com/id/51200/page/1

Re: [help] Linux DHCP - can't get an IP with new Sci Atlanta Cab

Mon, 03 Mar 2008 02:30:15 EDT

Thinkdiff posted : You could also take the webstar to the local CV walk-in store and have it exchanged for a Surfboard if they have them instock. If you still have your old surfboard, you should be able to use it as well.

Re: [help] Linux DHCP - can't get an IP with new Sci Atlanta Cab

Mon, 03 Mar 2008 02:15:52 EDT

Attack Gypsy posted : Don't bother calling OOL tech support for help. They won't support Linux.

Re: [help] Linux DHCP - can't get an IP with new Sci Atlanta Cab

Mon, 03 Mar 2008 00:31:22 EDT

xirian posted : Did you reboot the modem after changing the device plugged into it?

Re: [help] Linux DHCP - can't get an IP with new Sci Atlanta Cab

Mon, 03 Mar 2008 00:00:28 EDT

anon posted : have you logged in a root and do iprenew your Ethernet interface?

[help] Linux DHCP - can't get an IP with new Sci Atlanta Cablemo

Sun, 02 Mar 2008 23:55:25 EDT

ehoffman posted : I just moved and got my cable service "transferred" to the new house, which apparently means nothing - they opened a new account for me, gave me a new OV phone number, and a new cablemodem. The guy left yesterday and I begged him to let me keep my old modem (a Motorola SurfBoard, I think) which worked flawlessly, but he insisted that he was not allowed to do that. The modem he installed is a Scientific Atlanta 2203C. It seems to work ok when windows clients are directly connected to it (as now, I'm posting from my laptop via a Linksys WAP plugged directly into the modem), however my "router" is a linux box I've had for about 7 or 8 years and it cannot acquire an IP address, ifup eth0 fails, despite working fine at my last house. Long ago I had a similar problem when I was issued a Webstar cable modem, but fortunately I had held on to my Motorola cablemodem and called customer service and they took the MAC/Serial and activated it and I was off and running. Nothing has changed on my linux box and given my past experience with the Webstar I'm pretty sure this is some problem with the cablemodem. Is there any solution to this, or am I going to have to cop out and buy a crappy netgear/linksys/dlink router just so I can get an IP?

I've tried playing with some of the more obscure options for dhcpcd, like -r to try and use an old protocol, but nothing seems to work.