LinuxQuestions.org - [SOLVED] Can't access second network interface

- Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)

- - Can't access second network interface (https://www.linuxquestions.org/questions/linux-networking-3/cant-access-second-network-interface-871709/)

Can't access second network interface

Hi,

I'm having all sorts of problems connecting an access point to my computer, but here is one piece that I hope will get me going, if I can get it solved.

My computer has two network interfaces, eth0 and eth1. eth1 connects to the cable modem and thence the world, and works fine. eth0 is supposed to connect to the access point over a private network. Here is the output from route with my IP address blotted out:

Code:

Kernel IP routing table

Destination    Gateway        Genmask        Flags Metric Ref    Use Iface

192.168.1.0    *              255.255.255.0  U    0      0        0 eth0

***********      *              255.255.254.0  U    1      0        0 eth1

link-local      *              255.255.0.0    U    1000  0        0 eth1

default        ************.cpe. 0.0.0.0        UG    0      0        0 eth1

I used my laptop to set the address of the access point to 192.168.1.20 - no problem there, the browser connected right to it. Then I plugged the access point into eth0, pointed the browser to 192.168.1.20, and nothing (timed out). Moreover, ifconfig shows no traffic at all on eth0 - no packets received or transmitted. So I'm guessing that despite the entry in the routing table, my browser is looking on eth1 and that is why it is not finding it.

I restarted networking, no change. I am using ubuntu 10.04.

Thanks.

I'm not /that/ great at routing table details, but in the absence of other replies so far...

I believe you're missing a route to the .1.20 gateway on eth0, when it tries to get there it sees the .1.0 entry with no specific gateway set. So (my guess) is that it will use the default gateway, which is via eth1. Not eth0.

Maybe (not that sure), adding a route to 192.168.1.20 via eth0 would help (or resetting the existing default one, if that doesn't mess with other setup/plans), to point at eth0, will do it.

Hmm... Experts please?