Rebooting the computer will not connect to the internet using dhcp first try. Using the Verizon 327W Versalink router / modem gateway. First see the picture of it: http://onlinehelp.verizon.net/consumer/bin/images/Modems/WestellVersaLink_200.gif When (read below it gets interesting)I give you the steps to the problem. Reproducible: Always Steps to Reproduce: (read all) 1.Reboot the computer 2. Bringing eth0 up via DHCP.... [ waits 30 seconds about] 3. The modem/router combo lights go from green to red. (it reboots itself and disconnects from the phone line as shown by the lights). 4. The lights go from red to green again (line comes up) 5. Bringing eth0 up via DHCP.... ip received 192.168.X.XX correctly. 6. It does not seem a config error as I even copied from live cd's the dhcp info. Actual Results: What has happened here was it took "two times" between trying to connect switching to reset and switching to normal and getting the ip. Expected Results: The Dhcp ip should have been received on the first try on each boot. Without resetting the hardware which causes "2" minutes brining up. Which does not error out but reboots the equipment (modem/router gateway). Using "knoppox live cd" or gentoo live cd gives a normal (no reboot issues). Next few reboots from normal gentoo installed on the hardrive will get the ip quick. Then it starts again unless using any live cd. It seems like the ip expires or something and only live cd's renew To have no problem dhcp boot: 1. Insert morphix live cd or any with dhcp support. 2. bring dhcp up 3. remove cd 4. reboot computer 5. gentoo dhcp gets ip quick on next 100's of boots 6. Wait a while and reboot and it starts.
CORRECTION: Gentoo live cd does not let more dhcp boot to go normal. But it does allow to auto config it for that live cd session. Other dhcp live cd's allow those 100's of normal boots.
Could you test this using baselayout-1.11.12-r1 please?
It seems this version is not in portage. Additionally the latest version after this one. Does not work and brings eth0 errors! So far only with gentoo this been going on, I am speechless, I will try to reinstall everything 1 more time then see if anything can be done. Thanks Again will give a try bit longer. This is a severe problem here, not a normal liveable app! Networking!
Sorry, I got lost here in links with the comments section. I meant the baselayout seems not to fix anything and introduces more issues (latest).
If I can be of anymore help let me know. However, please provide me with needed info when requesting my output. Thanks. I am typing this in links, waiting for mozilla I know this has nothing to do with bug. But as you see my sloppy typing is because of this. emptytree emptytree grin :-D
This link below is a better step by step info on the bug. http://forums.gentoo.org/viewtopic-t-331146-highlight-dhcpcd+modem+resets.html
Could you test with dhcpcd-1.3.22_p4-r9 please? If that fails, try another dhcp client like udhcpc or dhclient as described at the below URL http://dev.gentoo.org/~uberlord/net-book/hb_part1_chap3.html#doc_chap3
It did not fix it got the new version as mentioned. Going try other clients maybe if I do will let you know.
Hi again, think I was able to find the root cause. It seems gentoo is a bit different. This issue was couple in one, going to run down my findings. * Versalink (327w) modem does its own dhcp not external. Running dhcp client will force the modem/router to act as an ip itself instead of getting one. According to the docs that is what has been happening. * Versalink needs to be set something like this: * Static net: 192.168.1.XX = XX The first machine on the network range 14-47. broadcast: 255.255.1.255 mask: 255.255.255.0 gateway: 192.168.1.1 * Or adsl-setup bypassing all the features of the product. Meaning, no features provided by its web control panel. After nearly 6 months, after getting this product, nearly giving up on fixing it. This issue seems to have been found and resolved. Please keep it open for a bit longer. In order so I could confirm it was indeed fixed. In about "2" day will get back with a solid confirm if true.
K everything is fine it indeed was the issue.
