I was somewhat surprised & pleased to see a BearShare 5.1 Beta peer that had been a firewalled peer for the past 5 months suddenly show up as non-firewalled. Plus they were sharing lots of files and over 4 days uptime. Now a totally responsible, respectable and valuable peer for both the BearShare and Gnutella community. Accolades to them for taking the effort.

I first sighted this peer mid-December. I suspect they were previously one of the firewalled culprits in the snapshots in my previous posts above. Good effort of them to become a non-firewalled user. And I have no doubt they are enjoying their experience a lot more with far better results.

I'd been busy over past week (such as with WS tasks) so hadn't used BS for previous 6 days.

Well, that barely even lasted one month. Now that host is TCP & UDP firewalled again. Good luck with that.
I'm guessing they forgot to set up a static internal address so their internal 192. or 10. address did not change between reboots. If it changes then the port forward rule would not work because it was set under a different address. (eg: 10.1.1.3 instead of 10.1.1.2) . .