Re: [Dnsmasq-discuss] Listen to two interfaces?
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 ### 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 si...@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: marku...@jabber.ccc.de
Re: [Dnsmasq-discuss] Listen to two interfaces?
On Tue, Nov 30, 2010 at 10:39 AM, Markus Bergholz marku...@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. Until you fix routing, the kernel may use the wrong interface to transmit packets generated by dnsmasq, which means devices won't get leases. 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 si...@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: marku...@jabber.ccc.de ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] Listen to two interfaces?
On Tue, Nov 30, 2010 at 5:00 PM, richardvo...@gmail.com
richardvo...@gmail.com wrote:
On Tue, Nov 30, 2010 at 10:39 AM, Markus Bergholz marku...@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 si...@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: marku...@jabber.ccc.de
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
--
icq: 167498924
XMPP|Jabber: marku...@jabber.ccc.de
Re: [Dnsmasq-discuss] Listen to two interfaces?
On Tue, Nov 30, 2010 at 12:52:08PM -0600, Frederick C. Damen wrote: Query: How does dnsmasq associate the interface with the dhcp-range? I do not detect an explicit connection, i.e. tags shared between config entries. I assume the implicit association is that the IP address assigned to the interface outside of dnsmasq, e.g. ifconfig, needs to be within the address range within dhcp-range Within the netblock, yes, but it should not be within the range itself. Refer to my example below: # eth0 being 192.168.4.1/24 interface=eth0 dhcp-range=192.168.4.128,192.168.4.191,255.255.255.0,12h 192.168.4.1 and the entire range are within 192.168.4.0/24. # wlan0 being 192.168.5.1/24 interface=wlan0 dhcp-range=192.168.5.64,192.168.5.127,255.255.255.0,12h 192.168.5.1 and the entire range are within 192.168.5.0/24. assigned within dnsmasq. (and dnsmasq marks the interfaces IP address as used). What happens to the dhcp-range that does not include one of the interfaces ip addresses? I don't know, but I would expect it to be logged as an error. -- Offlist mail to this address is discarded unless /dev/rob0 or not-spam is in Subject: header
Re: [Dnsmasq-discuss] Handling unknown RTYPEs and querying for version...
2010/11/29 Simon Kelley si...@thekelleys.org.uk: On 29/11/10 19:30, Nicholas Weaver wrote: RFC3597 specifically states how they should be handled (as opaque binary data which is passed unchanged), but almost all fail to process our request for a made-up type (type # 169). a) Could someone run Netalyzr against a NAT running the latest Dnsmasq code and send me the result link? OK, I just did this, and got the error. Your NAT has a built-in DNS proxy. We sent it a DNS request and our server received it from 62.253.128.100. Some or all specialized DNS types checked are not properly interpreted by the NAT's DNS proxy. The following tested queries were blocked/failed: * RTYPE=169 (deliberately unknown) records. 62.253.128.100 is cmbg-dnsany-1.server.virginmedia.net. which makes sense, as my ISP is viginmedia. I'm very sure that a query for RTYPE=169 will have been forwarded Ok by dnsmasq, so maybe the problem is at the ISP end? I would also guess it's not only a problem of broken dns proxys, but also cleaning provider server. dnsmasq is fine. From an dnsmasq 2.52 with it's own powerdns recurser, i get all green lights (OK, besides that i filter ad.doubleklick.net, but who wants to talk to _them_, anyway). [snip] Cheers, Simon. Greetings Jan -- Murphy's Law of Combat Rule #3: Never forget that your weapon was manufactured by the lowest bidder
Re: [Dnsmasq-discuss] Handling unknown RTYPEs and querying for version...
On 30/11/10 19:49, Jan Seiffert wrote: I would also guess it's not only a problem of broken dns proxys, but also cleaning provider server. dnsmasq is fine. From an dnsmasq 2.52 with it's own powerdns recurser, i get all green lights (OK, besides that i filter ad.doubleklick.net, but who wants to talk to _them_, anyway). Yes, that seems to be the case. My ISPs DNS servers return a NOTIMP RCODE for the RTYPE=169 query. ISP is Viginmedia in the UK. Simon.
