WAN is OK, but pfsense gives no network to PCs connected to it
-
This is a problem I've had off-on for a couple of years.
All is well then no PCs get internet connection. If I play with the various cable swaps and rebooting try's, I have been able to get the PCs back online after many hours of "play". I get frustrated trying to make things work, so this time I decided to see if I can get help.I know my modem connection works, I moved this PC from a port on my Unifi USW 24 Switch to a port on the AT&T Fiber Modem and I'm getting out on the internet OK.
I can move the LAN port from my pfsense router over to a port on the AT&T Fiber Modem and get out on the internet with all devices except ones that are configured as IoT devices in the Unifi OS. That makes sense to me.
If I connect a PC to the LAN port directly on the pfsense router, I get nothing. I tried connecting a small basic switch to the LAN port as well, but nothing I connect to the switch gets an internet connection.
Any ideas what else I can try?
Thanks!
-
Sorry. As I was reading my post, I realized I mentioned the IoT devices not being able to get on the internet. Those are on a VLAN that is configured in pfsense.
-
One other test I did was to switch the dual port NIC card with another (new) card of the same make/model. The results didn't change, so I feel that the issue is not a bad NIC.
-
Is the WAN on your pfsense getting a public IP address or are you double NAT'd?
If you look at the Services option on the Status Tab does everything have green check marks?
Can you "ping" anything from your pfsense box when this happens?
-
@chpalmer
I did get a public IP
What application are you using to get the screen shot you showed me? -
I'm pretty sure you're in pfsense. I don't know how to connect to that pc to get into pfsense.
-
@BEAR9861114 said in WAN is OK, but pfsense gives no network to PCs connected to it:
What application are you using to get the screen shot you showed me?
I just hit the "print screen" key then paste to my choice of photo editor.. in my case paint.net
Save as whatever file type and name. Easy Peasy.
-
Sorry. I think you're running pfsense on the router. I need to connect to the router, but I don't know how. I get no response when I connect a PC to the LAN port on the pfsense router.
The pfsense router is plugged into the Fiber Modem, as well as this PC I'm using to get on the internet. I tried to get to the pfSense router by doing a ping 192.168.1.1 from this PC, since they both are plugged into the modem, I thought that would work, but it doesn't.
-
@BEAR9861114 said in WAN is OK, but pfsense gives no network to PCs connected to it:
Sorry. I think you're running pfsense on the router. I need to connect to the router, but I don't know how. I get no response when I connect a PC to the LAN port on the pfsense router.
The pfsense router is plugged into the Fiber Modem, as well as this PC I'm using to get on the internet. I tried to get to the pfSense router by doing a ping 192.168.1.1 from this PC, since they both are plugged into the modem, I thought that would work, but it doesn't.
If you are connected to the LAN of the pfsense router then you would use the LAN address.. that is true.. But are you sure it is 192.168.1.1? What do you get if you bring up a command window on your PC and do an IPCONFIG /all ?
Unless you have opened up a firewall rule on your WAN you cannot access the pfsense from the WAN side. You cannot use the LAN address from the WAN side.
-
@chpalmer
When I plug a PC into the LAN port of the pfsense router and run IPCONFIG /all
It shows my PC address is 192.168.1.213 (this is the PC I plugged into the LAN port on the pfsense router)
It shows the default gateway is 192.168.1.1
It shows the DHCP server is 192.168.1.1 -
Also, I tried to ping the default gateway IP and it times out
-
@chpalmer
Thank you for your time!We are keeping our grand kids and I need to stop working this problem and go spend some time with them before bedtime.
I appreciate your looking at this. I'll have to look more into it tomorrow.
Thanks, Barry
-
@BEAR9861114 said in WAN is OK, but pfsense gives no network to PCs connected to it:
It shows my PC address is 192.168.1.213 (this is the PC I plugged into the LAN port on the pfsense router)
It shows the default gateway is 192.168.1.1
It shows the DHCP server is 192.168.1.1That looks fine.
I presume that you've set up your pfSense (port) like this :
which is the Netgate default pfSense LAN setup.
One very important info is missing : DNS. It should be 192.168.1.1 (== pfSense) also.
Anyway, your PC obtained a valid 192.168.1.213 DHCP from pfSense, that's a good sign.
If your pfSense LAN interface has the default 'Netgate pfSense' firewall rules, a generic IPv4 and IPv6 pass rule, you should be good.
Can you take a pencil and post-it ?
Write this down : "When you suspect network interface issues, use the pfSense most important interface right away : the console access".The very first console 'menu' shows important info :
The golden rule is : the LAN is set to static 192.168.1.1/24 so the WAN, set to DHCP mode (default also) shouldn't be 192.168.1.1/24, but something else. I use 192.168.10.1/24.
Next thing to test :
Your pfSense is a router, and as such it has at least two NICs. One is defined as 'WAN', the other one as 'LAN'. Make sure you didn't mix up these two.
If your pfSense box has more then two NICs, make sure you didn't make them up neither.You use VLANs and you've said :
@BEAR9861114 said in WAN is OK, but pfsense gives no network to PCs connected to it:
Those are on a VLAN that is configured in pfsense.
but devices normally should have VLAN setup info.
One one side, pfSense has to be set up to use VLAN(s) on one (ore more) pfSense LAN type interfaces. The other side of this pfSense interface should have a VLAN capable switch that matches the VLAN setup on pfSense.
When you suspect interface issues, drop the VLAN stuff everywhere, use a bare bone L2 switch and the pfSense LAN, hook up your PC also to this switch and you'll be fine. -
You should always be able to ping 192.168.1.1 from the client device at 192.168.1.213. So it that's failing it's something low level.
After you regained access by whatever means check the logs to see what pfSense thought was happening at the time.
Otherwise try some tests from the console dircetly. Try to ping out to the client device.
-
@stephenw10 and others...
As has happened in the past, when I came back to spend more time on this issue this morning, everything started working as expected.
I plugged a PC into the LAN port on the router and immediately got in to the router! I was able to get into pfSense and look around. The only thing that had a red mark when I looked at Status Services was on the line with SNORT. It was saying I needed to do an update. Everything else was green. I removed the SNORT package.
I plugged the router back into my USW24 switch and all APs, and other connected devices came back online working as expected.
I did notice that when I plugged the WAN cable from the AT&T Modem into the router, I didn't get a link light, so I changed that cable and tried again. It still wasn't getting a link light. I did a very deliberate "reset" of the plug and then I got a link light. It may be a flakey connector on the card. I will investigate that once things run for awhile.
As I understand it, my license for Plus is tied to that card, so I don't want to change it, unless that's my real problem!
As I was laying in bed last night, I was thinking of my next steps. One idea I had was to build pfSense on a different PC with totally different parts. I think to do that I have to use the Community Edition for the build and then ask Netgate to give me a code to switch to the Plus Version again.
Thoughts on that idea?
I appreciate the help given to me. I will review the info that came in later last night and see if I can use it to make more sense of this problem. I feel certain it will pop back up (this was the 3td time in 2 years!).
MANY Thanks to the 3 of you that took the time to help!!!
Barry -
Do you have Snort running in blocking mode? Always a chance it could have blocked your client IP if so. And in that situation it will expire the block after some time (unless set to never expire).
That should exist in the Snort logs if it happened though.
-
@stephenw10
I looked in the System (and all the others) Logs files. I saw where Snort was removed and there were a few other mentions of it getting updated. I didn't see anything that stood out as an issue.
I guess since I removed that package last night, if there was a Log File for Snort, it's gone.Thank you!
Privacy Policy · Cookie Policy