I have an issue right now where my current provider does not support MAC address resolution due to some proprietary back-end network software.
This means if I have 220.127.116.11/24 as server one, and 18.104.22.168/24 as server two, they cannot talk to each other. If I have 22.214.171.124/32 and 126.96.36.199/32, they can communicate without issue.
Unfortunately if I leave eth0 as DHCP and it receives the /32, it seems to not be able to use the 188.8.131.52 gateway because it is outside of the /32 range (single IP).
Right now, the only way around this is configure each interface as a /24 but add a static route so that if the destination is 184.108.40.206/24, it should use 220.127.116.11 as the default gateway.
Additionally, if I manually set the router eth0 external address as 18.104.22.168/24, it seems to not add 22.214.171.124 as a default gateway for out-going traffic. To get around this, I’ve had to switch to root (sudo su -) and run
Unfortunately it seems that upon a reboot, this route-add for the default-gw seems to not be persistent and disappears.
Additionally (yes, again) after setting the IP address:
It seems to save to the routing table as
Destination gateway 0.0.0.0/0 126.96.36.199
Destination gateway 0.0.0.0/0 188.8.131.52
Any clue what’s going on here?[/code]