[EMAIL PROTECTED] wrote:
So on the Limewire Advanced - Firewall config page enter a port
number, such as 6346 in both the Listen on Port and the Manual Port
Forward boxes.
Then after your NAT rule in pf.conf enter something like the following:
rdr on $ExtIF proto tcp from any to any port
On Fri, 28 Nov 2008 14:31:14 +0800
Fbsd1 [EMAIL PROTECTED] wrote:
I think you are missing the fact that limewire does not use dedicated
port numbers. Every session uses different port numbers and the remote
computers come in on different hight port numbers. Limewire starts off
with a proto
Fbsd1 said the following on 2008-11-28 08:19:
I checked the ipfilter online handbook and can not find anything about
rules for igmp packets, p2p or limewire. I know what a rdr statement
does but can not see how it can be applied to a p2p application which
does NOT use dedicated port numbers.
Fbsd1 said the following on 2008-11-28 08:19:
I checked the ipfilter online handbook and can not find anything about
rules for igmp packets, p2p or limewire. I know what a rdr statement
does but can not see how it can be applied to a p2p application which
does NOT use dedicated port numbers.
Fbsd1 wrote:
[snip]
The only way i can run limewire is
to disable my firewall and that does not make me happy.
This is simply not true. I have at one time or another run Limewire on
each of the three different firewalls. Currently for a little over
one year now it has been pf. The difference
On Fri, 28 Nov 2008 14:24:27 +0800
Fbsd1 [EMAIL PROTECTED] wrote:
How about explaining just why this is going to allow p2p limewire
work?
I think you are missing the fact that limewire does not use dedicated
port numbers.
Every session uses different port numbers
You can presumably set
Michael Powell [EMAIL PROTECTED] escribió:
Fbsd1 wrote:
[snip]
The only way i can run limewire is
to disable my firewall and that does not make me happy.
This is simply not true. I have at one time or another run Limewire on
each of the three different firewalls. Currently for a little over
What pf or ipf firewall keep-state rules needed to allow p2p application
such as limewire through? Using same firewall rules as in handbook example.
___
freebsd-questions@freebsd.org mailing list
On Thu, Nov 27, 2008 at 3:56 AM, Fbsd1 [EMAIL PROTECTED] wrote:
What pf or ipf firewall keep-state rules needed to allow p2p application
such as limewire through? Using same firewall rules as in handbook example.
Well, what port does limewire use? You need to figure out what port
each
Fbsd1 said the following on 2008-11-27 09:56:
What pf or ipf firewall keep-state rules needed to allow p2p application
such as limewire through? Using same firewall rules as in handbook example.
Put this in your /etc/ipnat.rules
rdr rl0 0.0.0.0/0 port port# - internal-ip port port# tcp
rdr
Bernt Hansson wrote:
Fbsd1 said the following on 2008-11-27 09:56:
What pf or ipf firewall keep-state rules needed to allow p2p
application such as limewire through? Using same firewall rules as in
handbook example.
Put this in your /etc/ipnat.rules
rdr rl0 0.0.0.0/0 port port# -
APseudoUtopia wrote:
On Thu, Nov 27, 2008 at 3:56 AM, Fbsd1 [EMAIL PROTECTED] wrote:
What pf or ipf firewall keep-state rules needed to allow p2p application
such as limewire through? Using same firewall rules as in handbook example.
Well, what port does limewire use? You need to figure out
Fbsd1 said the following on 2008-11-28 07:24:
Bernt Hansson wrote:
Fbsd1 said the following on 2008-11-27 09:56:
What pf or ipf firewall keep-state rules needed to allow p2p
application such as limewire through? Using same firewall rules as in
handbook example.
Put this in your
Bernt Hansson wrote:
Fbsd1 said the following on 2008-11-28 07:24:
Bernt Hansson wrote:
Fbsd1 said the following on 2008-11-27 09:56:
What pf or ipf firewall keep-state rules needed to allow p2p
application such as limewire through? Using same firewall rules as
in handbook example.
Put
14 matches
Mail list logo
