whenever i change my server bridge directive in my conf to not specify an ip address, i get a random address not on my remote lan at all (I think IP's starting with 169 usually can't connect to dhcp). I'm really confused as to what's going on at this point

Thanks for the reply James. I had set to subscribe to this thread but never got an email when you replied? Weird. Anyway, I can ping the server's remote LAN IP but no one else on the remote subnet. Viscosity is getting a proper IP address from the "server-bridge" directive in my server con...

Like the subject says. I'm able to open a bridged (tap) connection to my openvpn server, but I can't see any of the devices on the lan subnet that I'm connected to...I assume it's a routing issue. In my Viscosity connection preferences, I have "send all traffic over vpn connection" checked...