Re: [Mvpmc-devel] MVP acting odd = SOLVED

[JP V. <jp...@jp...>]

MVallevand wrote:
> On Sat, Nov 1, 2008 at 3:09 PM, JP Vossen <jp...@jp...> wrote:
>> So what we have is a serious (IMHO) bug in mvpmc's interface selection code.
>>  It seems like it will use wireless, if a signal is present and it can get
>> DHCP, even if the MVP firmware is set to prefer wired and if wired is
>> present.  Personally, I'd flip that.  If someone has gone to the trouble of
>> plugging an Ethernet cable in, I'd suggest they mean to use it, even if
>> wireless is also present.
> 
> No as I said I think the problem is the check for what is in flash, I
> can't remember what the issue I had over a year ago but I think the
> check was based on the ram being at true values 0xff 0xff etc but

Does "the check for what is in flash" mean you are checking for the 
firmware preferred network interface, to see if wireless is physically 
present, or something else?


> sometimes the wireless isn't there.

Right.  I have one MVP with and one without.  But like I said, I'd think 
that anyone who goes to the trouble of plugging the Ethernet cable in 
wants to use that, regardless of whether a wireless adapter and/or 
signal is present.  So I'd think trying to use wired first, but then 
failing-over to wireless (if present) would make sense.

Actually, honoring the Hauppauge "wireless setup", "preferred network" 
setting makes the most sense, but I can see how reliably determining 
that over a series of models and revisions not might be feasible.


> My suggestion is to open the case and take out the compact flash
> wireless card and the of course the little antenna connectors.

I can disconnect the antenna, but my wireless card is soldered in. 
Regardless of whether that solution will work for me (I suspect 
unplugging the antenna would), it doesn't seem appropriate for the 
average end-user.  I'll just keep mine as-is and kill my wireless AP on 
cold boots if necessary, now that I understand what was happening.  But 
I'd think someone with one of these units who does not have wireless but 
with a neighbor that does would never figure this out, and even if they 
did, they can't kill the other guy's wireless AP as needed.  (Perhaps a 
tinfoil hat for the MVP would work too. :)

And I'm happy to work with you to try and debug/test further, if you like.

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