natd - failed to write packet back (No route to host)

Question

Level 1

45 points

natd - failed to write packet back (No route to host)

Hello.

This has been an on going problem for a while no so I won't be able to determine if any specific app has caused it, but i've been getting tons of "natd[8826] failed to write packet back (No route to host)" and "natd[8826] failed to write packet back (Host is down)" filling up the log. I was able to determine that this happens when natd attempt to connect to 0.0.0.0. Little Snitch says the protocol is 254 (DIVERT) and the port is 2560 (labrat). Any possible cause for this? I know this has been asked on here, but there was no answer give and the post was archived so I could not reply.

20" Intel Core Duo iMac - 2GB RAM, Mac OS X (10.5.6), 30GB 5G iPod - 1GB 2G iPod shuffle - 16GB 1G iPod touch

Posted on Jan 31, 2009 8:16 AM

Reply

Answer 1

InfernoBoy Author

Level 1

45 points

Jan 31, 2009 8:29 AM in response to InfernoBoy

I think I stumbled upon the "fix" for it. In Terminal I did:

*sudo ipfw list*

Which said:

*00010 divert 8668 ip from any to any via en0*
*65535 allow ip from any to any*

The 8668 is somehow referring to natd, I'm not sure why that rule is there. So I did:

*sudo ipfw -f flush*

This cleared out all rules and has seemingly fixed natd connecting to 0.0.0.0. I'm not sure what this will affect in the long run, but so far everything seems fine.

Edit:

Ah, this seems to break Internet Sharing. So if you're using that you might want to leave that rule alone.

Message was edited by: InfernoBoy

Reply