Double NAT

Ofloo

That's the whole point SIP does work but it uses UDP, I wanted to give clients access to it using TCP cause in some networks UDP can't get passed a proxy, you need TCP but sip does work when it's using UDP it uses the same rules as TCP but for some reason TCP doesn't work.

And I have a sip server

johnpoz

"You do not need outbound rules with only 1 WAN/default gateway. pfSense is stateful."

Agreed.. But from his first few statements..
"I've got a second cable modem with isp setup the isp for some reason doesn't want to provide bridge"

But seems he using a different copy of pfsense, which is my bad for not reading it correctly. But which is why I asked if 2 wan connections.
"You have 2 wan connections right.."
" What wan connection will it go out of - the normal wan, or this new double nat wan?"
"If your traffic comes in in isp 2, and you send out the traffic in answer out isp 1?"

Ofloo

double, still working on that network map, have it ready in a bit

Ofloo

sorry not really good in these drawings tried to be as clear as possible

WAN2.png_thumb
network.png_thumb

mikeisfly

What ISP are you using, I may be able to help? Why not put your firewall in the DMZ of the ISP NAT device. Most of the time their DMZ will forward all unsolicited traffic to the DMZ IP.

Ofloo

The ISP nat is in dmz to 192.168.10.10, .. the target is the router, ..

Derelict

Aren't we just wasting time trying to double-NAT SIP?

mikeisfly

Who is your ISP?

Ofloo

The ISP with the issue is Telenet it's european, .. and no where not wasting time trying to make sip work, sip already works it uses udp. I'm trying to forward a tcp port, with netcat listening on the end, if you want I can make it port 10000, but i don't think this will change the issue, .. why is portforward not working i think it's strange. It shouldn't matter if the traffic before it is NAT it has dmz all is forwarded, .. so why does the traffic stop at the 192.168.10.10 IP

If I setup netcat on IP 192.168.10.10, then I can connect to it, then if I forward the port, it can't connect, I'm pretty sure it's some configuration issue. But I wouldn't know where to start.

# sysctl -a | grep forward
kern.smp.forward_signal_enabled: 1
net.inet.ip.forwarding: 1
net.inet.ip.fastforwarding: 0
net.inet6.ip6.forwarding: 1
#

nat on vr0 inet from 127.0.0.0/8 to any port = isakmp -> 192.168.10.10 static-port
nat on vr0 inet from 127.0.0.0/8 to any -> 192.168.10.10 port 1024:65535
nat on vr0 inet from 172.16.1.0/24 to any port = isakmp -> 192.168.10.10 static-port
nat on vr0 inet from 172.16.1.0/24 to any -> 192.168.10.10 port 1024:65535
nat on vr0 inet from 192.168.1.0/24 to any port = isakmp -> 192.168.10.10 static-port
nat on vr0 inet from 192.168.1.0/24 to any -> 192.168.10.10 port 1024:65535
rdr on vr0 inet proto tcp from any to 192.168.10.10 port = 5060 -> 192.168.1.40
rdr on vr0 inet proto udp from any to 192.168.10.10 port = 5060 -> 192.168.1.40
rdr on vr1 inet proto tcp from any to 192.168.10.10 port = 5060 tag PFREFLECT -> 127.0.0.1 port 19000
rdr on vr1 inet proto udp from any to 192.168.10.10 port = 5060 tag PFREFLECT -> 127.0.0.1 port 19000

also i can connect to the ssh pfsense from the outside, however I can't forward it to any other ssh

Ofloo

I think I know what the problem is, .. however I'm not sure how to solve this

from what i gather

tcp:

SYN =>
<= SYN ACK
ACK =>
connection established

however, ..

WAN2 is a secundairy gateway while WAN1 is the default gateway, .. traffic is comming in through WAN2, however since the WAN1 is the default gateway of the client, it responds through WAN1, connection failed.

Exactly like johnpoz said earlier.

edit:

yes, if i change the route for that specific ip i can connect to the tcp, however now my question how can i make a dynamic route so that when I connect to it that traffic goes through the correct gateway. And that's why UDP works. It all makes sense now.

can this be solved with a routing daemon?