| 1 |
On Sep 23, 2011 6:11 AM, "Adam Carter" <adamcarter3@×××××.com> wrote: |
| 2 |
> |
| 3 |
> > It's not the ICMP that is being prohibited. |
| 4 |
> |
| 5 |
> Understood, that's clear from the packet trace. |
| 6 |
> |
| 7 |
> > is an ICMP "host unreachable" response from .250. The extended reason |
| 8 |
> > for the unreachability is that there is an administrative policy |
| 9 |
> > preventing the traffic. It almost certainly *is* a firewall that's |
| 10 |
> > preventing this, one with a REJECT target, as REJECT specifies to |
| 11 |
> > return an ICMP unreachable packet. |
| 12 |
> |
| 13 |
> Most firewalls i've seen send a spoofed TCP reset, not an ICMP when |
| 14 |
> rejecting TCP. However, iptables can do either. I have run iptables -F |
| 15 |
> and the tables are shown as clear with iptables -L. |
| 16 |
> |
| 17 |
> proxy vhosts.d # iptables -L |
| 18 |
> Chain INPUT (policy ACCEPT) |
| 19 |
> target prot opt source destination |
| 20 |
> |
| 21 |
> Chain FORWARD (policy ACCEPT) |
| 22 |
> target prot opt source destination |
| 23 |
> |
| 24 |
> Chain OUTPUT (policy ACCEPT) |
| 25 |
> target prot opt source destination |
| 26 |
> |
| 27 |
> Chain fail2ban-SSH (0 references) |
| 28 |
> target prot opt source destination |
| 29 |
> |
| 30 |
> Chain fail2ban-apache (0 references) |
| 31 |
> target prot opt source destination |
| 32 |
> proxy vhosts.d # |
| 33 |
> |
| 34 |
|
| 35 |
Can you post the outputs of 'iptables-save' and 'ip rule show'? |
| 36 |
|
| 37 |
Rgds, |
Archives