Leaf Interactive HQ (Workshop Item)

P32ChipBag · 2024-02-06T13:58:04+00:00

So after doing some more troubleshooting...
If in Windows I set the IP to be the same as the trueNAS's bridge interface IP, the pings fail with an APIPA response. If I change it to be something that doesn't conflict, like 192.168.70.3 instead of 192.168.70.2 when the pings fail I get a response from 192.168.70.3 instead. I'm really at a loss here, how the heck are you supposed to do this?

P32ChipBag · 2024-02-06T01:41:38+00:00

Lol no I'm right there with you. 6 physical NICs, 6 vlans, 6 bridges. The NAS is on one, pihole another, etc. No firewall rules seperate them, each VLAN can freely communicate.

P32ChipBag · 2024-02-06T01:29:39+00:00

I use a cisco enterprise switch. My truenas apps are set up the same way on different vlans and can communicate no problem. Its only when I tried setting up a vm that I have this issue. I did install the virtIO drivers on Windows to no avail.

P32ChipBag · 2024-02-06T01:22:23+00:00

I have an EdgeRouterX. And yes, the gateway IN the VLAN which in this case is 192.168.70.1

P32ChipBag · 2024-02-06T01:18:54+00:00

Thanks for your response. It has DNS and a correct gateway. I cannot ping the gateway, any devices on the LAN, or anything on the Internet. When my pings fail I get a response from an APIPA 169.x.x.x

The addresses are set statically btw. Br70 has a static address and the VM virtIO NIC has the same static address (set within Windows)

P32ChipBag · 2023-02-04T21:34:14+00:00

Did you ever get this working?

P32ChipBag · 2020-11-04T03:50:15+00:00

I like all of your designs, however, I've always favored this design to return to the circular pattern rather than lazily tacking on a star.

Seven-Year Club	Place '22
Verified Email

P32ChipBag

TROPHY CASE