Ask
Reply
Solution
16-09-2019 01:27 PM - edited 16-09-2019 03:31 PM
I have a new THG3000 / VOX3 router which doesn't recognise a Sierra Wireless Compass 889 and doesn't work with a ZTE MF823 hostless USB modem which functions perfectly well without setup on my Linux laptop
Is this a bug with the THG3000 or does it have a limited compatibility with mobile dongles ?
Log output
Date Time Category Severity Log Details
16.09.2019 14:13:08 wan Debug Action teardown completed with return code 0 on interface wwan
16.09.2019 14:13:08 wan Debug Running teardown action on interface wwan
16.09.2019 14:13:08 wan Debug Action disconnected completed with return code 0 on interface wwan
16.09.2019 14:13:08 data Error Received event "session_state_changed" for unknown device
16.09.2019 14:13:08 wan Debug Queuing teardown action on interface wwan
16.09.2019 14:13:08 wan Debug Running disconnected action on interface wwan
16.09.2019 14:13:04 data Warning ubus call timeout on calling mobiled status. stack traceback:
16.09.2019 14:13:02 system Info async run: /usr/share/transformer/scripts/uci_system.sh;/etc/init.d/syslog_fwd restart;/etc/init.d/miniupnpd-tch restart
16.09.2019 14:13:02 system Info PROT_TRACE: LAST STATE: <Inform>
16.09.2019 14:13:02 system Info PROT_TRACE: Effective retry wait time 12
16.09.2019 14:13:02 system Info PROT_TRACE: Max retry wait time 13
16.09.2019 14:13:02 system Info PROT_TRACE: Min retry wait time 12
16.09.2019 14:13:02 system Info PROT_TRACE: Nb of retries 7766
16.09.2019 14:13:02 system Critical CONNECTION: Failed to create socket.
16.09.2019 14:13:02 system Error SOCK_TRACE: cwmp_createClientSocket - no ip to bind to on interface wan - fail
16.09.2019 14:13:02 system Error UBUS_CLIENT: Failed to retrieve external IP address
16.09.2019 14:13:02 system Info CONNECTION: Connecting to server retry 7765.
16.09.2019 14:13:02 system Info PROT_TRACE: Events are waiting, need to contact ACS
16.09.2019 14:13:00 data Warning ubus call timeout on calling mobiled status. stack traceback:
16.09.2019 14:11:20 wan Debug Action teardown completed with return code 0 on interface wwan
16.09.2019 14:11:20 wan Debug Running teardown action on interface wwan
16.09.2019 14:11:20 wan Debug Action disconnected completed with return code 0 on interface wwan
16.09.2019 14:11:20 data Error Received event "session_state_changed" for unknown device
16.09.2019 14:11:20 wan Debug Queuing teardown action on interface wwan
16.09.2019 14:11:20 wan Debug Running disconnected action on interface wwan
16.09.2019 14:11:20 wan Debug Queuing disconnected action on interface wwan
16.09.2019 14:11:20 system Info PROT_TRACE: LAST STATE: <Inform>
16.09.2019 14:11:20 system Info PROT_TRACE: Effective retry wait time 13
16.09.2019 14:11:20 system Info PROT_TRACE: Max retry wait time 13
16.09.2019 14:11:20 system Info PROT_TRACE: Min retry wait time 12
16.09.2019 14:11:20 system Info PROT_TRACE: Nb of retries 7758
16.09.2019 14:11:20 system Critical CONNECTION: Failed to create socket.
16.09.2019 14:11:20 system Error SOCK_TRACE: cwmp_createClientSocket - no ip to bind to on interface wan - fail
16.09.2019 14:11:20 system Error UBUS_CLIENT: Failed to retrieve external IP address
16.09.2019 14:11:20 system Info CONNECTION: Connecting to server retry 7757.
16.09.2019 14:11:13 data Warning ubus call timeout on calling mobiled status. stack traceback:
16.09.2019 14:11:10 wan Debug Action teardown completed with return code 0 on interface wwan
16.09.2019 14:11:09 wan Debug Running teardown action on interface wwan
16.09.2019 14:11:09 wan Debug Action disconnected completed with return code 0 on interface wwan
16.09.2019 14:11:09 data Error Received event "session_state_changed" for unknown device
16.09.2019 14:11:09 wan Debug Queuing teardown action on interface wwan
16.09.2019 14:11:09 wan Debug Running disconnected action on interface wwan
16.09.2019 14:11:09 wan Debug Queuing disconnected action on interface wwan
16.09.2019 14:11:07 system Info PROT_TRACE: LAST STATE: <Inform>
16.09.2019 14:11:07 system Info PROT_TRACE: Effective retry wait time 13
16.09.2019 14:11:07 system Info PROT_TRACE: Max retry wait time 13
16.09.2019 14:11:07 system Info PROT_TRACE: Min retry wait time 12
16.09.2019 14:11:07 system Info PROT_TRACE: Nb of retries 7757
16.09.2019 14:11:07 system Critical CONNECTION: Failed to create socket.
16.09.2019 14:11:07 system Error SOCK_TRACE: cwmp_createClientSocket - no ip to bind to on interface wan - fail
16.09.2019 14:11:07 system Error UBUS_CLIENT: Failed to retrieve external IP address
16.09.2019 14:11:07 system Info CONNECTION: Connecting to server retry 7756.
16.09.2019 14:11:07 system Info PROT_TRACE: Events are waiting, need to contact ACS
16.09.2019 14:10:59 wan Debug Action teardown completed with return code 0 on interface wwan
16.09.2019 14:10:59 wan Debug Running teardown action on interface wwan
16.09.2019 14:10:59 wan Debug Action disconnected completed with return code 0 on interface wwan
16.09.2019 14:10:59 data Error Received event "session_state_changed" for unknown device
16.09.2019 14:10:59 wan Debug Queuing teardown action on interface wwan
21-09-2019 02:14 PM
I'll be honest @motorway, this is the first time I've come across this issue, so I couldn't comment if it was a bug or not. I think we'd have to speak to our Tech team to see what they suggest to get this working for you. Can you please message me on Facebook or Twitter (Vodafone UK or @VodafoneUK) then we can take it from there!
23-09-2019 11:21 AM
Hi DaneB,
Do you have a method which does not use Facebook or Twitter ?
26-09-2019 01:22 PM
16-08-2020 02:53 PM
Hi Motorway,
Did you ever find out what the reason for this was ? Im having the same problem and its been goong on for nine days now, any advice would be great thanks.
13-09-2020 08:39 AM
Hi Gettingb0red.
I replaced the THG3000 with a router with a track record for reliability, the posts above are the sum total of Vodafone's involvement as I experienced it - whether they have done any testing - you would have to ask..
Best of luck if you stick with it.
13-09-2020 02:51 PM
Vodafone's routers have only ever offered compatibility with a small number of their own brand WiFi adapter dongles. Other routers may offer more compatibility, but it's often where they can recognise the chipset used rather than the specific device. Sometimes without the very specific device drivers, it can be a pain or even totally impossible to set up USB devices on even the most flexible of Linux based routers.
*That's from experience with my own routers and mobile, USB-networking (Pi-Zero direct to the USB port), Arduino, and Zigbee modules (a really bad idea as too close and they interfere with the router too)