For ethernet interfaces, we should be able to auto-determine the broadcast IP address and not require users to specify the IP address.

Apparently some people would find this useful.

We can't rely on udp-proxy-2020's auto-learn functionality with site-to-site VPN's because the client/initiator side must have it's packets forwarded over the point-to-point VPN tunnel before we can learn. Ideally, we should use some kind of POSIX API call to figure out the IP address or something of the other end, but for initial testing purposes I guess we can just have the user specify an IP address?

Rather than copy & pasting lines, just parse them.

Hi Aaron,

Thanks for taking the time to take a look! As far as I can tell, everything seems to be running udp-proxy-2020 service is running, I can ping my iPhone from the wireguard machine when it's connected via VPN. A few more notes:

1. Wireguard and udp-proxy-2020 are running on a Raspberry Pi 4. Appears in pcap logs as wireguard.udm-local (local IP 10.0.1.112)
2. Roon Rock (dedicated NUC) appears in logs as rock.udm-local (local IP 10.0.1.25)
3. Router is 10.0.1.1 (different from the wireguard machine, but needed wireguard port forwarding rules are already in place)
4. UDP-proxy version is udp-proxy-2020-0.0.11-linux-armv7
5. UDP-proxy is started via systemd script with: /usr/bin/udp-proxy-2020-0.0.11-linux-armv7 --port 9003 --interface eth0,wg0 --cache-ttl 500 --pcap --pcap-path /home/pi/udp/logs
6. systemctl status shows no errors
7. no difference when using --no-listen flag
8. iphone connects to Wireguard VPN, and I can access Roon (as well as other local resources). The iPhone just doesn't show as an audio zone.

I've included logs with this ticket. Please let me know if anything obvious jumps out at you.

Also, based on some other comments, I was under the impression that ump-proxy-2020 does work with a dedicated Roon Rock install like I have (with wireguard installed on a separate device), but if that's not the case, then please let me know.

Again, very much appreciate you taking a quick look.

-Greg W
Archive.zip

Generally improve logging and support writing logs directly to a file.

Specifically, there seems to be some bug which causes a crash? seems to happen quite rarely though.

On Loopback/Null interfaces, we can't use a broadcast address, but we still don't want to require users to specify the IP address on the CLI. The solution would be to automatically learn the source IP of packets we receive and then send those IP's any packets received on a different interface.

Have to figure out a timeout? Unlike mulitcast/IGMP, clients do not ever "leave". Also, I don't think we'd receive an ICMP host-unreachable error? If so, that would be nice??

Would make things a lot easier to debug if I just wrote a pcap file for each interface.

apparently some/all RasPi's are armv7/32bit not arm64/aarch64

The existing flags are probably confusing for non-technical people. In reality, they're more about what kind of interface you're using so it would be more like --ethernet and --loopback

Would be nice if udp-proxy-2020 supported running as a daemon and writing a pid file to /var/run/udp-proxy-2020.pid or other user defined path.

Dear all
I installed udp-proxy-2020 on a Raspberry 4 (hopefuly correctly) according the guide.
If I ask for the status I get an error like this:

What do I have to do?
P.S. How can I exit the window after receicving this message?
Thanks a lot.

Dear all
I am trying to install the docker image on my Synology.
After choosing "latest" the downlaod alwas fails.
What could be the reason?

this whole case statement should be re-examined and see if it can be optimized. I think we're parsing the packet 3 times ???? Should open a ticket.

Originally posted by @synfinatic in #22 (comment)

I think one of the reasons Roon on the iPhone tends to have issues is the timeout in udp-proxy-2020 is too short. maybe it should be much longer or never expire until it is over written? Should do more testing.

Could someone help me to compile a version for the UDM/UDMP, would be great. The version for the USG does not work

Need to create a container and add support to https://github.com/boostchicken/udm-utilities so that people can run udp-proxy-2020 in a container managed by podman on the latest Ubiqiuti gear.

Would be nice to get a build for pfSense 2.4

Need an old build chain for Asus MerlinLinux stuff. This seems to be the way: https://github.com/Adamm00/amcfwm.git

Needs a fair amount of disk space (>50GB for the build chain?) so getting out of disk space issues with Docker. maybe use Vagrant?

The whole thing about Raw interfaces is because LinkLayer for RAW is 101, but calling pcap.Handle.LinkType() returns the DLT not the LinkType! The result is for Raw interfaces you get either 12 or 14 (depending on OS) instead of 101 which causes nothing but pain. :-/

refactor to make easier to unit test

Originally posted by @synfinatic in #22 (comment)

Hi,

I tried following the instruction on the roon forum but it still don't work.

Below are the pcap files.
pcap files.zip

thxs.

Would love to try this out! I'm attempting to access PS Remote play via the internet behind a double NAT. So I'd like to do port forwarding through zerotier or tailscale on a intranet device that would relay the packets to the playstation and back.

