Re: Take 2: Advanced routing: multiple FIREWALLED IPs
DUH ... the problem is with the 64.x.x.x rule in table tnn ... for some
reason I don not entirely understand that rule seems to imply to the
kernel that the 64.x.x.x network should be a LOCAL network directly
connected to the interface. Removing that entry leads to all non-local
traffic going to the default gateway for that interface as intended.
Sorry for the static
Rudolf
--
The 3 'R's of Microsoft - Retry, Reboot, Reinstall...
|