![]() |
Hello and Welcome from United States to the UNIX and Linux Forums! Thank You for Visiting and Joining Our Global Community.
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| IP Networking Learn TCP/IP, Internet Protocol, Routing, Routers, Network protocols in this UNIX and Linux forum. |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| OLS: Kernel documentation, and submitting kernel patches | iBot | UNIX and Linux RSS News | 0 | 07-25-2008 11:10 AM |
| max number of slabs per kernel module (kernel 2.6.17, suse) | Brendan Kennedy | SuSE | 4 | 01-23-2008 09:40 AM |
| Kernel panic - not syncing: cannot execute a PAE-enabled kernel on PAE-less CPU | dave043 | Linux | 2 | 05-10-2007 01:57 AM |
| Req:Advanced kernel bible | gokulagiridaran | UNIX for Advanced & Expert Users | 3 | 12-27-2006 01:06 PM |
| Kernel Routing Table | redcrosskbg | UNIX for Dummies Questions & Answers | 1 | 12-24-2001 11:29 AM |
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
||||
|
advanced nix kernel routing
We have the following setup on several linux servers:
eth0 = Internet eth1 = LAN (10.100.X.X) For this example let's say we have: eth0 goes to the internet and the default gateway is set in ifcfg-eth0 Server A has three IPs on the LAN (10.100.0.2, 10.100.22.3, 10.100.33.4) The gateway is 10.100.9.1. Naturally, if one IP attempts to access another IP, it is going to take the shortest path. On Server A, the IP 10.100.0.2 attempts to access 10.100.22.3 or vice versa. We want to FORCE this traffic to go out eth1 on server A and to the gateway. The gateway is filtering traffic, so in this case we may have a rule blocking access from 10.100.0.2 to 10.100.22.3 - or perhaps a permit policy. ip rule add from 10.100.0.2 table TEST1 ip route add 10.100.0.2 dev eth1 table TEST1 ip route add default via 10.100.9.1 table TEST1 ip rule add from 10.100.22.3 table TEST2 ip route add 10.100.22.3 table TEST2 ip route add default via 10.100.9.1 table TEST2 My understanding of source based routing tells me the above should solve the problem; however, upon adding the default gateway (ip route add default via 10.100.9.1 table TEST1 and ip route add default via 10.100.9.1 table TEST2), traffic doesn't hit the gateway at all. Do you have any suggestions to resolve this issue - is it even possible? |
| Sponsored Links | ||
|
|
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|