The date I've found for Norway is that 2G dies in 2025. But they've said that before, and the amount of alarm installations, oil plattform applications and other stuff has stopped the deadline for 2G before, so I'm guessing around 2030. And 4G I'm expecting to have longer than my car. I like to keep new cars that I buy for at least five, preferably ten years, and with this Mercedes EQC I can't see myself needing anything else as long as the battery lasts. The warranty is 8 years/160 000 km (100 000 miles), so that's probably when I start looking for something else. By then I'm sure the cars are flying drones!

@stephenw10 let me retest and Ill post back... I left it a bit on the side as I had a pile of work. Thanks!

Available wifi interfaces are shown by the sysctl: [22.01-RELEASE][root@pfSense.home.arpa]/root: sysctl -n net.wlan.devices ath0 See: https://docs.freebsd.org/en/books/handbook/advanced-networking/#network-wireless Steve

Very unlikely. The 802.11ac chipsets are markedly different to the N/G/A chips that are supported. And in fact other people have tried that and failed.: https://www.mail-archive.com/freebsd-wireless@freebsd.org/msg05524.html Steve

Yes you could use pools in one subnet and filter them differently using aliases but you can't filter traffic between the clients on one subnet that way. Traffic would just go between them directly without passing through pfSense. Only one interface. Really you need to use VLANs in there to separate the traffic at layer 2. Steve

@stephenw10 after many hours digging the internet and various tryes, found that the modem card was correctlly installed for an older firmware of the apu4d4. With the one i have the modem was detected by the pfsense but the sim card was not internally linked to that slot. After moving it to the correct pci-slot. it worked like plug&play, with the &F init string and cuau0.0. one of the good sources of info to debug the modem is https://teklager.se/en/knowledge-base/pfsense-lte-troubleshooting/ thanks for all the help

Mmm, well the best device you can get is something based on one of the older 3x3 chipsets. I have a Sparklan WPEA-127N which works well. Any equivalent AR9380 based card should also work. Still pretty bad compared to any current AP. Steve

@bugman Avoid TP-Link. Some of their gear has problems with VLANs. I have a Unifi AC-Lite AP.

It depends what you are putting it in but a later Atheros based 3x3 card is about the best you can do. So for example I have here a Sparklan WPEA-127N. It works pretty good but I still mostly use it just to test the wifi components in pfSense. Steve

You have 5 modems? They all do this? Do you see new USB ports detected when this happens? The modem itself could be rebooting and creating a new device. Steve

Moved this to a new thread since that other one was from 2015 and just attracted spam! What have you tried? What was the result? I would expect that modem to work in some mode. Steve

@canhtuongvinh said in Sierra MC7354 LTE for WAN: CHAT: The modem is not responding to "AT" The port you're using is not configured as an AT interface. Try one of the other ports. But please keep this in one thread. It might be better to start a new thread than these older ones. Steve

hi, i'm planning to buy Sierra MC7700 to my newly built pfsense 2.5.2, does this module still working properly? Thanks.

@stephenw10 Brilliant, thanks

Run pciconf -lv at the command line. How does it appear? What PCI IDs? It might already be the best card you can get that will work. Probably isn't though. Steve

This is a Proxmox topic and i'm not an expert on it. @sujan-0 said in Wireless interface not visible: I have installed pfSence successfully with 2 network interface vmbr0 and vmbr1 vmbr1 has no network adapter connected yet. If you install pfSense with to interfaces, it uses the first one for WAN, the second for LAN. However, it allows only access on LAN, but that might be connected to vmbr1 which is not connected to any network. If you only enable one interface, the GUI should be accessible on this. Or if you're running other VMs on Proxmox, you can connect to vmbr1 as well as pfSense and access the GUI from there. However, basically if your router provides DHCP, pfSense should pull an IP from it on WAN if it's connected to vmbr0. post-up iptables -t nat -A POSTROUTING -s '192.168.8.0/24' -o wlan0 -j MASQUERADE I think, there is no reason to have a masqerading rule on the wifi.