Re: Annoying problem with dnsmasq
See release notes on Dnsmasq 2.35 http://freshmeat.net/projects/dnsmasq/?branch_id=1991release_id=239661 OpenBSD-4.0 is due for release very soon and no version of dnsmasq prior to 2.35 will do DHCP on OpenBSD-4.0. /Markus Manuel Ravasio wrote: Hello all. I'm trying to set up a firewall/web-proxy/dns-proxy/dhcp-server box at home, using a quite old i386-based pc (AMD k6-2 300, 256mb RAM, 2x10G IDE disks) and OpenBSD 4.0. OS installation, disk management, additional software installation and configuration... everything went fine. Problems started in configuring dnsmasq: I managed to make dns forwarding work ( I really don't need anything more than standard behaviour), then I created a DHCP range entry: expand-hosts domain=manuel.test dhcp-range=192.168.2.100,192.168.2.200,255.255.255.0,1h I chose to activate dnsmasq on the internal intercace only: interface=pcn1 pcn1,'s IP address is fixed and compatible with the range specified: # ifconfig pcn1 pcn1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr 00:0c:29:af:4f:47 media: Ethernet autoselect (autoselect) inet 192.168.2.11 netmask 0xff00 broadcast 192.168.2.255 inet6 fe80::20c:29ff:feaf:4f47%pcn1 prefixlen 64 scopeid 0x2 I read that creating a dhcp-range entry in /etc/dnsmasq.conf makes dnsmasq start the dhcp service automatically, but alas DHCP server apparently doesn't work: linux and windows clients can't grab IP addresses and other IP information, and netstat doesn't show anything listening on port 67/68. # ps -aux | grep dns nobody 16166 0.0 0.3 520 648 ?? S 12:58PM0:00.00 dnsmasq # netstat -an | grep tcp | grep -v tcp6 tcp0 0 127.0.0.1.53 *.*LISTEN tcp0 0 192.168.2.11.53*.*LISTEN tcp0 0 127.0.0.1.6010 *.*LISTEN tcp0 0 192.168.2.11.22192.168.2.1.48605 ESTABLISHED tcp0 0 *.22 *.*LISTEN What am I missing? Thank you everybody for your kind help. Byee, Manuel
Re: Annoying problem with dnsmasq
Markus Bergkvist wrote: See release notes on Dnsmasq 2.35 http://freshmeat.net/projects/dnsmasq/?branch_id=1991release_id=239661 OpenBSD-4.0 is due for release very soon and no version of dnsmasq prior to 2.35 will do DHCP on OpenBSD-4.0. I'm working on an update of the port to 2.38 Jonathan
Annoying problem with dnsmasq
Hello all. I'm trying to set up a firewall/web-proxy/dns-proxy/dhcp-server box at home, using a quite old i386-based pc (AMD k6-2 300, 256mb RAM, 2x10G IDE disks) and OpenBSD 4.0. OS installation, disk management, additional software installation and configuration... everything went fine. Problems started in configuring dnsmasq: I managed to make dns forwarding work ( I really don't need anything more than standard behaviour), then I created a DHCP range entry: expand-hosts domain=manuel.test dhcp-range=192.168.2.100,192.168.2.200,255.255.255.0,1h I chose to activate dnsmasq on the internal intercace only: interface=pcn1 pcn1,'s IP address is fixed and compatible with the range specified: # ifconfig pcn1 pcn1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr 00:0c:29:af:4f:47 media: Ethernet autoselect (autoselect) inet 192.168.2.11 netmask 0xff00 broadcast 192.168.2.255 inet6 fe80::20c:29ff:feaf:4f47%pcn1 prefixlen 64 scopeid 0x2 I read that creating a dhcp-range entry in /etc/dnsmasq.conf makes dnsmasq start the dhcp service automatically, but alas DHCP server apparently doesn't work: linux and windows clients can't grab IP addresses and other IP information, and netstat doesn't show anything listening on port 67/68. # ps -aux | grep dns nobody 16166 0.0 0.3 520 648 ?? S 12:58PM0:00.00 dnsmasq # netstat -an | grep tcp | grep -v tcp6 tcp0 0 127.0.0.1.53 *.*LISTEN tcp0 0 192.168.2.11.53*.*LISTEN tcp0 0 127.0.0.1.6010 *.*LISTEN tcp0 0 192.168.2.11.22192.168.2.1.48605 ESTABLISHED tcp0 0 *.22 *.*LISTEN What am I missing? Thank you everybody for your kind help. Byee, Manuel
Re: Annoying problem with dnsmasq
On 2/14/07, Manuel Ravasio [EMAIL PROTECTED] wrote: I read that creating a dhcp-range entry in /etc/dnsmasq.conf makes dnsmasq start the dhcp service automatically, but alas DHCP server apparently doesn't work: linux and windows clients can't grab IP addresses and other IP information, and netstat doesn't show anything listening on port 67/68. # ps -aux | grep dns nobody 16166 0.0 0.3 520 648 ?? S 12:58PM0:00.00 dnsmasq # netstat -an | grep tcp | grep -v tcp6 tcp0 0 127.0.0.1.53 *.*LISTEN tcp0 0 192.168.2.11.53*.*LISTEN tcp0 0 127.0.0.1.6010 *.*LISTEN tcp0 0 192.168.2.11.22192.168.2.1.48605 ESTABLISHED tcp0 0 *.22 *.*LISTEN What am I missing? Not sure about anything else you might be missing, but DHCP uses UDP, not TCP. See if PF is currently blocking traffic to your service(s) also. DS
Re: Annoying problem with dnsmasq
On my OpenWRT router, dnsmasq needs to be told that it is authoritative on dhcp requests with the ``dhcp-authoritative'' keyword in dnsmasq.conf On 2/14/07, Manuel Ravasio [EMAIL PROTECTED] wrote: Hello all. I'm trying to set up a firewall/web-proxy/dns-proxy/dhcp-server box at home, using a quite old i386-based pc (AMD k6-2 300, 256mb RAM, 2x10G IDE disks) and OpenBSD 4.0. OS installation, disk management, additional software installation and configuration... everything went fine. Problems started in configuring dnsmasq: I managed to make dns forwarding work ( I really don't need anything more than standard behaviour), then I created a DHCP range entry: expand-hosts domain=manuel.test dhcp-range=192.168.2.100,192.168.2.200,255.255.255.0,1h I chose to activate dnsmasq on the internal intercace only: interface=pcn1 pcn1,'s IP address is fixed and compatible with the range specified: # ifconfig pcn1 pcn1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr 00:0c:29:af:4f:47 media: Ethernet autoselect (autoselect) inet 192.168.2.11 netmask 0xff00 broadcast 192.168.2.255 inet6 fe80::20c:29ff:feaf:4f47%pcn1 prefixlen 64 scopeid 0x2 I read that creating a dhcp-range entry in /etc/dnsmasq.conf makes dnsmasq start the dhcp service automatically, but alas DHCP server apparently doesn't work: linux and windows clients can't grab IP addresses and other IP information, and netstat doesn't show anything listening on port 67/68. # ps -aux | grep dns nobody 16166 0.0 0.3 520 648 ?? S 12:58PM0:00.00 dnsmasq # netstat -an | grep tcp | grep -v tcp6 tcp0 0 127.0.0.1.53 *.*LISTEN tcp0 0 192.168.2.11.53*.*LISTEN tcp0 0 127.0.0.1.6010 *.*LISTEN tcp0 0 192.168.2.11.22192.168.2.1.48605 ESTABLISHED tcp0 0 *.22 *.*LISTEN What am I missing? Thank you everybody for your kind help. Byee, Manuel -- ID: AF133028 fp:9D6B DC0F CCDA 53FA 3F04 A551 BC23 374D AF13 3028
Re: Annoying problem with dnsmasq
Darren Spruell escreveu: On 2/14/07, Manuel Ravasio [EMAIL PROTECTED] wrote: I read that creating a dhcp-range entry in /etc/dnsmasq.conf makes dnsmasq start the dhcp service automatically, but alas DHCP server apparently doesn't work: linux and windows clients can't grab IP addresses and other IP information, and netstat doesn't show anything listening on port 67/68. # ps -aux | grep dns nobody 16166 0.0 0.3 520 648 ?? S 12:58PM0:00.00 dnsmasq # netstat -an | grep tcp | grep -v tcp6 tcp0 0 127.0.0.1.53 *.*LISTEN tcp0 0 192.168.2.11.53*.*LISTEN tcp0 0 127.0.0.1.6010 *.*LISTEN tcp0 0 192.168.2.11.22192.168.2.1.48605 ESTABLISHED tcp0 0 *.22 *.*LISTEN What am I missing? Not sure about anything else you might be missing, but DHCP uses UDP, not TCP. See if PF is currently blocking traffic to your service(s) also. DS Don't know why you would prefer dnsmasq when the default installation of OpenBSD already have both ISC dhcpd and bind daemons. I use then, rather then having to install a package and configure it. Also, if you want a caching nameserver only, simply putting named_flags= on /etc/rc.conf.local and opening requests to your internal net only, on both TCP and UDP port 53, will give a fully functional recursive dns. And the configuration of /etc/dhcpd.conf is the same as ISC dhcpd. There is even an example provided. Also, from the ISC dhcpd readme, http://www.isc.org/sw/dhcp/dhcpv3-README.php#firewall, you must let traffic coming from 0.0.0.0 port 68 udp to 255.255.255.255 port 67 for dhcp queries and also from your internal net port 68 udp to your firewall internal ip port 68 udp for dhcp renews. Try opening up these ports on your internal interface. My regards, -- Giancarlo Razzolini Linux User 172199 Red Hat Certified Engineer no:804006389722501 Moleque Sem Conteudo Numero #002 Slackware Current OpenBSD Stable Ubuntu 6.10 Edgy Eft Snike Tecnologia em Informatica 4386 2A6F FFD4 4D5F 5842 6EA0 7ABE BBAB 9C0E 6B85 [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
