4 votes
Accepted

Sharing same IP across two NICs, to route one IP over dedicated NIC

As 10.0.99.4 is part of 10.0.0.0/16 this IP address should be avoided. Else there would be a conflict with the actual 10.0.99.4/16 address, even on eth0 considering Linux is using the Weak Host Model ...
A.B's user avatar
  • 12.7k
2 votes

Multiple server processes on a Multihomed machine with one process bound to 0.0.0.0

0.0.0.0 is the unspecified address. When binding a socket it means this host, ie. on any interface or with any IP address. Accordingly, that behavior you describe seems to be correct. You need to ...
Zac67's user avatar
  • 11.5k
1 vote
Accepted

Multi-homing: do i need Route metrics for 2 interfaces of which only one can access the internet?

The OS uses the routing table netstat -rn to determine which interface to use. You probably have a default route that uses the "internet" interface. Unless you're doing something unusual, ...
Ron Trunk's user avatar
  • 2,179
1 vote

Sharing same IP across two NICs, to route one IP over dedicated NIC

Using A.B's excellent explanation, this is what I ended up doing to get it to work, for the benefit of anyone else using systemd: # /etc/systemd/network/50-eth1.network [Match] Name=eth1 # NIC with ...
Malvineous's user avatar
  • 1,145
1 vote

Windows 10 uses wrong NIC to reach certain IP addresses

I've seen this behaviour too. In my case, if 192.168.2.102 doesn't exist (no arp response), windows should say 'Destination host unreachable' or 'Request timed out' (not sure which is more correct). ...
Dan's user avatar
  • 11
1 vote

Multihomed Computers - wont communicate on a network

I recreated your issue in a lab environ today. The problem I saw (which matched your description) was indeed caused by IPv6. The machines tried to talk to each other over IPv6 first, and they ...
Ruscal's user avatar
  • 1,222

Only top scored, non community-wiki answers of a minimum length are eligible