Replying to my own email...

Matthew Dalton wrote:
> 2. The firewall's routing table causes it to send the packet out eth1
>  - at this stage the destination IP of the packet is 10.0.1.28, but
> since that IP is not on this segment, it never makes it there.

Ooops. Actually, the destination IP of the packet is always 10.0.1.28...
it's the ethernet address that causes routing to happen...

The gist of what I said is (probably) correct, but I'm sure there are
some people on this list who have far more routing experience than I,
who could explain it better...


-- 
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug

Reply via email to