New switch = boot problem

[stu-e]

I recently changed my broadband adsl router which I also use a the main switch in my home ethernet network. Now my mvp will not boot the vompclient. I changed back to my old router/switch and it works fine. Both routers are set as the network dhcp server. If the vompserver is not running I can ping the mvp at its dhcp assigned address, but after it has loaded the dongle it disappears from the network. Ping gets no response and after some time even the mac address disappears from arp. The new router is a Thomson TG585.

Anybody know why one switch would work and another will not?

Here is my vompserver.log

Code Select Expand

00:19:19.080715 [info]   Main - Logging started
00:19:19.080767 [debug]  Config - Config error: Key Server name not found
00:19:19.080809 [debug]  UDPReplier - UDP replier started
00:19:19.080870 [debug]  BOOTPD - Starting bootpd
00:19:19.080893 [debug]  BOOTPD - Bootp replier started
00:19:19.080925 [debug]  Config - Config error: Key TFTP directory not found
00:19:19.080948 [info]   Main - TFTP path '/video0/plugins/vompserver/'
00:19:19.080954 [debug]  Tftpd - Starting TFTPd
00:19:19.080897 [debug]  BOOTPD - Starting wait
00:19:19.080978 [debug]  Tftpd - Starting wait
00:19:19.080986 [debug]  Tftpd - TFTP server started with base path '/video0/plugins/vompserver/'
00:19:19.081019 [info]   Main - Not starting MVPRelay
00:19:19.081036 [debug]  Main - MVPServer run success
00:19:56.538360 [debug]  BOOTPD - Wait finished
00:19:56.538499 [debug]  BOOTPD - Got request
00:19:56.538540 [debug]  Config - Opened config file: /video0/plugins/vompserver/vomp-00-0D-FE-00-44-AB.conf
00:19:56.538562 [debug]  BOOTPD - Opened config file: /video0/plugins/vompserver/vomp-00-0D-FE-00-44-AB.conf
00:19:56.538620 [debug]  Config - Config error: Key IP not found
00:19:56.538643 [WARN]   BOOTPD - No IP found for MVP. Hopefully it has one already...
00:19:56.538680 [debug]  Config - Config error: Key Override IP not found
00:19:56.538701 [debug]  BOOTPD - Will not change MVP IP if it already has one
00:19:56.538721 [debug]  BOOTPD - No IP found to give to MVP
00:19:56.538741 [debug]  BOOTPD - Starting wait
00:20:05.558055 [debug]  BOOTPD - Wait finished
00:20:05.558165 [debug]  BOOTPD - Got request
00:20:05.558206 [debug]  Config - Opened config file: /video0/plugins/vompserver/vomp-00-0D-FE-00-44-AB.conf
00:20:05.558228 [debug]  BOOTPD - Opened config file: /video0/plugins/vompserver/vomp-00-0D-FE-00-44-AB.conf
00:20:05.558284 [debug]  Config - Config error: Key IP not found
00:20:05.558309 [WARN]   BOOTPD - No IP found for MVP. Hopefully it has one already...
00:20:05.558346 [debug]  Config - Config error: Key Override IP not found
00:20:05.558366 [debug]  BOOTPD - Will not change MVP IP if it already has one
00:20:05.558394 [debug]  BOOTPD - No IP found to give to MVP
00:20:05.558414 [debug]  BOOTPD - Starting wait
00:20:19.605161 [debug]  BOOTPD - Wait finished
00:20:19.605271 [debug]  BOOTPD - Got request
00:20:19.605313 [debug]  Config - Opened config file: /video0/plugins/vompserver/vomp-00-0D-FE-00-44-AB.conf
00:20:19.605335 [debug]  BOOTPD - Opened config file: /video0/plugins/vompserver/vomp-00-0D-FE-00-44-AB.conf
00:20:19.605395 [debug]  Config - Config error: Key IP not found
00:20:19.605418 [WARN]   BOOTPD - No IP found for MVP. Hopefully it has one already...
00:20:19.605455 [debug]  Config - Config error: Key Override IP not found
00:20:19.605476 [debug]  BOOTPD - Will not change MVP IP if it already has one
00:20:19.605496 [debug]  BOOTPD - Leave YI=0 as MVP already has good IP
00:20:19.605562 [debug]  BOOTPD - Starting wait
00:20:19.735737 [debug]  Tftpd - Wait finished
00:20:19.735846 [debug]  TftpClient - Client handler started
00:20:19.735910 [debug]  Tftpd - Starting wait
00:20:19.735919 [debug]  TftpClient - RRQ received for vomp-dongle-0.3.0cvs230509
00:20:19.736020 [info]   TftpClient - File: '/video0/plugins/vompserver/vomp-dongle-0.3.0cvs230509'
00:20:26.955852 [info]   TftpClient - File transfer finished
00:20:26.955978 [info]   TftpClient - processMessage terminating connection


