Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Route problem with 2 NIC

Status
Not open for further replies.

Sajtz

IS-IT--Management
Apr 23, 2002
75
EU
Hi. I´m having some problems with my network. I have connected an external and an Internal network.

I´m trying to make an route add from the internal machine, but all I get is network unreachable.

When I ping from the external machine to the internal machine, it works but not the other way around.

The external machine has 191.0.4.169, the gateway has 191.0.4.154, and the internal machine has 203.0.4.76

I will give you some more details:

This is the machine I want to set up on the internal net:

lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
hme0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 203.0.4.16 netmask ffffffc0 broadcast 203.0.4.63
ether 8:0:20:fa:3d:34
hme1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 203.0.4.76 netmask ffffffc0 broadcast 203.0.4.127
ether 8:0:20:fa:3d:34

When I do an route add like this:

route add 191.0.4.169 191.0.4.154
add host 191.0.4.169: gateway 191.0.4.154: Network is unreachable

Alright I think then, the computes are on different net and I have to route to the gateway 191.0.4.154 in some way.

But when I route from an another computer on the internal net It works correctly. I can, after the route add, ping the machine 191.0.4.169, so it shouldn´t be any wrong with the external machine.

Since there are 2 NICs on the internal machine I did the following:

hme1:
traceroute -s 203.0.4.76 191.0.4.169

traceroute to 191.0.4.169 (191.0.4.169) from 203.0.4.76, 30 hops max, 40 byte packets
1 203.0.4.1 (203.0.4.1) 0.885 ms 0.493 ms 0.491 ms
2 191.0.4.169 (191.0.4.169) 0.543 ms 0.438 ms 0.445 ms

hme0:
traceroute -s 203.0.4.16 191.0.4.169

traceroute -s 203.0.4.16 191.0.4.169
traceroute to 191.0.4.169 (191.0.4.169) from 203.0.4.16, 30 hops max, 40 byte packets
1 203.0.4.1 (203.0.4.1) 0.827 ms 0.466 ms 0.489 ms
2 *^C#

So when I use the hme1 NIC i can make a traceroute, but I still can´t make an route add using that NIC.

Any ideas?

br
Petter
 
Hi Petter,

first change the MAC Adress of the NICs; if they are in the same physical network, this will never work (in OBP set: 'setenv local-mac-adress? true')

next: would you please paint a network plan, or write something more detailed; please add networkadress, netmasklength and Interface-Adress to this plan (the netmask length causes imho the problems); sometimes it is easier to use different type-C-networks than Subnettet-type-C-nets

Best Regards, Franz
--
Solaris System Manager from Munich, Germany
I used to work for Sun Microsystems Support (EMEA) for 5 years
 
Make sure you don't have the file notrouter in /etc

Mike

"A foolproof method for sculpting an elephant: first, get a huge block of marble, then you chip away everything that doesn't look like an elephant.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top