Unfortunately, I only have a raspberry pi to work with as my relay device. Any chance you could do an armv7 release?

Should dig into this error a bit:

level=warning msg="Unable to send 130 bytes from ovpns6 out tun_wg0: send: Address family not supported by protocol family"

and:

level=warning msg="Unable to send 387 bytes from lagg0.500 out tun_wg0: send: Address family not supported by protocol family"

Interim until I can get system packages built

Asus RT-AC68U to be exact.

This should be simple right?

Hey,

Tkronic from the roon forums here. As the title says, roon does not find any audio zones / devices unless i stop and restart the service. After I have done this, the zones stay up and controllable until the device shuts down / disconnects from network. If I leave my desktop where I primarily listen to music at home on 24/7 it is not an issue. When I turn it off or suspend it, I need to access pfsense and stop and start the service. OpenVPN with my phone is not as convenient. I believe openVPN disconnects when the phone is idle / screen off for any significant amount of time. This means, every time I want to listen to Roon on my phone, i need to access pfsense and run the stop start commands.

Note: the phone connects to my core (ROCK on a VM) just fine, it just does not see it as a playable / stream able audio device / zone.

Please let me know what logs I can send, or additional information I can provide that can be of use.

Thanks so much again.

Basically, provide a single docker-compose.yaml file for running Roon, udp-proxy-2020 and OpenVPN. then people only need to worry about port forwarding the OpenVPN port via their firewall.

Is it possible to use AirPlay devices lets say from network two with the Roon Core on network one?

not really any docs. Should add some once I figure out #5 and #6

since I'm using this on pfSense, might be nice to build a proper package for it.

Great project, thanks for putting the time into this. I'm using a Peplink router and have limited access to it via SSH, meaning I can't install any package on my own. I still need to use this project, though, because I want to forward broadcast messages between my home network and my Wireguard network (whose service runs in an instance inside my homelab).

Does udp-proxy work if I run it inside the instance which also runs Wireguard instead of my router? I was trying to get it to work recently and failed, and was wondering if it was possible at all.

Whe I try to run the startup script /mnt/data/on_boot.d/40-udp-proxy-2020.sh on my UNifi UDM-Pro it ends with this error:

Trying to pull docker.io/synfinatic/udp-proxy-2020...
manifest unknown: manifest unknown

The problem is that the docker container image is referenced as synfinatic/udp-proxy-2020:latest in the script but this label does not exist. If i change the label to :v0.0.8 the image is available and the container starts successfully.

Hello,
With startup-scripts/udm-utilities/, no problem to execute the container.

But udp-proxy-2020 is not running in reallity on my UDM

Does anyone have an explanation?
Thanks

any PR which isn't properly formatted go code should fail.

libpcap makes cross compiling harder... how does this work?

we should have some

Not that important, but maybe a nice feature for the future: mDNS repeater like avahi struggle with the same problem that multicast is not supported on point-to-point connections like openvpn tun devices. Just using the mDNS port 5353 with udp-proxy-2020 doesn't work out of the box in a first test

Well centos is dead, but ubuntu would be useful right? Would be nice to have systemd and SysV covered at least

Not sure if there is a use case for this... definitely doesn't seem to be for OpenVPN, but might be nice to be able to specify a prefix or glob or simple regex eth[0-3] to dynamically match NIC's that come and go.

using the ticker for this is kinda ugly... but it works just fine for the needs. probably not worth fixing anytime soon?

Originally posted by @synfinatic in #22 (comment)

Right now the Vagrant file is copying the source code via rsync when the VM is built, not run. The result is that if you don't run make freebsd-clean you'll build an outdated binary. :(

Need to copy the code over and build after the VM comes up.

Thanks for this program, it works great! However, I was having issues with the pfsense startup script instructions. Here is what I got to work properly on 2.5:

1. udp-proxy-2020.conf should be in /usr/local/etc/

2. startup rc script udp-proxy-2020 should be in /usr/local/etc/rc.d/; made executable with chmod +x

3. /etc/rc.conf.local doesn't exist by default and will have to be created or copied from this repo. Unlike freebsd, the rc.conf file gets cleared at boot, so it's important to use rc.conf.local.

4. the freebsd-amd64 binary should be placed in /usr/local/bin; made executable with chmod +x

5. The rc script can't have the dashes in the variable name or a variable error is thrown; this means the start/stop/cleanup/status/commands need to be modified as well.

6. wget isn't installed on pfsense by default but fetch is. This was probably the easiest way to download the files from this repo to their proper directories over ssh.

ending up with a bunch of make targets that need to be documented

https://github.com/tpoechtrager/osxcross

Attached pcap.

Looking to make this work on a Netgate SG-3100
[https://store.netgate.com/SG-3100.aspx]

Maybe the easiest way to do it is create a wireguard tunnel...

https://github.com/WireGuard/wgctrl-go