Ross, I'm new to this stuff myself, but do you have any default routes set up for packets that are neither from 10.4.44.1 or 10.4.44.2? Are you testing from inside or outside? In my own trials what you list below will allow outside connections through either line, but inside-to-outside stuff isn't caught by either rule and depends on general defaults. I'm unclear though on just when a packet generated on the router takes on which IP as its identity (for instance, when it presents with the 'localhost' IP). It does seem that when a request comes in on a certain external IP that IP is preserved in the packets of a responding daemon, if the daemon's on the router, so rules like yours apply to it. Obviously I should spend an afternoon with a packet sniffer testing this stuff out - I haven't run across a full explanation of it yet. Whit On Mon, Dec 03, 2001 at 11:15:42AM -0800, Ross Simpson wrote: > echo 199 lucent >> /etc/iproute2/rt_tables (router #1) > echo 200 speed >> /etc/iproute2/rt_tables (router #2) > ip rule add from 10.4.44.1 table lucent > ip rule add from 10.4.44.2 table speed > > ip rule ls: > 0: from all lookup local > 32764: from 10.4.44.2 lookup speed > 32765: from 10.4.44.1 lookup lucent > 32766: from all lookup main > 32767: from all lookup 253 > > ip route add default via 10.4.44.1 dev eth0 table speed > ip route add default via 10.4.44.2 dev eth0 table lucent > ip route flush cache > > I can access forwarded ports on the external ip of the 'lucent' router, but > forwarded ports on the 'speed' router are not answering. > I've verified that port forwarding on the speed router works.
