@peter-5 said in Wifi not working PFSense on APU4D4 and WLE900VX: Any suggestion would be very much appreciated. pfSense: WLE200nx Apple AR5BXB112 SparkLan WPEA-127N OpenWRT: WLE600vx WLE900vx Intel 200/210 (only 2,4 GHz band in AP mode) RouterOS: APU2D4 (RealTek NICs) or APU2E4 (Intel NICs) Mirkotik R11e-5HnD 5.8ghz QCA9880 Mikrotik R11e-2HPnD 2.4ghz AR9582

Hmm, hard to say. You might swapping the ix and bce/bge NICs to see if the errors follow them. That might not be possible with the media types you have.

Yup, FreeBSD doesn't seem to know about that device: https://github.com/pfsense/FreeBSD-src/blob/devel-main/sys/dev/usb/usbdevs#L3459

Need to add a resistor: https://www.parkytowers.me.uk/thin/hp/hp_psu.shtml

Indeed it depends on the hardware. Many devices have a SIM slot that's wired to the miniPCIe/m.2 connected to provide that. The Netgate 2100, 3100, 6100 do. As well as many older devices. Steve

I want one for my SG-2100 a nice little GPS for perfect time keeping

Well if you just pulled the power that is the time both things would be likely to happen. Or perhaps at power up in the case of a drive sensor. But it's not that surprising both things could happen across one power cycle.

cool thanks to all it works

OK, until today I got it working. A miniPCIe card with U-blox LEA6-T chipset, for ~12 € at eBay.de together with an miniCPIe to USB adapter and a active GPS antenna plus an extra connection cable from the card to the antenna. All was done and working in 45 minutes ou of the box! [23.01-RELEASE][root@Dockmaster.Heimnetz]/root: ntpq ntpq> pe remote refid st t when poll reach delay offset jitter ============================================================================== GPS_NMEA(0) .GPS. 0 l 1564 64 0 0.000 -402.18 0.000 *GPS_NMEA(0) .GPST. 0 s 11 64 377 0.000 +13.282 2.877 [23.01-RELEASE][root@Dockmaster.Heimnetz]/root: cu -s 9600 -l /dev/cuaU1 Connected $GPRMC,220237.00,A,5225.50813,N,00928.42376,E,0.923,,200223,,,A*77 $GPGGA,220237.00,5225.50813,N,00928.42376,E,1,04,3.87,47.0,M,46.0,M,,*6B $GPGLL,5225.50813,N,00928.42376,E,220237.00,A,A*67 $GPZDA,220237.00,20,02,2023,00,00*63 $GPRMC,220238.00,A,5225.50766,N,00928.42412,E,0.941,,200223,,,A*74 $GPGGA,220238.00,5225.50766,N,00928.42412,E,1,04,3.87,47.0,M,46.0,M,,*6C $GPGLL,5225.50766,N,00928.42412,E,220238.00,A,A*60 $GPZDA,220238.00,20,02,2023,00,00*6C $GPRMC,220239.00,A,5225.50784,N,00928.42448,E,0.617,,200223,,,A*7A $GPGGA,220239.00,5225.50784,N,00928.42448,E,1,04,3.87,47.0,M,46.0,M,,*6E $GPGLL,5225.50784,N,00928.42448,E,220239.00,A,A*62 $GPZDA,220239.00,20,02,2023,00,00*6D $GPRMC,220240.00,A,5225.50754,N,00928.42476,E,0.775,,200223,,,A*71 $GPGGA,220240.00,5225.50754,N,00928.42476,E,1,04,3.88,47.0,M,46.0,M,,*6F $GPGLL,5225.50754,N,00928.42476,E,220240.00,A,A*6C $GPZDA,220240.00,20,02,2023,00,00*63 $GPRMC,220241.00,A,5225.50733,N,00928.42503,E,0.863,,200223,,,A*7A $GPGGA,220241.00,5225.50733,N,00928.42503,E,1,04,3.88,47.0,M,46.0,M,,*6C $GPGLL,5225.50733,N,00928.42503,E,220241.00,A,A*6F $GPZDA,220241.00,20,02,2023,00,00*62 $GPRMC,220242.00,A,5225.50733,N,00928.42507,E,0.905,,200223,,,A*7C $GPGGA,220242.00,5225.50733,N,00928.42507,E,1,04,3.89,47.0,M,46.0,M,,*6A $GPGLL,5225.50733,N,00928.42507,E,220242.00,A,A*68 $GPZDA,220242.00,20,02,2023,00,00*61 $GPRMC,220243.00,A,5225.50756,N,00928.42473,E,0.820,,200223,,,A*7A $GPGGA,220243.00,5225.50756,N,00928.42473,E,1,04,3.89,47.0,M,46.0,M,,*6A $GPGLL,5225.50756,N,00928.42473,E,220243.00,A,A*68 $GPZDA,220243.00,20,02,2023,00,00*60 $GPRMC,220244.00,A,5225.50759,N,00928.42473,E,0.785,,200223,,,A*72 $GPGGA,220244.00,5225.50759,N,00928.42473,E,1,04,3.89,47.0,M,46.0,M,,*62 $GPGLL,5225.50759,N,00928.42473,E,220244.00,A,A*60 $GPZDA,220244.00,20,02,2023,00,00*67 $GPRMC,220245.00,A,5225.50760,N,00928.42450,E,0.504,,200223,,,A*73 $GPGGA,220245.00,5225.50760,N,00928.42450,E,1,04,3.90,47.0,M,46.0,M,,*60 $GPGLL,5225.50760,N,00928.42450,E,220245.00,A,A*6A $GPZDA,220245.00,20,02,2023,00,00*66 $GPRMC,220246.00,A,5225.50779,N,00928.42443,E,0.451,,200223,,,A*7B $GPGGA,220246.00,5225.50779,N,00928.42443,E,1,04,3.90,47.0,M,46.0,M,,*69 $GPGLL,5225.50779,N,00928.42443,E,220246.00,A,A*63 $GPZDA,220246.00,20,02,2023,00,00*65 $GPRMC,220247.00,A,5225.50733,N,00928.42446,E,0.485,,200223,,,A*78 $GPGGA,220247.00,5225.50733,N,00928.42446,E,1,04,3.90,47.0,M,46.0,M,,*63 $GPGLL,5225.50733,N,00928.42446,E,220247.00,A,A*69 $GPZDA,220247.00,20,02,2023,00,00*64 MiniPCIe card ~12 € Antenna ~9 € Internal Connection cable ~8 € USB to miniCPIe adapter for WWAN cards for ~11 € Together with the shipping fee all in all for around 50 € You must install first over the USB to miniCPIe adapter on an Windows PC and configure the card according and matching your needs, LEA-6S is not sorted with an ability to flash, it has only a rom, you must store the config on the PC and reload it onto the rom and save then all is fine. This can be done with the Ublox software for free from U-blox companies website After this inserting it in pfSense choose NTP > GPS and wait several hours. Done. Mostly it uses 4 - 6 or seldom 4 - 8 satellites. Here are some pictures from this setup. [image: 1676930718996-gps2-resized.jpg] [image: 1676930728664-gps3_2-resized.jpg] [image: 1676930744218-gps4_2-resized.jpg] [image: 1676930754260-pfsense2.jpg]

