Talking to Roon from another VLAN (I got it working)

Tinkering
41

Roon core runs on LAN (my laptop - no dedicated device yet) (192.168.1.0/24)
Home Theater runs on VLAN 10 (192.168.10.0/24)
Kids are on VLAN 3 (192.168.3.0/24)

root:/ ifconfig
br0 Link encap:Ethernet HWaddr F6:92:BF:87:C0:7D
inet addr:192.168.1.1 Bcast:0.0.0.0 Mask:255.255.255.0
inet6 addr: fe80::f492:bfff:fe87:c07c/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:16481452 errors:0 dropped:23 overruns:0 frame:0
TX packets:12655578 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8177404872 (7.6 GiB) TX bytes:37422805970 (34.8 GiB)

br10      Link encap:Ethernet  HWaddr F6:92:BF:87:C0:7D  
          inet addr:192.168.10.1  Bcast:0.0.0.0  Mask:255.255.255.0
          inet6 addr: fe80::98e7:47ff:feba:8fe7/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4225073 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8842246 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:282170336 (269.0 MiB)  TX bytes:12629914444 (11.7 GiB)

br2       Link encap:Ethernet  HWaddr F6:92:BF:87:C0:7D  
          inet addr:192.168.2.1  Bcast:0.0.0.0  Mask:255.255.255.0
          inet6 addr: fe80::1460:adff:fe9b:22f9/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:933920 errors:0 dropped:0 overruns:0 frame:0
          TX packets:963676 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:231749505 (221.0 MiB)  TX bytes:421332734 (401.8 MiB)

br3       Link encap:Ethernet  HWaddr F4:92:BF:87:C0:81  
          inet addr:192.168.3.1  Bcast:0.0.0.0  Mask:255.255.255.0
          inet6 addr: fe80::8c1:fbff:fecc:3d57/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:309688 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1463729 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:39692013 (37.8 MiB)  TX bytes:1875145269 (1.7 GiB)

br46      Link encap:Ethernet  HWaddr F6:92:BF:87:C0:7D  
          inet addr:192.168.46.1  Bcast:0.0.0.0  Mask:255.255.255.0
          inet6 addr: fe80::289a:c5ff:fe9f:3ef8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:17136147 errors:0 dropped:0 overruns:0 frame:0
          TX packets:11017493 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:11606675332 (10.8 GiB)  TX bytes:891578315 (850.2 MiB)

eth0      Link encap:Ethernet  HWaddr F4:92:BF:87:C0:7C  
          inet6 addr: fe80::f692:bfff:fe87:c07c/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:52446 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:10808810 (10.3 MiB)  TX bytes:1070 (1.0 KiB)

eth1      Link encap:Ethernet  HWaddr F4:92:BF:87:C0:7D  
          inet6 addr: fe80::f692:bfff:fe87:c07d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:52465 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:10805291 (10.3 MiB)  TX bytes:1070 (1.0 KiB)

eth2      Link encap:Ethernet  HWaddr F4:92:BF:87:C0:7E  
          inet6 addr: fe80::f692:bfff:fe87:c07e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:52498 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:10813005 (10.3 MiB)  TX bytes:1070 (1.0 KiB)

eth3      Link encap:Ethernet  HWaddr F4:92:BF:87:C0:7F  
          inet6 addr: fe80::f692:bfff:fe87:c07f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:89945 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:20941097 (19.9 MiB)  TX bytes:1070 (1.0 KiB)

eth4      Link encap:Ethernet  HWaddr F4:92:BF:87:C0:80  
          inet6 addr: fe80::f692:bfff:fe87:c080/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:38780922 errors:0 dropped:67 overruns:0 frame:0
          TX packets:38911137 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:34830310007 (32.4 GiB)  TX bytes:28089555294 (26.1 GiB)

