[Dnsmasq-discuss] Listen to two interfaces?

[Markus Bergholz]

Ok, i guess i got now a correct dnsmasq setup with

dhcp-range=eth0,192.168.1.2,192.168.1.255,255.255.255.0,12h
dhcp-range=wlan0,192.168.2.2,192.168.2.255,255.255.255.0,12h

with eth0 it works fine, but with wlan0, the DHCPOFFER don't received
at the client :-/ and i've testet various, no one get an ip...


On Tue, Nov 30, 2010 at 5:12 PM, Markus Bergholz <markuman at gmail.com> wrote:
> On Tue, Nov 30, 2010 at 5:00 PM, richardvoigt at gmail.com
> <richardvoigt at gmail.com> wrote:
>> On Tue, Nov 30, 2010 at 10:39 AM, Markus Bergholz <markuman at gmail.com> wrote:
>>> Ok, i've did this
>>>
>>>
>>> ###
>>> log-queries
>>> interface=eth0
>>> dhcp-range=192.168.1.2,192.168.1.99,12h
>>> dhcp-option=3,192.168.1.1
>>> resolv-file=/etc/resolv.conf.dnsmasq
>>> listen-address=127.0.0.1
>>> bind-interfaces
>>> cache-size=150
>>> interface=wlan0
>>> dhcp-range=192.168.1.102,192.168.1.199,12h
>>> dhcp-option=3,192.168.1.101
>>> ###
>>
>> What is the IP address and netmask of each interface (eth0 and wlan0)?
>>
>> Right now, it looks as if you are trying to use the same address block
>> on two different networks, which breaks routing.  In such a scenario,
>> you must use bridging.  Or, you can use different subnets for devices
>> connected via eth0 and those connected via wlan0, and route between
>> them.
>
> thx for your fast reply
>
> i want
> dhcp-range=192.168.1.2,192.168.1.1,255.255.255.0,12h
> for both. but everytime i try to bridge, the hole network on server
> side don't work anymore.
> so i want to try without bridge.
> could
> interface=eth0
> dhcp-range=192.168.1.2,192.168.1.1,255.255.0.0,12h
> interface=wlan0
> dhcp-range=192.168.2.2,192.168.2.1,255.255.0.0,12h
> work?
>
>
>> Until you fix routing, the kernel may use the wrong interface to
>> transmit packets generated by dnsmasq, which means devices won't get
>> leases.
>>
>
> hm what did you mean? kernel on server or client?
> on server they are grounded i guess
>
> # less /etc/udev/rules.d/10-network.rules
> SUBSYSTEM=="net", ATTR{address}=="00:27:19:f2:c1:20", NAME="eth1"
> SUBSYSTEM=="net", ATTR{address}=="00:0d:b9:0d:13:a0", NAME="eth0"
> ...
>
>
>>>
>>> and disable for testing shorewall, it seems that the server deliver
>>> one ip adress from dnsmasq, but it don't receive at the client
>>> http://nopaste.info/73551f0a00.html
>>> in the messages.log from the client dhcpcd is just mentioned in two line.
>>> dhcpcd[1315]: version 5.2.8 starting
>>> dhcpcd[1315]: wlan0: broadcasting for a lease
>>>
>>> thats all...any clues?
>>>
>>> greetings
>>> markus
>>>
>>> On Mon, Nov 29, 2010 at 10:48 PM, Simon Kelley <simon at thekelleys.org.uk> wrote:
>>>> On 28/11/10 18:59, Markus Bergholz wrote:
>>>>>
>>>>> Hi
>>>>> is it possible that dnsmasq is listning to two interfaces (without
>>>>> bridge-utils!), so that they using same dhcp server?
>>>>
>>>> It is.
>>>>>
>>>>> That what my config atm looks like.
>>>>>
>>>>> interface=eth0
>>>>> listen-address=127.0.0.1
>>>>> bind-interfaces
>>>>> dhcp-range=192.168.1.2,192.168.1.99,12h
>>>>> dhcp-option=3,192.168.1.1
>>>>> resolv-file=/etc/resolv.conf.dnsmasq
>>>>> log-queries
>>>>> cache-size=150
>>>>>
>>>>> just interface=eth0,wlan0
>>>>> don't work for me, the client don't get an ip-adress.
>>>>>
>>>> You need two dhcp-range lines,  for each interface and network.
>>>>
>>>> HTH
>>>>
>>>> Simon.
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> icq: 167498924
>>> XMPP|Jabber: markuman at jabber.ccc.de
>>>
>>> _______________________________________________
>>> Dnsmasq-discuss mailing list
>>> Dnsmasq-discuss at lists.thekelleys.org.uk
>>> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
>>>
>>
>
>
>
> --
> icq: 167498924
> XMPP|Jabber: markuman at jabber.ccc.de
>



-- 
icq: 167498924
XMPP|Jabber: markuman at jabber.ccc.de