It's the way networks work.
One server will broadcast its existence using the network's broadcast IP.
So a server at 192.169.1.1(/24) will broadcast its existence only to
192.168.1.255 so only Clients at the
network 192.168.1.0 (/24) will of the server being there.
The best way I can imagine so that clients will know if a server is
online, would be to add the servers IP to the favorite tab of each
client so the the client asks the server if it's online.
--
feugatos
CEID Warfare | TF2, CS:GO, ZPS | ceidwarfare.net
On 11/9/2012 6:10 μμ, Steven Miano wrote:
I'm stuck at the moment trying to figure out dedicated servers on a LAN.
Right now I have 15 different VLANs on my network (15 separate
192.168.x.x/24s). I have them segregated for management, and visibility at
the LAN parties mostly.
Having my game servers sitting on 192.168.3.0/24 and having my guests on
(just citing one VLAN as an example) 192.168.6.0/24 makes it so that the
dedicated server does not show up in their LAN tab in game.
Running tcpdump -n "broadcast" isn't showing me anything on the game server
(hoping to forward the broadcasts via pfsense from one vlan to the others).
How can I assure that my source dedicated servers are viewable on the LAN
tab for this network?
Thanks for any assistance,
mianosm
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
