Dear Elmo,
The invalid UDP packet is a commonly seen error which is normally of interest only to aMule developers who are in the process of debugging, and is of no consequence to the general user.
In this case, however, it tells us that at least aMule is working well enough to notice UDP packets -- although the one it complained about could be from just about anywhere and any source -- not necessarily an aMule server or client.
There is another way besides the port test mentioned in the wiki to verify your ports are working. As before, run your Ethernet cable directly into the modem and disable OS X's internal firewall and any other firewall applications. Start aMule. A company called Gibson Research Corporation has an online service called "Shields Up!" <
https://www.grc.com/x/ne.dll?bh0bkyd2> to probe ports. It's intended for PCs to use in their never-ending battle with hackers, but will serve the occasional Mac user well enough.
Once on the GRC page, scoot to the bottom and click 'Proceed." Safari will complain it's a non-secure form (it may even complain twice). If you don't trust GRC -- or my suggestion to use them, for that matter -- to access your computer without your firewall on, then Google around a bit to see what the rest of the world thinks of the service.
On the page which appears after clicking on 'proceed,' type the range of ports you're using into the text-entry box (surrounded by the light blue border) and click on "User specified Custom Port Probe." Unlike most tests, you
want to fail this one -- that is, to have solicited TCP packets accepted and aMule's primary TCP port seen as open. The more things in
RED, the better.
If you are successful, then work your way backwards checking your ports while examining your settings for your Airport, and your firewalls.
Neither of Apple's Security updates have done anything to affect aMule's ability to connect.
