PfSense is unreachable after install
-
This post is deleted! -
@mathomas3 said in PfSense is unreachable after install:
version of pfsense and set up the WAN interface(ethernet port) with an IP
You seem to have a really hard time following simple instructions.. Where did I say setup a WAN interface with an IP?
What I wanted to accomplish was ruling out you changing the default IP of pfsense lan which is 192.168.1.1...
So what your saying is the freebsd driver for this nic is not working, while the linux version is - even though the interface shows that is up, has an IP, etc.. Which seems unlikely set of circumstances to be honest.
So vs installing linux, how about installing freebsd. Or using the usb interface as you lan interface - because this seems to come up and get an IP from your old boxes dhcp, etc.
-
@johnpoz said in PfSense is unreachable after install:
@mathomas3 said in PfSense is unreachable after install:
version of pfsense and set up the WAN interface(ethernet port) with an IP
You seem to have a really hard time following simple instructions.. Where did I say setup a WAN interface with an IP?
Gee... Thanks for that -_-But to be sure I reinstalled the OS and did EXACTLY like you said... and still nothing
the USB connection goes directly to a USBc hotspot... there is no USB to cat5 connection
I guess Ill try bsd and see what happens...
-
And the reason that I setup the WAN interface is because it was suggested before and I have tried everything else that has been suggested multiple times... I find it hard to believe that it's user error given my experience, and knowledge to include the number of different ways that I have tried to set this up
-
So vs installing linux, how about installing freebsd. Or using the usb interface as you lan interface - because this seems to come up and get an IP from your old boxes dhcp, etc.
I just installed FreeBSD on the box and it pulled an IP and I was able to ping the OldBox.
-
@mathomas3 said in PfSense is unreachable after install:
I just installed FreeBSD on the box
FreeBSD 12?
Ryan
Repeat, after me: MESH IS THE DEVIL! MESH IS THE DEVIL!
Requesting firmware for your Netgate device? https://go.netgate.com
Switching: Mikrotik, Netgear, Extreme
Wireless: Aruba, Ubiquiti -
@rcoleman-netgate said in PfSense is unreachable after install:
FreeBSD 12?
good question... 2.6 is 12.3, while 2.7 is 14... So try installing the the 2.7 snapshot..
Just seems like a crazy set of circumstances that whatever this nic is in some off brand china box... Never heard of G-PRO COMPUTER which is what comes up for that 00:23:24 mac address. And the nic is being identified as a I217 Intel?
So whatever driver is being used em, I would think igb would be what would come up for a i217? But I am not really a driver guy.. @stephenw10 is the driver/hardware guy around here - if anyone would know it would be him..
-
@rcoleman-netgate said in PfSense is unreachable after install:
@mathomas3 said in PfSense is unreachable after install:
I just installed FreeBSD on the box
FreeBSD 12?
I am downloading that now... The one that I first used was version 13.2
-
@johnpoz said in PfSense is unreachable after install:
@rcoleman-netgate said in PfSense is unreachable after install:
FreeBSD 12?
good question... 2.6 is 12.3, while 2.7 is 14... So try installing the the 2.7 snapshot..
Just seems like a crazy set of circumstances that whatever this nic is in some off brand china box... Never heard of G-PRO COMPUTER which is what comes up for that 00:23:24 mac address. And the nic is being identified as a I217 Intel?
So whatever driver is being used em, I would think igb would be what would come up for a i217? But I am not really a driver guy.. @stephenw10 is the driver/hardware guy around here - if anyone would know it would be him..
This machine is a Lenovo ThinkCentre M93P
And yes that NIC is a intel I217-LM
Unfortunately I did try the 2.7 Development snapshot yesterday the 20230215 build and with minimal testing, it didnt look hopeful
-
@mathomas3 said in PfSense is unreachable after install:
I am downloading that now... The one that I first used was version 13.2
If 13 didn't work 12 probably won't. As noted by @johnpoz 2.7-DEV (and 23.01-RELEASE) is 14.
-
I just got done with testing...
FreeBSD
v13 works... It pulls an IP and can ping the OldBox
v12 Doesnt work. Failed to pull an IP and after manually setting one it failed to ping OldBoxIll try the PfSense Dev build one more time. I didnt give it a fair chance I think
-
@mathomas3 if v13 of freebsd works, I would have to believe 2.7 would work since that is v14 of freebsd.. if the 2.7 doesn't work but freebsd 14 works then yeah time to get into the weeds on what could be going on - I would assume 2.7 would be using the same driver that comes with v14..
But when it comes to getting into the weeds with drivers Steve would be my go to guy that is for sure.
-
@johnpoz I just did a straight forward install of dev. I didnt change any IPs and just assigned the WAN and LAN. and connected this directly to a PC with an IP of 192.168.1.2. Tried to ping and checked the arp table. Nothing... Ill keep on looking into what I can find
-
@mathomas3 so did you try install freebsd 14 - does that work?
-
@johnpoz I just tried that and no it did not. Never pulled dhcp
-
@mathomas3 so v13 of freebsd works but v14 does not - so what could of changed in the driver?? And 12 doesn't work either that would explain why 2.6 or 2.7 doesn't work - but yeah this seems to need @stephenw10 expertise.
-
@johnpoz I went back and double checked everything on v13 and I couldnt replicate the same result... perhaps in my haste it was pinging itself but then again I check the ARP table and it was there(logs from earlier) so...
I did try and research this on other forums and there isnt much out there... but according to this https://bsd-hardware.info/?id=pci:8086-153a-1028-05cc it should so I dont know what to think
-
Mmm, I'm not aware of anything that behaves anything like this. Let alone something that is recognised as em which should be well understood and supported at this point.
The other thing we saw here was that the em NIC does still show the link status correctly even though it does not pull an IP or show any layer 2 connectivity. So that seems unlikely to be some weird unsupported PHY. Or somehow not the correct port.
So, some regression in FreeBSD edge? I see nothing listed.
I would try disabling hardware checksum off-loading on em0 just in case. Nothing else set there looks likely.
-
@stephenw10 what doesn't make any sense to me is that if there was a freebsd or pfsense even thing with I217 - wouldn't forums be a fire with complaints? I mean that is not an uncommon off brand nic.. But looking at the freebsd listing for em.. It doesn't specifically list the 217 only the 210 and 211
o Intel i210 and i211 Gigabit Ethernet Controller o Intel i350 and i354 Gigabit Ethernet ControllerYou have a pretty extensive lab from previous discussions, you don't have a I217 to test with?
Here is intel drivers for freebsd, would it be possible to try and load those?
It specifically calls out the I217-LM is that what is being detected?
-
@stephenw10 I tried the following in shell on a fresh install... ifconfig em0 -vlanhwfilter -vlanhwtso and tried to ping the OldBox and didnt get any response
If I did go down the road of building a new driver provided by intel... something I have done before but on systems that had network connectivity... how would I proceed? from the console I havent accessed/mounted a USB before
This feels like a simple solution should be out there... everything seems right but when it comes time to have an IP... nope -_-
