Topic: ipportfw bug

[AnthonyV]

I use ipportfw to allow winmx to operate on port 6699 in an internal network.
All was working fine till I rebooted E-Smith.
After that no one could download from me.
Checked ipmasqadm and spotted that my IP address had changed during the reboot but the change hadn't flowed on to the ipportfw rules.

I assume the fix here is to run a ipportfw script at every reboot in case the IP addr
of the external interface changes?

Where should I put the script to ensure this happens?

[Adam Rykala]

Stick the script at the end of /etc/rc.d/rc.local

Think of that as the "autoexec.bat" of the Linux world

[AnthonyV]

Thanks for that.
Works a treat.

[Shad Lords]

What I ended up doing is adding a link to the ip-change event as follows:

cd /etc/e-smith/events/ip-change
ln -s ../actions/conf-masq S11conf-masq

This way anytime your ip changes regardless of how it happens it should reconfigure the masq module and clean up any rules that need your external interface ip.

-Shad