Dave Ewart wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've now worked out exactly what DNS request 'poisons' the dnsmasq
cache. (This appears to be completely reproducible, although it is
possible there are other, related queries which might have the same
effect.)
After doing a
Ummm... I'm not very much convinced about that. In my installation,
dnsmasq provides both, BOOTP _and_ DHCP. I can't see any reason _not_
to provide dynamic adresses to BOOTP hosts. The client will accept any
address provided by the server. So where's the problem?
It's correct that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday, 22.08.2005 at 12:19 +0100, Simon Kelley wrote:
$ host apollo
apollo.ceu.ox.ac.uk has address 10.99.0.2
$ host -t any apollo
apollo.ceu.ox.ac.uk has address 163.1.168.2
$ host apollo
apollo.ceu.ox.ac.uk has address 10.99.0.2
Dan Shechter wrote:
Hi,
I've been trying to use dnsmasq in a wireless access point (802.11
a/b/g) environment.
In these types of environments it is very common for:
1. Clients to use windows machines
2. Clients to roam in from a different wireless network.
I'm encountering a scenario where
Eugene Prokopiev wrote:
Hi,
After starting dhcpd I see:
# netstat -pan --inet | grep dhcp
udp0 0 0.0.0.0:67 0.0.0.0:* 1408/dhcpd
raw0 0 0.0.0.0:1 0.0.0.0:* 7
1408/dhcpd
After starting dnsmask I see only:
#
Eugene Prokopiev wrote:
Hi,
Help me please to translate this simple dhcpd.conf to dnsmasq:
subnet 192.168.1.0 netmask 255.255.255.0 {
option routers 192.168.1.1;
option domain-name mydomain.ru;
option domain-name-servers 192.168.1.1;
I'm sure this is off-topic, but I know of this one:
http://www.granitecanyon.com/
On 8/22/05, kwon k...@ac1.dyndns.org wrote:
On 8/14/2005 20:19, kwon wrote:
dnsmasq[]: nameserver 65.39.196.215 refused to do a recursive query
dnsmasq[]: nameserver 65.39.192.130 refused to do a recursive
