Nate Williams wrote:
>
> > I had blocked incoming TCP connections coming into my network using
> > IPFW, and I noticed that my brother was able to establish a Napster
> > connection, even though I had blocked it earlier.
>
> *sigh*
>
> Thanks to Guy Helmer for being patient with me as I fretted about this.
>
> I just found out that Napster leaves a client running in the background,
> and even though I had added firewall rules to block new connections to
> the server, the old 'established' connection was still up and running.
>
This might be helpful to you and others. Since napster uses what ever
ports it can find the best way is to block the servers.
# Napster
$fwcmd add deny tcp from any to 208.178.163.56/29 via tun0
$fwcmd add deny tcp from any to 208.178.175.128/29 via tun0
$fwcmd add deny tcp from any to 208.49.239.240/28 via tun0
$fwcmd add deny tcp from any to 208.49.228.0/24 via tun0
$fwcmd add deny tcp from any to 208.184.216.0/24 via tun0
Jim
--
[EMAIL PROTECTED] http://www.FreeBSD.org The Power to Serve
[EMAIL PROTECTED] http://www.TheHousleys.net
---------------------------------------------------------------------
Unix is very user-friendly. It's just picky who its friends are.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
