Subject: Re: odd ipf behaviour
To: Paul Newhouse <firstname.lastname@example.org>
From: David Maxwell <email@example.com>
Date: 12/01/1999 16:20:45
> Platform i386 running a rather recent current.
> I have a multi-homed system. One connection is DSL (de1) and the other is with @home (ne0).
> >From a remote site, A (188.8.131.52), I can ping both connections and get responses.
> >From a second remote site, V (184.108.40.206), I can get ping to work on the DSL connection
> but, not on the @home connection. On my local system, while pinging from V, I get:
> 08:39:22.400850 demeter.veritas.com > c528574-b.stcla1.sfba.home.com: icmp: echo request
Was this tcpdump from interface ne0?
You have no explicit route to 220.127.116.11 (or its subnet)
You have no ipf rules to force 18.104.22.168 traffic back out ne0.
Your ping replies are likely exiting on de1.
Try traceroute -i ne0 22.214.171.124 and see if it tells you why your
replies can't get to V via the @home connection.
> Destination Gateway Flags Refs Use Mtu Interface
> default 126.96.36.199 UGS 6 903207 1500 de1
> 24 188.8.131.52 UGS 5 13635 1500 ne0
David Maxwell, firstname.lastname@example.orgemail@example.com --> Mastery of UNIX, like
mastery of language, offers real freedom. The price of freedom is always dear,
but there's no substitute. Personally, I'd rather pay for my freedom than live
in a bitmapped, pop-up-happy dungeon like NT. - Thomas Scoville