Stu-e

[Chris]

I can only provide clues..

The point when it has loaded the dongle and disappears from the network is the point when Linux starts booting. The network interface link is restarted and then DHCP is done again from the kernel. See if the network link light comes back on on the switch for the mvp (if it has lights).

[stu-e]

The led activity on the ethernet connector goes something like this:
Apply power
Orange on, Green occasionally flashes
Orange remains on, Green rapid flashing
Orange remains on, Green off
Orange off, Green off
Orange on, Green off

The Hauppauge splash screen is still showing on tv with all but one of the white progress squares filled.
And that is as far as it gets.
Does this tell us anything?

Stu-e

[stu-e]

Can Vomp operate without a DHCP server or can I force the Vompclient to ignore the DHCP server? I am having difficulty getting either way to work.

Stu-e

[stu-e]

In order to test whether the problem was with my new adsl router, I setup my old adsl router that works but turned off the dhcp server in it so that it was in effect just a basic ethernet switch. I set the pc ethernet address manually and also the MediaMVP address manually in its vomp-mymacaddresshere.conf file. This setup did not boot the MediaMVP with identical results to that I described earlier, that is boot stops at the point where the MediaMVP successfully downloads its dongle.

I replaced the adsl router with a bog standard 8port 100mbit ethernet switch with identical results.

Can anybody suggest where the problem is here?

Tonight I am going to try it without any form of switch, just a direct ethernet cable (with tx/rx swapped round). I can't simplify things anymore than that. I would like to try using a dhcp server in my pc but the Mandriva package I have has a buggy dhcpd.conf file that needs work.

Stu-e

[stu-e]

I'm still having no success getting my MVP to boot. I set up a DHCP server with the following dhcpd.conf file:

Code Select Expand

ddns-update-style none;

subnet 192.168.1.0 netmask 255.255.255.0 {
option routers 192.168.1.64;
option subnet-mask 255.255.255.0;

default-lease-time 21600;
max-lease-time 43200;
group {
next-server 192.168.1.64;          # IP address of your TFTP server

host mvp {
hardware ethernet  00:0d:fe:00:44:ab;
fixed-address 192.168.1.100;
filename "vomp-dongle-0.3.1";
}
}
}


I disabled the vompserver bootp server but enabled the vompserver tftp server.

The MVP is assigned the ip address ok but appears to make no contact with the tftp server. vompserver.log gets up to [debug]  Tftpd - Starting wait, then nothing.

The mvp is a rev d3a. I am using a basic ethernet switch. My Linux distro is Mandriva 2009.1. There are no other devices attached to my network.

Please, any help would be much appreciated.
Thanks

Stu-e

[davep]

I'm running VOMP on a Mandriva 2009.1 box and have no problem booting the client. My dhcpd.conf is identical to yours except for the IP addresses. However I use the Mandriva tftp server rather than the one in vompserver - could that be a solution?

[stu-e]

Ok I have had some success.
With my Linux box configured with a DHCP server and a TFTP server my MVP will boot fully with a plain ethernet switch or my new ADSL router (providing DHCP in the ADSL router is disabled). So I am happily back to a state where I can view my recordings!

The fact remains though I could not get the MVP to boot successfully using the vompserver built in bootp and tftp servers or even the built in tftp server and a separate dhcp server, using a plain ethernet switch.

Stu-e

[edit] Please note I have always disabled the Linux box firewall.

[dingo35]

I had the same problems when using dnsmasq as a dhcp server on my video-server, on which also tftp-server was running.

All problems disappeared when I started using my dslmodem/router as dhcp-server, from then on built in stuff from vomp worked fine; which is probably the setup of 99% of all users...

So you are right, there is some bug in there, but not a lot of people notice it, and the workaround is relatively simple.