Pfsense 2.6.0 CE - No internet access
-
I've given up trying everything alone, and I need help. I am a beginner, and I'm trying to install PFsense for my assignment. This is the configuration, everything is connected with cable:
ISP Router -> PC w/pfsense -> Router AP
ISP Router:
Gateway: 192.168.18.1
Subnet: 255.255.255.0
DHCP start-end: 192.168.18.2-254PFSense Interface:
WAN -> hn0 -> v4/DHCP4: 192.168.18.41/24
LAN -> hn1 -> v4: 192.168.11.1/24 (for the configurations of this LAN interface, i pressed "n" on every DHCP question)Router AP's Static WAN setting:
WAN IP Address: 192.168.11.100
Subnet: 255.255.255.0
Default Gateway: 192.168.11.1
DNS Server: 8.8.8.8 / 0.0.0.0Router AP's DHCP setting:
LAN IP Address: 192.168.0.1
DHCP start-end: 192.168.0.100-192.168.0.199
Default Gateway: 192.168.0.1
DNS Server: 8.8.8.8 / 0.0.0.0Devices that connect to the Router AP cannot get an Internet connection. What I've done:
- Ping 8.8.8.8 from PFsense > No route to host
- Ping 8.8.8.8 from Router AP > Request timed out
- Ping 192.168.18.1 from PFsense & Router AP > OK
- Ping 192.168.11.1 from PFsense & Router AP > OK
- Allowed every firewall rule (any, UDP, TCP/UDP, ICMP) for both LAN and WAN interface
If anyone needs additional info or anything, please let me know asap. I'm currently using HyperV and from the configurations everything should be fine.
I tried installing it to the PC baremetal before, and the same problem still occurs. -
@meowmere
Since pfSense gets its WAN IP from the ISP router, it should also get the gateway.
Check Status > Interfaces for the proper settings.Also post Diagnostic > Routes, please.
Can you ping the ISP router from pfSense?
If not check Diagnostic > ARP for an entry of the gateway. -
@meowmere said in Pfsense 2.6.0 CE - No internet access:
Allowed every firewall rule (any, UDP, TCP/UDP, ICMP) for both LAN and WAN interface
Allowing access to WAN allows people outside your network to connect to pfSense and attempt to log in. Usually, a Very Bad Idea.
Rules on WAN are irrelevant for access going out WAN, or coming in on any other interface. Rules are processed as a packet arrives on an interface.
pfSense 2.6 is a couple years out of date at this point.
https://docs.netgate.com/pfsense/en/latest/releases/#pfsense-ce-software -
Did you uncheck "Block private networks and loopback addresses" on the pfSense WAN?
-
@Jarhead That would be inbound, anyway.
-
@SteveITS
Im allowing every firewall as a last-ditch effort to at least get this configuration to have Internet access. Will it matter if I update to pfsense 2.7.2 CE?I will try updating, but what do you think I should do if updating doesn't do it?
-
@viragomann Here are the screenshots
With pfsense, pinging the ISP router 192.168.18.1 and the devices connected to it worked
-
@Jarhead yes I have
-
@meowmere
You have no default route for any reason. Normally pfSense should use the WAN gateway automatically here.To set it manually, go to System > Routing > Gateways and check if the Default Gateway is set to "automatic". If not set it, if it is already, select the ISP router from the drop-down.
-
@viragomann
This should be correct, right? -
@meowmere
No, the selected default gateway is disabled.Just at "Default gateway IPv4" select "Automatic" from the drop-down.
-
On your PC :
Not entering a DNS is "pure self inflicting pain generation" : so, don't.
If you really have to use static IP setting on your PC,, as this is your gateway :
and this
says the same thing,
set your DNS to 192.168.11.1 == pfSense.Btw : normally, when you feel a bit more confident, you could "reset" to default your pfSense.
Then hook up your WAN, and it will get an IP from your upstream (ISP) router, like :
and then you connect your PC to the LAN interface.
!! Set the PC back to the default !!) DHCP mode first !! (this works so well, and you have nothing to do).You can finish your pfSense doing just ONE ( 1 ) thing, and you need the keyboard for this : you have to create your own 'admin' password.
From then on, and I'm serious, do not use the keyboard anymore.
Never ever enter any DNS details into pfSense - leave it into the default settings.
Don't mess with the resover / unbound settings.
pfSense, when the WAN is the default DHCP - work, as any other router out there, out of the box.Again, don't believe me, fact check my words on this one.
And yes, using 2.6.0 ... that like installing Windows 7 these days ... why would you do that ?
-
@Gertjan @Jarhead @SteveITS @viragomann I'm going to update here, so:
I did what Gertjan instructed me, first was the version update. Then I set my PC's network adapter setting to default, after that, I reinstalled my pfsense. WAN uses DHCP, and the LAN uses static 192.168.1.1 as default.
I also returned my AP router to DHCP, and everything worked now! Thank you so much to everyone for saving my time. Before this solution, the reason I manually set the IPs static was from YouTube tutorials. 2.6.0 because hyperV got stuck on installation whenever I use 2.7.2.
Although, there is something odd. I tried doing the same thing to my other network with a different ISP and it did not work. What do you guys think is the possible problem? could it be from the ISP router configurations that I have to change?
-
@meowmere said in Pfsense 2.6.0 CE - No internet access:
could it be from the ISP router configurations that I have to change?
You tell us (the details) and we'll tell you ^^
