On Friday, March 30, 2018 at 2:21:49 PM UTC-7, awokd wrote: > On Fri, March 30, 2018 8:30 pm, Fox Gluv wrote: > > Looking at the network traffic, the UDP packets that are not making it > > through have a destination of 255.255.255.255 (broadcast), so I'm > > guessing a simple Port forwarding NAT won't work. Would a MASQUERADE work > > better? > > > > Summary question - how do I forward UDP broadcast (255.255.255.255) > > traffic from a separate Win10 machine, to a Qubes 4.0 VM running Debian > > 9? > > I'm not sure it's possible to inbound NAT broadcast traffic, have never > heard of a need for it. There's no way to change Steam to send to a > specific IP/port? The ugly hack approach would be to directly attach a > secondary NIC inside the VM you want to receive broadcast traffic but of > course, you lose a lot of layers of protection by doing that. > > > Also, should I just take this to a networking forum? > > Possibly, maybe some iptables wizard could figure out a way to turn that > broadcast traffic into directed.
To close the loop on this, awokd is correct that it is not easy to NAT broadcast traffic. I found a couple ways that might work, but it breaks the purpose/design of broadcast. The best solution I found was to set up a VPN between the server machine and the specific qubes VM. In the end, I sacrificed some security and set up mult-boot. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/18df7979-4dd7-40c5-8025-ce8df513928f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
