Windows Setup #28

NexuaTCN · 2023-04-16T21:42:52Z

NexuaTCN
Apr 16, 2023

Hello! Awesome project! So, I'm trying to connect to my controller on windows, but seem to be having some trouble. When I try to use ">uhppote-cli get-devices" it originally did nothing, but after i configured the device in the conf file, I'm receiving an error "Failed to write to UDP socket: A socket operation was attempted to an unreachable network.". I can't seem to figure out what I'm doing wrong. Thanks in advance for any help!

Answered by uhppoted

Apr 16, 2023

Hi,

Hmm, best guess is that you are running multiple networks (e.g. WiFi and one or two Ethernet LANs) and uhppote-cli is not using the correct one - it defaults to binding to either 0.0.0.0 or to the first LAN it finds (if there are multiple interfaces). As a start, try removing all the configuration information from uhppoted.conf (to get to a known state) and then:

Use ipconfig to list all your networks

ipconfig /all

You should get something like this:

Windows IP Configuration

   Host Name . . . . . . . . . . . . : MY-COMPUTER
   Primary Dns Suffix  . . . . . . . : example.com
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabl…

View full answer

uhppoted · 2023-04-16T23:30:23Z

uhppoted
Apr 16, 2023
Maintainer

Hi,

Hmm, best guess is that you are running multiple networks (e.g. WiFi and one or two Ethernet LANs) and uhppote-cli is not using the correct one - it defaults to binding to either 0.0.0.0 or to the first LAN it finds (if there are multiple interfaces). As a start, try removing all the configuration information from uhppoted.conf (to get to a known state) and then:

Use ipconfig to list all your networks

ipconfig /all

You should get something like this:

Windows IP Configuration

   Host Name . . . . . . . . . . . . : MY-COMPUTER
   Primary Dns Suffix  . . . . . . . : example.com
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : example.com

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : example.com
   Description . . . . . . . . . . . : Realtek PCIe GbE Family Controller
   Physical Address. . . . . . . . . : 00-11-22-33-44-55
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.1.2(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Friday, April 15, 2023 10:28:18 AM
   Lease Expires . . . . . . . . . . : Saturday, April 16, 2023 10:28:18 AM
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DNS Servers . . . . . . . . . . . : 192.168.1.1
...

You want to use the Ethernet adapter for the network that your access controller is on and then bind specifically to that adapter, e.g.:

uhppote-cli --debug --bind 192.168.1.2 --broadcast 192.168.1.255 get-devices

You can also try explicitly binding to the INADDR_ANY address (which may or may not work depending on how your network is configured):

uhppote-cli --debug --bind 0.0.0.0 --broadcast 255.255.255.255 get-devices

There are a couple of other potential reasons but they're a bit less likely:

The access controller is on a different network segment to the host computer
Your access controller may have very out of date firmware (pre v6.56). This is unlikely unless it's a very old controller - some of the less expensive controllers sold on AliExpress are old stock but even so the oldest version I've heard of is v6.62.
Your network may be configured to block UDP broadcast
You're not running a UHPPOTE controller (sorry, I do have to ask - it has happened :-))

0 replies

NexuaTCN · 2023-04-18T00:38:17Z

NexuaTCN
Apr 18, 2023
Author

You're the best! It was using a virtual adapter, still beating myself up haha. Thank for your help, got it working now. Really appreciate your work!

0 replies

uhppoted · 2023-04-18T01:46:12Z

uhppoted
Apr 18, 2023
Maintainer

Ok, that is one I haven't run into before :-) ... glad you're up and running!

I'm guessing you've probably already done this, but if not you can set the default bind, broadcast and listen addresses in the uhppoted.conf file, e.g.:

# SYSTEM
bind.address = 192.168.1.100
broadcast.address = 192.168.1.255
listen.address = 192.168.1.100:60001

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Windows Setup #28

Uh oh!

{{title}}

Uh oh!

Replies: 3 comments

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Windows Setup #28

Uh oh!

NexuaTCN Apr 16, 2023

Replies: 3 comments

Uh oh!

Uh oh!

uhppoted Apr 16, 2023 Maintainer

Uh oh!

NexuaTCN Apr 18, 2023 Author

Uh oh!

uhppoted Apr 18, 2023 Maintainer

NexuaTCN
Apr 16, 2023

uhppoted
Apr 16, 2023
Maintainer

NexuaTCN
Apr 18, 2023
Author

uhppoted
Apr 18, 2023
Maintainer