--- On Thu, 2/12/09, Rob Pimentel <[email protected]> wrote:
> From: Rob Pimentel <[email protected]>
> Subject: Re: Unable to connect to MediaMVP
> To: [email protected]
> Date: Thursday, February 12, 2009, 5:44 PM
> > From: Byron Jeff <[email protected]>
> > Subject: Re: [Mvpmc-users] Unable to connect to
> > the same on my network. It's a pretty simple
>
> Thank you. This was very helpful. Thank you to others who
> also offered advice on the dhcp server. It was actually
> easier to set up than I expected. Providing long enough
> leases relieved my concern of not having the DHCP server
> available when clients wanted to renew, since I won't
> have my myth box up 24/7.
>
> My new DHCP server is handing out IPs nicely to both
> Windows & Linux clients. However, it refuses to hand
> out
> an IP to the MVP. I'm using static IPs for all of the
> clients. I've double-checked the MAC for the MVP in my
> dhcpd.conf and it is correct. When I look at the router
> log,
> I see:
>
> [INFO] Fri Jul 04 19:29:34 2008 Access denied to LAN system
> with MAC address <my MVP's mac address>.
>
> I do have MAC filtering enabled in the router, but I
> double-checked, and the MVP's MAC is allowed access. Am
> I having problems because I need to load the firmware
> before
> it can get an IP? I took an initial stab at setting up the
> TFTP server, but the MVP didn't bite. I believe I am
> missing the dongle.bin.config file. I'll need to do
> more
> research into that.
>
> Thanks,
> pimy
Here is my dhcpd.conf file:
*******************************88
# dhcpd.conf
#
# Sample configuration file for ISC dhcpd
#
# option definitions common to all supported networks...
option domain-name-servers 192.168.10.1;
#option ip-forwarding off;
# Default lease is 4 weeks (2419200 sec.)
default-lease-time 2419200;
# Max lease is 16 weeks (9676800 sec.)
max-lease-time 9676800;
allow bootp;
allow booting;
ddns-update-style none;
# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
authoritative;
# No service will be given on this subnet, but declaring it helps the
# DHCP server to understand the network topology.
#subnet 10.152.187.0 netmask 255.255.255.0 {
#}
# This is a very basic subnet declaration.
subnet 192.168.10.0 netmask 255.255.255.0 {
#range 192.168.10.96 192.168.10.96;
option routers 192.168.10.1;
option broadcast-address 192.168.1.255;
option subnet-mask 255.255.255.0;
# Hosts which require special configuration options can be listed in
# host statements. If no address is specified, the address will be
# allocated dynamically (if possible), but the host-specific information
# will still come from the host declaration.
# office workstation
host lance {
hardware ethernet <the mac>;
fixed-address 192.168.10.96;
}
# mvp 1
host mvp1 {
hardware ethernet <mvp mac>;
fixed-address 192.168.10.97;
#filename "/tftpboot/dongle.bin.mvpmc";
filename "dongle.bin.mvpmc";
option root-path "/var/myth,rsize=4096,wsize=4096,nolock";
# IP address of TFTP sever
next-server 192.168.10.99;
option host-name "mvp1";
}
# laptop
host lappie {
hardware ethernet <another mac>;
fixed-address 192.168.10.98;
# IP address of TFTP sever
next-server 192.168.10.99;
filename "test.txt";
option root-path "/var/myth,rsize=4096,wsize=4096,nolock";
}
# windows machine
host blah {
hardware ethernet <mac add>;
fixed-address 192.168.10.101;
}
# print server
host ps1 {
hardware ethernet 00:40:05:4A:CD:AA;
fixed-address 192.168.10.100;
}
}
************************
Here is my /tftpboot/dongle.bin.mvpmc.config file:
# Setup time and date
TZ='EST+5EDT,M3.2.0/2,M11.1.0/2' ; export TZ
echo "TZ='EST+5EDT,M3.2.0/2,M11.1.0/2'; export TZ" > /etc/shell.config;
NTP=192.168.10.99
# Make the directory for mounting
mkdir /var/myth/
# and mount it (linux/windows)
/etc/nfsmount.sh 192.168.10.99:/var/video/ /var/myth/
# Setup some environmental variables so we can use the host name (mvp1 for
example)
HNAME=`hostname` ; export HNAME
# Now we invoke mvpmc adding the -F option
mvpmc -f /etc/helvB14.pcf -o composite -S 0 -s 192.168.10.99 -p thepass -u
theuser -y 192.168.10.99 -T
mythconverg -r /var/myth -F /var/myth/cfgs/$HNAME.cfg &
# If you don't want to make hostname available via the environment , you can
use -F /var/myth/cfgs/`h
ostname`.cfg
# and drop the Setup export line.
# Now on our mount we can save settings to a file called $HNAME.cfg which
translates to mvp1.cfg
# this file is saved on our mount point and can be created through the
Settings->save settings
# mvpmc menu. So go ahead and tweak the volume, brightness etc and your
setting file will be created
# then when you boot back up the mvp will fetch this file restoring your
settings
*********************************************
When I power on my mvp, I don't see a DHCPDISCOVER. All I see is a single red
bar on the front.
Any ideas what is wrong?
Thanks,
Rob
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Mvpmc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mvpmc-users
mvpmc wiki: http://mvpmc.wikispaces.com/
