/dev/rob0 wrote:
FWIW, Alberto, Windows clients do speak 2136. I think they do it by
default, regardless of the type of nameserver they're contacting.
A confusing thing about Alberto's description is the apparent idea
that dnsmasq does not support dynamic DNS. On the contrary, that's
What would you use for a default gateway for these clients? DHCP has
to issue them a default gateway in their own block, otherwise they
can't communicate with the DHCP server to accept the address, and
normally the address of the dnsmasq server is used for this.
On Fri, Jun 25, 2010 at 9:41 PM,
I get a defautl gateway from upstream say 66.10.20.1. Your right about the
gateway being in teh same subnet, but I'm not sure that the DHCP server has to
be the one to inforce it.
Thanks,
Kirk
-Original Message-
From: richardvo...@gmail.com richardvo...@gmail.com
Sent: Friday,
kfried...@syncadence.com wrote:
Hello,
I'm trying to emulate a behavior found on dhcpd running on linux 2.6.28
I have an interface eth0 with IP 192.168.13.100/24.
I want to serve out one or more IPs on a different subnet, say a range
of 66.10.20.100 to 66.10.20.200 from eth0
I want to avoid
kfried...@syncadence.com wrote:
Hello,
I'm trying to emulate a behavior found on dhcpd running on linux 2.6.28
Is this using dhcpd's shared network configuration option. I have
considered adding something similar to dnsmasq, even though it's
horribly confusing.
Simon.
The DHCP server has to provide the gateway address. Before DHCP, the
client has no gateway. To send DHCPACCEPT, the client has to send a
packet to the DHCP server, and if it isn't in the same subnet, the
gateway must be used.
What I was working toward is what Simon suggested: run a DHCP relay
