[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lwip-users] LWIP/STM32/Lan8720A - won't work with wifi bridge

From: Ben Birch
Subject: Re: [lwip-users] LWIP/STM32/Lan8720A - won't work with wifi bridge
Date: Thu, 12 May 2016 14:37:54 +1200

Hi, thanks for the response. 

Have learnt a bit about the perils of using an access point in 'client' mode/wireless bridge. Apparently (from openwrt, best explanation: https://wiki.openwrt.org/doc/howto/clientmode#bridgedclientmodeissues) 802.11 doesn't nicely handle MACs across more than 1 access point. Now got two additional wireless access points (TPlink 801nd and 701nd) set up one with master and other as slave in 'WDS' mode - this properly handles MACs and now any device plugged into the slave AP is properly acting with regards to dhcp and so on. 

I had managed some success behind the original setup if I set my board up to 'receive all' ie MAC filtering in hardware disabled. This would then happily work so long as I set a static IP as DHCP responses still weren't getting passed back. Now I have the above wireless AP problem solved I have disabled receive all, back to default HAL driver settings.

I am now focussing back on LWIP - device is pingable and a very simple single page web server (using netconn API) is working fine. Only issue I'm having now is a cyclical ping response - every 6 pings increase in value ie:
10/22/29/57/70/88/7/22/38/45/68/78. I can't see any reason in my code - freeRTOS tasks ethif is running at highest priority, and cpu usage is stable at about 21%.

On Thu, May 12, 2016 at 2:59 AM, Sergio R. Caprile <address@hidden> wrote:
Please post a capture file of the non-working scenario and I'll try to help with the networking stuff.
Try to actually describe what you have and what you do in terms of lwIP API function calls, some of us don't have a clue on vendor kits.
If you are "getting the IP address of the PC", either the server is nuts or the "bridge" is not bridging but masquerading, acting as a proxy and sending your requests as his. You should be able to know what it does and configure it accordingly. If it bridges, your MAC goes out on your request and you get assigned an IP. If it masquerades, usually that also means different IP networks, routing. You either run your own DHCP server on your internal interface or assign fixed addresses.
What is a TP-Link access point in 'client' mode ? Is it a wireless bridge ? Have you captured traffic in both ends to actually known what is going on and why it is notr working ? The most efficient way to solve networking problems is by looking at network traffic (after checking the socket light, the cable is in the socket, and issuing a couple pings...)

lwip-users mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]