Firewall/NAT

Hi there,

I've installed m0n0 on a Soekris board with the latest m0n0 firmware (1.33b1), and am running Linux on my desktop.  I am relatively new to both Linux and m0n0, and am having trouble setting up my SIP phone EKiga.   I used to have a Linksys router and had Ekiga working fine -- here is what I had on the Linksys:

Port Forwarding:
port: 5060-5061, UDP
port: 1720, TCP (H323)

Port Triggering:
trigger port: 3478-3479,  forwarded ports: 5000-5100

How can I set up this in m0n0 ?  I am new to having separate NAT and Rules pages, so please be easy with me...

Many thanks for any help you can send...

-Nino
nino@njaimo.net

...apparently Ekiga will not work with a "Symmetric NAT", is m0n0wall a symmetric NAT ?

http://wiki.ekiga.org/index.php/Documentation#Using_Ekiga_with_Routers_and_firewalls

-N

Hello Guys,

....help !?    I've seen other posts relating to SIP, but none that has the details of how I set this up.

I know this may be too basic for most of you, but I am sure I am not the first trying to get this figured out.... I am just starting to learn this and could use a little help...

Cheers !

-N

m0n0wall doesn't have the 'Port Triggering' feature that Linksys does.

You may have some success using the advanced outbound NAT feature.  You'll have to manually set up NAT rules.  There's not a huge amount of documentation but this will get you started: http://doc.m0n0.ch/handbook/nat-outbound.html

Thank you much for the feedback "iridis" !   I have read all the user manual, as you suggest, and you are right, there is not much info there.

In reading some of the other posts in this forum regarding SIP phones, it other users have tried it, I would love hear from anyone with some experience as to how to do this.

Ekiga is a "popular" free SIP phone in Linux distros, and I would have thought someone may have tried this already ?...

Being that m0noWall is aimed at the small bussiness/user (as opposed to enterprise level, as Manuel says in the UG) this would be a feature that would be good to have working.

So any users of SIP phones out there who have any suggestions or can share how they have made their VOIP SIP phones work ?  I would be very grateful for any help.

Even better, I'd be willing to pay an expert set me up.

Regards !

-N

It likely depends on your SIP provider.  I've set up a virtual machine of Askozia (a pbx based on m0n0wall) and tied it to a SIPGate account without any issues.  All I had to do to my m0n0wall router was NAT port 5060.

Thank you again "iridis" for your reply.  My SIP provider is Ekiga.net, the default provider for Ekiga.
I before posting my thread I set up inbound NATs and the corresponding auto rules for opening the ports Ekiga uses.  Since I could not figure out how to do the port-forwarding, I figured that it was worth the risk of having the open ports to see if I coudl get Ekiga to work... no luck.  So I posted this thread, hoping some user/reader may have also tried Linux's Ekiga and figured this out in m0noWall.

Have to say, I am getting a bit sad I have not been able to either figure it out myself (been googling and reading this forum all over), nor found anyone who may be able to help.  I really like m0n0wall, and since I've switched from my Linksys router to my new set-up I have been enjoying increased speed to the internet (not sure exactly why, but it is amazing).  ...but I am ready to drop m0n0wall, and try someting else -- I understand pfSense may run OK in my net5501, and that it has port-forwarding capabilities and much more...  pfSense may likely be way overkill for my home, but I'd rather use Ekiga than pay my local phone company for the higher long-distance charges... and I'd rather not use Skype if I can help it...

Again, many thanks for your replies !!  

-N

...update... probably I was the only one with this problem, but just in case I figured I post I have it working, and it was a simple fix, once I had the correct info, and I ignored the "it won't work w/out port triggering" etc...

I just forwarded UDP ports 5060-5100 for SIP, TCP 1720 for H323, and TCP 30,000-30,010 for SIP to my PC (NAT & rules).  It all works fine, and I am the only one in my LAN needing to do this.  I suppose it would not work if other PCs in the LAN also needed to...

Cheers...