[Dnsmasq-discuss] IPv6 RA issues when bound to IPv4

Vladislav Grishenko themiron at mail.ru
Fri Jul 17 14:13:43 BST 2015


Hi Michal
Use netstat -g to display multicast group memberships

Best Regards, Vladislav Grishenko

> -----Original Message-----
> From: Dnsmasq-discuss [mailto:dnsmasq-discuss-
> bounces at lists.thekelleys.org.uk] On Behalf Of Michal Zatloukal
> Sent: Friday, July 17, 2015 5:01 PM
> To: dnsmasq-discuss at lists.thekelleys.org.uk
> Subject: Re: [Dnsmasq-discuss] IPv6 RA issues when bound to IPv4
> 
> I'm not sure what you mean - what exactly should I have in the
> configuration?
> Is there a way to check, if the correct multicast address is being bound
to?
> netstat -tupan doesn't show any multicast addresses.
> 
> MZ
> 
> On 16 July 2015 at 19:49, Simon Kelley <simon at thekelleys.org.uk> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA256
> >
> > Dnsmasq needs to advertise the global address, I think. Receiving RAs
> > shouldn't be a problem, dnsmasq binds the correct multicast address.
> >
> > Cheers,
> >
> > Simon.
> >
> >
> > On 16/07/15 16:27, Michal Zatloukal wrote:
> >> Hi all,
> >>
> >> I'm using dnsmasq (2.68-1ubuntu0.1) on a machine where the need to
> >> run tftpd-hpa along with dnsmasq's own tftp server has arisen (both
> >> on just IPv4). I decided to use the "secondary IP address" feature in
> >> Linux networking system to bind tftpd-hpa to the secondary IP
> >> address, and set up dnsmasq to bind the following: - primary IPv4
> >> address - localhost IPv4 - For IPv6, I put in localhost, global and
> >> link-local addresses. IIUC, RA can't work in this config, since the
> >> destination on RS is multicast ff02::2 and therefore aren't delivered
> >> to any of the sockets opened by dnsmasq.
> >>
> >> Now, which IPv6 address do I enter so that IPv6 router announcements
> >> work correctly? (Is it even possible?) - adding
> >> ff02::2 doesn't work, dnsmasq reports error in syslog - cannot bind
> >> to this address. - replacing all IPv6 addresses with "::" allows
> >> dnsmasq to start and bind to wildcard IPv6, but it seems incoming RS
> >> packets are ignored - nothing appears in syslog when clients send
> >> solicitation. Is the filtering code in DSNmasq perhaps not expecting
> >> a wildcard address in the listen-address parameter and filters
> >> packets against it?
> >>
> >> Regards,
> >>
> >> MZ
> >>
> >> _______________________________________________ Dnsmasq-
> discuss
> >> mailing list Dnsmasq-discuss at lists.thekelleys.org.uk
> >> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
> >>
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1
> >
> >
> iQIcBAEBCAAGBQJVp+6bAAoJEBXN2mrhkTWitrYP/i/4dcuoEBWJohhXhjMS6lI
> 7
> >
> G9/jw80md0bSwzyddi8k+8+SM+oPqMBmnaqh9TWJ5pQT0j8rQsNd06ByJ85cf
> k4k
> >
> 2k5QKJoc1o6dfA/E6bJU9DtxMUqupBdQZdOo6c+b57nRRxwubXXmJe2qpDUF
> V1wQ
> >
> Z3INhtdVAHwNBAM1+amDGMrps1dmOv+cBKr81jpoX/ySvUL1j5nG2cMz+wi
> 4ux2Y
> >
> 0xf4RKsH2WqUOwVpVfmYMe/Mc5V2thdG6xpwdZ+qzMbrux/RWeNJ+4r/G7
> +mSS7l
> >
> TeAKtFkT5mrhxMIbrmC49a12WQtBZBpaAHUuSwkesGAytPelpuU5e3TwgvP0
> WCc8
> > QXoDGRm1YntM1dlu24TOPPz5jRk9L9qrJnzpXf1lyiojxpzsvRJa+Ei8uu2IWg4q
> >
> 75eVCs1wX4hLMmf9J7L759KpBrhqPoV2vu5J15vwsfXmP4bCIcDAuQOSLDiJjG
> XV
> >
> My3oeNw9Rws6qKCFYZX8YQ7SRtNDA7ssEM/aneJKTUMB7k6O3i41z2Y7DRP2
> m9uf
> >
> u5Yo3HUi9B+1G9fICNnicxZdAh5hLKilo4Fvswvn5dEMgo3LMkHiGUgHLebhsJW
> e
> >
> 68UwmvFmmZyStg1wd4qBJ4eUKIRpsvWgvaUA+Huv+nzfco2GOM8tZVPb2W
> Aq+XFj
> > Ct+n7zarBZQeIS0Ku/kJ
> > =Gn77
> > -----END PGP SIGNATURE-----
> >
> > _______________________________________________
> > Dnsmasq-discuss mailing list
> > Dnsmasq-discuss at lists.thekelleys.org.uk
> > http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
> 
> _______________________________________________
> Dnsmasq-discuss mailing list
> Dnsmasq-discuss at lists.thekelleys.org.uk
> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss




More information about the Dnsmasq-discuss mailing list