| 1 |
On 12/27/2012 06:11 PM, Walter Dnes wrote: |
| 2 |
> On Thu, Dec 27, 2012 at 11:28:15AM +0000, Graham Murray wrote |
| 3 |
> |
| 4 |
>> The problem is not really the OP's fault. The problem is that if you |
| 5 |
>> have tables with the form "-m state --state XXX" at the point you |
| 6 |
>> upgrade, iptables-save (quite possibly called automatically by |
| 7 |
>> /etc/init.d/iptables stop) will save it as "-m state --state" - ie |
| 8 |
>> 'forgetting' which state(s) the rule applies to. |
| 9 |
> |
| 10 |
> Thanks for pointing that out. I looked back at an archived version, |
| 11 |
> and it had stuff like... |
| 12 |
> |
| 13 |
> -A ICMP_IN -p icmp -m state --state NEW -j UNSOLICITED |
| 14 |
> -A TCP_IN -p tcp -m state --state NEW -m tcp -j UNSOLICITED |
| 15 |
> -A UDP_IN -p udp -m state --state NEW -j UNSOLICITED |
| 16 |
> |
| 17 |
> I.e. new external connection attempts were rejected, except for my |
| 18 |
> lan which bypasses this rule so I can scp/ssh etc between my machines. |
| 19 |
> No wonder I was puzzled by what I saw. |
| 20 |
> |
| 21 |
|
| 22 |
Ah, yes, the original problem. |
| 23 |
|
| 24 |
Once you've upgraded, you should be able to add all of your old --state |
| 25 |
rules normally, albeit with a warning. The new iptables will translate |
| 26 |
them to conntrack rules, and you can `/etc/init.d/iptables save` the result. |
| 27 |
|
| 28 |
The upgrade just fails in a horrible way. |
Archives