Hi Folks,
I have a basic setup for DHCP relay across VLANS in DNSMASQ.
My configuration file looks like:
bogus-priv
interface=ens160
log-dhcp
dhcp-range=10.168.102.100,10.168.102.150,255.255.255.0,12h
The client and server are running on a VMs in separate VLANS. DHCP requests
appear to be
Vlan1002
Single host running ESXi connected to single router.
Take Care
Jason
> On Apr 28, 2017, at 5:36 PM, Simon Kelley wrote:
>
> On 27/04/17 22:02, Jason Kary wrote:
>> Hi Folks,
>>
>> I have a basic setup for DHCP relay across VLANS in DNSMASQ.
>>
&g
Sneddon | Senior Principal Software Engineer
> dsned...@redhat.com | redhat.com/openstack
> dsneddon:irc| @dxs:twitter
>
> On 04/27/2017 02:02 PM, Jason Kary wrote:
>> Hi Folks,
>>
>> I have a basic setup for DHCP relay across VLANS in DNSMASQ.
Hi Chris,
Thank you for the update. We are running version 2.66
Take Care
Jason
> On Sep 22, 2017, at 8:44 AM, Chris Novakovic wrote:
>
> On 22/09/2017 13:42, Chris Novakovic wrote:
>> If you're using 2.76,
>
> It's implied by my later comment, but I should also clarify that this
> bug affect
rride: 0AA86601
Link selection: 10.168.102.0
End Option
Padding
Pls find my dnsmasq.conf as follows:
Take Care
Jason
> On Sep 25, 2017, at 4:10 PM, Jason Kary (jkary) wrote:
>
> Hi,
>
> Pls find my dnsmasq.conf as follows:
>
>
>
> Take Care
> Jaso
Information Option
>Length: 44
>Value: 010A01080006004C4F2A002F020658AC78B138E1970A0062...
>Agent Circuit ID: 01080006004C4F2A002F
>Agent Remote ID: 58AC78B138E1
>DHCPv4 Virtual Subnet Selection: 006262742D76786C616E
>Server Identif
PM, Jason Kary wrote:
>
> Hi Chris,
>
> I cloned the GIT repository and tested with version 2.78test2-gb697fbb
>
> I’m still seeing the server fail to respond to the request message:
>
> Frame 40189 (388 bytes on wire, 388 bytes captured)
>Arrival Time: Sep 25, 2017
Hello,
Does anyone have an issue if we make the change below?
If we keep the code then at the very least the code should log why we are
failing.
Take Care
Jason
> On Sep 28, 2017, at 4:44 PM, Jason Kary wrote:
>
> Hi Folks,
>
> I was able to fix the problem by removing the
Hi Folks,
I’m working on getting DNSMASQ to work with IP RELAY in a VxLAN environment.
Using tcpdump we were able to trace a DHCP relay request to the ‘request’
message. It appears the server is not sending an DHCP ACK message.
Here is a tcpdump of the request message:
11:18:56.868214 IP (