PfSense is unreachable after install

mathomas3

When I have been doing these freebsd 'tests' they have been using the minimal(small) usb image which requires an internet connection to download extra data to finish the install... I have been using this to test the different versions(downloads are slow) so basically I have been booting to usb installer and testing ping and what not...

Feels strange that the usb hotspot works well vs an intel NIC... -_-

stephenw10

Try: ifconfig em0 -txcsum -rxcsum

You're not using VLANs at all there from what I can see?

Whilst I have a lot of hardware (too much? ) I don't have anything that has an i217-lm NIC. Though I agree, if it was broken in general we'd be flooded with threads! So that implies there is something specific about this implementation of it that the FreeBSD driver has an issue with. Which is what made me suspect they might have used some odd PHY there.

mathomas3

@stephenw10 said in PfSense is unreachable after install:

Try: ifconfig em0 -txcsum -rxcsum

You're not using VLANs at all there from what I can see?

Whilst I have a lot of hardware (too much? ) I don't have anything that has an i217-lm NIC. Though I agree, if it was broken in general we'd be flooded with threads! So that implies there is something specific about this implementation of it that the FreeBSD driver has an issue with. Which is what made me suspect they might have used some odd PHY there.

I tried the command above without rebooting from the previous command that I mentioned... and still nothing... I tried to ping out and in on the private IP space... I am able to ping out via the internet though(through the usb hotspot... I know not really helping here but I had to have some POSITIVE result to say here)

A bonus of the internet access is that it will make it easier to build a new driver if needed... thoughts?

mathomas3

@stephenw10 I have read the instructions from intel and they seem pretty straight forward... If I were to follow though with them, I understand that any update to the OS would break things and also some functionality would break the drive via the web interface... beyond this are there concerns should I try this?

I know this would be a workaround vs solving the problem, but my existing system is failing(restarted the OldBox 5x friday, I suspect that the usb hotspot is drawing too much power and overheating the chip on this fanless system) thus having a stable workaround is favorable vs a dying one

mathomas3

I tried to follow the instructions for the driver install and when I issued the command to 'make' I the error 'unable to locate the kernal source tree"

Thoughts?

mathomas3

@stephenw10 As it would seem... This happens to be a card that has defeated you before :(

https://forum.netgate.com/topic/159452/gui-wont-show-nic-card-interfaces/3

and after doing some reading it would seem that building a driver for this OS is ill advised...

Rock>>ME<<Rock

johnpoz

@mathomas3 said in PfSense is unreachable after install:

command to 'make' I the error 'unable to locate the kernal source tree"

pfsense is not going to have the stuff to compile, you would need to compile the driver on a freebsd install that has the stuff installed for doing such stuff. I did this many years ago for the dhcp client that had a problem with setting the ttl too low.. It took freebsd like 2 years to actually fix the problem.

But once you build the driver, you should move it to your pfsense.

Simpler solution might be to just get a different nic.. Can you not swap out the nic in that system with a different one?

Remember pfsense runs on freebsd as its base layer OS. It doesn't come with all the bells and whistles that can be installed on the actual freebsd, ie the builder tools needed to compile stuff. While it is possible to do cross compiling on another OS.. if you want to try and build the driver from intel and see if that works - I would install a freebsd v14 current, or you could try with the 12.3 version if your goal is running it on 2.6, then move your driver to pfsense.

stephenw10

@mathomas3 said in PfSense is unreachable after install:

https://forum.netgate.com/topic/159452/gui-wont-show-nic-card-interfaces/3

That's not the same failure mode though. The i217-lm NIC was working OK there it was the other addition NIC they added that was not seen at all.

One thing you can try here is using Intels non-iflib kmod driver pkg. At the command line in 2.6 run:

pkg-static add https://pkg.freebsd.org/FreeBSD:12:amd64/release_4/All/intel-em-kmod-7.7.8.pkg

Then:

echo 'if_em_updated_load="YES"' >> /boot/loader.conf.local

Then reboot.
Obviously you will need the usb modem connected to do that so you are able to fetch the package.

The only thing I'm aware of that addresses is the mishandling of vlan0 tags which doesn't apply here. But it's worth trying.

Steve

mathomas3

@stephenw10 said in PfSense is unreachable after install:

@mathomas3 said in PfSense is unreachable after install:

https://forum.netgate.com/topic/159452/gui-wont-show-nic-card-interfaces/3

That's not the same failure mode though. The i217-lm NIC was working OK there it was the other addition NIC they added that was not seen at all.

One thing you can try here is using Intels non-iflib kmod driver pkg. At the command line in 2.6 run:
pkg-static add https://pkg.freebsd.org/FreeBSD:12:amd64/release_4/All/intel-em-kmod-7.7.8.pkg
Then:
echo 'if_em_updated_load="YES"' >> /boot/loader.conf.local
Then reboot.
Obviously you will need the usb modem connected to do that so you are able to fetch the package.

The only thing I'm aware of that addresses is the mishandling of vlan0 tags which doesn't apply here. But it's worth trying.

Steve

I followed the commands as suggested and everything seemed to go well... but there is no change...

Might I ask how VLANs was a thought as to why things were going wrong?

mathomas3

I went ahead and sent the unit back... I ordered something older then this one... hope that it works... and that the NIC is a gig port -_- FML

stephenw10

@mathomas3 said in PfSense is unreachable after install:

Might I ask how VLANs was a thought as to why things were going wrong?

It wasn't. You had disabled the hardware VLAN filtering and I was just checking you weren't using VLANs.

mathomas3

The replacement for the NewBox works flawlessly... Guess we are tossing this one up to the who done it gods -_-