2.0.3 -> 2.1 manual disconnect/connect issue's with usb 3g dongle



  • Hi people,

    whilst i was happily running 2.0.3 I could manually disconnect the wan interface & reconnect when ever I wanted with no issue's at all but now since I upgraded to 2.1 I get the following problem:

    
    Sep 23 00:00:59	ppp: [wan_link0] LCP: Down event
    Sep 23 00:00:59	ppp: [wan_link0] Link: DOWN event
    Sep 23 00:00:59	ppp: [wan_link0] MODEM: chat script failed
    Sep 23 00:00:59	ppp: [wan_link0] CHAT: The modem is not responding to "AT" at ModemCmd: label.
    Sep 23 00:00:44	ppp: [wan_link0] Link: reconnection attempt 1
    Sep 23 00:00:43	ppp: [wan_link0] Link: reconnection attempt 1 in 1 seconds
    Sep 23 00:00:43	ppp: [wan_link0] LCP: Down event
    Sep 23 00:00:43	ppp: [wan_link0] Link: DOWN event
    Sep 23 00:00:43	ppp: [wan_link0] MODEM: chat script failed
    Sep 23 00:00:43	ppp: [wan_link0] CHAT: The modem is not responding to "AT" at ModemCmd: label.
    Sep 23 00:00:30	ppp: [wan_link0] LCP: LayerStart
    Sep 23 00:00:30	ppp: [wan_link0] LCP: state change Initial --> Starting
    Sep 23 00:00:30	ppp: [wan_link0] LCP: Open event
    Sep 23 00:00:30	ppp: [wan_link0] Link: OPEN event
    Sep 23 00:00:30	ppp: [wan] Bundle: Interface ng0 created
    Sep 23 00:00:30	ppp: web: web is not running
    Sep 23 00:00:30	ppp: process 95767 started, version 5.6 (root@snapshots-8_3-i386.builders.pfsense.org 10:16 24-Jul-2013)
    Sep 23 00:00:30	ppp:
    Sep 23 00:00:30	ppp: Multi-link PPP daemon for FreeBSD
    Sep 23 00:00:30	ppp: process 58620 terminated
    Sep 23 00:00:30	ppp: [wan_link0] Link: Shutdown
    Sep 23 00:00:30	ppp: [wan] Bundle: Shutdown
    Sep 23 00:00:28	ppp: [wan] IPV6CP: Close event
    Sep 23 00:00:28	ppp: [wan] IPCP: Close event
    Sep 23 00:00:28	ppp: [wan] IFACE: Close event
    Sep 23 00:00:28	ppp: caught fatal signal term
    
    

    I had this exact same issue when 2.1 was in beta & I had hoped that it would have been resolved by the time 2.1 was RELEASE.

    During the debug of this I had to reset the ppp settings as the device defaulted to 'cuaU0' rather than using 'cuaU0.3'

    full ppp settings:

    
     <ppp><ptpid>0</ptpid>
                            <type>ppp</type>
                            <if>ppp0</if>
                            <ports>/dev/cuaU0.3</ports>
                            <username><password><apnum><bandwidth><mtu><mru><mrru><phone>*99#</phone>
                            <apn>internet</apn></mrru></mru></mtu></bandwidth></apnum></password></username></ppp> 
    
    

    the above are the exact same settings I used in 2.0.3 but to reconnect after a manual disconnect in 2.1 I have to power cycle the unit!!!

    here is the system log file from the time I upgraded & first had the disconnection problem after upgrade:

    
    Sep 23 00:10:09	check_reload_status: Linkup starting rl3
    Sep 23 00:10:09	check_reload_status: Linkup starting rl2
    Sep 23 00:10:09	kernel: rl3: link state changed to DOWN
    Sep 23 00:10:09	kernel: rl2: link state changed to DOWN
    Sep 23 00:10:09	kernel: rl1: link state changed to DOWN
    Sep 23 00:10:09	check_reload_status: Linkup starting rl1
    Sep 23 00:06:27	php: /index.php: Successful login for user 'admin' from: 192.168.1.251
    Sep 23 00:06:27	php: /index.php: Successful login for user 'admin' from: 192.168.1.251
    Sep 23 00:06:15	php: rc.start_packages: No pfBlocker action during boot process.
    Sep 23 00:06:15	php: rc.start_packages: No pfBlocker action during boot process.
    Sep 23 00:06:15	php: rc.start_packages: No pfBlocker action during boot process.
    Sep 23 00:06:15	php: rc.start_packages: No pfBlocker action during boot process.
    Sep 23 00:06:12	php: rc.start_packages: Restarting/Starting all packages.
    Sep 23 00:06:10	login: login on ttyv1 as root
    Sep 23 00:06:10	sshlockout[97644]: sshlockout/webConfigurator v3.0 starting up
    Sep 23 00:06:10	login: login on ttyv0 as root
    Sep 23 00:06:03	snmpd[85990]: disk_OS_get_disks: device 'cd0' not in device list
    Sep 23 00:06:03	snmpd[85990]: disk_OS_get_disks: device 'da0' not in device list
    Sep 23 00:06:03	check_reload_status: Starting packages
    Sep 23 00:06:03	php: rc.newwanip: pfSense package system has detected an ip change 41.151.39.6 -> 197.228.42.92 ... Restarting packages.
    Sep 23 00:06:02	php: rc.start_packages: No pfBlocker action during boot process.
    Sep 23 00:06:02	php: rc.start_packages: No pfBlocker action during boot process.
    Sep 23 00:06:02	php: rc.start_packages: No pfBlocker action during boot process.
    Sep 23 00:06:02	php: rc.start_packages: No pfBlocker action during boot process.
    Sep 23 00:06:02	check_reload_status: Reloading filter
    Sep 23 00:06:02	check_reload_status: Restarting OpenVPN tunnels/interfaces
    Sep 23 00:06:02	check_reload_status: Restarting ipsec tunnels
    Sep 23 00:06:02	check_reload_status: updating dyndns WAN_PPP
    Sep 23 00:06:01	php: rc.newwanip: Creating rrd update script
    Sep 23 00:06:01	php: rc.newwanip: Resyncing OpenVPN instances for interface WAN.
    Sep 23 00:06:00	php: rc.start_packages: Restarting/Starting all packages.
    Sep 23 00:05:59	syslogd: kernel boot file is /boot/kernel/kernel
    Sep 23 00:05:59	syslogd: exiting on signal 15
    Sep 23 00:05:59	php: rc.bootup: Creating rrd update script
    Sep 23 00:05:58	snmpd[50825]: disk_OS_get_disks: device 'cd0' not in device list
    Sep 23 00:05:58	snmpd[50825]: disk_OS_get_disks: device 'da0' not in device list
    Sep 23 00:05:54	php: rc.newwanip: ROUTING: setting default route to 10.64.64.0
    Sep 23 00:05:47	kernel: load_dn_sched dn_sched PRIO loaded
    Sep 23 00:05:47	kernel: load_dn_sched dn_sched WF2Q+ loaded
    Sep 23 00:05:47	kernel: load_dn_sched dn_sched RR loaded
    Sep 23 00:05:47	kernel: load_dn_sched dn_sched QFQ loaded
    Sep 23 00:05:47	kernel: load_dn_sched dn_sched FIFO loaded
    Sep 23 00:05:47	kernel: DUMMYNET 0 with IPv6 initialized (100409)
    Sep 23 00:05:47	kernel: ipfw2 (+ipv6) initialized, divert loadable, nat loadable, rule-based forwarding enabled, default to accept, logging disabled
    Sep 23 00:05:46	check_reload_status: Updating all dyndns
    Sep 23 00:05:46	dhcpleases: kqueue error: unkown
    Sep 23 00:05:45	dhcpleases: Could not deliver signal HUP to process because its pidfile does not exist, No such file or directory.
    Sep 23 00:05:44	php: rc.bootup: ROUTING: setting default route to 10.64.64.0
    Sep 23 00:05:40	check_reload_status: Linkup starting rl0
    Sep 23 00:05:40	kernel: rl0: link state changed to UP
    Sep 23 00:05:40	kernel: pflog0: promiscuous mode enabled
    Sep 23 00:05:40	check_reload_status: Rewriting resolv.conf
    Sep 23 00:05:39	dhcpleases: Could not deliver signal HUP to process because its pidfile does not exist, No such file or directory.
    Sep 23 00:05:39	php: rc.bootup: Resyncing OpenVPN instances.
    Sep 23 00:05:38	kernel: rl0: link state changed to DOWN
    Sep 23 00:05:38	check_reload_status: Linkup starting rl0
    Sep 23 00:05:38	php: rc.bootup: Starting 3gstats.php on device 'cuaU0.3' for interface 'wan'
    Sep 23 00:05:38	sshlockout[8643]: sshlockout/webConfigurator v3.0 starting up
    Sep 23 00:05:37	sshd[8530]: Server listening on 0.0.0.0 port 22.
    Sep 23 00:05:37	sshd[8530]: Server listening on :: port 22.
    Sep 23 00:05:37	kernel: ZFS storage pool version 28
    Sep 23 00:05:37	kernel: ZFS filesystem version 5
    Sep 23 00:05:37	kernel: in /boot/loader.conf.
    Sep 23 00:05:37	kernel: Consider tuning vm.kmem_size and vm.kmem_size_max
    Sep 23 00:05:37	kernel: ZFS WARNING: Recommended minimum kmem_size is 512MB; expect unstable behavior.
    Sep 23 00:05:37	kernel: add "vfs.zfs.prefetch_disable=0" to /boot/loader.conf.
    Sep 23 00:05:37	kernel: ZFS NOTICE: Prefetch is disabled by default on i386 -- to enable,
    Sep 23 00:05:37	kernel: Trying to mount root from ufs:/dev/ad4s1a
    Sep 23 00:05:37	kernel: da0: Attempt to query device size failed: NOT READY, Medium not present
    Sep 23 00:05:37	kernel: da0: 40.000MB/s transfers
    Sep 23 00:05:37	kernel: da0: <huawei tf="" card="" storage=""> Removable Direct Access SCSI-2 device
    Sep 23 00:05:37	kernel: da0 at umass-sim1 bus 1 scbus1 target 0 lun 0
    Sep 23 00:05:37	kernel: cd0: Attempt to query device size failed: NOT READY, Medium not present
    Sep 23 00:05:37	kernel: cd0: 40.000MB/s transfers
    Sep 23 00:05:37	kernel: cd0: <huawei mass="" storage="" 2.31=""> Removable CD-ROM SCSI-2 device
    Sep 23 00:05:37	kernel: cd0 at umass-sim0 bus 0 scbus0 target 0 lun 0
    Sep 23 00:05:37	kernel: (probe1:umass-sim1:1:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present)
    Sep 23 00:05:37	kernel: (probe1:umass-sim1:1:0:0): SCSI status: Check Condition
    Sep 23 00:05:37	kernel: (probe1:umass-sim1:1:0:0): CAM status: SCSI Status Error
    Sep 23 00:05:37	kernel: (probe1:umass-sim1:1:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
    Sep 23 00:05:37	kernel: (probe0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present)
    Sep 23 00:05:37	kernel: (probe0:umass-sim0:0:0:0): SCSI status: Check Condition
    Sep 23 00:05:37	kernel: (probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error
    Sep 23 00:05:37	kernel: (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
    Sep 23 00:05:37	kernel: umass1:1:1:-1: Attached to scbus1
    Sep 23 00:05:37	kernel: umass1: SCSI over Bulk-Only; quirks = 0x0000
    Sep 23 00:05:37	kernel: umass1: <huawei 0="" 2="" technologies="" huawei="" mobile,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr=""> on usbus1
    Sep 23 00:05:37	kernel: umass0:0:0:-1: Attached to scbus0
    Sep 23 00:05:37	kernel: umass0: SCSI over Bulk-Only; quirks = 0x0000
    Sep 23 00:05:37	kernel: umass0: <huawei 0="" 2="" technologies="" huawei="" mobile,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr=""> on usbus1
    Sep 23 00:05:37	kernel: u3g0: Found 4 ports.
    Sep 23 00:05:37	kernel: u3g0: <huawei 0="" 2="" technologies="" huawei="" mobile,="" class="" 0,="" rev="" 2.00="" 0.00,="" addr=""> on usbus1
    Sep 23 00:05:37	kernel: ugen1.2: <huawei technologies=""> at usbus1
    Sep 23 00:05:37	kernel: ugen1.2: <huawei technologies=""> at usbus1 (disconnected)
    Sep 23 00:05:37	kernel: ugen1.2: <huawei technologies=""> at usbus1
    Sep 23 00:05:37	kernel: uhub1: 2 ports with 2 removable, self powered
    Sep 23 00:05:37	kernel: uhub0: 2 ports with 2 removable, self powered
    Sep 23 00:05:37	kernel: uhub1: <via 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr=""> on usbus1
    Sep 23 00:05:37	kernel: ugen1.1: <via> at usbus1
    Sep 23 00:05:37	kernel: uhub0: <via 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr=""> on usbus0
    Sep 23 00:05:37	kernel: ugen0.1: <via> at usbus0
    Sep 23 00:05:37	kernel: ad4: 152627MB <wdc wd1600bevt-60zct1="" 13.01a13=""> at ata2-master UDMA33
    Sep 23 00:05:37	kernel: usbus1: 480Mbps High Speed USB v2.0
    Sep 23 00:05:37	kernel: usbus0: 12Mbps Full Speed USB v1.0
    Sep 23 00:05:37	kernel: IPsec: Initialized Security Association Processing.
    Sep 23 00:05:37	kernel: Timecounters tick every 1.000 msec
    Sep 23 00:05:37	kernel: Timecounter "TSC" frequency 997511476 Hz quality 800
    Sep 23 00:05:37	kernel: device_attach: est0 attach returned 6
    Sep 23 00:05:37	kernel: est: cpu_vendor CentaurHauls, msr 4090a0904000a09
    Sep 23 00:05:37	kernel: est: CPU supports Enhanced Speedstep, but is not recognized.
    Sep 23 00:05:37	kernel: est0: <enhanced speedstep="" frequency="" control=""> on cpu0
    Sep 23 00:05:37	kernel: unknown: <pnp0c01> can't assign resources (memory)
    Sep 23 00:05:37	kernel: vga0: <generic isa="" vga=""> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
    Sep 23 00:05:37	kernel: sc0: VGA <16 virtual consoles, flags=0x300>
    Sep 23 00:05:37	kernel: sc0: <system console=""> at flags 0x100 on isa0
    Sep 23 00:05:37	kernel: ppi0: <parallel i="" o=""> on ppbus0
    Sep 23 00:05:37	kernel: lpt0: Interrupt-driven port
    Sep 23 00:05:37	kernel: lpt0: [ITHREAD]
    Sep 23 00:05:37	kernel: lpt0: <printer> on ppbus0
    Sep 23 00:05:37	kernel: plip0: [ITHREAD]
    Sep 23 00:05:37	kernel: plip0: <plip network="" interface=""> on ppbus0
    Sep 23 00:05:37	kernel: ppbus0: <parallel port="" bus=""> on ppc0
    Sep 23 00:05:37	kernel: ppc0: [ITHREAD]
    Sep 23 00:05:37	kernel: ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
    Sep 23 00:05:37	kernel: ppc0: <standard parallel="" printer="" port=""> at port 0x378-0x37f irq 7 pnpid PNP0400 on isa0
    Sep 23 00:05:37	kernel: uart1: [FILTER]
    Sep 23 00:05:37	kernel: uart1: <16550 or compatible> at port 0x2f8-0x2ff irq 3 pnpid PNP0501 on isa0
    Sep 23 00:05:37	kernel: uart0: [FILTER]
    Sep 23 00:05:37	kernel: uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 4 flags 0x10 pnpid PNP0501 on isa0
    Sep 23 00:05:37	kernel: atkbd0: [ITHREAD]
    Sep 23 00:05:37	kernel: atkbd0: [GIANT-LOCKED]
    Sep 23 00:05:37	kernel: kbd0 at atkbd0
    Sep 23 00:05:37	kernel: atkbd0: <at keyboard=""> irq 1 on atkbdc0
    Sep 23 00:05:37	kernel: atkbdc0: <keyboard controller="" (i8042)=""> at port 0x60,0x64 irq 1 pnpid PNP0303 on isa0
    Sep 23 00:05:37	kernel: atrtc0: <at realtime="" clock=""> at port 0x70-0x71 irq 8 pnpid PNP0b00 on isa0
    Sep 23 00:05:37	kernel: unknown: <pnp0c01> can't assign resources (memory)
    Sep 23 00:05:37	kernel: pmtimer0 on isa0
    Sep 23 00:05:37	kernel: p4tcc0: <cpu frequency="" thermal="" control=""> on cpu0
    Sep 23 00:05:37	kernel: device_attach: est0 attach returned 6
    Sep 23 00:05:37	kernel: est: cpu_vendor CentaurHauls, msr 4090a0904000a09
    Sep 23 00:05:37	kernel: est: CPU supports Enhanced Speedstep, but is not recognized.
    Sep 23 00:05:37	kernel: est0: <enhanced speedstep="" frequency="" control=""> on cpu0
    Sep 23 00:05:37	kernel: cpu0 on motherboard
    Sep 23 00:05:37	kernel: device_attach: et1 attach returned 6
    Sep 23 00:05:37	kernel: et1: EEPROM status error 0x8b
    Sep 23 00:05:37	kernel: et1: <agere et1310="" gigabit="" ethernet=""> mem 0xfe800000-0xfe9fffff irq 16 at device 0.0 on pci129
    Sep 23 00:05:37	kernel: pci129: <pci bus=""> on pcib4
    Sep 23 00:05:37	kernel: pcib4: <mptable pci-pci="" bridge=""> at device 0.1 on pci128
    Sep 23 00:05:37	kernel: et0: [ITHREAD]
    Sep 23 00:05:37	kernel: truephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
    Sep 23 00:05:37	kernel: truephy0: <et1011c 10="" 100="" 1000baset="" phy=""> PHY 0 on miibus4
    Sep 23 00:05:37	kernel: miibus4: <mii bus=""> on et0
    Sep 23 00:05:37	kernel: et0: <agere et1310="" gigabit="" ethernet=""> mem 0xfea00000-0xfebfffff irq 16 at device 0.0 on pci130
    Sep 23 00:05:37	kernel: pci130: <pci bus=""> on pcib3
    Sep 23 00:05:37	kernel: pcib3: <mptable pci-pci="" bridge=""> at device 0.0 on pci128
    Sep 23 00:05:37	kernel: pci128: <pci bus=""> on pcib2
    Sep 23 00:05:37	kernel: pcib2: <pci-pci bridge=""> at device 19.0 on pci0
    Sep 23 00:05:37	kernel: isa0: <isa bus=""> on isab0
    Sep 23 00:05:37	kernel: isab0: <pci-isa bridge=""> at device 17.0 on pci0
    Sep 23 00:05:37	kernel: usbus1: <via vt6202="" usb="" 2.0="" controller=""> on ehci0
    Sep 23 00:05:37	kernel: usbus1: EHCI version 1.0
    Sep 23 00:05:37	kernel: ehci0: [ITHREAD]
    Sep 23 00:05:37	kernel: ehci0: <via vt6202="" usb="" 2.0="" controller=""> mem 0xfcffe800-0xfcffe8ff irq 22 at device 16.4 on pci0
    Sep 23 00:05:37	kernel: usbus0: <via 83c572="" usb="" controller=""> on uhci0
    Sep 23 00:05:37	kernel: uhci0: [ITHREAD]
    Sep 23 00:05:37	kernel: uhci0: <via 83c572="" usb="" controller=""> port 0xd000-0xd01f irq 20 at device 16.0 on pci0
    Sep 23 00:05:37	kernel: ata1: [ITHREAD]
    Sep 23 00:05:37	kernel: ata1: <ata channel=""> at channel 1 on atapci1
    Sep 23 00:05:37	kernel: ata0: [ITHREAD]
    Sep 23 00:05:37	kernel: ata0: <ata channel=""> at channel 0 on atapci1
    Sep 23 00:05:37	kernel: atapci1: <via ata="" controller=""> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 15.1 on pci0
    Sep 23 00:05:37	kernel: ata3: [ITHREAD]
    Sep 23 00:05:37	kernel: ata3: <ata channel=""> at channel 1 on atapci0
    Sep 23 00:05:37	kernel: ata2: [ITHREAD]
    Sep 23 00:05:37	kernel: ata2: <ata channel=""> at channel 0 on atapci0
    Sep 23 00:05:37	kernel: atapci0: [ITHREAD]
    Sep 23 00:05:37	kernel: atapci0: <via ata="" controller=""> port 0xec00-0xec07,0xdc00-0xdc03,0xd480-0xd487,0xd400-0xd403,0xd080-0xd08f mem 0xfcffec00-0xfcffefff irq 21 at device 15.0 on pci0
    Sep 23 00:05:37	kernel: rl3: [ITHREAD]
    Sep 23 00:05:37	kernel: rlphy3: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
    Sep 23 00:05:37	kernel: rlphy3: <realtek internal="" media="" interface=""> PHY 0 on miibus3
    Sep 23 00:05:37	kernel: miibus3: <mii bus=""> on rl3
    Sep 23 00:05:37	kernel: rl3: <realtek 10="" 8139="" 100basetx=""> port 0xd800-0xd8ff mem 0xfcfff000-0xfcfff0ff irq 19 at device 12.0 on pci0
    Sep 23 00:05:37	kernel: rl2: [ITHREAD]
    Sep 23 00:05:37	kernel: rlphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
    Sep 23 00:05:37	kernel: rlphy2: <realtek internal="" media="" interface=""> PHY 0 on miibus2
    Sep 23 00:05:37	kernel: miibus2: <mii bus=""> on rl2
    Sep 23 00:05:37	kernel: rl2: <realtek 10="" 8139="" 100basetx=""> port 0xe000-0xe0ff mem 0xfcfff400-0xfcfff4ff irq 18 at device 11.0 on pci0
    Sep 23 00:05:37	kernel: rl1: [ITHREAD]
    Sep 23 00:05:37	kernel: rlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
    Sep 23 00:05:37	kernel: rlphy1: <realtek internal="" media="" interface=""> PHY 0 on miibus1
    Sep 23 00:05:37	kernel: miibus1: <mii bus=""> on rl1
    Sep 23 00:05:37	kernel: rl1: <realtek 10="" 8139="" 100basetx=""> port 0xe400-0xe4ff mem 0xfcfff800-0xfcfff8ff irq 17 at device 10.0 on pci0
    Sep 23 00:05:37	kernel: rl0: [ITHREAD]
    Sep 23 00:05:37	kernel: rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
    Sep 23 00:05:37	kernel: rlphy0: <realtek internal="" media="" interface=""> PHY 0 on miibus0
    Sep 23 00:05:37	kernel: miibus0: <mii bus=""> on rl0
    Sep 23 00:05:37	kernel: rl0: <realtek 10="" 8139="" 100basetx=""> port 0xe800-0xe8ff mem 0xfcfffc00-0xfcfffcff irq 16 at device 9.0 on pci0
    Sep 23 00:05:37	kernel: vgapci0: <vga-compatible display=""> mem 0xf8000000-0xfbffffff,0xfd000000-0xfdffffff at device 0.0 on pci1
    Sep 23 00:05:37	kernel: pci1: <pci bus=""> on pcib1
    Sep 23 00:05:37	kernel: pcib1: <mptable pci-pci="" bridge=""> at device 1.0 on pci0
    Sep 23 00:05:37	kernel: agp0: aperture size is 256M
    Sep 23 00:05:37	kernel: agp0: <via 3314="" (p4m800ce)="" host="" to="" pci="" bridge=""> on hostb0
    Sep 23 00:05:37	kernel: pci0: <pci bus=""> on pcib0
    Sep 23 00:05:37	kernel: pcib0: <mptable host-pci="" bridge=""> pcibus 0 on motherboard
    Sep 23 00:05:37	kernel: padlock0: <aes-cbc,sha1,sha256> on motherboard
    Sep 23 00:05:37	kernel: cryptosoft0: <software crypto=""> on motherboard
    Sep 23 00:05:37	kernel: ACPI: Try disabling either ACPI or apic support.
    Sep 23 00:05:37	kernel: ACPI: Table initialisation failed: AE_NOT_FOUND
    Sep 23 00:05:37	kernel: ACPI Error: A valid RSDP was not found (20101013/tbxfroot-309)
    Sep 23 00:05:37	kernel: kbd1 at kbdmux0
    Sep 23 00:05:37	kernel: module_register_init: MOD_LOAD (ipw_monitor_fw, 0xc07bb830, 0) error 1
    Sep 23 00:05:37	kernel: ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
    Sep 23 00:05:37	kernel: ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
    Sep 23 00:05:37	kernel: module_register_init: MOD_LOAD (ipw_ibss_fw, 0xc07bb790, 0) error 1
    Sep 23 00:05:37	kernel: ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
    Sep 23 00:05:37	kernel: ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
    Sep 23 00:05:37	kernel: module_register_init: MOD_LOAD (ipw_bss_fw, 0xc07bb6f0, 0) error 1
    Sep 23 00:05:37	kernel: ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
    Sep 23 00:05:37	kernel: ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
    Sep 23 00:05:37	kernel: wlan: mac acl policy registered
    Sep 23 00:05:37	kernel: ioapic0 <version 0.3=""> irqs 0-23 on motherboard
    Sep 23 00:05:37	kernel: ioapic0: Assuming intbase of 0
    Sep 23 00:05:37	kernel: MPTable: <template etemplate=""></template></version></software></aes-cbc,sha1,sha256></mptable></pci></via></mptable></pci></vga-compatible></realtek></mii></realtek></realtek></mii></realtek></realtek></mii></realtek></realtek></mii></realtek></via></ata></ata></via></ata></ata></via></via></via></via></pci-isa></isa></pci-pci></pci></mptable></pci></agere></mii></et1011c></mptable></pci></agere></enhanced></cpu></pnp0c01></at></keyboard></at></standard></parallel></plip></printer></parallel></system></generic></pnp0c01></enhanced></wdc></via></via></via></via></huawei></huawei></huawei></huawei></huawei></huawei></huawei></huawei>
    


  • BUMP<

    sorry to bump but this is seriously annoying & also dial on demand is not working as expected with the same errors in logs as I posted when trying to disconnect/re-connect manually



  • Ok So I have finally worked out what was causing this & what you can potentially do to avoid this yourselves.

    In previous versions of pfsense I had to assign /dev/cdu0.3 as the management/main device for this ppp which can be confirmed via connecting to it using minicom OR plugging it in to a linux pc & cat /dev/cdu0.3 which will give you the quality stats for the cell it is talking to along with other info, also you can ECHO AT commands to this "port"

    With the new driver within pfsense 2.1 you must assign /dev/cdu0.0 as the main device for the ppp otherwise it looses control each reload of the ppp call script.

    As much as a pita this is I actually think that the driver is now communicating to ALL 4 ports of the device hence why we now have all the quality info displayed on the interface status page.

    I think this is more of a gotcha for 2.0.3 upgraders to 2.1

    Thread Solved


  • Netgate Administrator

    Thanks for coming back with that.  :)

    I assume you mean /dev/cuaU0.0 and that cdu was just a typo? Important to note that the capital 'U' in the name indicates a USB attached device.

    Steve


Log in to reply