I'm not on 192.168.2.*

gatonero on May 9, 2025

Category: Software

My home network is 192.168.178.* and I can't access my Pluto via ssh with USB under 192.168.2.1. I'm running with Linux. My routers adress is 192.168.178.1. I tried different settings. My actual config.txt is:

# Analog Devices PlutoSDR Rev.C (Z7010-AD9363)
# Device Configuration File
# 1. Open with an Editor
# 2. Edit this file
# 3. Save this file on the device USB drive
# 4. Eject the device USB Drive
# Doc: wiki.analog.com/.../customizing

[NETWORK]
hostname = pluto
ipaddr = 192.168.178.190
ipaddr_host = 192.168.178.1
netmask = 255.255.255.0

[WLAN]
ssid_wlan = MyWLAN
pwd_wlan = xxxxxxxxxx
ipaddr_wlan = 192.168.178.190

[USB_ETHERNET]
ipaddr_eth = 192.168.178.190
netmask_eth = 255.255.255.0

[SYSTEM]
xo_correction =
udc_handle_suspend = 0
# USB Communication Device Class Compatibility Mode [rndis|ncm|ecm]
usb_ethernet_mode = ncm

[ACTIONS]
diagnostic_report = 0
dfu = 0
reset = 0
calibrate = 0

Thanks for your help in advance!

Edit Notes

added router adress
[edited by: gatonero at 2:32 PM (GMT -4) on 9 May 2025]

Parents

IonutMuthi

on May 12, 2025 1:32 AM
0
Hello,

Can you check if the drivers are installed there are detailed steps on how to do this here
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
gatonero on May 12, 2025 2:25 AM in reply to IonutMuthi
0

Everything is installed.

iio_info -s
Available contexts:
       0: (mt7921_phy0,hidpp_battery_0,acpitz,hidpp_battery_1,coretemp,nvme on Default string) [local:]
       1: 0456:b673 (Analog Devices Inc. PlutoSDR (ADALM-PLUTO)), serial=10447318ac0f0011060036002b8c172932 [usb:3.9.5]
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
IonutMuthi

on May 12, 2025 2:33 AM in reply to gatonero
0
Seems like it only sees the usb.
Considering your router ip is 192.168.178.1 can you try these settings

[NETWORK]
hostname = pluto
ipaddr = 192.168.178.2
ipaddr_host = 192.168.178.1
netmask = 255.255.255.0

[WLAN]
ssid_wlan =
pwd_wlan =
ipaddr_wlan =

[USB_ETHERNET]
ipaddr_eth =
netmask_eth = 255.255.255.0

[SYSTEM]
xo_correction =
udc_handle_suspend = 0
# USB Communication Device Class Compatibility Mode [rndis|ncm|ecm]
usb_ethernet_mode = ncm

[ACTIONS]
diagnostic_report = 0
dfu = 0
reset = 0
calibrate = 0

if this does not work can you try to connect using usb connection just to make sure you are able to access Pluto ?
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
gatonero on May 12, 2025 2:52 AM in reply to IonutMuthi
0
Seems that there is the same result:

iio_info -s                                                                                                                   
Available contexts:
       0: (mt7921_phy0,hidpp_battery_0,acpitz,hidpp_battery_1,coretemp,nvme on Default string) [local:]
       1: 0456:b673 (Analog Devices Inc. PlutoSDR (ADALM-PLUTO)), serial=10447318ac0f0011060036002b8c172932 [usb:3.9.5]

But there are three new files:

ipaddr-usb0, which is empty

status, content: "here 1:"

SUCCESS_ENV_UPDATE, which is empty also

These files disapear after a reboot.
Cancel
Up +1 Down

Reply

Verify Answer

Cancel
IonutMuthi

on May 12, 2025 2:57 AM in reply to gatonero
0
can you run iio_info -u ip:192.168.178.2
To check if we are able to see the context like this ?
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
gatonero on May 12, 2025 2:59 AM in reply to IonutMuthi
0

iio_info -u ip:192.168.178.2 
Unable to create IIO context ip:192.168.178.2: Connection refused (111)
Cancel
Up 0 Down

Reply

Verify Answer

Cancel

Reply

gatonero on May 12, 2025 2:59 AM in reply to IonutMuthi
0

iio_info -u ip:192.168.178.2 
Unable to create IIO context ip:192.168.178.2: Connection refused (111)
Cancel
Up 0 Down

Reply

Verify Answer

Cancel

Children

IonutMuthi

on May 12, 2025 3:07 AM in reply to gatonero
0
can you try to make a firmware update following the instructions here and then try again to configure your custom ip config ?
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
gatonero on May 12, 2025 3:09 AM in reply to gatonero
0

On 192.168.178.2 there was a repeater. The repeater is now offline and I removes it's settings in my router. Now:

