PfSense newbie configuration problem

wallabybob

This is the traceroute result

I take it from the preceding text in your reply that the tracert output is taken from one of the VMs that can't reach the internet.

@vdecristofaro:

C:\>tracert www.google.com

Tracing route to www.google.com [173.194.35.146]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.69.121.2

This is allegedly on a machine that is using pfSense as its default gateway and gets it IP address from DHCP server running on pfSense LAN interface. Therefore why is the nexthop address on a completely different subnet from the pfSense LAN interface (192.168.83.1/24)?

In short, the information you have provided is horribly contradictory. Until you correct that I doubt I can help you.

stephenw10

Traceroute in Windows (XP sp3 at least) gives the WAN gateway as the first hop:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Steve>tracert google.com

Tracing route to google.com [74.125.230.97]
over a maximum of 30 hops:

  1     5 ms     6 ms     7 ms  217.32.145.233
  2     6 ms     5 ms     6 ms  217.32.146.30
  3    10 ms    10 ms    10 ms  213.120.181.118
  4    10 ms    10 ms    10 ms  217.41.169.203
  5    10 ms    10 ms    10 ms  217.41.169.109
  6    10 ms    10 ms    10 ms  acc2-10GigE-9-2-0.sf.21cn-ipp.bt.net [109.159.251.221]
  7    19 ms    18 ms    19 ms  core1-te0-2-2-0.ilford.ukcore.bt.net [109.159.251.145]
  8    18 ms    18 ms    18 ms  peer1-xe3-1-0.telehouse.ukcore.bt.net [109.159.254.213]
  9    19 ms    19 ms    19 ms  195.99.125.21
 10    15 ms    16 ms    15 ms  209.85.252.188
 11    17 ms    17 ms    17 ms  209.85.251.62
 12    16 ms    16 ms    16 ms  lhr14s01-in-f1.1e100.net [74.125.230.97]

Trace complete.

C:\Documents and Settings\Steve>ipconfig

Windows IP Configuration

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . : fire.box
        IP Address. . . . . . . . . . . . : 192.168.2.10
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.2.1

@vdecristofaro:

rule 1/0(match): block in on em0: 10.169.121.X.137 > 10.169.121.255.137

This implies your WAN is in 10.169.121.* but that doesn't appear in the traceroute. However 10.69.121.* does, typo?

Steve

vdecristofaro

@wallabybob:

This is allegedly on a machine that is using pfSense as its default gateway and gets it IP address from DHCP server running on pfSense LAN interface. Therefore why is the nexthop address on a completely different subnet from the pfSense LAN interface (192.168.83.1/24)?
In short, the information you have provided is horribly contradictory. Until you correct that I doubt I can help you.

I did a mistake I am sorry.
In effect when doing traceroute form my HOST or from the pfSense VM the result is the one I have posted.
When doing traceroute from a VM of the virtual network I just see this

C:\>tracert google.com

Tracing route to www.google.com [173.194.35.146]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  harper.localdomain [192.168.83.1]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.

I am sorry for the mistake…

vdecristofaro

@stephenw10:

This implies your WAN is in 10.169.121.* but that doesn't appear in the traceroute. However 10.69.121.* does, typo?

Steve

I do not know how the network is made because it is very complex and spreads between multiple countries.
What I know for sure is that my IP address (the Host as well as the WAN in the pfSense) is in the family 10.69.121.* and if I traceroute to google I can see that the first hop is the gateway defined statically in the NIC configuration.
Why are you saying that it does'nt appear in traceroute?

podilarius

If you are not NATing, then you need to make sure that the upstream routers knows how to route the traffic back to the LAN side of your pfSense machine. If you don't have control of that, then you need to stick with NATing.

In all my traceroutes under 2.1 the LAN of my firewall is the first hop. In your case that should 192.168.83.1. In my traceroutes under 2.0.1, the WAN IP if the pfSense FW is the first. Strange!?.

If you have control over the downstream routers, I would check them to make sure the routing is correct and then test by pinging them. With firewall turned off, there is no rule or NAT problem that will affect packets getting to the destination, only routing issues.

vdecristofaro

@podilarius:

If you are not NATing, then you need to make sure that the upstream routers knows how to route the traffic back to the LAN side of your pfSense machine. If you don't have control of that, then you need to stick with NATing.

Ok. I am almost sure that I am not NATing.
I went to the webconfigurator, setup -> advanced -> Firewall/NAT
and it is so configured:

Disable NAT reflection for port forward : Checked
Reflection timeout: empty
Disable NAT Reflection for 1:1 NAT: Checked
Automatically create outbound NAT rules […] : Not Checked
TFTP Proxy: I have selected the WAN interface and specified proxy params in the Miscellaneous TAB

@podilarius:

