News: This forum is now permanently frozen.
Pages: [1]
Topic: m0n0wall & Full Cone NAT  (Read 2157 times)
« on: May 15, 2012, 09:59:59 »
free *
Posts: 3

Does m0n0wall supports Full Cone NAT, or not?
I ask because it is very important for the proper working of SIP applications.
Thanks in advance.
« Reply #1 on: May 15, 2012, 18:41:35 »
Fred Grayson *****
Posts: 994

If you mean 1:1 NAT, then yes.

--
Google is your friend and Bob's your uncle.
« Reply #2 on: May 17, 2012, 02:54:43 »
free *
Posts: 3

Quote
Going by Wikipedia's definition.
"Once an internal address (iAddr:iPort) is mapped to an external address (eAddr:ePort), any packets from iAddr:iPort will be sent through eAddr:ePort.
Any external host can send packets to iAddr:iPort by sending packets to eAddr:ePort."
Quote
Full Cone NAT allows any external host to use the existing state table entry to access the internal host, kind of like a temporary port forward.
« Reply #3 on: May 17, 2012, 03:48:07 »
Fred Grayson *****
Posts: 994

1:1 NAT doesn't require specifying any ports, they are all forwarded.

--
Google is your friend and Bob's your uncle.
« Reply #4 on: May 17, 2012, 06:39:32 »
free *
Posts: 3

1:1 NAT is a mode of NAT that maps one internal address to one external address.
But my ISP gives me only one public IP address, my private network of over 10 machines and can not take more than one public IP address from the ISP.
« Reply #5 on: May 17, 2012, 15:17:03 »
Fred Grayson *****
Posts: 994

If you only have one public IP address, 1:1 NAT is not appropriate for you.

--
Google is your friend and Bob's your uncle.
« Reply #6 on: May 17, 2012, 15:41:43 »
Lennart Grahl ***
Posts: 153

Quote
Going by Wikipedia's definition.
"Once an internal address (iAddr:iPort) is mapped to an external address (eAddr:ePort), any packets from iAddr:iPort will be sent through eAddr:ePort.
Any external host can send packets to iAddr:iPort by sending packets to eAddr:ePort."
Quote
Full Cone NAT allows any external host to use the existing state table entry to access the internal host, kind of like a temporary port forward.

I sort of get your problem but why don't you just add a forwarding rule?

Never had any issues with my SIP phone behind m0n0wall (while using STUN).
« Last Edit: May 17, 2012, 15:45:35 by Lennart Grahl »
 
Pages: [1]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines