This is brilliant, very useful information. A point that I found particularly useful was about diversity, which others new to the wireless aspects of pfsense might easily be wondering also - A wireless card might have two antennas but each antenna cannot be used at the same time either transmitting or receiving (effectively doubling bandwidth contrary to one antenna) - it doesn't work like that; the two antennas are used separately and purely to create robustness where there is multipath distortion. In single antenna scenarios one should disable diversity and set the tx and rx antennas, available under the wireless configuration pages under the interface. I know I repeat what you posted (thanks again for your help in my previous post, its still working all good!) I repeat it incase others arrive at this page if searching for related issues!
Depending on the capabilities of the APs, the following flags can be included in the output:
E - Extended Service Set (ESS). Indicates that the station is part of an infrastructure network (in contrast to an IBSS/ad-hoc network).
I - IBSS/ad-hoc network. Indicates that the station is part of an ad-hoc network (in contrast to an ESS network).
P - Privacy. Data confidentiality is required for all data frames exchanged within the BSS. This means that this BSS requires the station to use cryptographic means such as WEP, TKIP or AES-CCMP to encrypt/decrypt data frames being exchanged with others.
S - Short Preamble. Indicates that the network is using short preambles (defined in 802.11b High Rate/DSSS PHY, short pre- amble utilizes a 56 bit sync field in contrast to a 128 bit field used in long preamble mode).
s - Short slot time. Indicates that the network is using a short slot time.
AID = Association ID (describes the ID that the AP has given to a certain mac/client)
IDLE = idletime
TXSEQ = Transmit Sequence
RXSEQ = Receive Sequence
ERP set to 0 means the device is 802.11 compliant. For more info about ERP read up on the 802.11 standard.
RSSI = Receive Signal Strength Indicator
RSSI to dBm can be calculated like this for Atheros cards:
RSSI_Max = 60
Convert % to RSSI
Subtract 95 from RSSI to derive dBm
Notice that this gives a dBm range of –35dBm at 100% and –95dBm at 0%.
PS. RSSI is different for most vendors. and can not be campared easily (ex. Cisco has 0 -->100 ). Also it is not a very acurate means to measure signal quality, rather it measures strengt only.
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.
My next plan is to see if I can update the bios, if that fails I might have a dead slot on the board.
As Steve say: try that card in a other MoBo (if available). If you have an other mini PCIe-Card, that you know she is working, put her in and see if the system recognize it. So you can see if the slot has a problem. The BIOS is of course a possible culprit (I dont think so).
I was not able to spot any relevant difference between the successful and unsuccessful attempt, even the assigned IP is the same. To me it seems that the issue seems to be located somewhere else than in WAN connectivity.
Upvoted some of your posts, you have a +5 rep now you should be able to post.
I have one of those modems but I don't use it because it's always been a bit flaky for me.
The modem itself sometimes gets stuck in a boot loop causing it to appear and disappear.
If you're not using the ue0 interface I would recommend trying to use an em7305 or em7455 if you can. I'm currently using an em7305 in an SG-3100 here and it's been reliable. Speed is not huge but it's a backup.
I had a similar issue: Dell 9020m with m.2 slot, but needing to use a mpcie. I picked up an Atheros 9280 card and used this adapter in mine: “M.2 (NGFF) Key A/E/A+E to Mini PCI-E Adapter with FFC Cable”
Yes, that's probably the single best supported card in pfSense currently.
It's a 2x2 N card so theoretical 300Mbps. You can get a similar generation 3x3 N Atheros card that will work and give 450Mbps (theoretical connection rate). I had one of those running for some time. I used this but anything AR9380 based should work.
The fact it's in a J1900 system is largely irrelevant.
If you've added the interface and clients can connect to it then check they are getting an IP address from dhcp correctly. If they are then you are probably missing a firewall rule or possibly an outbound NAT rule if it not in automatic mode.
Thank you for your support.
I have already implemented the delay, that is correct. Unfortunately, my problem still exists. Currently I use a workaround. I reboot the device once a night and start a reset of the modem via cron 10 minutes later. So it works - for whatever reason.....
The wifi card will not work at all. There isn't any 802.11AC support in FreeBSD/pfSense, yet, let alone .AX.
I've set an ASUS Router I had to AP mode and put it behind pfSense. My exact setup looks like this:
Provider Router - pfSense - Switch - AP. QNAP is connected to the switch and I can access it with my mobile phone.
We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.
Subscribe to our Newsletter
Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.