Thanks for reply.
I have just tried this.
conflg:
#dhcp-range=tag:vlan-2-port-16,10.1.2.2,10.1.2.245,255.255.255.0,10.1.2.255,10m
#dhcp-range=tag:#vlan-2-port-16,172.16.33.2,172.16.33.249,255.255.255.0,10m
dhcp-host=48:5b:39:36:a2:73,10.1.2.100
Absolutely nothing happened with such config,
Hi,
dhcp-relay is very much possible with dnsmasq. the keyword is dhcp proxy
Also, when you setup the ranges, I think you are supposed to use the keyword
'proxy'.
I don;t think thats quite well documented in the example conf file.
I remember having seen it in the man page though.
Regards,
Hi Vladimir,
can you more explain your network-setup?
The Problem with dhcp-relay is, that dnsmasq trys to find a address
within the dhcp-relay its ip-address.
So, when the DHCP-Relay have the IP-Address 192.168.0.2/24, dnsmasq trys
to allocate a ip within the dhcp-range 192.168.0.0/24. If
SpiderX wrote:
Thanks for reply.
I have just tried this.
conflg:
#dhcp-range=tag:vlan-2-port-16,10.1.2.2,10.1.2.245,255.255.255.0,10.1.2.255,10m
#dhcp-range=tag:#vlan-2-port-16,172.16.33.2,172.16.33.249,255.255.255.0,10m
dhcp-host=48:5b:39:36:a2:73,10.1.2.100
Absolutely nothing happened
Shantanu Gadgil
I don't understand how dhcp-proxy will help me.
As I understand from man, dhcp-proxy is needed in case I need unicast
dhcp packet from client came through dhcp relay too.
In my situation dnsmasq dont accept even relayed broadcast client packet.
And I have already tried this option
SpiderX wrote:
I think what's happening is that the relay adds its 172 address to
the relayed DHCP packet
Thanks for reply, Simon.
Are you talking about giaddr field?
That's the one.
If no, then there is no any other
172... in the packet:
IP: 172.16.33.50 (1c:bd:b9:9b:68:5c)
On Mon, Sep 12, 2011 at 3:09 PM, Simon Kelley si...@thekelleys.org.uk wrote:
SpiderX wrote:
I think what's happening is that the relay adds its 172 address to
the relayed DHCP packet
Thanks for reply, Simon.
Are you talking about giaddr field?
That's the one.
If no, then there is no
On 09/12/2011 03:16 PM, Jan Psota wrote:
I'm running dnsmasq-2.57 on Linux (Ubuntu 11.04), and am starting two dnsmasq
processes to serve DHCP on two interfaces to VMs I'm running. Initial
packets
(broadcast MAC/broadcast IP) are handled fine, but when it comes time to
renew
and the VMs
Unfortunately using multiple range and interface arguments won't work since I
will need to run 100, with different conf files for each.
Didn't you forget to set bind-interfaces?
--
jasiu
On 09/12/2011 03:54 PM, Jan Psota wrote:
Unfortunately using multiple range and interface arguments won't work since I
will need to run 100, with different conf files for each.
Didn't you forget to set bind-interfaces?
No, I set --bind-interfaces, --listen-address=1.2.3.4 and --interface=br0,
10 matches
Mail list logo
