This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Quote from: avvdr on February 11, 2006, 23:42:16
Hi Dejuh,
I had similar problems on a Suse9.3 - shortly after starting with vomp (looks very nice...)
Finally I explored that it was really important to have the server machine being setup as router in the DHCP setting, here is my /etc/hdcpd.conf:
#my server is 10.222.11.4, my mvp should get 10.222.10.40
#the next is the important line!
option routers 10.222.11.4;
ddns-update-style none;
allow bootp;
allow booting;
default-lease-time 14400;
subnet 10.222.11.0 netmask 255.255.255.0 {
range 10.222.11.20 10.222.11.40;
default-lease-time 14400;
max-lease-time 172800;
}
group {
next-server 10.222.11.4;
host mvp { # NOTE: Change the hardware ethernet to the MAC address of your actual MVP
hardware ethernet 00:0d:fe:00:78:e6;
fixed-address 10.222.11.40;
filename "dongle.bin.mvp";
}
}
--
you can check this when you login to the mvp with telnet:
telnet 10.222.10.40
root
ping 255.255.255.255
- should give a reply from your server
if you get network unreachable - you missed the router entry.
you can also try
route
if there is a default - OK, otherwise it will fail.
Maybe this helps...
--> Chris - would it be possible to add an error message to the socket send in the vompclient, this will ease searching for such problems (you should really get a socket error there...)
Regards
Andreas
