natd.plist

[Anonymous]

I read the file /etc/nat/natd.plist.default section:

[quote:4014ab0130] redirect_port – array of redirect_port dictionaries; optional

redirect_port dictionary keys:
proto – string; required
targetIP – string; required
targetPortRange – string; required
aliasIP – string; required
aliasPortRange – string; required[/quote:4014ab0130]

and build with Apples PlistEditor a test like this:

[quote:4014ab0130] <key>redirect_port</key>
<array>
<dict>
<key>aliasIP</key>
<string></string>
<key>aliasPortRange</key>
<string>20</string>
<key>proto</key>
<string>tcp</string>
<key>targetIP</key>
<string>192.168.1.254</string>
<key>targetPortRange</key>
<string>20</string>
</dict>
<dict>
<key>aliasIP</key>
<string></string>
<key>aliasPortRange</key>
<string>21</string>
<key>proto</key>
<string>tcp</string>
<key>targetIP</key>
<string>192.168.1.254</string>
<key>targetPortRange</key>
<string>21</string>
</dict>[/quote:4014ab0130]

unfortunatly all I get from natd after trying to startup is:

[quote:4014ab0130]Feb 23 15:45:24 gw servermgr_nat: nat config:Notice:Deleted old NAT rule
Feb 23 15:45:24 gw servermgr_nat: nat config:Notice:natd process is stopped
Feb 23 15:45:34 gw servermgr_nat: nat config:Error:Cannot launch natd[/quote:4014ab0130]

I left aliasIP blank, because it is dynamically from PPPoE (ppp0). the originally syntax from natd.conf at FreeBSD (my old router) was:

[quote:4014ab0130]redirect_port tcp 192.168.1.254:20 20
redirect_port tcp 192.168.1.254:21 21[/quote:4014ab0130]

At the moment I have no more ideas 🙁

Greetings from Europe
-=IceHouse=-

[ed209]

I can confirm this behaviour – an aliasIP key is required in the plist when it should not be. Native natd permits the aliasIP parameter to be omitted for precisely this scenario – where the nat interface is dynamcally addressed.

Marc Bailey

[Author]

Posts