Not to sound like a jerk, but have you checked it out very much? A quick search of lingo port forward hit this: http://portforward.com/english/routers/port_forwarding/Lingo/Primus-iAN- 02ex/Echolink.htm perhaps that's not your model number or something, but you might find that useful.. If you have multiple IP's a DMZ entry isn't horrid, but kinda overkill. I've always loved how Vonage doesn't need any special firewall rules to work.
-----Original Message----- From: BSD Wiz [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 03, 2008 10:41 PM To: [email protected] Subject: Re: [pfSense Support] rule not working correctly lingo... yeah, i wish i could only forward the specific ports needed but lingo support is terrible and they don't know jack... i tried to figure out what ports are being used but the range is HUGE! so i'm pretty much stuck putting it into my dmz and allowing all traffic from a single IP. -phil On Sep 3, 2008, at 10:24 PM, Christopher B. Uthe wrote: > What kind of VOIP are you working with, can specific ports be > used/configured? Better Idea to forward specific ports vs all traffic > if you can do it. > > Chris > > > -----Original Message----- > From: BSD Wiz [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 03, 2008 7:36 PM > To: [email protected] > Subject: Re: [pfSense Support] rule not working correctly > > yes, it's causing problems. my phone won't ring when it get's > blocked. that's exactly how i figured out it was getting blocked, > people where telling me they were calling me but my phone never rang. > i then went back and looked in the log files and noticed that the > call was getting blocked. > > > thanks, > > -phil > > > > On Sep 3, 2008, at 7:10 PM, Chris Buechler wrote: > >> On Wed, Sep 3, 2008 at 7:54 PM, BSD Wiz <[EMAIL PROTECTED]> wrote: >>> please allow me to pose this question again. i am trying to allow >>> all >>> traffic from a specific source ip into my DMZ(10.0.0.0/24) for my >>> VoIP >>> phone. the problem is that it's not always passing the traffic and >>> some >>> times it's getting blocked. >>> >>> i have created a rule on my WAN interface as follows: >>> >>> UDP 216.181.136.7 * 10.0.0.0/24 * * >>> >>> >>> >>> even with the above rule in place i'm seeing the following entry >>> in my logs. >>> it's important to note that it doesn't always get blocked, perhaps >>> it has >>> something to do with the high ports as mentioned on this list >>> before? >>> >>> Sep 3 18:43:43 WAN 216.181.136.7:5065 >>> xx.xx.xx.xx:52042 >>> UDP >>> >>> >>> when i click on the blocked log it says: The rule that triggered >>> this >>> action is: >>> >>> @118 block drop in log quick all label "Default deny rule" >>> >>> >>> >>> >>> any suggestions? >>> >> >> Is it causing problems, or are you seeing it and thinking it's a >> problem? If there are no noticeable issues it's likely just normal >> out >> of state traffic which will happen periodically. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
