very annoying persistent problem Hi, I am having internet connection
MandrivaThis Forum is for the discussion of Mandriva (Mandrake) Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
very annoying persistent problem Hi, I am having internet connection
Hi, I am having internet access problems. I have a BT Voyager 210 router modem connecting through an Edimax PCI ethernet 10/100 card with the RTL 8139 chipset. I am running Mandriva 2006 official. If I install a fresh hard drive and configure the network connection as LAN -> DHCP -> nothing is entered for host name, zeroconf etc, I just click through them. I choose for "allow users to start" it puts the connection in place. On reboot I can go on the net. After shutdown, the next boot up cannot connect to the internet. Using firefox to connect to the routers IP address I get "connection was refused". If I ping the IP address I get "network is unreachable". Using ether-wake on the ethernet cards mac address it seems to do it, also same applies for the routers mac address. Using telnet with the open (IP add) command I get "the network is unreachable" using the open command on the routers mac address I get "temporary failure in name resolution". Also, every time I boot up some program changes my /etc/resolv.conf file. It contains the search as home and the nameserver with the correct IP add of the router. I added the gateway add of the router as a nameserver. After the next boot up, resolv.conf has been overwritten and contains search home and nameserver (modems IP), but the gateway has gone. Sometimes I can use the "monitor network" tool and it will connect, most times it will not. Sometimes, if I delete the connection and re-introduce it, it will work, but most times not. Sometimes, if I delete the connection and boot up with the install DVD, run update, not install, and configure the LAN, it works, but not always. What is happening??? Is this a denial of service bug from our friends in north west USA? I think it must be a config error somewhere and when booting, the system is seeing a (non existent)LAN error, fixing it, and ultimately dropping the connection. Any help greatly appreciated.
PLEASE NOTE: this is happening on 3 different hard drives, one of them running the 64 bit version and the other 2 on 32 bit. I am reduced to using the laptop to put this thread.
Hi, I am having internet access problems. I have a BT Voyager 210 router modem connecting through an Edimax PCI ethernet 10/100 card with the RTL 8139 chipset. I am running Mandriva 2006 official. If I install a fresh hard drive and configure the network connection as LAN -> DHCP -> nothing is entered for host name, zeroconf etc, I just click through them. I choose for "allow users to start" it puts the connection in place. On reboot I can go on the net.
so far so good... though I would have expected the connection to work right away.
Quote:
After shutdown, the next boot up cannot connect to the internet. Using firefox to connect to the routers IP address I get "connection was refused". If I ping the IP address I get "network is unreachable".
Which prompts us to look suspiciously at that router there...
Quote:
Using ether-wake on the ethernet cards mac address it seems to do it, also same applies for the routers mac address. Using telnet with the open (IP add) command I get "the network is unreachable" using the open command on the routers mac address I get "temporary failure in name resolution".
... it is possible we should rule out the card going to sleep: boot with noacpi.
You should be able to bring the card up with ifup eth0, also show us the result of ifconfig (CLI tools are very informative.)
Quote:
Also, every time I boot up, some program changes my /etc/resolv.conf file. It contains the search as home and the nameserver with the correct IP add of the router. I added the gateway address of the router as a nameserver. After the next boot up, resolv.conf has been overwritten and contains search home and nameserver (modems IP), but the gateway has gone.
Sounds like you don't know what /etc/resolv.conf is supposed to be doing.
Quote:
I think it must be a config error somewhere and when booting, the system is seeing a (non existent)LAN error, fixing it, and ultimately dropping the connection.
What error? Try dmesg after this happens and look for network-type messages.
Quote:
PLEASE NOTE: this is happening on 3 different hard drives, one of them running the 64 bit version and the other 2 on 32 bit. I am reduced to using the laptop to put this thread.
The HDD is not the problem at all, there is no reason to think it would be. It is either the nic, the router, or a setting. Have you tried with a different nic? Have you tried with a different router?
Well, before I read your answer, I booted up on 1 of the 32 bit drives, got same result, no LAN. I then turned the router OFF. Then I switched it on again, BINGO, connection, after the router booted, was instant AND I am here on the 32 bit drive. I will try booting up with a dead router and THEN, once fully booted, switch the router on. If this works, it is the way to do it. The Voyager 210 is specifically designed to work with windows and at least one of the support team at Voyager thinks it can NEVER be made to work under Linux. So much for his knowledge. Thank you for your speedy reply to my problem. If this makes you see something else, I would love to know but if the above method works every time, then so be it. I will let you know on here what result I get. Thanks again.
Then I rebooted, expecting to be able to give an ifconfig result with the connection down and, would you believe, it came straight up from boot. Will post an ifconfig result the next time I get a down result from boot.
The Voyager 210 is specifically designed to work with windows
BT Voyager 210 is known for intermittent faults - overheating, random disconnects, etc. Some people never see it, others find it persistently annoying. Most of these people get a new router. It is common to read that switching the router off, wait a bit, switch on, fixes connection issues. Sometimes a firmware upgrade will do the trick.
I'd also look carefully through the router settings... something usually called "bridging mode" or similar is an MS specific setting and should be set to something else. Also look at the length of time the DHCP lease is for. You could also try using a static IP LANside.
Just in case it helps, today I booted up with the router already on. It failed to connect. I switched the router off and back on again, still no connect. Here is the ifconfig at that point:
eth0 Link encap:Ethernet HWaddr 00:0E:2E:BE:33:1F
inet6 addr: fe80::20e:2eff:febe:331f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:322 (322.0 b) TX bytes:720 (720.0 b)
Interrupt:19 Base address:0xc00
THen I switched the router off, rebooted and after reboot, switched the router on. It connected. So annoying. I will now look at the links you have given me. Thank you.
Thank you for all your help and attention to this problem. It does seem now that it is the router and not Linux at fault. I have just booted up with the router OFF and, once boot was done, I switched the router on and got instant connection. Seems this is the way to work it. I consider this thread now closed.
Hi again. This is getting ridiculous. The above scenario happens every time. I have just spent 1 hour trying to get my connection working until, finally a switch off and on of the router worked. I will post some files, starting with ifconfig when the connection could not be made:
I note a reference to inet6. I thought IPv6 had to be turned off. Also MTU 1500 is shown. The router is set to 1400 and is supposed to be 1400.
I then tried ifup eth0 and got this:
[root@home Documents]# ifup eth0
Determining IP information for eth0...SIOCSIFNETMASK: Cannot assign requested address
SIOCGIFADDR: Cannot assign requested address
SIOCSIFBROADCAST: Cannot assign requested address
SIOCSIFBRDADDR: Cannot assign requested address
SIOCADDRT: Network is unreachable
done.
/etc/sysconfig/network-scripts/ifup-aliases: line 120: Mask: command not found
[root@home Documents]#
There is no MASK on line 120, however there is a LONG line 119 which is all one line that runs for 5 lines of the page in the file ifup-aliases.
I also am having similar probs with a Dell Latitude 610 laptop and a Voyager 190 router. In this situation AOL confirm no line faults and that the connection is live and active. The laptop shows the internet connection is up BUT I cant gey past the router to the internet. I CAN get on the router but firefox refuses all page requests other than the routers main page. Do I go back to Microsoft?
Last edited by joeclem111; 09-22-2007 at 12:27 PM.
I CAN get on the router but firefox refuses all page requests other than the routers main page.
Clear cause - it's the router. Everything on the computer-side is working, but the router ain't letting traffic out.
Quote:
Do I go back to Microsoft?
Sometimes routers are preconfigured to work only with windows - it's a phenomenon called lockin. You have to go through the entire configuration to find where this is and change it. Normally it is something like "bridged mode"... or something. But it could just be that you have network adress translation turned off or similar... have you tried switching the routers firewall off for eg? If it is blocking port 80 then that would cause this.
Talk to the router supplier (British Telecom?) and/or your ISP, tell them your router doesn't let you connect to the internet- you can see and edit the configuration screen - where do you go from there.
Use a different router... best bet. 99.99% routers work out of the box with linux. You seem to be magnetically attracted to the other 0.01%, so get someone else to choose.
Same with the 210 - we know it doesn't go well with linux. Hell, it isn't all that good with windows.
OK, thank you for your latest input. In the case of the Dell + Voyager 190, where a connection is made but no traffic can pass, I do believe it is a locked router.The 190 is made to be locked on to AOL and has no area where any of the 190's config can be changed. There is only 1 page that displays all the settings and the only bit you can use is the AOL test. This is the one that gave the "DNS_LookupError" when used. It does say to log out of everything before testing, which obviously you cannot do.
I am, however, answering this on my PC with the Voyager 210. Same again today, boot up, no connection. I tried ifup -v and got a "no configuration for -v" error. I used the ifconfig -a to add the routers IP and gateway, did ifup and got the SIOC errors posted previously. I shut the modem off, turned it back on and got connection. This off and back on routine doesnt always work, probably when the ifconfig has no IP's in it. Once I have added them, the on off routine seems to do it. How can I ensure the IP's are in ifconfig from boot up? This might be the cure!!
I have talked to Voyager support. Steve says that I will never connect using a 210 with Linux, so much for his knowledeg and value. Clare seems more knowledgeable. The "bridged mode" you mention is not in the data that can be amended by admin on the router, I think it is embedded these days. I suggested to Clare that they put it back in the admin accessible area with the next upgrade. She agreed to put it to the powers that be to look at that option. She also agreed to put it to them to look at opening up the voyager to Linux users ( now they know that Dell and HP are shipping their PCs with Linux loaded ), so maybe they will step into todays world.
As for the 210, I can always ( EVENTUALLY ) get it going, so there must be only a small thing that is giving the problem. I will look again at the admin set up for the 210. I cannot remember where I saw anything that might let me disable the firewall on it. I know that NAT is enabled and that all settings appear to be as they should be. Will post any results I get and thanks for all your advice.
!!! I have just done some more testing. I reset the 210 back to factory defaults, then went through all the admin again. The only thing I could see was that the gateway connection is Br0, which is different to the others, which give the standard IP address. After all this I went through all the usual routines for non-connection. Couldnt get on till I did the ifconfig -a routine to add the IP and Gateway to ifconfig. At that point I switched off the router and, when switching back on, I got the connection. The answer is to ensure the inclusion of the IP and Gateway in ifconfig at boot, THEN I should get the automatic connection. So, if I know how to do this, we should be fixed. How do I achieve this? Thanks.!!!
Last edited by joeclem111; 09-23-2007 at 08:13 AM.
Well, I did think it was the bridge mode you referred to. I spoke to Voyager and convinced them to consider that setting. It used to be open to the admin but now it is in the firmware. They are now, in the light of Linux being shipped as the standard installation on Dell and HP comps, considering putting it back to admin access for setting.
I have now proved conclusively that my 210 problem is ifconfig eth0 is not picking up the IP and Gateway at boot up. This is what is stopping the connection, SO again, how do I ensure that ifconfig picks them up. This will cure the problem.
As for the 190 router/modem, YES, I am sure it is not just locked to AOL, but also to windows so Linux will never connect through it.
Well, I did think it was the bridge mode you referred to. I spoke to Voyager and convinced them to consider that setting. It used to be open to the admin but now it is in the firmware. They are now, in the light of Linux being shipped as the standard installation on Dell and HP comps, considering putting it back to admin access for setting.
I have now proved conclusively that my 210 problem is ifconfig eth0 is not picking up the IP and Gateway at boot up. This is what is stopping the connection, SO again, how do I ensure that ifconfig picks them up. This will cure the problem.
As for the 190 router/modem, YES, I am sure it is not just locked to AOL, but also to windows so Linux will never connect through it.
I found the fix. I upgraded to 2007.1 This release has fixed many bugs in the 2006 release, including this one. Connection is automatic from boot every time now. I consider this is now closed.
Well, I did think it was the bridge mode you referred to. I spoke to Voyager and convinced them to consider that setting. It used to be open to the admin but now it is in the firmware. They are now, in the light of Linux being shipped as the standard installation on Dell and HP comps, considering putting it back to admin access for setting.
I have now proved conclusively that my 210 problem is ifconfig eth0 is not picking up the IP and Gateway at boot up. This is what is stopping the connection, SO again, how do I ensure that ifconfig picks them up. This will cure the problem.
As for the 190 router/modem, YES, I am sure it is not just locked to AOL, but also to windows so Linux will never connect through it.
I have solved this problem but not the 190 problem. The fix supplied by upgrading to 2007 will not work on the laptop. I am going to install SuSE on the laptop and see if it is any different. If not, then we have proved the windows lock theory. I consider this thread to be now closed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
