manu031597
asked on
Routing/Subnetting Solaris 2.3
First, I don't have any upstream gateway. Lans Gateways, which are all connected to the Wan, have to take care themselves about routing table. A default routing entry or running RIP protocol would cost a lot of money on a Wan, based on X.25 (about 150 Lans are interconnected).
route add net lan_ip_b wan_ip_b 1
or
route add net lan_ip_a wan_ip_a 1
is exactly what I did on my lans gateways.
The problem is that Solaris ( 2.3 or 2.5 ) don't keep subnets in routing table
for routes from subnetted B nets to subnetted A nets (and vice versa).
Only routes from a subnetted B net to another one or from a subnetted A net to another one is ok (still via the wan of course).
The only solution I found is to create a logical interface (subnetted A address for B gateways and subnetted B address for A gateways).
I don't understand why Solaris avoids to route on sub-networks for which
you don't have an interface in the same class with the same netmask.
route add net lan_ip_b wan_ip_b 1
or
route add net lan_ip_a wan_ip_a 1
is exactly what I did on my lans gateways.
The problem is that Solaris ( 2.3 or 2.5 ) don't keep subnets in routing table
for routes from subnetted B nets to subnetted A nets (and vice versa).
Only routes from a subnetted B net to another one or from a subnetted A net to another one is ok (still via the wan of course).
The only solution I found is to create a logical interface (subnetted A address for B gateways and subnetted B address for A gateways).
I don't understand why Solaris avoids to route on sub-networks for which
you don't have an interface in the same class with the same netmask.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Edited text of question
I don't understand why you say that "... Solaris ( 2.3 or 2.5 ) don't keep subnets in routing table ...". Here is an entry from one of my routers (netstat -rn):
xxx.xxx.75.0 xxx.xxx.74.16 UG 0 2969
This machine is physically connected to two nets: xxx.xxx.74.0 and xxx.xxx.131.0, but it does know about the router to the xxx.xxx.75.0 subnet. I think this is a very similar situation as yours. Moreover the xxx.xxx.74.0 net has a different netmask than the other nets. I never had problems with this.
Could you please explain, what you mean with "class" ?
Peter
xxx.xxx.75.0 xxx.xxx.74.16 UG 0 2969
This machine is physically connected to two nets: xxx.xxx.74.0 and xxx.xxx.131.0, but it does know about the router to the xxx.xxx.75.0 subnet. I think this is a very similar situation as yours. Moreover the xxx.xxx.74.0 net has a different netmask than the other nets. I never had problems with this.
Could you please explain, what you mean with "class" ?
Peter
How or where can I change the default gatweays IP addresse under Solaris 2.5?
ASKER
route add net lan_ip_b wan_ip_b 1
or
route add net lan_ip_a wan_ip_a 1
is exactly what I did on my lans gateways.
The problem is that Solaris ( 2.3 or 2.5 ) don't keep subnets in routing table
for routes from subnetted B nets to subnetted A nets (and vice versa).
Only routes from a subnetted B net to another one or from a subnetted A net to another one is ok (still via the wan of course).
The only solution I found is to create a logical interface (subnetted A address for B gateways and subnetted B address for A gateways).
I don't understand why Solaris avoids to route on sub-networks for which
you don't have an interface in the same class with the same netmask.