Hi,
I have here a H3 successfully booting to the point where it udp broadcasts 255.255.255.255 port 3024 to find the server.
The problem is, that my VDR is in a different subnet. Is there any way to get this configuration work (without changing the subnet)?
Perhaps with a directed x.x.x.255 broadcast to the VDR subnet ?
Or better: A DHCP option to tell the client where the next server is?
jack
Hi,
I had the same problem. I've post a correction into this section : http://www.loggytronic.com/forum/index.php?topic=159.msg882#msg882.
@+
Quote from: ramses2 on October 31, 2006, 12:44:36I had the same problem. I've post a correction into this section : http://www.loggytronic.com/forum/index.php?topic=159.msg882#msg882.
I think your problem is a different one, correct me if I'm mistaken:
Your MVP still is directly connected to the VDR w/vompserver.
So if the MVP is booting up it will find the vompserver by the 255.255.255.255 port 3024 broadcast.
Your problem was the answer from the vompserver to the mvp.
My problem is that the MVP after booting the firmware did NOT FIND the vompserver by the 255.255.255.255 port 3024 broadcast.
So the vompserver does not have any chance at all to tell the MVP in which subnet it is.
Here my configuration:
VOMPSERVER ----subnet1---- Router (w/DHCP server) ----subnet2---- MVP (H3)
jack
You're right the problem is different. Sorry!
To solve your problem, you will have to transform the broadcast (blocked by the router) to an unicast packet (routed by the router).
@+
What's the model of your router ? If it's a cisco you can use a "helper address".
@+
The router is a linux server with multiple interfaces.
jack