If you have control over the downstream routers, I would check them to make sure the routing is correct and then test by pinging them. With firewall turned off, there is no rule or NAT problem that will affect packets getting to the destination, only routing issues.

It seems so easy to me to logically understand things that you are explaining :)
But unfortunately I am not able to troubleshoot routing issues :-[
Could you please drive me in applying your suggestion? Thanks

stephenw10

@podilarius:

In all my traceroutes under 2.1 the LAN of my firewall is the first hop. In your case that should 192.168.83.1. In my traceroutes under 2.0.1, the WAN IP if the pfSense FW is the first. Strange!?

Indeed I thought it should show the pfSense machine as the first hop but it doesn't. :-\

@vdecristofaro:

Ok. I am almost sure that I am not NATing.
I went to the webconfigurator, setup -> advanced -> Firewall/NAT
and it is so configured:

Automatically create outbound NAT rules […] : Not Checked

If you have turned off outbound NAT, and it looks like you have, then you will need to have all your routing tables correct or nothing knows where to go. Ping replies from your second hop do not have a route back your internal machines.

I suggest your turn Auto Outbound NAT back on unless you really need to have it disabled.

Steve

podilarius

If you are going to get NAT going, you need to uncheck the option to disable all firewall filtering. This will turn NAT back on so that you can use Automatic NAT.

The thing is that every router behind your public IP (which is doing the main NAT), is going to have to know how to route 192.168.83 to your pfSense machine. Without that, you are not going to get this working. (IF you are not NATing)

okay, so the main confusion is if you are going to NAT or not, firewall or not. Once you let us know, then we can help further. Otherwise, we are going to talk in generalities to help you make up your mind on NATing or not. It can be done either way, its just that the config is very different.

vdecristofaro

@podilarius:

…
The thing is that every router behind your public IP (which is doing the main NAT), is going to have to know how to route 192.168.83 to your pfSense machine. Without that, you are not going to get this working. (IF you are not NATing)
...

Well… I thought to this very very long time, and at the end, came to the decision to use NAT (mainly because I cannot ask nobody to configure routers behind my WAN...)
Which parameters should I setup?

:)

podilarius

Okay … in advanced setup -> uncheck the option to disable firewalling. Save and apply.
Then head to firewall -> advanced outbound NAT and select auto. Save and apply.
After that, head to firewall -> rules -> LAN. Setup a rule to allow any protocol with source LAN subnet to Any/Any. Save and apply.
Then go to Services -> DHCP and enable that on LAN. give is a range like 192.168.83.50-250. save and apply.
reboot the FW.

Get on a machine behind the FW and trace route to www.google.com and see how far your get.

vdecristofaro

@podilarius:

Okay … in advanced setup -> uncheck the option to disable firewalling. Save and apply.

Done!

@podilarius:

Then head to firewall -> advanced outbound NAT and select auto. Save and apply.

Do you mean the tab Firewall/NAT on the Advanced Setup page?

I went to System - > Advanced Setup and then to the Firewall/NAT tab.
These are my settings now

@podilarius:

After that, head to firewall -> rules -> LAN. Setup a rule to allow any protocol with source LAN subnet to Any/Any. Save and apply.

Here it is!

@podilarius:

Then go to Services -> DHCP and enable that on LAN. give is a range like 192.168.83.50-250. save and apply.
reboot the FW.

Done!

@podilarius:

Get on a machine behind the FW and trace route to www.google.com and see how far your get.

I have tried. Now i am able to traceroute any public server. I can see that, respect to traceroute when done from the HOST, now the first hop is the pfSense router itself. Very good. Unfortunately anyway I am not able to navigate on the internet. I have used Fiddler to see what's going on and I can see that the request terminate with HTTP 502 - Connection Failed.

I suspect that is the proxy server…

podilarius

@vdecristofaro:

Do you mean the tab Firewall/NAT on the Advanced Setup page?

Yes I do. Not the Advanced in system setup.

Error 502 does seem to be a proxy stopping the connection (lists as bad gateway).

Check your DNS settings on the FW to make sure you websites are resolving correctly. Can you get to a page that other Clients can get to as well?

vdecristofaro

@podilarius:

@vdecristofaro:

Do you mean the tab Firewall/NAT on the Advanced Setup page?

Yes I do. Not the Advanced in system setup.

Error 502 does seem to be a proxy stopping the connection (lists as bad gateway).

Check your DNS settings on the FW to make sure you websites are resolving correctly. Can you get to a page that other Clients can get to as well?

For other reasons this morning I was trying to install wget.
So from the pfSense box I've choosen "8 - Shell" and then:

Went to /etc/csh.cshrc to setup http_proxy, https_proxy and ftp_proxy environment variables
restarted the box
Again to the shell I have tried to install wget with the command /usr/sbin/pkg_add -r wget

