FS#1304 - DDNS does not function with QMI protocol and IP does not appear in LuCI #6877
Comments
|
jow-: The QMI protocol handler will spawn a virtual sub-interface "wwan_4" which handles the actual IPv4 connectivity. Instruct the DDNS subsystem to pull its IP from there. |
|
yurtesen: Yes but I am setting this up from LuCI and it sets it automatically. The only fix is if I edit configuration manually using an text editor. Do you understand that LuCI does not allow me to set what you are telling me? Therefore it is a bug? |
|
yurtesen: Look, clearly WWAN has IP but system is not able to detect it. Sure, I can login using SSH and set it manually in the DDNS config file as "wwan_4" but it is simply a workaround. It is impossible to get DDNS working from within LuCI. See the screenshots I attached and ifconfig output below.
wwan0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:193.210.229.58 P-t-P:193.210.229.58 Mask:255.255.255.252
inet6 addr: fe80::ff4a:a9a6:aa7d:b218/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:1585754 errors:0 dropped:0 overruns:0 frame:0
TX packets:701900 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2231485624 (2.0 GiB) TX bytes:116659854 (111.2 MiB)
|
|
mkresin: LuCI is an independent project and not part of OpenWrt base system. It is maintained at https://github.com/openwrt/luci/. Do not get confused by the fact that it is in the OpenWrt repository. Would you please open a bug report at https://github.com/openwrt/luci/issues to make sure that the appropriate people get aware of the issue. |
|
jow-: Mathias, the issue is not in LuCI, its a problem of the netifd / qmi protocol handler which does not properly propagate the IP information to the netifd ubus state. |
|
yurtesen: I recently found out the issue exists in 18.06.2 with NCM also... |
yurtesen:
I am using OpenWrt SNAPSHOT, r5934-059b2f5 with an ec-25e card using QMI.
Device gets an IP properly.
Thu Jan 25 18:26:27 2018 daemon.notice netifd: Interface 'wwan' is now downThu Jan 25 18:26:28 2018 daemon.notice netifd: Interface 'wwan' is setting up now
Thu Jan 25 18:26:28 2018 daemon.notice netifd: wwan (16229): Device does not support 802.3 mode. Informing driver of raw-ip only for wwan0 ..
Thu Jan 25 18:26:28 2018 daemon.notice netifd: wwan (16229): Waiting for network registration
Thu Jan 25 18:26:28 2018 daemon.notice netifd: wwan (16229): Starting network wwan
Thu Jan 25 18:26:28 2018 daemon.notice netifd: wwan (16229): Setting up wwan0
Thu Jan 25 18:26:28 2018 daemon.notice netifd: Interface 'wwan' is now up
Thu Jan 25 18:26:28 2018 daemon.notice netifd: Network device 'wwan0' link is up
Thu Jan 25 18:26:28 2018 daemon.notice netifd: Network alias 'wwan0' link is up
Thu Jan 25 18:26:28 2018 daemon.notice netifd: Interface 'wwan_4' is enabled
Thu Jan 25 18:26:28 2018 daemon.notice netifd: Interface 'wwan_4' has link connectivity
Thu Jan 25 18:26:28 2018 daemon.notice netifd: Interface 'wwan_4' is setting up now
Thu Jan 25 18:26:28 2018 daemon.notice netifd: wwan_4 (16355): udhcpc: started, v1.27.2
Thu Jan 25 18:26:28 2018 daemon.notice netifd: wwan_4 (16355): udhcpc: sending discover
Thu Jan 25 18:26:28 2018 daemon.notice netifd: wwan_4 (16355): udhcpc: sending select for 10.36.238.224
Thu Jan 25 18:26:29 2018 daemon.notice netifd: wwan_4 (16355): udhcpc: lease of 10.36.238.224 obtained, lease time 7200
Thu Jan 25 18:26:29 2018 daemon.notice netifd: Interface 'wwan_4' is now up
However in LuCI the IP address is not shown in the interfaces section, at
wwaninterface.Also DDNS scripts fail with error
182633 ERROR : Can not detect local IP using network_get_ipaddr 'wwan' - Error: '1' - TERMINATEI believe the issue is because the interface name which gets the IP is
wwan_4instead ofwwanbut I am not able to set this interface in DDNS setup from LuCI and also well LuCI does not show thewwanIP address. I am not sure what would be the fix but this clearly is a problem and may effect other things as well.Thanks!
The text was updated successfully, but these errors were encountered: