[solved] Turris Omnia doesnt get IPv4 adress

[EricHughes]

Hello all,

I am running a Turris Omnia (TurrisOS 6.3.3) on a fiber media converter (FiberTwist-P2110) of the German provider htp.net.
So far it was a DualStack-Lite connection.

I recently had it converted to a real dual stack connection (it is already displayed as such in the customer portal).
However, the Turris is not assigned a public IPv4 address, it still shows DS-Lite (RFC633) in the overview.
In addition, the IPv4-only websites and the web portal (192.168.1.1, so the clients doesn’t receive local IPv4 adresses when connecting) are not accessible when initially connecting to end devices (smartphones). Frequent reconnecting of the clients helps against this.

The /etc/config/network looks like this:

[...lan stuff...]
config interface 'wan'
        option device 'eth2.22'
        option proto 'pppoe'
        option vpi '0'
        option vci '0'
        option ipv6 'auto'
        option username 'username'
        option password 'password'

config interface 'wan6'
        option device '@wan'
        option proto 'dhcpv6'

[...batman-adv stuff...]

In Luci, WAN_6 with corresponding IPv6 addresses and WAN_6_4 with 192.0.0.2/32 are displayed as virtual dynamic interfaces.

So hopefully you got any tips for me.

I’ve solved this by preventing installing ds-lite package.

Greetings from Germany.