iio_info -u ip:192.168.178.2  1 ✘  3s 
Unable to create IIO context ip:192.168.178.2: No route to host (113)
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
IonutMuthi

on May 12, 2025 3:26 AM in reply to gatonero
0
For now try to update the firmware.
After the update try to run iio_info -u ip:192.168.2.1 with no other changes made.
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
IonutMuthi

on May 12, 2025 3:30 AM in reply to IonutMuthi
0
If this does not work use the config file bellow.
After you update and save the file eject the device and do a power cycle this should allow you to see the ip

[NETWORK]
hostname = pluto
ipaddr = 172.169.2.3
ipaddr_host = 172.169.2.10
netmask = 255.255.255.0

[WLAN]
ssid_wlan =
pwd_wlan =
ipaddr_wlan =

[USB_ETHERNET]
ipaddr_eth =
netmask_eth = 255.255.255.0

[SYSTEM]
xo_correction =
udc_handle_suspend = 0

[ACTIONS]
diagnostic_report = 0
dfu = 0
reset = 0
calibrate = 0
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
gatonero on May 12, 2025 3:52 AM in reply to IonutMuthi
0

iio_attr --uri usb:3.12.5 -C fw_version                                                                                     1 ✘
fw_version: v0.39

iio_info -u ip:192.168.2.1                                                                                                    
Unable to create IIO context ip:192.168.2.1: Connection timed out (110)

New config.txt as you mentioned above.

iio_info -u ip:172.169.2.3                                                                                                    
Unable to create IIO context ip:172.169.2.3: Connection timed out (110)
   ~ 
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
IonutMuthi

on May 12, 2025 4:04 AM in reply to gatonero
0
Can you try to change the USB Ethernet compatibility mode like explained here ?
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
gatonero on May 12, 2025 4:10 AM in reply to IonutMuthi
0
With

blank

rndis

ncm

ecm

all

[cs@Mini-IT13 ~]$ iio_info -u ip:172.169.2.3
Unable to create IIO context ip:172.169.2.3: Connection timed out (110)
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
IonutMuthi

on May 12, 2025 4:22 AM in reply to gatonero
0
after the configuration is done properly by ejecting make sure you disconnect and reconnect the usb cable for a restart
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
gatonero on May 12, 2025 4:32 AM in reply to IonutMuthi
0

I did this after every change. Nothing changed.
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
gatonero on May 12, 2025 4:37 AM in reply to gatonero
0

Here is my ifconfig

[cs@Mini-IT13 ~]$ ifconfig
br-1ab76231e119: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
       inet 172.19.0.1 netmask 255.255.0.0 broadcast 172.19.255.255
       inet6 fe80::e086:7dff:fee3:bbec prefixlen 64 scopeid 0x20<link>
       ether e2:86:7d:e3:bb:ec txqueuelen 0 (Ethernet)
       RX packets 3 bytes 84 (84.0 B)
       RX errors 0 dropped 0 overruns 0 frame 0
       TX packets 91 bytes 9299 (9.0 KiB)
       TX errors 0 dropped 2 overruns 0 carrier 0 collisions 0

br-9983f0598889: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
       inet 172.22.0.1 netmask 255.255.0.0 broadcast 172.22.255.255
       ether 2a:06:43:97:68:51 txqueuelen 0 (Ethernet)
       RX packets 0 bytes 0 (0.0 B)
       RX errors 0 dropped 0 overruns 0 frame 0
       TX packets 0 bytes 0 (0.0 B)
       TX errors 0 dropped 42 overruns 0 carrier 0 collisions 0

br-a1c9d36480db: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
       inet 172.18.0.1 netmask 255.255.0.0 broadcast 172.18.255.255
       inet6 fe80::3c53:8bff:fe2c:8726 prefixlen 64 scopeid 0x20<link>
       ether 3e:53:8b:2c:87:26 txqueuelen 0 (Ethernet)
       RX packets 775 bytes 129815 (126.7 KiB)
       RX errors 0 dropped 0 overruns 0 frame 0
       TX packets 915 bytes 78300 (76.4 KiB)
       TX errors 0 dropped 3 overruns 0 carrier 0 collisions 0

br-c31a3195cb1f: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
       inet 172.20.0.1 netmask 255.255.0.0 broadcast 172.20.255.255
       inet6 fe80::7443:feff:fed1:3027 prefixlen 64 scopeid 0x20<link>
       ether 76:43:fe:d1:30:27 txqueuelen 0 (Ethernet)
       RX packets 3 bytes 84 (84.0 B)
       RX errors 0 dropped 0 overruns 0 frame 0
       TX packets 90 bytes 9237 (9.0 KiB)
       TX errors 0 dropped 3 overruns 0 carrier 0 collisions 0

