Hi Gerd, I don’t know why the content is not received in the mail list. It is shown correctly in the forum post here : http://voyage-linux.34677.n3.nabble.com/DHCP-server-not-working-using-dnsmasq-config-and-nat-sh-scripts-td4026374.html However, I tried with Windows, Linux, Android and even SmartTV clients :) none of them gets an IP address. The thing that bugs me is that even if I set the manual IP on the client, I will never reach the gateway on the AP. I am copy pasting the files so the mail list can read: /etc/network/interfaces.d/wlan0.conf auto wlan0 iface wlan0 inet static address 192.168.1.247 netmask 255.255.255.0 gateway 192.168.1.1 dns-nameservers 192.168.1.1 80.58.61.250 #wpa-driver wext wpa-ssid My_SSID wpa-psk xxxxxxxxxxxxxxx wpa-key-mgmt WPA-PSK ## for WPA wpa-pairwise TKIP wpa-group TKIP wpa-proto WPA ## for WPA2 #wpa-pairwise CCMP TKIP #wpa-group CCMP TKIP #wpa-proto RSN #wireless-mode Managed /etc/network/interfaces.d/wlan1.conf auto wlan1 iface wlan1 inet static address 192.168.3.1 netmask 255.255.255.0 broadcast 192.168.3.255 hostapd /etc/hostapd/hostapd.wlan1.conf up nat.sh wlan1 wlan0 "192.168.3.0/24" /etc/hostapd/hostapd.wlan1.conf interface=wlan1 driver=nl80211 ssid=testing channel=11 hw_mode=g auth_algs=3 ignore_broadcast_ssid=0 wep_default_key=1 wep_key1="abcde" wep_key_len_broadcast="5" wep_key_len_unicast="5" wep_rekey_period=300 /etc/dnsmasq.more.conf interface=wlan1 dhcp-range=192.168.3.10,192.168.3.250,12h dhcp-leasefile=/var/tmp/dnsmasq.leases iptables --list Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination wlan1-INBOUND all -- anywhere 192.168.3.0/24 wlan1-FORWARD all -- 192.168.3.0/24 anywhere Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain wlan1-FORWARD (1 references) target prot opt source destination ACCEPT all -- 192.168.3.0/24 anywhere Chain wlan1-INBOUND (1 references) target prot opt source destination ACCEPT all -- anywhere 192.168.3.0/24 tail -f /var/log/syslog (on client auth) Aug 10 21:33:27 localhost dnsmasq[3062]: reading /var/run/dnsmasq/resolv.conf Aug 10 21:33:27 localhost dnsmasq[3062]: using nameserver 80.58.61.250#53 Aug 10 21:33:27 localhost dnsmasq[3062]: using nameserver 192.168.1.1#53 Aug 10 21:34:50 localhost hostapd: wlan1: STA 4c:74:03:21:d4:42 IEEE 802.11: authenticated Aug 10 21:34:50 localhost hostapd: wlan1: STA 4c:74:03:21:d4:42 IEEE 802.11: associated (aid 1) Aug 10 21:34:50 localhost hostapd: wlan1: STA 4c:74:03:21:d4:42 RADIUS: starting accounting session 55C91884-00000000 Routing table Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 wlan0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 192.168.3.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan1 > Date: Tue, 11 Aug 2015 19:33:24 +0200 > From: gerd.bit...@web.de > To: cotare...@hotmail.com > Subject: Re: [Voyage-linux] DHCP server not working using dnsmasq config and > nat.sh scripts > > Hi, > > On 08/11/2015 06:41 PM, cotarelo2 wrote: > > Hi :) > > > > I have configured my alix 2d2 running voyage 0.9.5 with two wireless > > interfaces. One is in client mode (wlan0) and the other is in AP mode > > (wlan1). Everything works fine but once the clients are authenticated in the > > AP network they don't get an IP via DHCP and they can't ping any host on the > > network. > > > > These are my configuration files > > > > /etc/network/interfaces.d/wlan0.conf > > > > > > /etc/network/interfaces.d/wlan1.conf > > > > > > /etc/hostapd/hostapd.wlan1.conf > > > > > > /etc/dnsmasq.more.conf > sorry, the content of these files is missing > > > > > > > > So, what happens is when the client authenticates in the AP no DHCP request > > is received. Just in case I am attaching here some logs > if the clients have success associating the WLAN, but no broadcasts are > received by the DHCP servers, the clients get no leased IP adress and > for sure can not ping. Then you should check the clients if they really > are configured to be DHCP clients, and if they really perform DHCP > broadcasts > > > > > > > iptables --list > > > > > > tail -f /var/log/syslog (on client auth) > sorry, no content visible > > > > > > > And my routing table > no content visible. But as DHCP is broadcast based, it works only in one > subnet (without a DHCP proxy). So routing should hardly be the cause of > your prob > > > > > > > > What is wrong here? :confused: > Maybe you should post kind of a picture of your networks and your setup. > And regarding your clients, I believe it's kind of a Linux, may be > Debian. Is this the case ? > > > > > > > > > > -- > > View this message in context: > > http://voyage-linux.34677.n3.nabble.com/DHCP-server-not-working-using-dnsmasq-config-and-nat-sh-scripts-tp4026374.html > > Sent from the Voyage Linux mailing list archive at Nabble.com. > > > > _______________________________________________ > > Voyage-linux mailing list > > Voyage-linux@list.voyage.hk > > http://list.voyage.hk/mailman/listinfo/voyage-linux >
_______________________________________________ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
