<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi Gerd,<div><br></div><div>I don’t know why the content is not received in the mail list. It is shown correctly in the forum post here : <a href="http://voyage-linux.34677.n3.nabble.com/DHCP-server-not-working-using-dnsmasq-config-and-nat-sh-scripts-td4026374.html">http://voyage-linux.34677.n3.nabble.com/DHCP-server-not-working-using-dnsmasq-config-and-nat-sh-scripts-td4026374.html</a></div><div><br></div><div>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.</div><div><br></div><div>I am copy pasting the files so the mail list can read:</div><div><br></div><div>/etc/network/interfaces.d/wlan0.conf
<br><pre>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
</pre><br>/etc/network/interfaces.d/wlan1.conf
<br><pre>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"
</pre><br>/etc/hostapd/hostapd.wlan1.conf
<br><pre>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
</pre><br>/etc/dnsmasq.more.conf
<br><pre>interface=wlan1
dhcp-range=192.168.3.10,192.168.3.250,12h
dhcp-leasefile=/var/tmp/dnsmasq.leases</pre><br>iptables --list
<br><pre>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
</pre><br>tail -f /var/log/syslog (on client auth)
<br><pre>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
</pre><br>Routing table<br><pre>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
</pre><div><br></div></div><div><br></div><div><br><div><div>On 11 Aug 2015, at 19:33, G.Bitzer <<a href="mailto:gerd.bitzer@web.de">gerd.bitzer@web.de</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi,<br><br>On 08/11/2015 06:41 PM, cotarelo2 wrote:<br><blockquote type="cite">Hi :)<br><br>I have configured my alix 2d2 running voyage 0.9.5 with two wireless<br>interfaces. One is in client mode (wlan0) and the other is in AP mode<br>(wlan1). Everything works fine but once the clients are authenticated in the<br>AP network they don't get an IP via DHCP and they can't ping any host on the<br>network.<br><br>These are my configuration files<br><br>/etc/network/interfaces.d/wlan0.conf<br><br><br>/etc/network/interfaces.d/wlan1.conf<br><br><br>/etc/hostapd/hostapd.wlan1.conf<br><br><br>/etc/dnsmasq.more.conf<br></blockquote>sorry, the content of these files is missing<br><br><br><blockquote type="cite"><br><br>So, what happens is when the client authenticates in the AP no DHCP request<br>is received. Just in case I am attaching here some logs<br></blockquote>if the clients have success associating the WLAN, but no broadcasts are<br>received by the DHCP servers, the clients get no leased IP adress and<br>for sure can not ping. Then you should check the clients if they really<br>are configured to be DHCP clients, and if they really perform DHCP<br>broadcasts<br><br><br><br><blockquote type="cite"><br>iptables --list<br><br><br>tail -f /var/log/syslog (on client auth)<br></blockquote>sorry, no content visible<br><br><blockquote type="cite"><br><br>And my routing table<br></blockquote>no content visible. But as DHCP is broadcast based, it works only in one<br>subnet (without a DHCP proxy). So routing should hardly be the cause of<br>your prob<br><br><br><blockquote type="cite"><br><br>What is wrong here? :confused:<br></blockquote>Maybe you should post kind of a picture of your networks and your setup.<br>And regarding your clients, I believe it's kind of a Linux, may be<br>Debian. Is this the case ?<br><br><br><blockquote type="cite"><br><br><br>--<br>View this message in context: <a href="http://voyage-linux.34677.n3.nabble.com/DHCP-server-not-working-using-dnsmasq-config-and-nat-sh-scripts-tp4026374.html">http://voyage-linux.34677.n3.nabble.com/DHCP-server-not-working-using-dnsmasq-config-and-nat-sh-scripts-tp4026374.html</a><br>Sent from the Voyage Linux mailing list archive at <a href="http://Nabble.com">Nabble.com</a>.<br><br>_______________________________________________<br>Voyage-linux mailing list<br><a href="mailto:Voyage-linux@list.voyage.hk">Voyage-linux@list.voyage.hk</a><br>http://list.voyage.hk/mailman/listinfo/voyage-linux<br></blockquote><br><br></blockquote></div><br></div></body></html>