br-f661b67932d9: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
       inet 172.21.0.1 netmask 255.255.0.0 broadcast 172.21.255.255
       ether 3e:e1:68:73:73:6f txqueuelen 0 (Ethernet)
       RX packets 0 bytes 0 (0.0 B)
       RX errors 0 dropped 0 overruns 0 frame 0
       TX packets 0 bytes 0 (0.0 B)
       TX errors 0 dropped 42 overruns 0 carrier 0 collisions 0

docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
       inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
       ether 1e:cd:00:bf:1b:04 txqueuelen 0 (Ethernet)
       RX packets 0 bytes 0 (0.0 B)
       RX errors 0 dropped 0 overruns 0 frame 0
       TX packets 0 bytes 0 (0.0 B)
       TX errors 0 dropped 42 overruns 0 carrier 0 collisions 0

enp0s20f0u5u4u4: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
       ether 00:e0:22:9f:1c:c5 txqueuelen 1000 (Ethernet)
       RX packets 39 bytes 5356 (5.2 KiB)
       RX errors 0 dropped 0 overruns 0 frame 0
       TX packets 0 bytes 0 (0.0 B)
       TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
       inet 192.168.178.10 netmask 255.255.255.0 broadcast 192.168.178.255
       inet6 fe80::733c:eb20:ddd6:539f prefixlen 64 scopeid 0x20<link>
       inet6 2a02:908:1064:50c0:df5b:df6f:7b75:bbb1 prefixlen 64 scopeid 0x0<global>
       inet6 fd00::6966:8660:802e:39b prefixlen 64 scopeid 0x0<global>
       ether 38:f7:cd:c7:4b:8c txqueuelen 1000 (Ethernet)
       RX packets 178712 bytes 105697312 (100.8 MiB)
       RX errors 0 dropped 0 overruns 0 frame 0
       TX packets 94752 bytes 40735095 (38.8 MiB)
       TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
       device memory 0x6c300000-6c3fffff

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
       inet 127.0.0.1 netmask 255.0.0.0
       inet6 ::1 prefixlen 128 scopeid 0x10<host>
       loop txqueuelen 1000 (Local Loopback)
       RX packets 1404 bytes 1319626 (1.2 MiB)
       RX errors 0 dropped 0 overruns 0 frame 0
       TX packets 1404 bytes 1319626 (1.2 MiB)
       TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

veth125d805: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
       inet6 fe80::c420:76ff:fe7a:326a prefixlen 64 scopeid 0x20<link>
       ether c6:20:76:7a:32:6a txqueuelen 0 (Ethernet)
       RX packets 3 bytes 126 (126.0 B)
       RX errors 0 dropped 0 overruns 0 frame 0
       TX packets 148 bytes 15038 (14.6 KiB)
       TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

veth23ca42c: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
       inet6 fe80::582f:6eff:fed0:ddfa prefixlen 64 scopeid 0x20<link>
       ether 5a:2f:6e:d0:dd:fa txqueuelen 0 (Ethernet)
       RX packets 3 bytes 126 (126.0 B)
       RX errors 0 dropped 0 overruns 0 frame 0
       TX packets 149 bytes 15100 (14.7 KiB)
       TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vethe5b6f5e: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
       inet6 fe80::f8d6:88ff:fedf:628d prefixlen 64 scopeid 0x20<link>
       ether fa:d6:88:df:62:8d txqueuelen 0 (Ethernet)
       RX packets 775 bytes 140665 (137.3 KiB)
       RX errors 0 dropped 0 overruns 0 frame 0
       TX packets 973 bytes 84101 (82.1 KiB)
       TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vmnet1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
       inet 172.16.1.1 netmask 255.255.255.0 broadcast 172.16.1.255
       inet6 fe80::250:56ff:fec0:1 prefixlen 64 scopeid 0x20<link>
       ether 00:50:56:c0:00:01 txqueuelen 1000 (Ethernet)
       RX packets 0 bytes 0 (0.0 B)
       RX errors 0 dropped 0 overruns 0 frame 0
       TX packets 432 bytes 0 (0.0 B)
       TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

vmnet8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
       inet 192.168.120.1 netmask 255.255.255.0 broadcast 192.168.120.255
       inet6 fe80::250:56ff:fec0:8 prefixlen 64 scopeid 0x20<link>
       ether 00:50:56:c0:00:08 txqueuelen 1000 (Ethernet)
       RX packets 0 bytes 0 (0.0 B)
       RX errors 0 dropped 0 overruns 0 frame 0
       TX packets 105 bytes 0 (0.0 B)
       TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Cancel
Up 0 Down

Reply

Verify Answer

Cancel

Popular Forums

Product Forums

Application Forums

Design Center Forums

Highlighted Webinar

Places

Libraries

Upcoming Learning & Events

Challenge Yourself!

What's Brewing

Places

Resources

Visit ContentZone

The Latest Read

New Release

Recent Technical Insights

Thread Details

I'm not on 192.168.2.*

Edit Notes