JP

On 9 Nov 2008 at 15:40, JP Vossen wrote:

> 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:

These are the older Model 86001 Rev D3A units.

>       69/udp          "regular" tftp server
>       16869/udp       "MVP" tftp server       

I saw some of that (mediamvp boot server) in wireshark, but IIRC it was port 
16867 sending and 16868 receiving...

>       16881/udp       MVP boot handler [1]
> [1] I'm using http://mvpmc.wikispaces.com/mvpboot

Right as I remember from previous threads that's needed with the new models 
right?
 
> I'm hazy on how much of the info they get from the DHCP server they 
> actually use.

That's what I need to find out and also what is being served.
 
> I think for my versions, it finds the MVP boot hander by a *broadcast*, 

I do see some broadcast packets,

> 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), 

This router has some dhcp/bootp relay agents, also policy routing to push 
through stuff that wouldn't normally get transmitted.

> doubt it.  Your router might have a way to forward broadcasts but that's 
> not too likely either.  

No, it's an enterprise class router so it just might have that, however I 
suspect it's not exposed at the gui level and I'll have to drop to the cli 
for that sort of thing.

> You might be stuck having to run an mvpboot instance on a machine on
> each subnet, 

I am trying to avoid that as I don't have ANY (and don't want any) PC's on 
the other subnet other than transiently.

> or making the router a bridge and having physical segments in one
> logical broadcast domain.  

Nope, want to avoid that also so I can lockdown the types of traffic that 
flow from the wifi subnet onto the main lan subnet.  What with the WPA/WPA2
potentially going to fall soon 

    http://pacsec.jp/

    See the second talk... rumour has it WPA2 can be broken in under 15
    minutes...

The above is info from a colleague on a sysadmin list.

and the Russian guys using Nvdia GPU's to speed up brute forcing wpa keys, 
it's time to tighten up!

http://blogs.zdnet.com/hardware/?p=2724

> Which is probably what you have now that you are trying to get rid of. 

Yeah :-(
 
> Though all bets are off if you have different MVP devices that work 
> differently than mine.  :-)

Well I'm hoping the original mvp's are simple enough that with just a bit of 
tweaking it'll work.  Then hopefully some of the voip phones will work in the 
same way and tftp boot off the asterisk server on the main lan. 
 
> Also, it is my understanding the tftp is a pain with a firewall, for 
> reasons similar to FTP.  

With proper connection tracking, it shouldn't be too bad.

> 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... 

It's both, however I can control what it does easily between logical lans.

> HTH and good luck,

Thanks
-- 
Harondel J. Sibble 
Sibble Computer Consulting
Creating Solutions for the small and medium business computer user.
[EMAIL PROTECTED] (use pgp keyid 0x3AD5C11D) http://www.pdscc.com
(604) 739-3709 (voice/fax)      (604) 686-2253 (pager)


-------------------------------------------------------------------------
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/

Reply via email to