IP Address of unmanaged link

[aashishkul]

Hi,
I am using OpenVPN and followed the guide to configure OpenVPN client (tcp-client). This creates at tun/tap link. This creates a tun0 interface when connection is established. When I check using ip addr command on ssh terminal, I can see the IP address assigned by the server. However this IP Address is not shown on the interfaces list. (I added a new TUN interface with unmanaged protocol type). Is there any way to show this IP Address on the Luci GUI? In case it requires code change, can someone point me to the appropriate code in OpenWRT code base so that I can try to fix it myself.

[lleachii]

@aashishkul

However this IP Address is not shown on the interfaces list. (I added a new TUN interface with unmanaged protocol type).

Similar issue(s) with an unmanaged interface named tunl0:

[CLOSED] Bug - no further response on report

Hello all, A few months ago, I made the following bug report: https://bugs.openwrt.org/index.php?do=details&task_id=917 I have an IPENCAP tunnel that stopped appearing on LuCI at: Realtime Graph > Traffic - upon the installation of LEDE 17.01. I was able to see these IPENCAP tunnels on the GUI in 15.05. I was asked to provide some results from the CLI, and then it was assuemd that the interface was not listed in the various outputs - but it was included in the output. Any followup would be g…

FS#917 - Tunnels not vavalaiable in Realtime Graphs

[SOLVED] Possible 18.06.0 bug - selecting interface type

All, I have an IPIP interface that I configure using Unmanaged (interface: tunl0). When I change this interface to Static Address, or vice versa, it improperly selects a Wireguard interface as the option ifname (interface: azire_wireguard) and save/tmp-rollback the wrong interface name. Any ideas? Current workaround: manually editing /etc/config/network EDIT: DISREGARD. Physical interface tunl0 is not defined anywhere else in /etc/network/config (hence why I use "unmanaged").

Edit:
@jow - he closed it, seems his patch never made it to version 18?

[lleachii]

tunl0     Link encap:UNSPEC  HWaddr 00-00-00-00-xx-xx-xx-xx-00-00-00-00-00-00-00-00  
          inet addr:xxx.xxx.xxx.xxx  Mask:255.255.255.255
          inet6 addr: fe80::xxxx:xxxx:xxxx:xxxx/64 Scope:Link
          UP RUNNING NOARP MULTICAST  MTU:1480  Metric:1
          RX packets:6484461 errors:0 dropped:0 overruns:0 frame:0
          TX packets:589628 errors:20 dropped:0 overruns:0 carrier:20
          collisions:0 txqueuelen:1000 
          RX bytes:518064069 (494.0 MiB)  TX bytes:64295656 (61.3 MiB)

Powered by LuCI openwrt-23.05 branch (git-23.118.79121-6fb185f) / OpenWrt 23.05.0-rc2 (r23228-cd17d8df2a)

Already a reported bug - issue still exists.

@lleachii

Therefore, I have no way to test the bugfix...and technically, the fix never solved the original problem (as it seems that code was introduced to ignore interfaces named tunlx - in the first place).

The workaround still applies - browse to http://<SERVER_IP>/cgi-bin/luci/admin/status/realtime/bandwidth?dev=tunl0

I don't recall when this workaround stopped working for the Realtime Graphs link - I will try to see if I have a record by having noted it in some other thread.

[CLOSED] Bug - no further response on report

The workaround no longer appears to work.

@lleachii

It's more so necessary to recall, especially if tunlx is an unmanaged Interface, as TX/RX stats no longer display no the interface page either.

[vgaetera]

This requires to implement the OpenVPN protocol for netifd similar to OpenConnect:

• https://github.com/openwrt/packages/blob/master/net/openconnect/files/openconnect.sh
• https://github.com/openwrt/luci/tree/master/protocols/luci-proto-openconnect

[aashishkul]

Ok, thanks. I will take a look at it.