Search found 7 matches
- Sat Aug 18, 2018 2:58 am
- Forum: General Discussion
- Topic: Weird WiFi disconnect issues
- Replies: 0
- Views: 2678
Weird WiFi disconnect issues
I have a few boards all with ESP32 WROOM modules on them. There is a weird issue I'm noticing with one of the chips, it seems that it is unable to connect to any SoftAPs created by the other modules. It can however connect to a normal wifi access point and the other modules can connect to this parti...
- Wed Jul 11, 2018 4:26 am
- Forum: General Discussion
- Topic: Interface addresses in APSTA mode
- Replies: 4
- Views: 6013
Re: Interface addresses in APSTA mode
Okay, so I've been digging into the tcpip_adapter source. This is the set_ip_info function I'm calling esp_err_t tcpip_adapter_set_ip_info(tcpip_adapter_if_t tcpip_if, tcpip_adapter_ip_info_t *ip_info) { struct netif *p_netif; tcpip_adapter_dhcp_status_t status; TCPIP_ADAPTER_IPC_CALL(tcpip_if, 0, i...
- Wed Jul 11, 2018 3:58 am
- Forum: General Discussion
- Topic: Interface addresses in APSTA mode
- Replies: 4
- Views: 6013
Re: Interface addresses in APSTA mode
Just realised that I removed the wrong line. I tried starting and stopping both client and server before posting this. The actual code I ran was: ESP_ERROR_CHECK(tcpip_adapter_dhcps_stop(TCPIP_ADAPTER_IF_AP)); //ESP_ERROR_CHECK(tcpip_adapter_dhcpc_stop(TCPIP_ADAPTER_IF_STA)); tcpip_adapter_ip_info_t...
- Wed Jul 11, 2018 2:37 am
- Forum: General Discussion
- Topic: Interface addresses in APSTA mode
- Replies: 4
- Views: 6013
Interface addresses in APSTA mode
Hi all, I am running with wifi initialised in APSTA mode currently. What I'm trying to do is setup the station and softAP interface with different IP addresses in different subnets when the Station has connected to an AP. So what happens is the Station connects to its network, then the AP is reconfi...
- Thu May 03, 2018 4:51 am
- Forum: General Discussion
- Topic: Using LWIP Raw API
- Replies: 8
- Views: 15266
Re: Using LWIP Raw API
@kolban
I wanted to implement my own protocols that handled forwarding and routing packets from one interface to another (STA -> AP) and vice versa via callbacks from the API, as opposed to waiting for the data to pass through the whole stack and sending it back out another socket.
I wanted to implement my own protocols that handled forwarding and routing packets from one interface to another (STA -> AP) and vice versa via callbacks from the API, as opposed to waiting for the data to pass through the whole stack and sending it back out another socket.
- Wed May 02, 2018 11:22 am
- Forum: General Discussion
- Topic: Using LWIP Raw API
- Replies: 8
- Views: 15266
Re: Using LWIP Raw API
Hi Angus,
Ahh yes I guess this makes sense. The netconn API is definitely the way to go.
I've found the LWIP implementation in regards to ESP IDF to be sparsely available. Does it mention anywhere about this API not being supported?
Ahh yes I guess this makes sense. The netconn API is definitely the way to go.
I've found the LWIP implementation in regards to ESP IDF to be sparsely available. Does it mention anywhere about this API not being supported?
- Wed May 02, 2018 6:22 am
- Forum: General Discussion
- Topic: Using LWIP Raw API
- Replies: 8
- Views: 15266
Using LWIP Raw API
Hi, I'm attempting to implementing protocol using TCP and would like to use to the LwIP Raw API. Apart from this http://lwip.wikia.com/wiki/Raw/TCP lwip specific wiki page I can't find any documentation that talks about using the Raw API from within the ESP IDF. I am wondering what the process is in...