Larian Studios Forums Baldur's Gate III Baldur's Gate III - Suggestions & Feedback Multiplayer Direct Connect / Lan Improvements

So here I am at home. I bought three copies of the game. One for myself and two for my two sons.
I was hoping to get an actual direct connect game going but it was met with complete frustration.

While we share the same household, the machines are on different vlans.
This presents a problem for the "LAN" connection because we aren't on the same lan.
As for Direct Connect, that has to traverse the firewall and get some weird token from Larian servers.
Presumably that'll involve Larian servers for all gameplay.
Not only that, that traffic have to actually leave and traverse firewalls and get Nat'd back to the host machine.

What this set of options needs is for the ability for someone to input the ip address of the machine they want to connect to directly. (or hostname for that matter)
This would a) alleviate the need to talk to Larian servers and b) allow more advanced users to input an ip address of their choosing and just let their routers do the work.

There's no reason why people on different L2 segments need to have to revert to traversing firewalls at the edges w/ reverse nat and all that jazz.

Multiple vlans in a home setting isn't common; completely understand and agree, but letting end users physically give an ip address to connect to a host isn't "magical" either.

Great game btw and thank you!

It's called a 4 port routor and you can find them as cheep as $10 in op shops + 3 bits of network cable = problem solved without touching your vlans

You could of course also set those vlans to share the same network instead (or as well) of being different lines

If you have a /24 segmented into several /26's and you want to route between each segment that's the job of the router. I HAVE the router.

The problem here is I cannot tell BG3 to direct connect to an ip within a different segment than the one I'm currently on.

Direct Connect pokes a hole in your firewall w/ reverse nat (I presume) and then anyone connecting to you within your home needs needs to traverse your firewall twice and have that same packet natted twice .. once for outbound and again for inbound.

The opportunity to route doesn't even occur because the destination isn't one on your network.

Really the easiest solution is for multiplayer to simply offer the opportunity to connect to a specific ip. With that, the router can actually route the packets away from the firewall/nat and onto the appropriate lan segment.



Your comment about setting those vlans to share the same network makes no sense.
Instead it seems like you meant to say put all those machines in the same vlan which yes, would work, but defeats the purpose of keeping unstrusted networks segregated from trusted networks.