Revision history [back]

my network is (sometimes) linked to the internet via 6to4, but the local network is always dual-stack. so from time to time IPv6 works over the LAN boundary, sometimes not.

till 2.0.1.7 this wasn't a problem, but since the update the dns resolution fails. i guess its stuck at trying via IPv6, which doesn't provide a path to the internet right now.

as soon as i deactivate WLAN and am only on the mobile network connection, the dns client (and therefore mail, browser, store, ...) come to live again.

my network is (sometimes) linked to the internet via 6to4, but the local network connection is always dual-stack. so from time to time IPv6 works over the LAN boundary, sometimes not.

till 2.0.1.7 this wasn't a problem, but since the update the dns resolution fails. i guess its stuck at trying via IPv6, which doesn't provide a path to the internet right now.

as soon as i deactivate WLAN and am only on the mobile network connection, the dns client (and therefore mail, browser, store, ...) come to live again.

my My network is (sometimes) linked to the internet via 6to4, but the local connection is always dual-stack. so from time to time IPv6 works over the LAN boundary, sometimes not.

If the network is "uplinked" via v6, the router indicates this with the "default router" flag set in the router advertisements. So there shouldn't be a default route available for sailfish to use otherwise.

till 2.0.1.7 this wasn't a problem, but since the update the dns resolution fails. i guess its stuck at trying via IPv6, which doesn't provide a path to the internet right now.

as soon as i deactivate WLAN and am only on the mobile network connection, the dns client (and therefore mail, browser, store, ...) come to live again.

My network is (sometimes) linked to the internet via 6to4, but the local connection is always dual-stack. so from time to time IPv6 works over the LAN boundary, sometimes not.

If the network is "uplinked" via v6, the router indicates this with the "default router" flag set in the router advertisements. So there shouldn't be a default route available for sailfish to use otherwise.

till 2.0.1.7 this wasn't a problem, but since the update the dns resolution fails. i guess its stuck at trying via IPv6, which doesn't provide a path to the internet right now.

as soon as i deactivate WLAN and am only on the mobile network connection, the dns client (and therefore mail, browser, store, ...) come to live again.

facts

• routes are set up correct (ping a public IP works)

doesn't seem to be part of the problem, as even on working mobile connection resolv.conf just points to the localhost.

• resolv.conf is missing server entries

full story

seems that i might have bin mislead by my setup. now it looks like networkmanager is ignoring the DNS provided by DHCP{4,6} at all. just the specific conditions remain unclear.

My network is (sometimes) linked to the internet via 6to4, but the local connection is always dual-stack. so from time to time IPv6 works over the LAN boundary, sometimes not.

If the network is "uplinked" via v6, the router indicates this with the "default router" flag set in the router advertisements. So there shouldn't be a default route available for sailfish to use otherwise.

till 2.0.1.7 this wasn't a problem, but since the update the dns resolution fails. i guess its stuck at trying via IPv6, which doesn't provide a path to the internet right now.

as soon as i deactivate WLAN and am only on the mobile network connection, the dns client (and therefore mail, browser, store, ...) come to live again.

facts

• routes are set up correct (ping a public IP works)
• dns-lookups fail

doesn't seem to be part of the problem, as even on working mobile connection resolv.conf just points to the localhost.

• resolv.conf is missing server entries

full story

seems that i might have bin mislead by my setup. now it looks like networkmanager is ignoring the DNS provided by DHCP{4,6} at all. just the specific conditions remain unclear.

My network is (sometimes) linked to the internet via 6to4, but the local connection is always dual-stack. so from time to time IPv6 works over the LAN boundary, sometimes not.

If the network is "uplinked" via v6, the router indicates this with the "default router" flag set in the router advertisements. So there shouldn't be a default route available for sailfish to use otherwise.

till 2.0.1.7 this wasn't a problem, but since the update the dns resolution fails. i guess its stuck at trying via IPv6, which doesn't provide a path to the internet right now.

as soon as i deactivate WLAN and am only on the mobile network connection, the dns client (and therefore mail, browser, store, ...) come to live again.

facts

• routes are set up correct (ping a public IP works)
• dns-lookups fail

doesn't seem to be part of the problem, as even on working mobile connection resolv.conf just points to the localhost.

• resolv.conf is missing server entries

questions

how can i debug the DNS connection, as nslookup and nmcli are missing?

full story

seems that i might have bin mislead by my setup. now it looks like networkmanager is ignoring the DNS provided by DHCP{4,6} at all. just the specific conditions remain unclear.

My network is (sometimes) linked to the internet via 6to4, but the local connection is always dual-stack. so from time to time IPv6 works over the LAN boundary, sometimes not.

If the network is "uplinked" via v6, the router indicates this with the "default router" flag set in the router advertisements. So there shouldn't be a default route available for sailfish to use otherwise.

till 2.0.1.7 this wasn't a problem, but since the update the dns resolution fails. i guess its stuck at trying via IPv6, which doesn't provide a path to the internet right now.

as soon as i deactivate WLAN and am only on the mobile network connection, the dns client (and therefore mail, browser, store, ...) come to live again.

facts

• routes are set up correct (ping a public IP works)
• dns-lookups fail

doesn't seem to be part of the problem, as even on working mobile connection resolv.conf just points to the localhost.

• resolv.conf is missing server entries

questions

how can i debug the DNS connection, as nslookup and nmcli are missing?

full story

seems that i might have bin mislead by my setup. now it looks like networkmanager is ignoring the DNS provided by DHCP{4,6} at all. just the specific conditions remain unclear.

My network is (sometimes) linked to the internet via 6to4, but the local connection is always dual-stack. so from time to time IPv6 works over the LAN boundary, sometimes not.

If the network is "uplinked" via v6, the router indicates this with the "default router" flag set in the router advertisements. So there shouldn't be a default route available for sailfish to use otherwise.

till 2.0.1.7 this wasn't a problem, but since the update the dns resolution fails. i guess its stuck at trying via IPv6, which doesn't provide a path to the internet right now.

as soon as i deactivate WLAN and am only on the mobile network connection, the dns client (and therefore mail, browser, store, ...) come to live again.

facts

• routes are set up correct (ping a public IP works)
• dns-lookups fail

doesn't seem

facts

• routes are set up correct (ping a public IP works)
• dns-lookups failfail for WLAN = enabled
• connman service has the correct namserver ip set, but it seems to be unused
• as soon as WLAN is deactivated, dns works again

questions

how can i debug the DNS connection, as nslookup and nmcli are missing?

full story

seems that i might have bin mislead by my setup. now it looks like networkmanager is ignoring the DNS provided by DHCP{4,6} at all. just the specific conditions remain unclear.

My network is (sometimes) linked to the internet via 6to4, but the local connection is always dual-stack. so from time to time IPv6 works over the LAN boundary, sometimes not.

If the network is "uplinked" via v6, the router indicates this with the "default router" flag set in the router advertisements. So there shouldn't be a default route available for sailfish to use otherwise.

till 2.0.1.7 this wasn't a problem, but since the update the dns resolution fails. i guess its stuck at trying via IPv6, which doesn't provide a path to the internet right now.

as soon as i deactivate WLAN and am only on the mobile network connection, the dns client (and therefore mail, browser, store, ...) come to live again.