Nope, the problem persists.
I'm starting to think it might be some kind of problem with the packet's routing over the kernel.
I started a dhcpd daemon just to make sure I was not screwing some kind of ip assignment, my config looks like this:
option routers 192.168.128.1;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.128.255;
option netbios-name-servers 192.168.128.1;
default-lease-time 86400;
max-lease-time 86400;
authoritative;
subnet 192.168.128.0 netmask 255.255.255.0 {
range 192.168.128.100 192.168.128.200;
}
I started the daemon with dhcpd wlan0 (and the leases file exists). No errors seem to show up.
Then, in my client (linked with wpa_supplicant) I run dhclient wlan0 and it tries to send messages but none of them arrive to my ap. I saw in tcpdump that it sends packets to 255.255.255.255 but they get not logged in my ap's tcdump... In the end it said that no DHCPOFFERS where received.
Also, as I said, if I ping from the AP to the client ping requests do arrive, but the reply from the client to the AP does not arrive to the AP. That's why I'm starting to think that the problem is that my ap is rejecting or dropping packets.
I don't know how to check if that's my problem. As my AP is opensuse I rechecked in yast that my firewall is disabled, but as far as I know there could be other kind of firewalls like iptables and configuration files to reject connections and packets, but I don't know how to check and change those. Any ideas?
If I can I'll try to do the same with another computer as AP to see if the problem is a misconfiguration somewhere.


