Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
Small network of 2 windows and 1 Mepis computers. All static ip addresses on eth1. Only eth1 and loop-back are set to start at boot. Mepis is the only connection to the internet via dial-up.
Problem: I can dial up and connect ok but firefox or konquerer won't go anywhere. I mean they come up but just say "looking up www.mepis.com". Then I must disconnect the dialup, stop eth1, reconnect with dialup and then I can surf. I think it has someting to do with the default gateway address in my eth1. It is set to it's network address.
Ideally I'd like to keep eth1 set to start at boot but not need to stop it before I dial the internet.
Looking for some suggestions.
Distribution: debian, gentoo, os x (darwin), ubuntu
Posts: 940
Rep:
that is either because of your routing table (default route) or your resolv.conf (not pointing to the right dns servers)
run
#cat /etc/resolv.conf
and
#route
wile both interfaces are up, then post the output here.
your default route would have to be pointing to your ppp0 device (add will have a non private address range in the collum 'gateway')
your dns records need to be set to your isp's dns servers
in the form of
nameserver <ipaddress>
With both interfaces up...
#cat /etc/resolv.conf
nameserver 63.173.217.2
nameserver 208.0.125.3
nameserver 63.173.217.2 #kppp temp entry
nameserver 208.0.125.3 #kppp temp entry
When I type route, it just display headers and just keeps trying.
--------------------------------------------------
With eth1 down and ppp0 up...
#cat /etc/resolv.conf
nameserver 63.173.217.2
nameserver 208.0.125.3
nameserver 63.173.217.2 #kppp temp entry
nameserver 208.0.125.3 #kppp temp entry
(same as before)
and
#route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
199-3.usachoice * 255.255.255.255 UH 0 0 0 ppp0
default 199-3.usachoice 0.0.0.0 UG 0 0 0 ppp0
Distribution: debian, gentoo, os x (darwin), ubuntu
Posts: 940
Rep:
can you see the lines in each routeing tables starting with 0.0.0.0 ?
that is your default route.
you might need to change settings in you dhclient.conf file, or your interfaces config files
you basically need to state that eth1 is not responsible for your default toute. either ppp0 will then automatically be the default route when you dial up, or you also tell it to be default route in your interface config or dhclient config (could also be called dhcpcd)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.