Tom Eastep wrote:
Those are duplicate packets (only the checksum and window size are
different and there is no intervening packet in the other direction)
which suggests that the recipient (161.184.172.35) isn't getting them.
Looks like it's time to get a packet trace on 161.184.172.35.
I just noticed something that I suspect is the crux of the problem. With
Shorewall running, no loc <->loc traffic works despite their being a loc
loc ACCEPT policy in effect.
When I attempt to ping, telnet, ssh, etc from 10.0.50.10 with Shorewall
on, I get a connection refused error. With Shorewall cleared, the
connection succeeds. The routing table looks the same, but with
shorewall on an attempt to ping 10.0.50.50 from 10.0.50.10 results in a
'destination host unreachable' error.
This is officially over my head.
J
begin:vcard
fn:Jon Watson
n:Watson;Jon
email;internet:[EMAIL PROTECTED]
tel;work:1.403.875.6048
x-mozilla-html:FALSE
url:http://www.jonwatson.ca
version:2.1
end:vcard
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users
