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

MVP doesn't work on a new router

Started by ofenheizer, July 25, 2007, 23:42:29

Previous topic - Next topic

ofenheizer

Hi,

I have an new router (D-Link DGL-4300) with 4-Port-Gigabit-Switch.
Now the MVP loads 4 of 5 blue stripes. And than nothing. The log of vompserver:00:29:26.950849 [debug]  BOOTPD - Wait finished
00:29:26.950890 [debug]  BOOTPD - Got request
00:29:26.951029 [debug]  Config - Opened config file: /etc/vdr/plugins/vomp-00-0D-FE-00-6C-83.conf
00:29:26.951048 [debug]  BOOTPD - Opened config file: /etc/vdr/plugins/vomp-00-0D-FE-00-6C-83.conf
00:29:26.951219 [debug]  BOOTPD - Found IP 192.168.0.8 for MVP
00:29:26.951300 [debug]  BOOTPD - Will enforce IP 192.168.0.8 on MVP even if it already has another
00:29:26.951321 [debug]  BOOTPD - Giving MVP IP from config
00:29:26.951501 [debug]  BOOTPD - Starting wait
00:29:27.082281 [debug]  Tftpd - Wait finished
00:29:27.082333 [debug]  TftpClient - Client handler started
00:29:27.082464 [debug]  Tftpd - Starting wait
00:29:27.082500 [debug]  TftpClient - RRQ received for dongle.bin
00:29:27.082532 [info]   TftpClient - File: '/tftpboot/dongle.bin'
00:29:32.520958 [info]   TftpClient - File transfer finished
00:29:32.521033 [info]   TftpClient - processMessage terminating connection

MVP gets a reserved IP per DHCP from the router.

The same config works with the old enviroment (FLI4L-Router with Gigabit-Switch)

Any ideas??

THX and greets,
ofenheizer

dbm

I ran into this a while back - i believe that the MVP *firmware* bootloader successfully gets a DHCP address, but the newly booted MVP kernel asks DHCP *again* (now that linux is running), and *that* second DHCP request does not interact well with your setup - DHCP protocol problem we're guessing.

options - fix the MVP's linux DHCP, or get a different DHCP server that interacts better with the MVP's linux-based DHCP requests. or ???

we used a different router...

good luck!

--dbm

Bandit2001

I know this well.
My vdr now acts as DHCP-Server and it works fine.
Aller Anfang ist schwer..
New VDR:
HP Microserver Gen8 G1610T, 4GB RAM, TBS-6982,  easyVDR 2.5.0 stable

fxmx86

That was the same for me when I changed my router, so my VDRLive machine now act as DHCP server...
The kernel's DHCP needs to be fixed, may be replaced by the busybox udhcp client ?

A+