Oh and if I ping it from my firewall or another internal host I get replies
21:05:40.222793 IP (tos 0x0, ttl 64, id 38515, offset 0, flags [DF],
proto ICMP (1), length 84)
24-212-187-114.cable.teksavvy.com > 184-75-215-106.amanah.com:
ICMP echo request, id 2505, seq 13, length 64
21:05:40.240260 IP (tos 0x0, ttl 57, id 10886, offset 0, flags [none],
proto ICMP (1), length 84)
184-75-215-106.amanah.com > 24-212-187-114.cable.teksavvy.com:
ICMP echo reply, id 2505, seq 13, length 64
21:05:41.224485 IP (tos 0x0, ttl 64, id 38516, offset 0, flags [DF],
proto ICMP (1), length 84)
24-212-187-114.cable.teksavvy.com > 184-75-215-106.amanah.com:
ICMP echo request, id 2505, seq 14, length 64
21:05:41.240902 IP (tos 0x0, ttl 57, id 10887, offset 0, flags [none],
proto ICMP (1), length 84)
184-75-215-106.amanah.com > 24-212-187-114.cable.teksavvy.com:
ICMP echo reply, id 2505, seq 14, length 64
21:05:42.226104 IP (tos 0x0, ttl 64, id 38517, offset 0, flags [DF],
proto ICMP (1), length 84)
24-212-187-114.cable.teksavvy.com > 184-75-215-106.amanah.com:
ICMP echo request, id 2505, seq 15, length 64
21:05:42.242817 IP (tos 0x0, ttl 57, id 10888, offset 0, flags [none],
proto ICMP (1), length 84)
184-75-215-106.amanah.com > 24-212-187-114.cable.teksavvy.com:
ICMP echo reply, id 2505, seq 15, length 64
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users
