;; MSG SIZE rcvd: 90
However, earlier today I suddenly got responses to both the (FQDN)
and PTR queries, but I cannot reproduce this right now. Really weird.
Cheers,
Simon.
Vale,
Quintus
--
Blog: http://www.quintilianus.eu
I will reject HTML emails
that the temporary address requestion is only part of the
problem. What do you think?
Vale,
Quintus
--
Blog: http://www.quintilianus.eu
I will reject HTML emails. | Ich akzeptiere keine HTML-Nachrichten.
|
Use GnuPG for mail encryption: | GnuPG für Mail-Verschlüsselung
:cafe:383::1
dnsmasq[1513]: forwarded atlantis.cable.internal.xxx.eu to 62.141.38.230
dnsmasq[1513]: forwarded atlantis.cable.internal.xxx.eu to 10.37.59.1
dnsmasq[1513]: reply atlantis.cable.internal.xxx.eu is NODATA-IPv6
--
Valete,
Quintus
signature.asc
network I’m not doing SLAAC, but stateful DHCPv6 so that this option
won’t work. SLAAC does not work at all with /80 subnets.
Amicalement,
Vale,
Quintus
signature.asc
Description: OpenPGP digital signature
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss
Am Sat, 5 Oct 2013 14:21:26 +0100
schrieb Kevin Darbyshire-Bryant ke...@darbyshire-bryant.me.uk:
Hi All,
Hi Kevin,
dnsmasq2.67rc3 - possibly odd behaviour, probably I misunderstand :-)
I have an interface that has a /64 on it. dnsmasq.conf has amongst
other things
dhcp-range=::100,
Hi there,
I’m trying to divide my home network into useful IPv6 subnets. I’ve got
a /64 network from SiXxs and wanted to use a /80 for cable clients and
another /80 for wifi clients (with the other /80s staying unused for
now). Here’s what I’ve tried for cable:
Am Tue, 3 Sep 2013 14:15:21 +0200
schrieb Quintus quin...@quintilianus.eu:
I did, and to double-check I just tried again. This yields the same
error as before.
Nevermind, I solved my problem by changing my network setup. Reading
dnsmasq’s manpage again, I found this:
For directly connected
Hi guys,
I’m trying to get dnsmasq to provide IPs from different ranges based on
the interface the requests come in. That is, I want it to provide
different IPs for wired clients (interface eth0) and wireless clients
(interface wlan0, hostapd already running correctly).
I tried the following
Am Tue, 03 Sep 2013 13:53:39 +0200
schrieb Albert ARIBAUD albert.arib...@free.fr:
Did you try moving the 'set:wired' specification after the
'interface:eth0' one? I.e.,
dhcp-range=interface:eth0,set:wired,10.37.59.3,10.37.59.62,12h
I did, and to double-check I just tried again.