The result really surprised me.


Error: Unable to get to ftp://ftp.freebsd.org/......: No address record
pkg_add: Unable to fetch 'ftp://ftp.freebsd.org/.....' by URL

this seems to be a nameserver problem. Right? my resolv.conf file seems to have right values anyway

domain localdomain
nameserver 127.0.0.1
nameserver 10.182.209.132
nameserver 10.254.49.133
nameserver 8.8.8.8
nameserver 8.8.4.4

I dont understand what the "domain" entry and the "nameserver 127.0.0.1" are for, but I guess their presence shall not be a problem….Do I am right?

johnpoz

Ok here is the thing - you mention your in a large network right.

Large networks quite often do a few things for security reasons. 1 they normally only allow a proxy internet access, so to get to the internet you have to use that proxy. Direct internet access is blocked - only the proxy is allowed internet access.

2 they normally block dns, your local dns you point to - ie those 10.182 and 10.254 IPs more than likely don't even resolve public domains. quick enough to check, using nslookup or dig - do a query to them directly for outside something, www.google.com, ftp.freebsd.org, etc. Along with not allowing the local nameservers to resolve public domains they normally do not allow you to query outside dns, ie the those googledns you have there at 8.8.8.8

This is common practice for corp networks. Why you would need to run a router/firewall inside your corp network without support and details from corp IT is beyond me.

But unless you bounce off your corp proxy is more than likely your never getting off the corp network.

So does your workstation have internet access? If so look to see what proxy your browser is pointing to.

you state

"Now i am able to traceroute any public server"

Lets see this! And what are you using for your dns? You doing this from your PC or pfsense? Please post the details of where you doing this traceroute ip address, gateway and nameserves - along with the full trace to www.google.com – here is example


C:\Windows\system32>tracert www.google.com

Tracing route to www.google.com [74.125.225.210]
over a maximum of 30 hops:

  1     2 ms    <1 ms    <1 ms  pfsense.local.lan [192.168.1.253]
  2    28 ms    28 ms    29 ms  c-24-13-176-1.hsd1.il.comcast.net [24.13.176.1]
  3    13 ms    10 ms    11 ms  te-1-2-ur07.mtprospect.il.chicago.comcast.net [68.85.131.149]
  4    11 ms    11 ms     9 ms  te-8-4-ur08.mtprospect.il.chicago.comcast.net [68.86.187.202]
  5    16 ms    15 ms    15 ms  te-1-2-0-5-ar01.area4.il.chicago.comcast.net [68.87.230.53]
  6    15 ms    23 ms    23 ms  pos-3-10-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.93.181]
  7    12 ms    14 ms    16 ms  pos-1-8-0-0-pe01.350ecermak.il.ibone.comcast.net [68.86.87.166]
  8    21 ms    12 ms    13 ms  66.208.228.202
  9    13 ms    13 ms    28 ms  209.85.254.128
 10    13 ms    13 ms    27 ms  72.14.237.130
 11    25 ms    23 ms    24 ms  209.85.241.22
 12    66 ms    33 ms    34 ms  72.14.239.49
 13    32 ms    34 ms    37 ms  216.239.46.149
 14    33 ms    33 ms    34 ms  209.85.251.111
 15    34 ms    34 ms    33 ms  den03s06-in-f18.1e100.net [74.125.225.210]

Trace complete.

stephenw10

For the record you can just use fetch instead of wget and it's already installed.

Also the pkg source location is now out of date for 2.0.1 so you have to specify the full path to the file. E.g.

pkg_add -r ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/i386/packages-8.1-release/Latest/wget.tbz

Also if ftp is blocked upstream you can use http instead:

pkg_add -r http://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/i386/packages-8.1-release/Latest/wget.tbz

Steve

podilarius

what johnpoz says is very true of corporate networks. I would use a DNS server other than corporate if I was going to try to get around security. Most likely they have it so that only certain IP or users can even get to the internet. Can you get to local web servers? They may even have a captive portal or something.

vdecristofaro

@johnpoz:

Ok here is the thing - you mention your in a large network right.

Large networks quite often do a few things for security reasons. 1 they normally only allow a proxy internet access, so to get to the internet you have to use that proxy. Direct internet access is blocked - only the proxy is allowed internet access.

Right!

@johnpoz:

2 they normally block dns, your local dns you point to - ie those 10.182 and 10.254 IPs more than likely don't even resolve public domains. quick enough to check, using nslookup or dig - do a query to them directly for outside something, www.google.com, ftp.freebsd.org, etc. Along with not allowing the local nameservers to resolve public domains they normally do not allow you to query outside dns, ie the those googledns you have there at 8.8.8.8

