[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CANk_n4Y9bDmDCah2Tm66=X2o6uwcTz1amxcod6=AW4ZJE=1NsA@mail.gmail.com>
Date: Thu, 11 Mar 2021 11:06:41 +0200
From: Mihai <m@...alife.ro>
To: netdev@...r.kernel.org
Subject: Kernel Routing tabel
Hello,
I have 2 NIC with ips
eth1: 10.100.1.2/30
eth2: 10.200.1.2/30
both of them must reach IP: 172.16.16.1
what i've done so far:
eth1:
ip route add 10.100.1.0/30 dev eth1 src 10.100.1.2 scope link table 100
ip route add default via 10.100.1.1 dev eth1 table 100
ip rule add from 10.100.1.0/30 dev eth1 table 100
ip rule add to 10.100.1.0/30 dev eth1 table 100
ip rule add to 172.16.16.1 lookup 100
eth2:
ip route add 10.200.1.0/30 dev eth1 src 10.200.1.2 scope link table 200
ip route add default via 10.200.1.1 dev eth2 table 200
ip rule add from 10.200.1.0/30 dev eth2 table 200
ip rule add to 10.200.1.0/30 dev eth2 table 200
ip rule add to 172.16.16.1 lookup 200
It kinda works if I ping with source interface, but i have the problem:
- that the packet goes on the interface with the lowest priority
between eth1 and eth2.
How can I make it work so that when the packet originates from eth1 it
goes through eth1 and so on.?
Powered by blists - more mailing lists