This is the output:
root@vm103-db:~# ip -f inet6 addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
9: eth0@if10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
inet6 fe80::3065:65ff:fe39:3035/64 scope link
valid_lft forever preferred_lft forever
root@vm103-db:~# ip -f inet6 route show
fe80::/64 dev eth0 proto kernel metric 256
root@vm103-db:~# ip -f inet6 neigh show
root@vm103-db:~#
Looks normal to me...
Am 04.04.2016 um 16:12 schrieb Simon Hobson:
On 4 Apr 2016, at 12:24, c.mo...@web.de wrote:
I have NOT configured any IPv6 connection.
That's why I said it makes no sense that apt update is trying to resolve an
IPv6 address.
OK, we'll take a step back.
Apt is **NOT** trying to resolve an IPv6 address. It will have done a DNS lookup and
these days anything that claims to be IPv6 capable is most likely asking for "any A
or AAAA record for this host". Even if the machine is single stack, the program will
probably just ask for both classes as it makes the programming simpler - in many cases
it'll need to ask for AAAA records as part of deciding if IPv6 is usable.
The next step is to decide what source address and protocol to use. These days,
many programs default to using IPv6 first if available. So IFF at least one
AAAA record is returned, AND the machine is IPv6 configured, THEN it'll try
connecting with IPv6 - whether it will try with IPv4 if the connection fails is
program dependent. If no AAAA records are returned, or the machine isn't IPv6
configured, then it'll start with IPv4.
The key thing is, if the machine is not configured for IPv6, clients won't try
and use it. That's one of the fundamentals of IPv6 enabling a program - you now
need to figure out which protocols are available before attempting a connection.
So, time to figure out if it is so configured, and if so, why. I'll admit at
this point that I'm not exactly expert at this myself, so this probably isn't
the best way ...
Does "ip -f inet6 addr show" show any IPv6 addresses other than
fe80::xxxx...xxxx/64 ?
Next you need to be looking at "ip -f inet6 route show" and "ip -f inet6 neigh
show" to figure out where it is looking to send IPv6 traffic.
Route will probably include lines like this :
fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0
That's normal for an IPv4 only system unless the IPv6 stack has been turned off
altogether.
If you see anything like :
2001:xxxx:xxxx:xxxx::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss
1440 hoplimit 0
default via 2001:xxxx:xxxx:xxxx::1 dev he-ipv6 metric 1024 mtu 1480 advmss
1420 hoplimit 0
then that indicates that the machine has been configured with an IPv6 routing
information.
------------------------------------------------------------------------------
_______________________________________________
Shorewall-users mailing list
Shorewall-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shorewall-users
------------------------------------------------------------------------------
_______________________________________________
Shorewall-users mailing list
Shorewall-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shorewall-users
