Port forwarding problems
-
I just tried analyzing the setup in the link you've posted but I'm not sure if it is applicable in my case. Anyone else have any ideas on this?
-
BUMP!
-
Help needed here guys? Please?
-
BUMP!
-
Daily BUMP!
Is this a hard-to-solve issue, really?
-
Packet capture traffic on the firewall for a host you can not access externally. Get a friend on the phone and ask them to try. Analyse the capture. Best guess the traffic hits the target but the target does not know where to send it back.
Also I have a feeling Sab has a setting in the ini file that tells it what networks it will talk to. That might be worth a look just to make sure it's not restricted to the local net.
edit/
No it doesn't I've just looked but it's default bind is the loopback so make sure it is bound to the IP of the box. Also I hope the port you are trying to redirect to is the https port of Sab and not the http. -
Have an nearly-same problem,
I got two WAN´s, too, but i can only access the LanPC which are on the Default-WAN.
The problem is that the packet from the secondary WAN comes in and dont find out (because it goes over the Default-WAN). -
Packet capture traffic on the firewall for a host you can not access externally. Get a friend on the phone and ask them to try. Analyse the capture. Best guess the traffic hits the target but the target does not know where to send it back.
Also I have a feeling Sab has a setting in the ini file that tells it what networks it will talk to. That might be worth a look just to make sure it's not restricted to the local net.
How do you actually do a packet capture on the firewall?
As I've probably mentioned above, I've already tried using SAB with a computer that's only connected to a simple DD-WRT router and I can access it from outside the network without any problems. When I bring this same computer and connect it to the network with pfsense as the main firewall, then I cannot access it from outside the network.
-
Under diagnostics -> Packet Capture
Select the LAN interface Set the host address to the IP address of the internal device you are trying to connect to Set the level of detail to full, leave all others at their default. Then get someone outside the network to attempt a connection. Don't try to use NAT reflection as that will confuse things. If you look at the capture and your response is WTF post it and we can take a look.
-
Here it goes (I'm trying to access 192.168.1.2 from outside the network and it did captured some packets. I replaced the source IP address with x.x.x.x):
http://pastebin.com/6YNr4ifL
Any thoughts?
-
Well I see incoming traffic for 192.168.1.2 but I'm not seeing an outgoing response.
Off the top of my head it's a routing issue. Is the LAN interface the default route? Try doing a traceroute from the device 192.168.1.2 and see where it thinks the packet should go. -
Did you defined static routes or is there a second router in your network which reaches the other lan networks? What is the client default gateway? Could you ping all the clients defined from the pfsense "ping tool"?
-
Well I see incoming traffic for 192.168.1.2 but I'm not seeing an outgoing response.
Off the top of my head it's a routing issue. Is the LAN interface the default route? Try doing a traceroute from the device 192.168.1.2 and see where it thinks the packet should go.So that means that the port forwarding works, right?
The default gateway is WAN2 as set by pfsense. From the device 192.168.1.2, which IP should I do a traceroute to? By the way, 192.168.1.2 is a switch (switch-configured linksys router) that has a webgui.
Did you defined static routes or is there a second router in your network which reaches the other lan networks? What is the client default gateway? Could you ping all the clients defined from the pfsense "ping tool"?
My setup is like this:
The default gateway is WAN2. If I setup the interface as LAN in the ping tool of pfsense, yes I can ping all the clients.
-
If you know the address of the person trying to connect try that IP. Otherwise just do a traceroute to something like www.bbc.co.uk or your local google site. Also take a look at your firewall logs just to make sure it's not blocking outgoing traffic.
I'm assuming the switch is just a standard layer 2 device with no acls or VLANs defined on it but if it has and it won't do a traceroute outside your network maybe post the running conf although that is getting beyond the scope of these forums but we do try to help.
Yes your port forward appears to be working correctly.
-
If you know the address of the person trying to connect try that IP. Otherwise just do a traceroute to something like www.bbc.co.uk or your local google site. Also take a look at your firewall logs just to make sure it's not blocking outgoing traffic.
I'm assuming the switch is just a standard layer 2 device with no acls or VLANs defined on it but if it has and it won't do a traceroute outside your network maybe post the running conf although that is getting beyond the scope of these forums but we do try to help.
Yes your port forward appears to be working correctly.
Ok. Should I copy here the result of the traceroute and my firewall logs?
Yes, the switch is a standard non-managed switch, so no worries on that.
When port forwarding, do you usually specify the source port? Which port would the source use anyway when accessing my devices from outside the network?
-
It will be a random port for the source. Yes you can post the traceroute just obscure the IP if it's not to a public server.
-
It will be a random port for the source. Yes you can post the traceroute just obscure the IP if it's not to a public server.
Ok, I'll do that.
Why will it be a random port? I thought the source port is also, usually, the destination port?
-
I thought the source port is also, usually, the destination port?
No. Almost never.
http://en.wikipedia.org/wiki/Ephemeral_port
-
@cmb:
I thought the source port is also, usually, the destination port?
No. Almost never.
http://en.wikipedia.org/wiki/Ephemeral_port
So it's always random?
-
So it's always random?
Short answer yes.
Long answer. It is possible to force the use of a specific port or range but unless you understand the full implications of making such changes it's probable safer to just accept the short answer.I'd like to see your issue resolved so any info you could post would help. There is nothing worse than finding a forum post that resembles your problem and after reading through them all finding it just stops with no resolution.