Harondel J. Sibble wrote:
> In a nutshell, I am separating out my wifi subnet with my 2 mvp's from the
> main subnet. This is using a fortinet router with separate logical lans.
>
> Now, I've gone into the dhcp server (on the router) that handles the wifi
> subnet and added options
>
> 150 - tftp server address
> 67 - boot file
> 17 - root path
>
> These point to the primary subnet which hosts the tftp server. The MVP is
> attached to a WRT54G running DD-WRT V24-SP1 in wireless bridged mode.
>
> But it doesn't work, running dhcp server debug on the fortinet router and
> wireshark on a laptop attached to the WRT, basically tells me what I already
> know, that:
>
> a) the mvp is getting an ip initial address from the router, but it's not
> getting any of the other tftpbooting info it needs.
>
> Now this may be because I have to pass more options to the dhcp server or
> because the option arguments I've already passed are incorrect.
>
> So here's what I've tried for options so far, in all cases I've converted
> them to hex using this site http://www.string-functions.com/string-hex.aspx
>
> 150 - 10.11.12.14 (ip address of mythtv/tftp box on main lan)
> 67 - dongle.bin.mvpmc
> 17 - root-path "/home/mvp,rsize=4096,wsize=4096,nolock"
>
> Any ideas, suggestions etc?
Ouch, that's could be tricky depending on what MVP rev(s) you have. I
have revH boxes, and in addition to the regular MythTV stuff they require:
69/udp "regular" tftp server
16869/udp "MVP" tftp server
16881/udp MVP boot handler [1]
[1] I'm using http://mvpmc.wikispaces.com/mvpboot
I'm hazy on how much of the info they get from the DHCP server they
actually use.
I think for my versions, it finds the MVP boot hander by a *broadcast*,
and that is NOT going to be routed. Then that handler gives it
everything else it needs to know. I'm not sure how to get around the
broadcast domain problem. Sometimes there are proxies for stuff like
this (e.g. for bootp and WINS), but since this one is so specialized I
doubt it. Your router might have a way to forward broadcasts but that's
not too likely either. You might be stuck having to run an mvpboot
instance on a machine on each subnet, or making the router a bridge and
having physical segments in one logical broadcast domain. Which is
probably what you have now that you are trying to get rid of.
Though all bets are off if you have different MVP devices that work
differently than mine. :-)
Also, it is my understanding the tftp is a pain with a firewall, for
reasons similar to FTP. I know you said "router," so if routing works
that stuff *should* be OK once you get to that point. In theory. If
it's really a router and not trying to be a firewall too...
HTH and good luck,
JP
----------------------------|:::======|-------------------------------
JP Vossen, CISSP |:::======| jp{at}jpsdomain{dot}org
My Account, My Opinions |=========| http://www.jpsdomain.org/
----------------------------|=========|-------------------------------
"Microsoft Tax" = the additional hardware & yearly fees for the add-on
software required to protect Windows from its own poorly designed and
implemented self, while the overhead incidentally flattens Moore's Law.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Mvpmc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mvpmc-users
mvpmc wiki: http://mvpmc.wikispaces.com/
