Thanks for the replies. As Simon suggested, there must have been
something wrong in how I had configured IPv6 address for the WLAN
interface.
After I added IPv6 address 2001:db8:0:1::1 with prefix 64 in
NetworkManager IPV6 Settings of the hotspot WLAN connection, my Android
device got two IPv6
On Tue, Jan 07, 2020 at 01:42:45PM +0100, Michal Zatloukal wrote:
> On Tue, 7 Jan 2020 at 11:43, Geert Stappers wrote:
> > On 07-01-2020 03:52, Juha Heinanen wrote:
> > > In order to support IPv6 address allocation to Android clients I have
> > > tried to extend default Debian NetworkManager Wifi
On 07/01/2020 02:52, Juha Heinanen wrote:
> Jan 7 04:46:10 char dnsmasq-dhcp[18847]: router advertisement on
> 2001:db8:0:1::, old prefix for wlp1s0
> Jan 7 04:46:10 char dnsmasq-dhcp[18847]: DHCPv4-derived IPv6 names on
> 2001:db8:0:1::, constructed for wlp1s0
> Jan 7 04:46:10 char
Last time I checked, Android doesn't do DHCP6 (at all, even if
instructed with M/O bits in RA).
Either way, IMHO you should first be looking for RTR-SOLICIT and
RTR-ADVERT log messages. The solicitation and advertisement packets
themselves should be relatively easy to find in a pcap capture with
On 07-01-2020 03:52, Juha Heinanen wrote:
> In order to support IPv6 address allocation to Android clients I have
> tried to extend default Debian NetworkManager Wifi hotspot dnsmasq
> configuration:
>
> 18240 ?S 0:00 /usr/sbin/dnsmasq --conf-file=/dev/null --no-hosts
>