Hmm, curious. Maybe some fixes in some underlying driver removing whatever was preventing it being seen. There wasn't anything that would do that explicitly I'm aware of.

I wouldn't expect there to be any. No different in 2.7 either. I could just about imagine a floating block all rule might apply to localhost. But probably not from localhost also. I've never tried to block that!

What exactly is the module? The SFP port in the 2100 is fixed at 1G and does not provide interaction with the module inserted to the chipset. So there is almost no configuration, it works or it doesn't. Steve

I changed the heatsink compound and swapped the unit into production. It is sitting at 29-31deg now in my basement and is stable. I have left "Turbo" off, as I don't think it is needed or helpful on a passive cooled system. FYI - anyone with the same unit. the igb7 and igb6 are reversed, so it is igb0, 1, 2, 3, 4, 5, 7, 6

@admins Here's a good list of NICs and their OEM equivalents. https://forums.servethehome.com/index.php?threads/list-of-nics-and-their-equivalent-oem-parts.20974/ i340 and i350 chipsets are relatively current and inexpensive.

@provels Well imho WiFi doesn't belong on a pfSense ... (well firewall) So now you're logging to the internal 500GB ?? I'm syslogging to a remote Linux Syslog server , always liked that best. You have a neat system now ... /Bingo

I've not tried to set any values. The default values work well for me on the APU.

@stephenw10 Yes.

Yeah, you don't need a serial port. A USB connected com device is built into the SG-1100. Just connect to it with a standard USB to USB micro cable and you should see the new virtual com port device detected. Steve

@xt_ntwrk said in Sierra Wireless MC8805/DW5570 not working: @ctrlzundo Thanks for the remark. I saw that in some datasheet before. What i was not 100% aware of is that most (if not all) providers in Germany killed already the UMTS frequencies... Do you have any other LTE or 5G card which you can recommend; which works fine with pfSense and is for mini-pci port? I am using a Sierra Wireless MC7710 here in Germany with T-Mobile

@ph0ton said in Improving power consumption on Nuc 11 pro: I have never come a across a machine in the past 15 years how had problems with C-states, unless it was related to instabilities in the BIOS / UEFI bios. I have now reactivate (because I cannot exclude that maybe something else has caused the shutdowns - at that time I made also some changes regarding the USB-Ports and the update from 2.5.2 -> 2.6.0) the setting: hw.acpi.cpu.cx_lowest=C3 (it sets automatic the dev.cpu.0/1.cx_lowest to C3) and I keep a eye on it and will give feedback if something happends ... Result: dev.cpu.0.cx_usage: 30.82% 69.17% 0.00% last 637us dev.cpu.1.cx_usage: 59.30% 13.53% 27.15% last 267us Interesting: dev.cpu.0 never go to C3 Edit 09.05.23: After rebooting the system dev.cpu.0 is going also to C3: dev.cpu.0.cx_usage: 62.51% 7.06% 30.42% last 1250us Regards, fireodo