Yikes. I'm using aMule under Ubuntu but this is usually self-compiled SVN. Having strange aMule fork by default is strange and disruptive. Ubuntu guys did a quite strange thing. Do not forget to vote on bug by ticking "this bug also affects me" thingie.
P.S. but how about ability to connect lowid to lowid? This is often possible via STUN-like protocol and you already have buddies which can do same trick as STUN server does. So minor protocol change can relax things to a number of users and save them from reinventing wheel.
Inability to connect LowID to LowID caused people to research how to work this around. And ignorance of aMule\eMule dev's caused fork to appear. Now this ignorance backfired and caused a major damage. Don't you think that you should be a bit more responsive to users troubles? For example Lowid to lowid transfers could be implemented easily. So maybe at some day people will not need to reinvent the wheel but can use aMule?
P.P.S. Btw, as for me, I also have ISP with fast LAN which uses private addresses (10.x.x.x range). It would be great if aMule can operate in local network in addition to internet. This probably requires second instance of Kad to start-up and form local-only network with relaxed countermeasures (subnetworks vs contacts limits, etc). There is a number of such networks where ISP runs two nets - internet and intranet and such feature can help users in such networks. Btw some neat ideas including bootstrapping Kad via broadcast in hope someone in our segment responds with bootstrap contacts.