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 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.
I made it. For other folks experiencing the same issue, please find the steps I had to perform below:
Verify whether you are running QMI or DIP. You need to have DIP.
If it shows /dev/cuau1, then you're in QMI mode; if it's /dec/cuaU1, then you're in DIP mode.
There is a switching Windows utility from Sierra, google for "BZ31018_DIP_QMI_ModeSwitch.zip".
If you prefer to verify on Windows, install Sierra MC drivers, find MC7710 in the device manager and look for the USB PID in details. 68A2 = QMI
68A3 = DIP
Upgrade your device firmware. I did on Windows. Go to Sierra Website and look for the latest firmware in an exe file. Note: Run it as administrator. (I used 126.96.36.199 btw.) https://source.sierrawireless.com/resources/airprime/software/mc7710-swi9200x_03,-d-,05,-d-,29,-d-,03_dip/#sthash.2BUNVsJm.dpbs
You may verify your card with the Sierra Windows Tool to make sure, hardware is all ok https://source.sierrawireless.com/resources/airprime/development_kits/airprime-mc-series-connection-manager-dip-build-3830/#sthash.qUh6avRG.dpbs
The Windows Store App did not work for me.
Put your card back into your APU and connect pigtail.
Add PPP interface using GUI, but use /dev/cuaU3.0. /dev/cuaU1.0 did not work for me.
Reboot. My APU automatically received a WAN IP, no additional config needed. Well, I had to plug my antenna, which I noticed quite well ;-)
By the way, this is a thread duplicate to: https://forum.netgate.com/topic/125081/pc-engines-alix-6f2-mc7710-issue-2-3-5-release-p1-i386/4
While true you can take any old soho wifi router and just use its AP features... soho wifi routers, include a routing function, switch ports and a AP in 1 box..
The switch is dumb, and therefor almost always the AP is dumb.. Or atleast configured that way via the native firmware. Other then allowing "guest" ssid that is not bridged to the switch ports.
While the hardware quite often, but not always does support doing vlans. I have never seen the native firmware leverage them for anything other than maybe the "guest" network most of them allow you to create, which really is just not bridged to the switch ports vlan.
Normally they do actual use vlans, this is how they isolate the wan and the lan. But the interface doesn't allow the user to change or manipulate them really in any way.
So simple way to just use them as a dumb AP is just turn off dhcp on them, and connect them to your network via one of the lan ports. Now anything on wifi (not guest ssid) is bridged to your switch ports = AP..
So if you want to actual do vlans, either put 3rd party firmware on the device to expose way to configure the vlans. Or get an actual AP, then yes normally would support vlans..
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.