vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Fellow AIX'ers; I have a situation that I cannot seem to get configured properly. Perhaps someone can advise? System has single NIC with two IP's (primary + alias) both in the private range 192.168.0.4 primary 192.168.250.4 alias The default gateway IP is 192.168.0.1 There is a static route for the alias for a specific IP as follows: 170.186.14.xxx / 255.255.255.0 --> 192.168.250.1 which is the IP of a secondary router on a different network. From the host I can ping both routers just fine. And I can ping or traceroute anything else that goes through the primary gateway. I can ping the secondary router 192.168.250.1 just fine but NOTHING beyond. If I traceroute with a -s parameter of 192.168.250.4 the trace will properly go through the secondary router to the destination just fine. If I do NOT specify the -s (source IP) parameter it appears to attempt to go through the primary router of which the destination IP is unreachable. My question is this: Other than defining a static route, how can I force the access to the 170.186.14.xxx to go through the secondary router IP of 192.168.250.1 ??? Any advice/recommendations greatly appreciated. B |
| ||||
| On Mon, 03 May 2004 18:42:52 +0200, Holger van Koll <holger@vankoll.de> wrote: >> I can ping the secondary router 192.168.250.1 just fine but NOTHING >> beyond. >> > >r u sure the routers/nodes behind that sec. routers know where to send their reply-packet (know the "way back")? Yes - sure; Finally got this going. The smit tcpip router maintenance commands seemed to be screwing me up. No matter what static router was being added, this command always inserted a second default command for the same IP going to the primary router. Using the manual route command from the CLI, I was able to delete ALL the offending routes and re-establish them, one at a time, and eventually they all worked. It's NOT supposed to work like this. But hey, at least it is now working... |