PfSense does not support more than 10 3G modems connected
-
But why??
-
Only 10 USB modems? Oh noes, unusable!!! We are all doomed!!!
-
What does the 11th one do? System log, PPP log, anything else relevant you're seeing.
-
I am interested in this topic.
Where is this failing? On creating the 11th PPP interface or when adding the 11th PPP interface to OPT interfaces?
-
3G modems used: Huawei E1550
I don't see any errors on General/PPP log. The modem is detected normally just like the rest of the 10 3G modems. The only problem is on PPPs Configuration>Link Interfaces. The 11th link interface does not appear. Attached is a photo of PPPs configuration.
General log upon inserting the 11th modem
Jul 14 17:45:59 kernel: ugen8.6: <vendor 0x1a40=""> at usbus8 Jul 14 17:45:59 kernel: uhub20: <vendor 6="" 9="" 0x1a40="" usb="" 2.0="" hub,="" class="" 0,="" rev="" 2.00="" 1.11,="" addr=""> on usbus8 Jul 14 17:46:00 kernel: uhub20: 4 ports with 4 removable, self powered Jul 14 17:46:05 kernel: ugen8.7: <huawei technology=""> at usbus8 Jul 14 17:46:05 kernel: ugen8.7: <huawei technology=""> at usbus8 (disconnected) Jul 14 17:46:08 check_reload_status: updating dyndns WAN9_PPP Jul 14 17:46:08 check_reload_status: Restarting ipsec tunnels Jul 14 17:46:08 check_reload_status: Restarting OpenVPN tunnels/interfaces Jul 14 17:46:08 check_reload_status: Reloading filter Jul 14 17:46:11 php: rc.dyndns.update: MONITOR: WAN7_PPP is down, removing from routing group ADDEDWAN Jul 14 17:46:11 php: rc.filter_configure_sync: MONITOR: WAN7_PPP is down, removing from routing group ADDEDWAN Jul 14 17:46:13 kernel: ugen8.7: <huawei technology=""> at usbus8 Jul 14 17:46:13 kernel: u3g10: <huawei 0="" 7="" technology="" huawei="" mobile,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr=""> on usbus8 Jul 14 17:46:13 kernel: u3g10: Found 3 ports. Jul 14 17:46:13 kernel: umass20: <huawei 0="" 7="" technology="" huawei="" mobile,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr=""> on usbus8 Jul 14 17:46:13 kernel: umass20: SCSI over Bulk-Only; quirks = 0x0000 Jul 14 17:46:13 kernel: umass20:20:20:-1: Attached to scbus20 Jul 14 17:46:13 kernel: umass21: <huawei 0="" 7="" technology="" huawei="" mobile,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr=""> on usbus8 Jul 14 17:46:13 kernel: umass21: SCSI over Bulk-Only; quirks = 0x0000 Jul 14 17:46:13 kernel: umass21:21:21:-1: Attached to scbus21 Jul 14 17:46:13 kernel: (probe0:umass-sim20:20:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 Jul 14 17:46:13 kernel: (probe0:umass-sim20:20:0:0): CAM status: SCSI Status Error Jul 14 17:46:13 kernel: (probe0:umass-sim20:20:0:0): SCSI status: Check Condition Jul 14 17:46:13 kernel: (probe0:umass-sim20:20:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) Jul 14 17:46:13 kernel: (probe1:umass-sim21:21:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 Jul 14 17:46:13 kernel: (probe1:umass-sim21:21:0:0): CAM status: SCSI Status Error Jul 14 17:46:13 kernel: (probe1:umass-sim21:21:0:0): SCSI status: Check Condition Jul 14 17:46:13 kernel: (probe1:umass-sim21:21:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) Jul 14 17:46:13 kernel: cd10 at umass-sim20 bus 20 scbus20 target 0 lun 0 Jul 14 17:46:13 kernel: cd10: <huawei mass="" storage="" 2.31=""> Removable CD-ROM SCSI-2 device Jul 14 17:46:13 kernel: cd10: 40.000MB/s transfers Jul 14 17:46:13 kernel: cd10: Attempt to query device size failed: NOT READY, Medium not present Jul 14 17:46:13 kernel: da10 at umass-sim21 bus 21 scbus21 target 0 lun 0 Jul 14 17:46:13 kernel: da10: <huawei mmc="" storage="" 2.31=""> Removable Direct Access SCSI-2 device Jul 14 17:46:13 kernel: da10: 40.000MB/s transfers Jul 14 17:46:13 kernel: da10: Attempt to query device size failed: NOT READY, Medium not present</huawei></huawei></huawei></huawei></huawei></huawei></huawei></huawei></vendor></vendor>
-
could you post the result of this:
ls -alh /dev/cua*
try this with and without the 10th dongle in place…. this would atleast show if the "dailer-device' gets added to the system
-
I expect the problem is in /usr/local/www/interfaces_ppps_edit.php
https://github.com/pfsense/pfsense/pull/1752
That pull request is against master, but you can try to see if it fixes it by:
Diagnostics->Edit file
/usr/local/www/interfaces_ppps_edit.php and Load
Search for "glob"
The glob expresion "/dev/cua?[0-9]{,.[0-9]}" - remove the dot so it is just "/dev/cua?[0-9]{,[0-9]}"
SaveThat should allow cuau0 cuau1 cuau2 … cuau10 cuau11 ... cuau99 devices to be matched. Then you can have 100 3G modems :)
Edit add: RedMine bug created for tracking purposes: https://redmine.pfsense.org/issues/4836
-
Thanks Phil. Merged that to master and RELENG_2_2.
rowell: next 2.2.4 snapshot @ https://snapshots.pfsense.org past the date of this post (probably the first with a July 15th date) will have that fix, please test and report back.
Now how long until someone comes and posts they can't use more than 100 3G modems? :) I'd say 100 is more than enough.
-
PfSense Swat Team in Action!!! Good job all. Fixed and commited in one day. That is some kind of awesome.
-
@Phishfry:
PfSense Swat Team in Action!!! Good job all. Fixed and commited in one day. That is some kind of awesome.
We will see - it just occurred to me that the change I made will now not match device names like /dev/cuau1.1 - which it would have matched before. I made a comment on the commit and @cmb and @jimp will know if device names in that format actually exist and need matching.
-
The finalised version of this was committed a few days ago.
@rowell - can you try https://github.com/pfsense/pfsense/blob/RELENG_2_2/usr/local/www/interfaces_ppps_edit.php (that is the version to be released in 2.2.4)
Does that fix the issue?