Virtual Node Mode

[Weston Bustraan]

Well, based on recent threads, this is probably an appropriate time to say that I do have code available that introduces a "virtual node mode" in RepeaterPhone. This would make use of a node number and the DNS registration system that goes with that.

I wrote the code many months ago, but I haven't really had enough time, personally, to spend on ASL nets in order to fully test it out. The plan has always been to open it up to a (limited) beta test group. I usually like to have it more polished before I do that, but I'm realizing that if I wait for that time, I may never get it, and there may be people out there willing to do some of this testing.

So, what is the general consensus of the list? Should I fire up a beta test with it as-is and let people have a go at testing it?

I am calling it "virtual" node mode to help manage expectations a bit. Because of the policies for background apps on the iOS platform, apps are not allowed to continuously run in the background (with a small handful of exceptions), so it is unlikely that we'll ever be able to accept incoming connections to a iOS-based "node".

There are some other potential gotchas:

- Mobile devices tend to change IP addresses a lot as they switch from cell to WiFi. I have code in RepeaterPhone that is intended to detect this and refresh the registration, but it remains to be seen how the DNS infrastructure and caching reacts to frequent changes

- We could see some issues with shared (NAT) addresses. In this, I'm not 100% sure how the backend registration system works. So, here's a hypothetical scenario: let's say you're at work and want to monitor a net, so you fire up RepeaterPhone. Since you're on your work's WiFi, it would update the registration for your node number with the external IP address of your workplace. So far, so good. But what if you have a coworker who also wants to connect? If they connect using the same WiFi, then you'll end up with the work IP address registered to two different node numbers. If the node registration system permits duplicate IP addresses, then everything should be okay. However, if it does not, then whoever gets there first is the winner.

These are things that are not usually a problem for people who set up traditional nodes because they are generally assigned a static IP address.

- Wes W8WJB

[Patrick Perdue]

Wes:

I am all for testing your virtual node mode code. Bring it on, I say.

Having multiple nodes registered to the same IP address probably won't matter in this case, because neither of them will field incoming connections.

I personally have 8 nodes on the same dynamic public IP here at my house, each with it's own path for incoming connections.

--
You received this message because you are subscribed to the Google Groups "repeaterphone-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repeaterphone-u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/repeaterphone-users/CAEeLBeXYLtOnZ5M%2BWKRZSJh-h343mXn2vhHP52wvv%3DfK5NLCZg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Steven Davidson]

Wes-

Put me down for your beta. I only have three nodes active on the same dynamic Ip and no problem connecting in to each of them. 

73 de K3FZT / Steve 

--

Steve Davidson K3FZT

Winlink Gateway K3FZ...@145.67mHz direct or via W3EOC-3

WIRES-X Room #85218 “MARC-DARBY” 444.050 mHz

K3...@sjdmd.com FN20ja

On Jul 15, 2025, at 13:43, Weston Bustraan <wbus...@gmail.com> wrote: