ESP32 Border Router using esp_wifi_ap

I have already created another topic on this problem called Border Router OTA using WiFi, which was getting rather long and if I continue that thread, it might deviate from what I initially asked. So I wanted to raise a new topic to ask this question.

Since I do not have IPv6 on my WiFi network, I am currently attempting a workaround by making an ESP32 AP. I setup a Linux (Ethos) ā†” ESP32 (WiFi_AP) router using the same gnrc_border_router example, to which other ESP32 boards running the actual WiFi<->SLIP router from my original setup can be connected. I am not sure if this will work and Iā€™d appreciate some suggestions.

I added a line in the Makefile.board.dep of the gnrc_border_router example to setup an Ethos<->WiFi router.

@@ +7,5
ifeq (,$(filter native,$(BOARD)))
  ifeq (slip,$(UPLINK))
    USEMODULE += slipdev_stdio
  else ifeq (ethos,$(UPLINK))
    USEMODULE += stdio_ethos
   +USEMODULE += esp_wifi_ap
  else ifeq (wifi,$(UPLINK))
    ifneq (,$(filter esp32 esp8266,$(CPU)))
      USEMODULE += esp_wifi

I can see the following ifconfig output on ESP32 (AP)

Iface  8  HWaddr: 24:6F:28:95:D1:19  Channel: 0  Link: up 
          L2-PDU:1500  MTU:1500  HL:64  RTR  
          RTR_ADV  
          Source address length: 6
          Link type: wireless
          inet6 addr: 2001:db8::266f:28ff:fe95:d119  scope: global  VAL
          inet6 group: ff02::2
          inet6 group: ff02::1
          inet6 group: ff02::1:ff95:d119
          
Iface  9  HWaddr: 66:91:6E:95:1E:58 
          L2-PDU:1500  MTU:1500  HL:64  RTR  
          Source address length: 6
          Link type: wired
          inet6 addr: fe80::6491:6eff:fe95:1e58  scope: link  VAL
          inet6 addr: fe80::2  scope: link  VAL
          inet6 group: ff02::2
          inet6 group: ff02::1
          inet6 group: ff02::1:ff95:1e58
          inet6 group: ff02::1:ff00:2

Using the suggested Makefile changes from the topic Border Router OTA using WiFi, I connected another ESP32 to the AP, setup the ESP32-Nucleo connection and got the same outputs as before.

ESP32 (Router):

2023-10-19 14:32:21,072 # ifconfig
2023-10-19 14:32:21,077 # Iface  7  HWaddr: A4:CF:12:9A:2D:C8  Channel: 1  Link: up 
2023-10-19 14:32:21,081 #           L2-PDU:1500  MTU:1500  HL:64  RTR  
2023-10-19 14:32:21,084 #           Source address length: 6
2023-10-19 14:32:21,086 #           Link type: wireless
2023-10-19 14:32:21,092 #           inet6 addr: fe80::a6cf:12ff:fe9a:2dc8  scope: link  VAL
2023-10-19 14:32:21,095 #           inet6 group: ff02::2
2023-10-19 14:32:21,097 #           inet6 group: ff02::1
2023-10-19 14:32:21,101 #           inet6 group: ff02::1:ff9a:2dc8
2023-10-19 14:32:21,102 #           
2023-10-19 14:32:21,103 # Iface  8 
2023-10-19 14:32:21,107 #           Long HWaddr: 66:11:DA:1D:BE:FC:7E:AF 
2023-10-19 14:32:21,110 #           MTU:65535  HL:64  RTR  
2023-10-19 14:32:21,112 #           RTR_ADV  
2023-10-19 14:32:21,114 #           Link type: wired
2023-10-19 14:32:21,120 #           inet6 addr: fe80::6411:da1d:befc:7eaf  scope: link  VAL
2023-10-19 14:32:21,126 #           inet6 addr: 2001:db8::6411:da1d:befc:7eaf  scope: global  VAL
2023-10-19 14:32:21,129 #           inet6 group: ff02::2
2023-10-19 14:32:21,131 #           inet6 group: ff02::1
2023-10-19 14:32:21,135 #           inet6 group: ff02::1:fffc:7eaf

Nucleo (RIOT Node):

2023-10-19 14:23:00,959 # ifconfig
2023-10-19 14:23:00,963 # Iface  4  HWaddr: EA:C8:61:14:DB:02  Link: down 
2023-10-19 14:23:00,967 #           L2-PDU:1500  MTU:1500  HL:64  RTR  
2023-10-19 14:23:00,970 #           Source address length: 6
2023-10-19 14:23:00,973 #           Link type: wired
2023-10-19 14:23:00,979 #           inet6 addr: fe80::e8c8:61ff:fe14:db02  scope: link  VAL
2023-10-19 14:23:00,982 #           inet6 group: ff02::2
2023-10-19 14:23:00,984 #           inet6 group: ff02::1
2023-10-19 14:23:00,988 #           inet6 group: ff02::1:ff14:db02
2023-10-19 14:23:00,989 #           
2023-10-19 14:23:00,990 # Iface  5 
2023-10-19 14:23:00,994 #           Long HWaddr: AE:97:D8:31:A6:13:BD:6E 
2023-10-19 14:23:00,997 #           MTU:65535  HL:64  RTR  
2023-10-19 14:23:00,998 #           
2023-10-19 14:23:01,001 #           Link type: wired
2023-10-19 14:23:01,007 #           inet6 addr: fe80::ac97:d831:a613:bd6e  scope: link  VAL
2023-10-19 14:23:01,013 #           inet6 addr: 2001:db8::ac97:d831:a613:bd6e  scope: global  VAL
2023-10-19 14:23:01,016 #           inet6 group: ff02::2
2023-10-19 14:23:01,018 #           inet6 group: ff02::1
2023-10-19 14:23:01,022 #           inet6 group: ff02::1:ff13:bd6e
2023-10-19 14:23:01,023 #

I am able to ping the ESP32 router which is connected to the PC (Ethos<->WiFi). I need to know how to setup a route so that I can ping the Nucleo node from the Linux PC. The end goal is actually to trigger a SUIT update on the node, but initially I want to know if this is going to work.