Re: [TCLUG:5537] EQL & Masquerade...

["Chad C. Walstrom" <chewie@soncom.com>]

More info...  Interesting stuff, really.  I did some traceroutes of a
simple ping...  Here's what I got after enslaving two devices... (I
cut em up a bit for brevity's sake).  It seems that a echo request is
delivered across the eql device and passed off to ppp1; the reply
being delivered on ppp0.  Yet, they're not being recombined into a
single buffer for 'ping' to figure out that it's actually getting a
reply to its request...  Any suggestions?


fozzy:~/ipchains# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
127.0.0.0       0.0.0.0         255.255.255.255 UH    0      0        0 lo
209.18.239.3    0.0.0.0         255.255.255.255 UH    0      0        0 eql
209.18.239.3    0.0.0.0         255.255.255.255 UH    0      0        0 ppp0
209.18.239.3    0.0.0.0         255.255.255.255 UH    0      0        0 ppp1
192.168.2.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
0.0.0.0         0.0.0.0         0.0.0.0         U     0      0        0 eql

tcpdump: listening on eql
19:21:50.901450 209.18.239.8 > 206.147.67.195: icmp: echo request
19:21:51.901415 209.18.239.8 > 206.147.67.195: icmp: echo request

tcpdump: listening on ppp0
19:21:59.411304 206.147.67.195 > 209.18.239.8: icmp: echo reply
19:22:00.321334 206.147.67.195 > 209.18.239.8: icmp: echo reply

tcpdump: listening on ppp1
19:22:05.901470 209.18.239.8 > 206.147.67.195: icmp: echo request
19:22:06.901423 209.18.239.8 > 206.147.67.195: icmp: echo request


Chewie...frustrated...