d6jg wrote: > VLANs may work but there are reports of UDP traffic jumping across them > - I think it is hardware vendor specific as to whether it blocks or > not. > > However what should work would be segregated routers i.e. > > 1. Router 1 that connects to Internet and serves one part of your > network topology on one subnet (network 1) > 2. Router 2 that connects from its WAN side to Router 1 on a LAN port > and serves the other portion of your network on an entirely different > subnet (network 2) > > Router 2 should automatically block UDP traffic leaving network 2 on its > WAN side. > > network 2 is then double NATd but for internet traffic there will be no > issue. > > Obviously whether or not you can do this depends a little on your > cabling structure.
I'm afraid having two routers with double NAT is not an option due to constraints from my ISP... In the mean time I did the following test which leaves me somewhat confused: I disabled port 3483 both tcp and udp on the second server that runs LMS-B and restarted LMS-B. All but one of the clients have the -s option set to connect to server LMS-A. One client (client-B) has the -s option set to connect to LMS-B. When accessing LMS-B from another machine using the Default web interface, all clients but the one client-B are visible. When accessing LMS-B from that same machine using the new Material skin, it hangs on "Looking for players". Enabling port 3483 udp has no effect. Only after enabling 3483 tcp is client-B found on the 'Material' interface and client-B also shows up on the Default interface... ------------------------------------------------------------------------ baggins's Profile: http://forums.slimdevices.com/member.php?userid=63843 View this thread: http://forums.slimdevices.com/showthread.php?t=109914 _______________________________________________ Squeezecenter mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/squeezecenter
