On 2017-04-20 14:03, Frederic Bonnard wrote:
~ # ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enP5p1s0f0: <BROADCAST,MULTICAST> mtu 1500 qdisc mq qlen 1000
link/ether 70:e2:84:14:24:ed brd ff:ff:ff:ff:ff:ff
3: enP5p1s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq qlen
1000
link/ether 70:e2:84:14:24:ee brd ff:ff:ff:ff:ff:ff
inet6 2002:903:15f:550:72e2:84ff:fe14:24ee/64 scope global dynamic
valid_lft 2591627sec preferred_lft 604427sec
inet6 fe80::72e2:84ff:fe14:24ee/64 scope link
valid_lft forever preferred_lft forever
/etc/resolv.conf shows correct content with "search" field
corresponding to the
domain I provided and "nameserver" is the one I provided also.
It's a bit unhelpful though that you didn't provide that information.
You seem to indicate that you need to use IPv4 to access the nameserver?
Is the real failure you report that it did not configure IPv4 correctly?
I.e. didn't show a prompt and continued without it? Is a DHCPv4 server
on the network where you tried this? Because the DHCP client seems to be
unable to acquire an address. Does an IPv6 nameserver work? (Assuming
your 6to4 connectivity actually works.)
Also it'd be helpful to see "ip -6 route" and "ip route".
Kind regards
Philipp Kern