I dont really know how to read dig results but here is the result of that command when executed inside the pfSense VM

@johnpoz:

This is common practice for corp networks. Why you would need to run a router/firewall inside your corp network without support and details from corp IT is beyond me.
But unless you bounce off your corp proxy is more than likely your never getting off the corp network.

The reason is quick explained. I dont mind about the firewall. I have several VM (5/6) that resemble networks and that I use to develop software solutions. Having a software router for those "virtual labs", which is the only thing I need, has a couple of advantages for me. First of all I have a network lab that is really very similar to the production environment. In addition having 5/6 VM running inside my laptop, every one with two NIC (1 for internal network and one for the internet, will completely jeopardize my host NIC…
For those reasons I just thought that having a "software router" would be a solution. Maybe this solution does not apply on the network where I am now and will work without any further configuration if I would have DIRECT access to the Internet.

@johnpoz:

So does your workstation have internet access? If so look to see what proxy your browser is pointing to.

Yes. I can browse the internet from my host using a proxy. I have statically (in /etc/csh.cshrc) setup the same proxy inside the pfSense.
but unfortunately, even if I follow stephenw10 suggestion I cannot get to the record because of the same "No address record" error.

@johnpoz:

you state

"Now i am able to traceroute any public server"

Lets see this! And what are you using for your dns? You doing this from your PC or pfsense? Please post the details of where you doing this traceroute ip address, gateway and nameserves - along with the full trace to www.google.com – here is example

Well I have just posted the result of doing dig in the pfSense VM. So let's see how the host and the VM in the Virtual network behaves.

When I execute nslookup from the host PC I get these results

C:\>nslookup www.google.com
Server:  usdnsl201-ficus.usinet.it
Address:  10.182.209.132

Non-authoritative answer:
Name:    www.google.com
Addresses:  2a00:1450:400c:c06::6a
          74.125.132.106
          74.125.132.147
          74.125.132.99
          74.125.132.103
          74.125.132.104
          74.125.132.105

Finally this is the result when I execute nslookup from a windows PC/server inside the virtual network

C:\>nslookup www.google.com
1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa
        primary name server = 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.ip6.arpa
        responsible mail addr = (root)
        serial  = 0
        refresh = 28800 (8 hours)
        retry   = 7200 (2 hours)
        expire  = 604800 (7 days)
        default TTL = 86400 (1 day)
Server:  UnKnown
Address:  ::1

Non-authoritative answer:
Name:    www.google.com
Addresses:  2a00:1450:400c:c06::63
          74.125.132.106
          74.125.132.147
          74.125.132.99
          74.125.132.103
          74.125.132.104
          74.125.132.105

johnpoz

Well your vm there it asked itself for dns on the ipv6 loopback, so is then forwarding or looking up direct from roots?

Same thing with your pfsense - it asked its dns forwarding process for that address, you don't actually know which dns server it asked for that. I believe it asks all of them and uses the one that answers first? Or does it ask in order? There was a thread back a while back that went over this - but I don't recall the details on that.

So clearly you can do outside dns queries - but if your having to use a proxy to actually get outbound access, the ability to do dns doesn't help much ;)

Now in
System: Advanced: Miscellaneous

There is a way to point to an upstream proxy to allow pfsense access - but not sure on how that actually functions, does that mean that need to be using proxy on pfsense? Or does pfsense just route all that traffic to that proxy?

vdecristofaro

@johnpoz:

Well your vm there it asked itself for dns on the ipv6 loopback, so is then forwarding or looking up direct from roots?

Same thing with your pfsense - it asked its dns forwarding process for that address, you don't actually know which dns server it asked for that. I believe it asks all of them and uses the one that answers first? Or does it ask in order? There was a thread back a while back that went over this - but I don't recall the details on that.

So clearly you can do outside dns queries - but if your having to use a proxy to actually get outbound access, the ability to do dns doesn't help much ;)

Now in
System: Advanced: Miscellaneous

There is a way to point to an upstream proxy to allow pfsense access - but not sure on how that actually functions, does that mean that need to be using proxy on pfsense? Or does pfsense just route all that traffic to that proxy?

I did already setup proxy as you're suggesting. Me too, I dont have idea on how this works. In the next days I will try this setup in a network with direct access just to verify that in effect this can be a problem caused by the presence of the proxy.

For now, I would like to thank all the people that spent some of it's time trying to help.
:)

stephenw10

There is no need to add the proxy information to pfSense, you only need to do that as a convenience for machines behind pfSense and to enable the box itself to have web access. You can just add the proxy to the clients behind pfSense as would for boxes in front it. You won't be able to update from the webgui.
It maybe that the upstream proxy has a problem with NATed clients connecting to it perhaps by design. It would seem reasonable for your network admin to not won't people running their own routers.

Steve