[Dnsmasq-discuss] IPv6 dhcp/ra-issue

Wed Apr 23 11:12:27 UTC 2014

On 21/04/14 14:28, Oliver Rath wrote:
> Hi list,
> 
> Im trying to give my network-computers IPv6-Addresses constructed from
> ppp0. In my config I get from my provider i.e. these (dynamic) IPv4 and
> IPv6-addresses:
> 
> # ifconfig ppp0
> ppp0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>  mtu 1492
>         inet 80.137.126.83  netmask 255.255.255.255  destination
> 87.186.224.66
>         inet6 fe80::43c:5b54:cea:b7ea  prefixlen 10  scopeid 0x20<link>
>         inet6 2003:62:487f:b168:43c:5b54:cea:b7ea  prefixlen 64  scopeid
> 0x0<global>
>         ppp  txqueuelen 3  (Punkt-zu-Punkt Verbindung)
>         RX packets 2546359  bytes 3258224683 (3.0 GiB)
>         RX errors 0  dropped 0  overruns 0  frame 0
>         TX packets 1550070  bytes 133189854 (127.0 MiB)
>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> 
> One of my additional interfaces has this address:
> # ifconfig p3p1
> p3p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
>         inet 192.168.2.254  netmask 255.255.255.0  broadcast 192.168.2.255
>         inet6 fe80::210:f3ff:fe07:f7bf  prefixlen 64  scopeid 0x20<link>
>         ether 00:10:f3:07:f7:bf  txqueuelen 1000  (Ethernet)
>         RX packets 2806761  bytes 3337921408 (3.1 GiB)
>         RX errors 0  dropped 0  overruns 0  frame 0
>         TX packets 1832066  bytes 326375284 (311.2 MiB)
>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> 
> 
> 
> If I understand right, ive got an IPv6-subnet with the ability of ~250
> clients (Telekom Germany), directly addressable from internet. Now i
> want to configure dnsmasq in a way, that the clients get IPv4- (works,
> internal only) and IPv6-addresses in a from internet addressable way.
> 
> Imho the fe80.. number is the *router*-ipv6-address, the 2003:... the
> *host* ipv6-address. Now my clients should also get an ipv6-router *and*
> -host address. Is this right?
> 
> My dnsmasq.conf (stripped):
> 
> except-interface=ppp0
> dhcp-range=set:gw2,192.168.2.50,192.168.2.150,255.255.255.0,12h
> dhcp-range=tag:gw2,::,constructor:ppp0
> ddhcp-option=tag:gw2,128,192.168.2.254
> enable-ra
> dhcp-option=mtu,1492
> dhcp-option=option6:dns-server,[::]
> dhcp-option=252,"http://heimserver/wpad.dat"
> log-queries
> log-dhcp
> 
> Now I would assume, that my clientpc (p3p1 is bridged with wlan-ap)
> would get an fe80:.. and another, from internet routable address. While
> my card has the mac-address 00:21:6a:37:3f:72, i would assume getting an
> IPv6 address like 2003:62:487f:b168:0021:6aFF:FE373f:72, but he doesnt:
> 
> wlan0 on my client-pc:
> 
> # ifconfig wlan0
> wlan0     Link encap:Ethernet  Hardware Adresse 00:21:6a:37:3f:72 
>           inet Adresse:192.168.2.100  Bcast:192.168.2.255 
> Maske:255.255.255.0
>           inet6-Adresse: fe80::221:6aff:fe37:3f72/64
> Gültigkeitsbereich:Verbindung
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
>           RX-Pakete:2981577 Fehler:0 Verloren:0 Überläufe:0 Fenster:0
>           TX-Pakete:2979080 Fehler:0 Verloren:0 Überläufe:0 Träger:0
>           Kollisionen:0 Sendewarteschlangenlänge:1000
>           RX-Bytes:3059635559 (3.0 GB)  TX-Bytes:2883630423 (2.8 GB)
> 
> 
> Here /var/log/syslog on my client (sorry for the german parts):
> 
> Apr 21 14:57:29 hp dhclient: DHCPREQUEST of 192.168.2.100 on wlan0 to
> 255.255.255.255 port 67 (xid=0x48327e63)
> Apr 21 14:57:29 hp dhclient: DHCPACK of 192.168.2.100 from 192.168.2.254
> Apr 21 14:57:29 hp dhclient: bound to 192.168.2.100 -- renewal in 21016
> seconds.
> Apr 21 14:57:29 hp dhclient: DHCPACK of 192.168.2.100 from 192.168.2.254
> Apr 21 14:57:29 hp dhclient: bound to 192.168.2.100 -- renewal in 21016
> seconds.
> Apr 21 14:57:29 hp NetworkManager[827]: <info> (wlan0): DHCPv4 state
> changed preinit -> reboot
> Apr 21 14:57:29 hp NetworkManager[827]: <info>   address 192.168.2.100
> Apr 21 14:57:29 hp NetworkManager[827]: <info>   prefix 24 (255.255.255.0)
> Apr 21 14:57:29 hp NetworkManager[827]: <info>   gateway 192.168.2.254
> Apr 21 14:57:29 hp NetworkManager[827]: <info>   hostname 'hp'
> Apr 21 14:57:29 hp NetworkManager[827]: <info>   nameserver '192.168.2.254'
> Apr 21 14:57:29 hp NetworkManager[827]: <info> Activation (wlan0) Stage
> 5 of 5 (IPv4 Configure Commit) scheduled...
> Apr 21 14:57:29 hp NetworkManager[827]: <info> Activation (wlan0) Stage
> 5 of 5 (IPv4 Commit) started...
> Apr 21 14:57:29 hp avahi-daemon[801]: Joining mDNS multicast group on
> interface wlan0.IPv4 with address 192.168.2.100.
> Apr 21 14:57:29 hp avahi-daemon[801]: New relevant interface wlan0.IPv4
> for mDNS.
> Apr 21 14:57:29 hp avahi-daemon[801]: Registering new address record for
> 192.168.2.100 on wlan0.IPv4.
> Apr 21 14:57:30 hp NetworkManager[827]: <info> (wlan0): device state
> change: ip-config -> secondaries (reason 'none') [70 90 0]
> Apr 21 14:57:30 hp NetworkManager[827]: <info> Activation (wlan0) Stage
> 5 of 5 (IPv4 Commit) complete.
> Apr 21 14:57:30 hp NetworkManager[827]: <info> (wlan0): device state
> change: secondaries -> activated (reason 'none') [90 100 0]
> Apr 21 14:57:30 hp NetworkManager[827]: <info> NetworkManager state is
> now CONNECTED_GLOBAL
> Apr 21 14:57:30 hp NetworkManager[827]: <info> Policy set
> 'WLAN-001F3FD648F9' (wlan0) as default for IPv4 routing and DNS.
> Apr 21 14:57:30 hp NetworkManager[827]: <info> Writing DNS information
> to /sbin/resolvconf
> Apr 21 14:57:30 hp dnsmasq[1563]: vorgelagerte Server von DBus gesetzt
> Apr 21 14:57:30 hp dnsmasq[1563]: Benutze Namensserver 192.168.2.254#53
> Apr 21 14:57:31 hp avahi-daemon[801]: Joining mDNS multicast group on
> interface wlan0.IPv6 with address fe80::221:6aff:fe37:3f72.
> Apr 21 14:57:31 hp avahi-daemon[801]: New relevant interface wlan0.IPv6
> for mDNS.
> Apr 21 14:57:31 hp avahi-daemon[801]: Registering new address record for
> fe80::221:6aff:fe37:3f72 on wlan0.*.
> Apr 21 14:57:41 hp NetworkManager[827]: <info> Activation (wlan0)
> successful, device activated.
> Apr 21 14:57:41 hp dbus[684]: [system] Activating service
> name='org.freedesktop.nm_dispatcher' (using servicehelper)
> Apr 21 14:57:41 hp wpa_supplicant[1062]: wlan0: CTRL-EVENT-SCAN-STARTED
> Apr 21 14:57:41 hp dbus[684]: [system] Successfully activated service
> 'org.freedesktop.nm_dispatcher'
> Apr 21 14:57:48 hp ntpdate[8010]: adjust time server 91.189.94.4 offset
> 0.007383 sec
> Apr 21 14:57:50 hp NetworkManager[827]: <info> (wlan0): IP6 addrconf
> timed out or failed.
> Apr 21 14:57:50 hp NetworkManager[827]: <info> Activation (wlan0) Stage
> 4 of 5 (IPv6 Configure Timeout) scheduled...
> Apr 21 14:57:50 hp NetworkManager[827]: <info> Activation (wlan0) Stage
> 4 of 5 (IPv6 Configure Timeout) started...
> Apr 21 14:57:50 hp NetworkManager[827]: <info> Activation (wlan0) Stage
> 4 of 5 (IPv6 Configure Timeout) complete.
> Apr 21 14:59:27 hp wpa_supplicant[1062]: message repeated 2 times: [
> wlan0: CTRL-EVENT-SCAN-STARTED ]
> Apr 21 14:59:31 hp wpa_supplicant[1062]: nl80211:
> send_and_recv->nl_recvmsgs failed: -33
> Apr 21 15:00:50 hp wpa_supplicant[1062]: wlan0: CTRL-EVENT-SCAN-STARTED
> 
> 
> What Im doing wrong?
> 
As an experiment, rather than a long-term solution, try assiging  p3p1
an address on the 2003:62:487f:b168:: subnet with prefix length 64, and
see if that improves things.

Cheers,

Simon.