OpenWrt Forum Archive

Topic: Problem with stability as WLAN client and AP

The content of this topic has been archived on 12 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hello,

version is CHAOS CALMER (15.05, r46767)

I have a setup as follows:

Internet <-> provider-router <> LAN <-> TP-Link (stock fw) <-> WLAN <-> TP-Link (owrt) <-> WLAN <-> guest network

TP-Link all = TL-WR1043ND V2

The main config points are:

/etc/config/network

config interface 'lan'
        option ifname 'eth1'
        option force_link '1'
        option type 'bridge'
        option proto 'static'
        option ipaddr '192.168.33.198'
        option netmask '255.255.255.0'
        option ip6assign '60'
        option gateway '192.168.0.1'
        option dns '192.168.0.1'

config interface 'wan'
        option ifname 'eth0'
        option proto 'dhcp'

config interface 'wwan'
        option proto 'dhcp'

config interface 'stabridge'
        option proto 'relay'
        option network 'lan wwan'
        option ipaddr '192.168.0.21'

config interface 'guests'
        option proto 'static'
        option ipaddr '10.55.0.1'
        option netmask '255.255.255.0'


/etc/config/wireless

config wifi-device 'radio0'
        option type 'mac80211'
        option hwmode '11g'
        option path 'platform/qca955x_wmac'
        option htmode 'HT20'
        option country '**'
        option txpower '20'
        option channel '1'
        option disabled '0'

config wifi-iface
        option device 'radio0'
        option network 'wwan'
        option mode 'sta'
        option ssid 'MainRemoteSID'
        option encryption 'psk2+ccmp'
        option key '****'

config wifi-iface
        option device 'radio0'
        option mode 'ap'
        option ssid 'guestsSID'
        option encryption 'psk2+ccmp'
        option isolate '1'
        option network 'guests'
        option key '***'
        option macfilter 'deny'
        list maclist '**:**:**:**:**:**'


For testing purpose i disabled the firewall.

As a client in the guests-wlan using the internet this setup does work for a
certain, unpredictable, time. Suddenly it stops working as follows:

As client in the guests-wlan:
* I can not access the internet
* I can not access the router itself (.21)
* but I can access the LAN (.1 etc.)

As client in the LAN:
* I can not acces the router itself (.21)

Needless to say under normal conditions everything said above
does work.

A reboot of the TP-Link (owrt) does help but also a reboot of the other
TP-Link (stock fw) does help.

For the time it stops working I get no messages in system oder kernel
log. Everything looks normal.

Regarding this problem I made 2 cron jobs to restart the router in
the night and afternoon but this does not help.

Could someone help me with this problem or point me in a cerntain
direction?

Thanks in advance,
regards
CD

Maybe this has also something to do with DNS. Today was the first
day where I observed:

openwrt .21 accessible from the LAN but not from the guests wlan.
A client in the guests wlan can access the internet an the LAN.
A ping from the router itself: ping: bad address 'dev.openwrt.org'.

After restarting the device everything works as expected.

Any hints?

Regards,
CD

Once again me:

Regarding my last post i found out:

ping localhost or 127.0.0.1 100% lost

ping 192.168.0.1 ist "normal" 1.7 to 2.6ms

traceroute to 192.168.0.1 needs really long (6-9 seconds) to
output a message (it is only one hop ...) output is:
1  192.168.0.1 (192.168.0.1)  1.741 ms  1.751 ms  2.068 ms

after a

root@XXX:/tmp# wifi

everything works normal again. ?!?

Probably the DNS configuration.

N.B. - wifi restarts the service

Thanks for your answer.

DNS maybe influenced but I think the cause is another.
A ping or traceroute to an IP in the lan should not suffer
from wrong DNS.

I restarted the box, pinged 127.0.0.1 - pass
After about one hour ping to 127. - 100% loss!

Current, all other things I wrote work normaly but I think
here lies the problem.

So I restarted one daemon after the other:
dnsmasq restart - 100% loss!
firewall restart (all rules accept!) - 100% loss!
odhcpd restart - 100% loss!
relayd restart - !?!? - 0% loss!

so relayd is the problem or causes a restart of a daemon
which produces this problem.

What could I test or look for to get this working?

O.k. I try it the other way round:

What could be the cause if i can not ping 127.0.0.1
after a certain, unpredictable, amount of time.

Thanks,

Have exactly the same issue. Sometimes after a couple of hours, mostly after several days.
CHAOS CALMER (15.05, r46767)

I really like mesh mode instead of AP-STA for in-house links where you have control of both routers.

relayd in particular is something to avoid if at all possible.

(Last edited by mk24 on 29 Nov 2016, 16:39)

The discussion might have continued from here.