General discussion

Locked

Routing problem

By irek_zar ·
We have 3 hosts h1,h2,h3. h1 has 1 network adapter 100Mb Ethernet, the host h2 has 100Mb Ethernet and FDDI adapters, h3 has 10Mb Ethernet and FDDI. We need make path between h3 and h1 over h2, i.e make 100Mb link. How to do this? And why not work the following?

The host h1 has following routing table:
h1# netstat -rn

Routing Table:
Destination Gateway Flags Ref Use Interface
-------------------- -------------------- ----- ----- ------ ---------
192.9.200.0 192.168.128.100 UG 0 33
192.168.128.0 192.168.128.1 U 4 51586 hme0
192.8.100.0 192.8.100.100 U 4 2349 hme0:1
224.0.0.0 192.8.100.100 U 4 0hme0:1
127.0.0.1 127.0.0.1 UH 0 140564 lo0

h2 has FDDI and 100Mb Ethernet adapters. It's routing table is:
h2# netstat -rn
Routing tables
Destination Gateway Flags Refs Use If PMTU Exp Groups
Netmasks:
(0)

This conversation is currently closed to new comments.

6 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Routing problem

by Hasse MCSE/Brainbench In reply to Routing problem

Hi!

I'm missing alot of info here and I have no idea of how to set a static route in Solaris.

But this is how you should do it.

In order to get the 100Mb link you'll need to setup a route that uses the FDDI interface on h3->FDDI h2->h1.If the two FDDI interfaces are on same subnet, then you should be able to accomplish this by setting up a route to h1 by setting that routes gateway to the FDDI interface address of h2.

Like this:

either one of thees two should work when doneon h3:
route add -host
route add -host

to also get thr route the other way araound run on h1:
rotue add -host
route add -host

where the second ip represent which gateway should be used.

PS! Also on machine h2 remove /etc/norouter if it exists. D.S.

Hope this helps.
/Hasse

Collapse -

Routing problem

by irek_zar In reply to Routing problem
Collapse -

Routing problem

by Hasse MCSE/Brainbench In reply to Routing problem

Hi again!

Also of course you might need a route between FDDI and 100 interface on h2, but enabling ip forwarding this might be done automatically.

The route command is found in /usr/sbin.

/Hasse

Collapse -

Routing problem

by irek_zar In reply to Routing problem

Thanks for answer Hasse.
The problem is in ip forwarding between FDDI and Ethernet in the host h2. h2 is AIX4.2.1, and problem is in enabling ip forwarding in the AIX4.2.1 host.
Irek.

Collapse -

Routing problem

by ustutz In reply to Routing problem

The route command is:

route add host <destination> netmask <mask> <gateway> count

The netmask and count are typically optional. If you are doing something 'unusual' (variable length subnetting, e.g.) you'll have to specify them.

If your IPaddresses are in /etc/hosts or DNS, you can enter the route by host name versus IP address. But: Each interface needs its own hostname. (h1le1, h1le2, etc). Your applications need to identify the "correct host" to access the other box on the designated interface.

You may need to set the default route:

add route net default <lanic>

where <lanic> is the IP address for the LAN interface you want to be the default interface. Alternatively you may need to specify additional local and remote gatewways (routers) along the path.

route add net 192.8.100.0 192.8.100.10 2

From the little info you included above, check your subnetmask as well. That may be part of your problem.

The sequence of route commands should come out to something like this - n

Collapse -

Routing problem

by irek_zar In reply to Routing problem

Thanks for answer

Back to Linux Forum
6 total posts (Page 1 of 1)  

Related Discussions

Related Forums