News:

Latest versions:
Server plugin: 0.5.1
MVP dongle: 0.5.2
Raspberry Pi client: 0.5.2
Windows client: 0.5.2-1

Main Menu

Trying to use builtin bootp/tftp

Started by dingo35, February 13, 2008, 14:29:53

Previous topic - Next topic

dingo35

Hi all,

I'm using vomp for several years now, and I am very happy with it. One thing bugs me, and that is that I've never succeeded in using the built in bootp/tftp functionality. Now that I am going to use a new router without tftp functionality, I want to give it another try.

Having modified vomp.conf and vomp-xx-xx.conf according to the instructions, my vomp-logfile reports:

14:34:13.694852 [info]   Main - Logging started
14:34:13.695080 [debug]  UDPReplier - UDP replier started
14:34:13.695205 [debug]  BOOTPD - Starting bootpd
14:34:13.695281 [debug]  BOOTPD - Starting wait
14:34:13.695314 [debug]  BOOTPD - Bootp replier started
14:34:13.695389 [info]   Main - TFTP path '/var/lib/tftpboot/'
14:34:13.695413 [debug]  Tftpd - Starting TFTPd
14:34:13.695480 [debug]  Tftpd - Starting wait
14:34:13.695511 [debug]  Tftpd - TFTP server started with base path '/var/lib/tftpboot/'
14:34:13.695585 [debug]  MVPRelay - MVPRelay replier started
14:34:13.695612 [info]   Main - MVPRelay started
14:34:13.695763 [debug]  Main - MVPServer run success
14:36:35.935878 [debug]  BOOTPD - Wait finished
14:36:35.936003 [debug]  BOOTPD - Got request
14:36:35.936424 [debug]  Config - Opened config file: /usr/local/vdr/etc/plugins/vomp-00-0D-FE-00-3F-92.conf
14:36:35.936452 [debug]  BOOTPD - Opened config file: /usr/local/vdr/etc/plugins/vomp-00-0D-FE-00-3F-92.conf
14:36:35.936550 [debug]  BOOTPD - Found IP 10.0.0.120 for MVP
14:36:35.936628 [debug]  BOOTPD - Will enforce IP 10.0.0.120 on MVP even if it already has another
14:36:35.936655 [debug]  BOOTPD - Giving MVP IP from config
14:36:35.936900 [debug]  BOOTPD - Starting wait
14:36:44.955845 [debug]  BOOTPD - Wait finished
14:36:44.955936 [debug]  BOOTPD - Got request
14:36:44.956207 [debug]  Config - Opened config file: /usr/local/vdr/etc/plugins/vomp-00-0D-FE-00-3F-92.conf
14:36:44.956236 [debug]  BOOTPD - Opened config file: /usr/local/vdr/etc/plugins/vomp-00-0D-FE-00-3F-92.conf
14:36:44.956343 [debug]  BOOTPD - Found IP 10.0.0.120 for MVP

and so on...

I turned my dhcp server and my xinetd (with tftpd) off, and used manual IP override by vomp, but it seems that Tftpd and Tftpclient do not kick in. There is also nothing listening on port 69, where usually tftp listens.

I read somewhere that vdr needs to run as root to access ports <1027 . Do I need to run vdr as root to have vompserver listen to port 69, or is there some other problem?  Any suggestions on solving/debugging this problem?

Thanks in advance!

P.S.: Running vdr as root is not an option on my production platform, so that's why I didn't try running as root myself....

dingo35

Running as root did not solve the problem.

Eventually I got it working by changing from my dnsmasq - dhcp server (on the same machine as vdr) to the dhcp server of my router; this network topology is more general and now it works exactly as documented...

Thanks Chris & all others, for this great software!