Connecting Server and PS3 on Different nets

[SirLouen]

I have my Server with PMS in a net 192.168.100.X connected to a Router 192.168.100.1

And the PS3 is in another net 192.168.200.X connected to a Router 192.168.200.1

Thing is if I ping my PS3 from the server I get a correct response from the PS3.
But I cannot know if the PS3 is reaching the Server since I don't have a ping tool on the PS3

The problem is that the Server does not find the PS3
I have forced the network interface and the IP address to my servers settings
And I don't find any strange errors on the debug console:
INFO 2013-01-04 16:06:09.901 [main] Using forced address 192.168.100.100
INFO 2013-01-04 16:06:09.902 [main] Created socket: /192.168.100.100:5001

What might be happening?

[meskibob]

While the ping test listed in the FAQ is a quick way to generally test the subnet, there are ways to configure a network to allow the ping while not forwarding the UDP broadcasts.
Is there a need for the two different subnets? Can you explain your network setup a bit more clearly (maybe including a diagram)?

[SirLouen]

I have this configuration

WIFI Router --- PS3 (DLNA Client, 192.168.200.3)
|(192.168.200.1)
|
|Wifi
|
|(192.168.200.2)
WIFI Router (Wireless Client && DD-WRT)
|(192.168.100.1)
|
PC1 (DLNA Server, 192.168.100.100)

Why Wireless Client (multiple subnets) and not Wireless Bridged Client (keep it simple with one subnet)?
Because in PC1 I have multiple Virtual Machines running, and in Bridged Client mode, when one access Internet, the others lose connection (even the host lose connection), is like a problem of data multiplexing or something, but in Wireless Client mode, everything goes fine.

[meskibob]

Given that setup, you'll need to configure udp forwarding so 192.168.100.1 forwards the broadcast across the subnet to 192.168.200.1. I do not know if DD-WRT has a direct setting for it or if it will be possible with IP tables.
As to why you have this configuration, is it that 192.168.100.1 just craps out when running as a wireless bridge and connecting multiple VM clients on PC1? Could you (just throwing out some ideas here)
a) wire (either directly or with homeplugs) .100 to .200 so you can test a wired bridged subnet?
b) change your setup so .200 is slaved to .100?

[SirLouen]

As i see here is a huge problem to make DLNA work on diff subnets: http://superuser.com/questions/421532/h ... rent-ip-ne

a) My PMS server was running well before (before I had wired connections P2P, but in my new home, I had to this "wireless tricky system" in order to get things working temporarly), so is not a problem of the server itself, seems to be a network issue
b) As you say, when I connect multiple VM to PC1 wireless bridge craps out. I believe that the wireless bridge binds just one IP to the end-point, then when I assign multiple IPs (1 to the host, and X to the multiple VMs), it tries to do a multiplexed connection someway, and goes crazy, don't know if it is an issue of DD-WRT itself, or some config I have not detected, since I do this config by following the dd-wrt manual step by step.

As I expect DLNA is a PnP protocol with broadcast methods, so it may be impossible to restrict the connection to just one host (to point directly to the DLNA server). So the only solution I find, is to create somehow a "virtual" broadcast in the other subnet (if it is possible).

[meskibob]

I've heard of UDP broadcasts being forwarded from one LAN out to another, but
a) I can't find the reference where I saw that (so I may just be making stuff up)
b) IIRC it didn't mention UPnP/DLNA specifically, so there might be an additional wrinkle that makes it impossible in this case
c) I haven't tried it

[SirLouen]

I feel i must find any other solution
As I've read on DD-WRT:
In this case, the UDP packet arrive on the WAN port and is forwarded to the LAN. By default, latest Tomato (v1.25) and DD-WRT (24SP2) do not support UDP forward to a broadcast address.

[meskibob]

That's the opposite case, where an external device is sending into the LAN. In this case, .100 is receiving the broadcast on a LAN port, and then (if this worked) sending that broadcast on its WAN port to a LAN port on .200.

[DrakeFS]

you need to setup router tables or change the subnet mask to 255.255.0.0

[SirLouen]

DrakeFS, I've changed the mask to 255.255.0.0, but I believe the problem is behind the Wireless Client setting. For some reason, it "encapsulates" the network, so for example If I configure all the network with 255.255.0.0 parameter I cannot ping for example from 192.168.200.100 to 192.168.100.100, even routing is not working for some reason, while with a 255.255.255.0 at least routing works fine.

About setting router tables, any more concrete idea based on the config I displayed above?