kokizzu / muggles

Automatically exported from code.google.com/p/muggles
0 stars 0 forks source link

masq_ipconf - investigate making it run from /etc/network/if-up.d/ #4

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Figure out why running masq_ip from /etc/network/if-up.d/ add iptables
badly, and set it up there. (when you do that, fix the installer code too.

Useful for later debianization as per debian policy manual.

Original issue reported on code.google.com by pandesuchi72 on 18 Dec 2009 at 9:54

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
iptables errors on load when the kernel is really busy, which it is during 
start up,
which is pretty much when if-up.d stuff is run.

Two possible workarounds. Use iptables-save/iptables-restore, which is much more
efficient. Or retry on error.

Original comment by pandesuchi72 on 23 Dec 2009 at 9:55

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Set up a retry on error wrapper for the iptables entries, because it seems 
simpler.
iptables-save/restore would mean generating stuff which gets to shorewall-like
complexity.

Original comment by pandesuchi72 on 24 Dec 2009 at 12:15

GoogleCodeExporter commented 9 years ago

Original comment by pandesuchi72 on 1 Jan 2010 at 6:59