> What is wrong with this:
Well, for starters you're using *BSD, I believe.
> unclad:www {281} netstat -an |grep LISTEN
> tcp4 0 0 212.238.105.241.53 *.*
> tcp4 0 0 127.0.0.1.53 *.*
> tcp4 0 0 10.0.0.10.53 *.*
Looks like you forgot your bind entries in /etc/named.conf..
second, you posted your IP addy to the list. Third, this
is obviously on your firewall. I believe demon internet
is a new zealand-based dialup ISP. Given the DNS entry,
I believe it is safe to assume you work there, as it is
not part of their normal dialup blocks.
As a humorous aside, ns0.demon.nl is not properly rejecting
requests for zone xfers. I wonder whether you setup those
servers or not. =)
After eliminating the well-known ports in your list,
we're left with:
> tcp4 0 0 *.587 *.*
> tcp4 0 0 *.1022 *.*
> tcp4 0 0 *.2049 *.*
> tcp4 0 0 *.1023 *.*
Now, I know that 1023 is not a well-known service,
but I often find that port open - the reason I
disrecall, so let's drop that one from the list.
This leaves:
> tcp4 0 0 *.587 *.*
> tcp4 0 0 *.1022 *.*
> tcp4 0 0 *.2049 *.*
I'm going to also drop 587 and 1022 because they are
under the "1024" priveledged ports. I don't know for
sure if Freenet runs as root, but I believe it is safe
to assume the developers are trying to make sure that
is not necessary. This leaves us with 2049, our freenet
node.
Do I get a prize?
~ Signal 11
_______________________________________________
Freenet-dev mailing list
Freenet-dev at lists.sourceforge.net
http://lists.sourceforge.net/mailman/listinfo/freenet-dev