eth4.201  Link encap:Ethernet  HWaddr F4:92:BF:87:C0:80  
          inet6 addr: fe80::f692:bfff:fe87:c080/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:38779223 errors:0 dropped:2 overruns:0 frame:0
          TX packets:38909950 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:34830160243 (32.4 GiB)  TX bytes:28633386468 (26.6 GiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:56438845 errors:0 dropped:0 overruns:0 frame:0
          TX packets:56438845 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:72060503794 (67.1 GiB)  TX bytes:72060503794 (67.1 GiB)

ppp0      Link encap:Point-to-Point Protocol  
          inet addr:97.115.126.65  P-t-P:207.225.84.53  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1492  Metric:1
          RX packets:38753587 errors:0 dropped:0 overruns:0 frame:0
          TX packets:38884317 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3 
          RX bytes:34519037812 (32.1 GiB)  TX bytes:27777161656 (25.8 GiB)

ra0       Link encap:Ethernet  HWaddr F4:92:BF:87:C0:81  
          inet6 addr: fe80::f692:bfff:fe87:c081/64 Scope:Link
          UP BROADCAST RUNNING PROMISC ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:35112 errors:26 dropped:491 overruns:0 frame:0
          TX packets:30708 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:4994172 (4.7 MiB)  TX bytes:4066470 (3.8 MiB)
          Interrupt:78 

ra1       Link encap:Ethernet  HWaddr F6:92:BF:97:C0:81  
          inet6 addr: fe80::f492:bfff:fe97:c081/64 Scope:Link
          UP BROADCAST RUNNING PROMISC ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:9238834 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5025489 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:6694325142 (6.2 GiB)  TX bytes:314469792 (299.9 MiB)

ra2       Link encap:Ethernet  HWaddr F6:92:BF:A7:C0:81  
          inet6 addr: fe80::f492:bfff:fea7:c081/64 Scope:Link
          UP BROADCAST RUNNING PROMISC ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

ra3       Link encap:Ethernet  HWaddr F6:92:BF:B7:C0:81  
          inet6 addr: fe80::f492:bfff:feb7:c081/64 Scope:Link
          UP BROADCAST RUNNING PROMISC ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:514621 errors:0 dropped:0 overruns:0 frame:0
          TX packets:705848 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:51178873 (48.8 MiB)  TX bytes:952984097 (908.8 MiB)

ra4       Link encap:Ethernet  HWaddr F6:92:BF:C7:C0:81  
          inet6 addr: fe80::f492:bfff:fec7:c081/64 Scope:Link
          UP BROADCAST RUNNING PROMISC ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

ra4.10    Link encap:Ethernet  HWaddr F6:92:BF:C7:C0:81  
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:122108 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:28179288 (26.8 MiB)

ra4.2     Link encap:Ethernet  HWaddr F6:92:BF:C7:C0:81  
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:204382 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:40286279 (38.4 MiB)

ra4.3     Link encap:Ethernet  HWaddr F6:92:BF:C7:C0:81  
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:129231 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:28824642 (27.4 MiB)

ra4.46    Link encap:Ethernet  HWaddr F6:92:BF:C7:C0:81  
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:149200 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:36368848 (34.6 MiB)

rai0      Link encap:Ethernet  HWaddr F4:92:BF:87:C0:82  
          inet6 addr: fe80::f692:bfff:fe87:c082/64 Scope:Link
          UP BROADCAST RUNNING PROMISC ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:337788 errors:5 dropped:60580 overruns:0 frame:0
          TX packets:1283504 errors:3368877 dropped:3368877 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:41833337 (39.8 MiB)  TX bytes:1825180812 (1.6 GiB)
          Interrupt:77 

rai1      Link encap:Ethernet  HWaddr F6:92:BF:97:C0:82  
          inet6 addr: fe80::f492:bfff:fe97:c082/64 Scope:Link
          UP BROADCAST RUNNING PROMISC ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

rai2      Link encap:Ethernet  HWaddr F6:92:BF:A7:C0:82  
          inet6 addr: fe80::f492:bfff:fea7:c082/64 Scope:Link
          UP BROADCAST RUNNING PROMISC ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:805227 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1842751 errors:403872 dropped:403872 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:504397391 (481.0 MiB)  TX bytes:2322840503 (2.1 GiB)

rai3      Link encap:Ethernet  HWaddr F6:92:BF:B7:C0:82  
          inet6 addr: fe80::f492:bfff:feb7:c082/64 Scope:Link
          UP BROADCAST RUNNING PROMISC ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

rai3.10   Link encap:Ethernet  HWaddr F6:92:BF:B7:C0:82  
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:122108 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:28179288 (26.8 MiB)

rai3.2    Link encap:Ethernet  HWaddr F6:92:BF:B7:C0:82  
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:204382 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:40286279 (38.4 MiB)

rai3.3    Link encap:Ethernet  HWaddr F6:92:BF:B7:C0:82  
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:129231 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:28824642 (27.4 MiB)

rai3.46   Link encap:Ethernet  HWaddr F6:92:BF:B7:C0:82  
          UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:149200 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:36368848 (34.6 MiB)

switch0   Link encap:Ethernet  HWaddr F6:92:BF:87:C0:7D  
          inet6 addr: fe80::f492:bfff:fe87:c07d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:19817679 errors:2 dropped:0 overruns:0 frame:2
          TX packets:37268259 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:8069362212 (7.5 GiB)  TX bytes:48305385797 (44.9 GiB)

switch0.1 Link encap:Ethernet  HWaddr F6:92:BF:87:C0:7D  
          inet6 addr: fe80::f492:bfff:fe87:c07d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:14647839 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10601059 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:7553914528 (7.0 GiB)  TX bytes:34592285763 (32.2 GiB)

switch0.10 Link encap:Ethernet  HWaddr F6:92:BF:87:C0:7D  
          inet6 addr: fe80::f492:bfff:fe87:c07d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4228069 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8842252 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:282553824 (269.4 MiB)  TX bytes:12629915132 (11.7 GiB)

switch0.2 Link encap:Ethernet  HWaddr F6:92:BF:87:C0:7D  
          inet6 addr: fe80::f492:bfff:fe87:c07d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:938601 errors:0 dropped:0 overruns:0 frame:0
          TX packets:963686 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:232699609 (221.9 MiB)  TX bytes:421333804 (401.8 MiB)

switch0.3 Link encap:Ethernet  HWaddr F6:92:BF:87:C0:7D  
          inet6 addr: fe80::f492:bfff:fe87:c07d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:723 errors:0 dropped:0 overruns:0 frame:0
          TX packets:158436 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:30366 (29.6 KiB)  TX bytes:34287998 (32.6 MiB)

switch0.46 Link encap:Ethernet  HWaddr F6:92:BF:87:C0:7D  
          inet6 addr: fe80::f492:bfff:fe87:c07d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1230 errors:0 dropped:0 overruns:0 frame:0
          TX packets:297174 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:51660 (50.4 KiB)  TX bytes:64108155 (61.1 MiB)
42

Okay, I whipped this up really quick. Not sure if it works, but I think it might??

43

ok. I will check it out. I have to step away for a bit so will be later when I reply.

Thanks again!!

44

This is indeed what you need. (add wireguard to the mix and you can even have a Roon Mobile experience). Your on-boot-script will have to re-download udm-proxy-2020 and configure from scratch.

Caution is advised: if you mess things up, it could get really ugly and you may have a bricked udm that you will need to restore via ssh and cli.

45

hey @Nepherte: since you’re paying attention, I got a quick question:

So I was noticing all the other apps are running via docker/podman? Do you know what the story is there? I’m pretty sure you can’t run udp-proxy-2020 in a docker container and expect it to work due to needing to use libpcap on the host network interfaces.

46

Hey @Aaron_Turner. Paying attention, but not always quick to answer :sweat_smile:

I’m assuming Ubiquiti went the docker route as a safeguard, to not pollute and posssibly break the host os at all costs. I suppose it has its charms, and it allows one to make sure all dependencies are provided.

Docker and Podman allow you to use the host’s network stack, which is what e.g. wireguard setup from boostchicken/udm-utilities is actually doing. If you don’t do any port mapping, this comes with a close to 0% performance penalty.

So in my limited understanding of how Docker and Podman work, one would be able to provide a docker container that contains libpcap that does have access to the host network interfaces.

47

hmmm… well, a functioning network is mission critical for me at the moment…giving me a little pause. I’d love to be the first to test this out and I’d really like to have roon working as designed, but I may have to wait until somebody tries it out on a DM or until I can dedicate a little time to it.

How likely would it be to have something go south? The steps when I first looked at them did not seem too bad.

48

@Nepherte:

Well the problem is that libpcap bypasses the host IP stack. On Linux there is no /dev/bpf device like on *BSD to use, so it uses a special PF_PACKET socket. I suppose I could test locally on one of my Linux boxes at home.

fwiw, udp-proxy-relay-redux won’t have this problem. However it can’t easily support Roon over OpenVPN like udp-proxy-2020 does. Not sure about Wireguard. The issue with OpenVPN tunnel interfaces is that they do not support broadcasts. To see those packets, you need to do the PF_PACKET socket thing that libpcap uses.

I am curious about one thing you mentioned earlier: “Your on-boot-script will have to re-download udm-proxy-2020 and configure from scratch.” The binary and startup scripts are in the same directory- so I’m confused why the binary would be lost on boot, but the startup script isn’t?

@Robert_Schuff:

So there probably is one risk. Basically udp-proxy-2020 doesn’t support a daemon mode… It requires something like upstart, systemd or other tool to run in the background. I have no idea if the Ubiquiti startup scripts are executed serially in a blocking manner, but that could be a problem.

49

On a bit further consideration it seems like there’s a really chance of getting udp-proxy-2020 to work. Things like ping also require PF_PACKET sockets and I’m sure they would work in a container like wireguard does.

50

So tempted to try this, but a bit gun shy still! So @Aaron_Turner, are you saying that executed serially in a blocking manner, that would be a problem?

51

Check out the latest scripts in my copy of the udm-utilities repo. It’s now using docker/podman like everything else which should prevent any startup script issues.

I can’t image anything going wrong so bad where you have to re-image your system or anything like that, so it’s about as safe as anything else. That said, since I don’t own a UDM or UDMPro I can’t test it. I can say I tested the docker container on a Linux box of mine and it didn’t do anything bad. :slight_smile:

Beyond that, standard disclaimer applies; no warranty is expressed or implied. If your house burns down our your wife decides she suddenly likes rap music don’t blame me. :slight_smile:

Oh, I should mention I just released v0.0.6 of udp-proxy-2020 here: https://github.com/synfinatic/udp-proxy-2020/releases Big thing really is the startup scripts/docker-compose files: https://github.com/synfinatic/udp-proxy-2020/tree/main/startup-scripts

52

In all honestly , that’s a bit out of my depth (not a networking engineer). I was operating on the assumption that it was sufficient to have access to the network interfaces.

Not sure I follow. Anything placed in on_boot.d will be treated as a script that needs to be executed on boot. It’s a bit unclear to me where the installed docker ends up. Usually containers are installed in a dedicated directory (and I’m guessing it’ll get wiped on either a reboot or a firmware update on udm).

There are however a few folders that get preserved, on_boot.d being one of them, and I believe /mnt/data as well. Dockers will allow you to map / mount those folders from the host to the actual container. That’s how the actual configuration gets preserved.

53

Depends a bit on how confident you are in your skills to revive the udm when things go south :slight_smile: To give you an example on a personal incident I experienced:

I had my usg configured to run wireguard + udp-proxy-2020 setup. Everything was working fine, even with reboots. What I hadn’t realised is that a firmware upgrade wipes stuff, including my udp-proxy-2020 and wireguard executables.

When that rare firmware upgrade finally occurred, it ended up suck in a reprovisioning loop, as it was trying to launch the no longer existing wireguard and udp-proxy-2020.

To recover from this, I had to ssh into the usg, look at some logs to determine what went south, delete the scripts that caused the issues, update the config.gateway.json file on my unifi controller as well, …

If that sounds a bit scary, then maybe hold off until you get a bit more familiar with these things :slight_smile:

54

With a docker image now in place, it should be relatively easy to get this working. What you need is the on-boot-script system from udm-utilities and a script that will download/install/launch Aaron’s docker image. It should be very similar to the wireguard-go boot script from udm-utilities.

I plan on eventually getting the uxg (similar to udm-pro). Otherwise I would have all done this myself by now :slight_smile:

55

Ah, got it. Sounds like I need to update my udp-utilities to place the config file somewhere else and update the paths. Probably do that tomorrow… gonna sign off for the night, read a book, listen to some jazz and drink some whiskey.

1 Like
56

OK. I might give this a go next weekend. thank you both!!

57

well everything should be ready to go. LMK how it goes

58

Curious if you had a chance to get this a try?

59

Hey there, got waylaid with a couple of urgent things. but in 2 weeks I’ll be doing a staycation so will be trying then.

Thanks for checking in and sorry for the delay.

1 Like
60

This is awesome work! This subnet thing with roon really drives me nuts. I have two UDM pros running a site to site VPN which I just set up tonight. I’m too tired to try this script tonight, but would like to give this a shot ASAP. I’d like to control a roon endpoint on a different subnet. I don’t know why roon has to make their networking so annoying. I have a bluesound on a different subnet from my core and I can’t access it using roon… However with the BluOS app running from a separate subnet there are no issues. Annoying because roon is overall a much better app but with one big networking limitation on my opinion.