[Dnsmasq-discuss] IPv6 dhcp/ra-issue

2014-04-21 Thread Oliver Rath
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=4305UP,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 0x20link
inet6 2003:62:487f:b168:43c:5b54:cea:b7ea  prefixlen 64  scopeid
0x0global
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=4163UP,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 0x20link
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.

Re: [Dnsmasq-discuss] IPv6 dhcp/ra-issue

2014-04-21 Thread Stéphane Guedon
Le lundi 21 avril 2014, 15:28:30 Oliver Rath a écrit :
 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=4305UP,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
 0x20link inet6 2003:62:487f:b168:43c:5b54:cea:b7ea  prefixlen 64 
 scopeid 0x0global
 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=4163UP,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
 0x20link 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 

Re: [Dnsmasq-discuss] IPv6 dhcp/ra-issue

2014-04-21 Thread Timo Buhrmester
 inet6 fe80::43c:5b54:cea:b7ea  prefixlen 10  scopeid 0x20link
This is the link-local address, established by stateless autoconfiguration.

 inet6 2003:62:487f:b168:43c:5b54:cea:b7ea  prefixlen 64  scopeid
This is the /64 your ISP assigned you.

 If I understand right, ive got an IPv6-subnet with the ability of ~250
 clients (Telekom Germany), directly addressable from internet.
Looks like you got a /64, therefore there's slightly more than 250 adresses ;).

 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?
As per the above (though i'm not quite sure what you mean by router/host 
addresses, this doesn't sound right.

 My dnsmasq.conf (stripped):
Unfortunately I can't help you on the dnsmasq specifics for I'm rather new to 
it, however I just felt like clarifying these IPv6 specifics.


Best Regards,

Timo

___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss


Re: [Dnsmasq-discuss] IPv6 dhcp/ra-issue

2014-04-21 Thread Stéphane Guedon
Le lundi 21 avril 2014, 15:50:04 Timo Buhrmester a écrit :
  inet6 fe80::43c:5b54:cea:b7ea  prefixlen 10  scopeid
  0x20link
 
 This is the link-local address, established by stateless
 autoconfiguration.
  inet6 2003:62:487f:b168:43c:5b54:cea:b7ea  prefixlen 64 
  scopeid
 
 This is the /64 your ISP assigned you.
 
  If I understand right, ive got an IPv6-subnet with the ability of
  ~250 clients (Telekom Germany), directly addressable from
  internet.
 Looks like you got a /64, therefore there's slightly more than 250
 adresses ;).

network /64 is the minimum. so yes, millions of addresses available !

  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?

fe80:: adresses are local adresses, non-routable.

 
 As per the above (though i'm not quite sure what you mean by
 router/host addresses, this doesn't sound right.
  My dnsmasq.conf (stripped):
 Unfortunately I can't help you on the dnsmasq specifics for I'm
 rather new to it, however I just felt like clarifying these IPv6
 specifics.

I wanted myself to improve Timo's answer.

 
 
 Best Regards,
 
 Timo
 
 ___
 Dnsmasq-discuss mailing list
 Dnsmasq-discuss@lists.thekelleys.org.uk
 http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss


signature.asc
Description: This is a digitally signed message part.
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss


Re: [Dnsmasq-discuss] IPv6 dhcp/ra-issue

2014-04-21 Thread Oliver Rath
Hi Stéphane!

Am 21.04.2014 15:35, schrieb Stéphane Guedon:
 Le lundi 21 avril 2014, 15:28:30 Oliver Rath a écrit :
 [..]I don't understand many of what you say. But your setup looks like
 mine, and I wrote an article about that :
 http://www.22decembre.eu/2014/04/14/local-dns-setup-with-dnsmasq-nsd-and-unbound/
 You may just have a quick look at it, maybe it will help you a bit ?

Thanks for the link! At the moment i cant see the big difference between
our configs. But maybe it is some more basicly? My ppp0 interface has
the only routeable IPv6-address, the p3p1-Interface doesnt. Does it need
a routeable address? If yes, which one should it be (according to ppp0)?

Oliver


___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss


Re: [Dnsmasq-discuss] Dnsmasq and bond0

2014-04-21 Thread Ryan A. Chapman
Hi,

This looks like a bonding issue rather than a dnsmasq issue.  What happens when 
you remove the bonding config on the host, down all interfaces but one, and 
unplug all interfaces but one on to the switch?
If that fixes it, then you have a bonding config issue on either the host or 
switch side.  In order to troubleshoot that, you need cat 
/proc/net/bonding/bond0 as well as the port channel and interface configs off 
the switch.  If it's a Cisco, then it's something like sh run int 
port-channelN as well as each interface in the port-channel sh run int 
GigabitEthernetX/Y/Z.

Not sure that everyone on this list is interested in a bonding issue, so I'm 
happy to help troubleshoot it off list.

Ryan


On Apr 20, 2014, at 6:31 AM, fa500...@skynet.be fa500...@skynet.be wrote:

 Hello everyone,
  
 I've got some problem with dnsmasq and it seems bond0. I'm not sure this is 
 why I'm asking some help. 
  
 I'm under gentoo using
 net-dns/dnsmasq-2.66  USE=dbus dhcp idn ipv6 nls tftp -auth-dns -conntrack 
 -dhcp-tools -lua -script (-selinux) LINGUAS=-de -es -fi -fr -id -it -no -pl 
 -pt_BR -ro 0 kB
  
 3 interfaces : enp1s0, enp7s0 and enp8s0. enps7s0 and enp8s0 are bonded. I 
 used the kernel method. From the kernel documentation ifenslave is has been.
  
 Interface seem to work :
  
 ip a
  
 1: lo: LOOPBACK,UP,LOWER_UP mtu 65536 qdisc noqueue state UNKNOWN 
 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 
 inet 127.0.0.1/8 brd 127.255.255.255 scope host lo 
valid_lft forever preferred_lft forever 
 inet6 ::1/128 scope host 
valid_lft forever preferred_lft forever 
 2: enp7s0: BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP mtu 1500 qdisc mq master 
 bond0 state UP qlen 1000 
 link/ether d0:50:99:0a:63:05 brd ff:ff:ff:ff:ff:ff 
 3: enp8s0: BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP mtu 1500 qdisc mq master 
 bond0 state UP qlen 1000 
 link/ether d0:50:99:0a:63:05 brd ff:ff:ff:ff:ff:ff 
 4: sit0: NOARP mtu 1480 qdisc noop state DOWN 
 link/sit 0.0.0.0 brd 0.0.0.0 
 5: ip6tnl0: NOARP mtu 1452 qdisc noop state DOWN 
 link/tunnel6 :: brd :: 
 6: enp1s0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state 
 UP qlen 1000 
 link/ether 64:66:b3:02:3c:91 brd ff:ff:ff:ff:ff:ff 
 inet 192.168.2.2/24 brd 192.168.2.255 scope global enp1s0 
valid_lft forever preferred_lft forever 
 inet6 fe80:::b3ff:fe02:3c91/64 scope link 
valid_lft forever preferred_lft forever 
 9: bond0: BROADCAST,MULTICAST,MASTER,UP,LOWER_UP mtu 1500 qdisc noqueue 
 state UP 
 link/ether d0:50:99:0a:63:05 brd ff:ff:ff:ff:ff:ff 
 inet 10.0.0.1/8 brd 10.0.0.255 scope global bond0 
valid_lft forever preferred_lft forever 
 inet6 fe80::d250:99ff:fe0a:6305/64 scope link 
valid_lft forever preferred_lft forever
  
 dnsmasq.conf
 domain-needed 
 bogus-priv 
 filterwin2k 
 bridge-interface=bond0,enp7s0,enp8s0 
 interface=bond0 
 expand-hosts 
 domain=arcade.lan 
 resolv-file=/etc/resolv.dnsmasq.conf 
 listen-address=127.0.0.1 
 listen-address=10.0.0.1 
 dhcp-range=10.0.0.1,10.0.0.50,72h 
 dhcp-host=bc:5f:f4:fe:10:26,infinite 
 dhcp-host=outrun,10.0.0.10 
 dhcp-host=00:26:b0:e6:31:30,10.0.0.12 
 dhcp-host=WDTVLive,10.0.0.40 
 dhcp-host=00:14:38:d4:c4:21,printer,10.0.0.45 
 dhcp-host=00:22:6b:f7:1c:eb,camera,10.0.0.46 
 dhcp-host=90:f6:52:75:d8:70,10.0.0.49,infinite 
 dhcp-host=10:fe:ed:ff:f9:4e,10.0.0.50,infinite 
 dhcp-option=3,10.0.0.1 
 dhcp-option=6,208.67.222.222,8.8.8.8 
 dhcp-option=66,10.0.0.1 
 dhcp-option=67,syslinux.efi 
 dhcp-option=128,10.0.0.1 
 #dhcp-option-force=211,30i 
 pxe-service=x86PC, Launch PXE_BIOS, pxelinux, 10.0.0.1 
 pxe-service=X86-64_EFI, Launch PXE-UEFI, syslinux, 10.0.0.1 
 dhcp-option=42,0.0.0.0 
 dhcp-option=19,0   # option ip-forwarding off 
 dhcp-option=44,0.0.0.0 # set netbios-over-TCP/IP nameserver(s) aka WINS 
 server(s) 
 dhcp-option=45,0.0.0. 0# netbios datagram distribution server 
 dhcp-option=46,8   # netbios node type 
 dhcp-option=47 
 dhcp-match=mactels, option:client-arch, 7 #EFI x86-64 
 tftp-root=/tftproot/ 
 tftp-lowercase 
 dhcp-leasefile=/var/lib/misc/dnsmasq.leases 
 server=/www.google.com/8.8.8.8 
 bogus-nxdomain=64.94.110.11
  
 As you can see, I've already tried the solution 
 bridge-interface=bond0,enp7s0,enp8s0.
  
 I've got no dhcp response for my client.
  
 Thanks. Best regards.
  
 Happy easter.
  
 ___
 Dnsmasq-discuss mailing list
 Dnsmasq-discuss@lists.thekelleys.org.uk
 http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss


___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss