![]() ![]() ![]() (see the expected outcome screenshot, they have 2 gateway with different metrics) The ping should be sent from my specified interface. But I am using 2 completely different interfaces and if I specify the interface to use, then the default gateway metric should not matter. This behavior is similar to IP aliasing on a single interface. If I use lower metric for eth0 gateway, then all pings are being sent from eth0 regardless of what interface I specify. Most probably because eth1 gateway has a lower metric. The expected outcome is also mentioned in the mwan3 documentation.īoth the ping commands are being sent from eth1 ![]() In the above commands, the ping should be sent via eth0 and eth1 respectively. Now, I am specifying the interface to use for ping using: ping -I eth0 8.8.8.8 Now, I connected the ISP cables to the respective pre-planned ports. The outputs of ip a show and ip route show are attached at the end of this post. I WILL USE THIS LOGICAL INTERFACE `LAN` IN /ETC/CONFIG/WIRELESS ISP-2 (172.30.138.151/24) (Planned about connecting it to WAN2-eth1) I used the following network config /etc/config/network config interface 'loopback' I recently got 2 connections from 2 different ISPs and thought to remove eth1 from the bridge and use it as a 2nd WAN port.īoth of my ISPs provided static IPs for router configuration. eth1 and wlan0 are bridged together ( br-lan). It has 3 interfaces: eth0 (single WAN port), eth1 (single LAN port), and wlan0 (WIFI). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |