First- Newbie when it comes to Linux commands and OS…
I just reflashed my Jetson Orin Dev Kit using the latest SDK Manager images and now for some reason the Wifi SSID it used to connect to just fine, its now uable to. I can connect just fine to the other 2 SSID’s I run, but the specific SSID I created for this device its now uable to… Even though I reflashed/reinstalled everything is there a profile or setting somewhere that’s retaining that old configuration or something?
Here is some output from- sudo journalctl -b
Jul 08 14:03:15 localhost.localdomain NetworkManager[1449]: [1783540995.4240] dhcp4 (wlP1p1s0): state changed new lease, address=192.168.43.220, acd pending
Jul 08 14:03:15 localhost.localdomain NetworkManager[1449]: [1783540995.4413] device (wlP1p1s0): IP address 192.168.43.220 cannot be configured because it is already in use in the network by host 04:A7:41:6B:CB:85
Jul 08 14:03:15 localhost.localdomain NetworkManager[1449]: [1783540995.4538] dhcp4 (wlP1p1s0): state changed new lease, address=192.168.43.220, acd conflict
Jul 08 14:03:17 localhost.localdomain systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jul 08 14:03:17 localhost.localdomain systemd[1]: NetworkManager-dispatcher.service: Unit process 7641 (99-nv-set-sae-p) remains running after unit stopped.
Jul 08 14:03:17 localhost.localdomain systemd[1]: NetworkManager-dispatcher.service: Unit process 8167 (sleep) remains running after unit stopped.
Jul 08 14:03:17 localhost.localdomain wpa_supplicant[1479]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface.Mesh dbus_property=MeshPeers getter failed
Jul 08 14:03:20 localhost.localdomain wpa_supplicant[1479]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface.Mesh dbus_property=MeshPeers getter failed
Jul 08 14:03:34 localhost.localdomain systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Jul 08 14:03:35 localhost.localdomain NetworkManager[1449]: [1783541015.3256] device (wlP1p1s0): IP address 192.168.43.219 cannot be configured because it is already in use in the network by host 04:A7:41:6B:CB:85
Jul 08 14:03:35 localhost.localdomain NetworkManager[1449]: [1783541015.5546] dhcp4 (wlP1p1s0): state changed new lease, address=192.168.43.221, acd pending
Jul 08 14:03:35 localhost.localdomain NetworkManager[1449]: [1783541015.5789] device (wlP1p1s0): IP address 192.168.43.221 cannot be configured because it is already in use in the network by host 04:A7:41:6B:CB:85
Jul 08 14:03:35 localhost.localdomain NetworkManager[1449]: [1783541015.6059] dhcp4 (wlP1p1s0): state changed new lease, address=192.168.43.221, acd conflict
Jul 08 14:03:36 localhost.localdomain wpa_supplicant[1479]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface.Mesh dbus_property=MeshPeers getter failed
Jul 08 14:03:37 localhost.localdomain systemd[1]: systemd-timedated.service: Deactivated successfully.
Jul 08 14:03:37 localhost.localdomain systemd[5937]: Started app-gnome-ubuntu\x2dadvantage\x2dnotification-8380.scope - Application launched by gnome-session-binary.
Jul 08 14:03:37 localhost.localdomain systemd[5937]: Started app-gnome-update\x2dnotifier-8377.scope - Application launched by gnome-session-binary.
Jul 08 14:03:38 localhost.localdomain geoclue[6763]: Service not used for 60 seconds. Shutting down..
Jul 08 14:03:38 localhost.localdomain systemd[1]: geoclue.service: Deactivated successfully.
Jul 08 14:03:39 localhost.localdomain wpa_supplicant[1479]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface.Mesh dbus_property=MeshPeers getter failed
Jul 08 14:03:42 localhost.localdomain wpa_supplicant[1479]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface.Mesh dbus_property=MeshPeers getter failed
Jul 08 14:03:42 localhost.localdomain systemd-networkd-wait-online[8118]: Timeout occurred while waiting for network connectivity.
Thank you,
James K
— 🤖 This is an automated AI response. I’m here to help, but please verify important details! —
I could not find clear support for that in the provided Jetson Orin Nano documentation. The issue seems to be related to WiFi connectivity and NetworkManager, but the provided context does not contain specific information about troubleshooting WiFi issues on the Jetson Orin Nano.
However, the output from sudo journalctl -b suggests that there might be a conflict with another device on the network, as indicated by the “IP address … cannot be configured because it is already in use in the network by host” messages. This could be a starting point for further investigation, but without more specific information about the Jetson Orin Nano’s network configuration and settings, it’s difficult to provide a more detailed answer.
If you’re looking for general information about networking on the Jetson Orin Nano, you might want to consult the official NVIDIA documentation or forums for more detailed guidance.
— We support team will also look into your issue to have further suggestions soon. please stay tuned. —
Thank you, greatly appreciate that..
Now I would like to add some additional information-
When I let the Wifi cycle and attempt to connect and grab an IP address I see this-
vlan43 192.168.43.9 502e.9127.f661 114
vlan43 192.168.43.8 502e.9127.f661 414
vlan43 192.168.43.7 502e.9127.f661 714
vlan43 192.168.43.6 502e.9127.f661 1014
vlan43 192.168.43.254 502e.9127.f661 1314
vlan43 192.168.43.253 502e.9127.f661 1614
vlan43 192.168.43.252 502e.9127.f661 1914
vlan43 192.168.43.251 502e.9127.f661 2214
vlan43 192.168.43.250 502e.9127.f661 2514
vlan43 192.168.43.249 502e.9127.f661 2815
vlan43 192.168.43.248 502e.9127.f661 3115
vlan43 192.168.43.247 502e.9127.f661 3415
vlan43 192.168.43.246 502e.9127.f661 3715
vlan43 192.168.43.245 502e.9127.f661 4016
vlan43 192.168.43.244 502e.9127.f661 4316
vlan43 192.168.43.243 502e.9127.f661 4616
vlan43 192.168.43.242 502e.9127.f661 4916
vlan43 192.168.43.241 502e.9127.f661 5216
vlan43 192.168.43.240 502e.9127.f661 5516
vlan43 192.168.43.239 502e.9127.f661 5817
vlan43 192.168.43.238 502e.9127.f661 6117
vlan43 192.168.43.237 502e.9127.f661 6417
vlan43 192.168.43.236 502e.9127.f661 6717 <--- MAC of Jetson WLAN (all)
vlan43 192.168.43.235 502e.9127.f661 7017
vlan43 192.168.43.234 502e.9127.f661 7317
vlan43 192.168.43.233 502e.9127.f661 7617
vlan43 192.168.43.232 502e.9127.f661 7917
vlan43 192.168.43.231 502e.9127.f661 8217
vlan43 192.168.43.230 502e.9127.f661 8518
vlan43 192.168.43.229 502e.9127.f661 8818
vlan43 192.168.43.228 502e.9127.f661 8978
vlan43 192.168.43.227 502e.9127.f661 9058
vlan43 192.168.43.226 502e.9127.f661 9098
vlan43 192.168.43.225 502e.9127.f661 9118
vlan43 192.168.43.224 502e.9127.f661 9128
wlP1p1s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.41.100 netmask 255.255.255.0 broadcast 192.168.41.255
ether 50:2e:91:27:f6:61 txqueuelen 1000 (Ethernet) ← MAC of Jetson WLAN
Jul 08 17:48:22 localhost.localdomain NetworkManager[1449]: [1783554502.3926] device (wlP1p1s0): IP address 192.168.43.236 cannot be configured because it is already in use in the network by host 04:A7:41:6B:CB:85 ← MAC of my VLAN43 interface on my Cisco FTD
Jul 08 17:48:52 localhost.localdomain NetworkManager[1449]: [1783554532.4013] device (wlP1p1s0): IP address 192.168.43.236 cannot be configured because it is already in use in the network by host 04:A7:41:6B:CB:85 ← MAC of my VLAN43 interface on my Cisco FTD
Jul 08 17:49:22 localhost.localdomain NetworkManager[1449]: [1783554562.4048] dhcp4 (wlP1p1s0): state changed new lease, address=192.168.43.237, acd pending
Interface Vlan43 “vlan43”, is up, line protocol is up
Hardware is EtherSVI, BW 100 Mbps, DLY 100 usec
MAC address 04a7.416b.cb85, MTU 1500 ← MAC of my VLAN43 interface on my Cisco FTD
As you can see it does pull an IP address from my DHCP server but then shows an error saying its already taken when it was the device that took it…
Let me know if there are any commands you would like to me to run to collect any additional information.
Hi @jkeddington,
Thank you for the additional details. The new logs show that the Jetson associates with the Wi-Fi network and receives a DHCP lease, but NetworkManager then rejects the offered address during IPv4 address-conflict detection.
For every offered address, NetworkManager reports the same conflicting MAC address, 04:A7:41:6B:CB:85, which you identified as the VLAN43 interface on the Cisco FTD. This suggests that the FTD is replying to the Jetson’s ARP probes, rather than the problem being caused by a retained Wi-Fi profile.
-
Check proxy ARP on the FTD
Please run this read-only command on the FTD and share the output:
show nat proxy-arp interface vlan43
Cisco documents this behavior when FTD proxy ARP responds to address-conflict probes with the firewall’s MAC address:
https://www.cisco.com/c/en/us/support/docs/security/secure-email-threat-defense/225755-disable-proxy-arp-on-ftd-interfaces.html
NetworkManager documents that connection activation fails when its duplicate-address check detects a conflict:
ipv4: NetworkManager Reference Manual
-
Confirm the installed Jetson software versions
Please also run these commands on the Jetson and share the output:
head -n 1 /etc/nv_tegra_release
NetworkManager --version
Recommendation: If the FTD output shows a proxy-ARP entry covering the VLAN43 DHCP pool, have the network administrator review the matching NAT rule and disable proxy ARP on that specific rule where appropriate. Cisco recommends rule-level control when possible, because disabling proxy ARP for the entire interface can affect NAT mappings that require it. NetworkManager’s address-conflict detection should remain enabled.
Hello,
I was able to read through the Cisco link you provided which talks about- Hosts on an FTD interface are unable to use statically assigned IP addresses and report “duplicate IP address” errors. However, the Jetson was configured for DHCP.
I started collecting additional information to show how I can have other devices connect to my JKedman-Jetson SSID and retrieve an IP address just fine and how my Jetson could connect to my other Wifi networks and retrieve an IP address just fine. I was then going to show how when my Jetson was attempting to connect to the JKedman-Jetson SSID the signal was “poor” and then it successfully connected.
show arp
vlan42 192.168.42.9 502e.9127.f661 12 ← Jetson (SSID JKedman-Solar)
vlan43 192.168.43.10 ee22.b844.5595 34 ← Pixel phone (SSID JKedman-Jetson)
vlan41 192.168.41.100 502e.9127.f661 24 ← Jetson (SSID JKedman-WLAN)
vlan43 192.168.43.11 502e.9127.f661 65 ← Jetson (SSID JKedman-Jetson)
show dhcpd binding
192.168.42.9 0150.2e91.27f6.61 3575 seconds Automatic ← Jetson
192.168.43.10 01ee.22b8.4455.95 3524 seconds Automatic ← Pixel phone
192.168.41.100 0150.2e91.27f6.61 3474 seconds Automatic ← Jetson
192.168.43.11 0150.2e91.27f6.61 3489 seconds Automatic ← Jetson
I initially connected to my wired network and when I first logged in I was prompted to “update” all installed software and the system software. That is the only difference… I have made no changes to my Firewall…
While I’m happy this is now working as expected its a bit “annoying” that it self-healed and I have no idea how to resolve if this comes back… : ) The joys of troubleshooting…
Anyways for now please consider this resolved…
Thank you for your timely responses!