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.
I have two network cards. One is getting it's IP dynamically from the router connected to the internet. The second I have set the IP statically (192.168.1.1) and have a router connected to it. If I ping 192.168.1.1 I get the splash page from the locally running Apache as if I requested 127.0.0.1 rather than the web interface that I should get from the router.
What do I do to be able to start talking to the router connected to eth1?
I have two network cards. One is getting it's IP dynamically from the router connected to the internet. The second I have set the IP statically (192.168.1.1) and have a router connected to it. If I ping 192.168.1.1 I get the splash page from the locally running Apache as if I requested 127.0.0.1 rather than the web interface that I should get from the router.
What do I do to be able to start talking to the router connected to eth1?
Well, I've read for four times your post and I'm not sure if I got it.
Anyway, have you tried this?---->
#route add default gw ip.of.your.router
it should makes your host to talk with your router, anyway.
your second nic is set to use 192.168.1.1 and if you ping it you get a web page back? i think you must have invented a brand new icmp packet if you think you can get a web page from a ping... just a tad impossible. either way, that seems to be doing exactly what you've told it to...
I meant that I can ping 192.168.1.1 and get a ping back. When I hit that address in my web browser I get the "Seeing this instead of the website you are expecting" splash page from the Apache server running on the same machine.
The 'route add default gw ip.of.your.router' did not help.
I agree. I changed my configuration (see below) and did another little test. I have two nic cards. I am currently connected to a 2Wire router to the internet through eth0. I can ping the 2Wire router (192.168.1.254) through eth0. I moved my cable connected to the 2Wire router to the Linksys router so eth0 faces the Linksys router. I can ping the Linksys router (192.168.1.1). Both routers work and can be reached through eth0.
When I move the nic end of the cable to eth1 and try to ping either router on the other end I cannot get a connection. The only thing different is the nic (eth1). It would seem that something is rotten in Denmark as far as the eth1 nic card goes. The strange thing is that I can ping the card itself (192.168.1.200) just fine. My configuration is:
Quote:
# Config information for eth0:
IPADDR[0]=""
NETMASK[0]=""
USE_DHCP[0]="yes"
DHCP_HOSTNAME[0]=""
# Config information for eth1:
IPADDR[1]="192.168.1.200"
NETMASK[1]="255.255.255.0"
USE_DHCP[1]="no"
DHCP_HOSTNAME[1]=""
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.