On Mon, Apr 12, 2010 at 01:11, Rod Whitworth wrote:
> On Mon, 12 Apr 2010 00:18:31 -0300, Hugo Osvaldo Barrera wrote:
> 8>< snip long message. My reply would be easy to miss in all that and
> it doesn't address lots of the thread.
>
> Caveat: I don't do pidgin etc BUT I do VoIP behind NAT with mul
On Mon, 12 Apr 2010 00:18:31 -0300, Hugo Osvaldo Barrera wrote:
8>< snip long message. My reply would be easy to miss in all that and
it doesn't address lots of the thread.
Caveat: I don't do pidgin etc BUT I do VoIP behind NAT with multiple
ATAs and the audio uses RTP.
I use sipproxy from packag
On Thu, Apr 8, 2010 at 11:47, James Shupe
wrote:
> My idea is to maintain a table of RTP servers, if that is possible. RTP
> uses any unprivileged port (or a port above 1024) to send traffic on. Your
> rule would be a rule that would allow any of that unprivileged UDP traffic
> from only those hos
Sorry, I too, forgot to send to misc@
On Thu, Apr 8, 2010 at 11:47, James Shupe wrote:
> My idea is to maintain a table of RTP servers, if that is possible. RTP
> uses any unprivileged port (or a port above 1024) to send traffic on. Your
> rule would be a rule that would allow any of that unprivi
On 2010-04-08, Hugo Osvaldo Barrera wrote:
> Effectively, it uses RTP.
> However, I'm not sure I don't quite understand your idea. How would
> the table be updated with which ports to redirect? Or do you mean it
> to be static with the port range currently in use?
most software like this allows
My idea is to maintain a table of RTP servers, if that is possible. RTP
uses any unprivileged port (or a port above 1024) to send traffic on. Your
rule would be a rule that would allow any of that unprivileged UDP traffic
from only those hosts. It's not the perfect solution, but probably is the
mos
On Thu, Apr 8, 2010 at 10:21, James Shupe
wrote:
> Forgot to send to the list, twice!
>
> If it's RTP, (http://en.wikipedia.org/wiki/Real-time_Transport_Protocol),
> which some quick Googling indicates, your best bet may be to make a table
> of sending hosts with a pass ... inet proto udp ... from
Forgot to send to the list, twice!
If it's RTP, (http://en.wikipedia.org/wiki/Real-time_Transport_Protocol),
which some quick Googling indicates, your best bet may be to make a table
of sending hosts with a pass ... inet proto udp ... from to ? port
>1024 rule.
> On Thu, Apr 8, 2010 at 00:54, J
On Thu, Apr 8, 2010 at 00:54, James Shupe
wrote:
> Use "log (all)" and tcpdump to figure out exactly what is being blocked.
>
> On 4/7/10 10:40 PM, Hugo Osvaldo Barrera wrote:
>> I'm using OpenBSD 4.6 at home as an access point, firewall and home
>> server (with pf).
>> I've recently had some issu
I'm using OpenBSD 4.6 at home as an access point, firewall and home
server (with pf).
I've recently had some issues trying to use pidgin's [XMPP] video
support on one of my client computers, yet, if I connect it directly
to the internet it works fine; hence the problem is the firewall
configuration
10 matches
Mail list logo
