 BAINCHPremium,VIP,MVM
join:2003-04-02
Middletown, NY
kudos:10 | reply to TazMainiac
Re: arp info overwritten (OpenBSD) Well, the issue seems to be caused by a particular type of home gateway/router that reports a generic MacID when it has an error. Get two on the same part of the network (and thus two devices with the same MacID) and is causes an arp issue. We are trying to determine what material impact this has on customer performance (if any) and what the best course of action would be to resolve it. |
|
 UHFAll static, all day, ForeverPremium,MVM
join:2002-05-24
 ·Callcentric
 ·DIRECTV
 ·surpasshosting
·Dish Network
·VOIPo
| Nice. You would think manufacturers would try to stick to the 802.3 specs for ethernet devices and not do screwy things with the MACs. I sure would like to know which device this is so I can be sure I don't buy one.
Thanks for the update Bainch. |
|
|
|
| reply to BAINCH
said by BAINCH:
Well, the issue seems to be caused by a particular type of home gateway/router that reports a generic MacID when it has an error. Get two on the same part of the network (and thus two devices with the same MacID) and is causes an arp issue. We are trying to determine what material impact this has on customer performance (if any) and what the best course of action would be to resolve it.
Is this something that Mediacom is seeing, or is this something that I would be seeing? I can tell you for certain that what I am seeing is a misconfig of Mediacom's router service (I've already proven that to them, and I've also verified it by asking other people who are knowledgeable enough to explain it). I say that because this _sounds_ like upper management's answer to something that they don't want to spend the time/money on hiring someone who knows what they're doing to fix it.
What do you mean, "generic MacID?" Furthermore, can you identify "a particular type of home gateway/router?" Are you talking about a hardware router, a gateway, a firewall system with NAT, etc? That sounds a little like upper management's bs as well... (I figured I would ask because perhaps you could shed some light on that).
As for the post suggesting that ARP has little to do with DHCP... Perhaps you should read a little more into it (the link provided in my last post explains this very clearly... Read the Friendly Manuals). Without ARP, DCHP simply won't work efficiently. That's just the way it was designed.
Furthermore, _if_ there is a virus problem as someone has suggested, then it would be a problem with either lazy sysadmin or mediacom trying to do a NIX job with a MS product (not trying to sound anti-MS or anything, but... well... sometimes the truth hurts).
I haven't ran a scan to find out what OSes mediacom is running locally, but I would at least _hope_ that they're not that bad off (Out of I-don't-know-how-many, I actually got to hold conversation with two people who at least knew what they were talking about, so I still give them the benefit of the doubt, there).
If there _are_ needless ARP requests for a single IP address being broadcast as you have suggested, then what you're seeing is a client that has either been mis-configured or compromised (both of which are common, btw because people in general are clueless). If Mediacom doesn't have the know-how (or at least the desire) to pinpoint this, then perhaps you would be wise to bring the specifics to their attention (such as firewall logs, explaining what each entry means)... Perhaps they'll be able to figure out who it is from that and get them straightened out).
Reiteration... (not trying to be too obvious, here) The original problem posted in this thread has been resolved. Mediacom had a defunct router, the router was replaced (I guess they couldn't figure out how to fix it), and the problem that I had (past tense) no longer exists. The rest of this thread has nothing to do with it...
Cheers,
WizLayer |
|
BAINCHPremium,VIP,MVM
join:2003-04-02
Middletown, NY
kudos:10 | The router issue was a bad I/O card and was just responding, badly, to the ARP issue. It wasn't the cause. The problem was created by three Linksys BEFW11S4v4s. It has been acknowledge by Linksys and they have a fix available on their website (a firmware upgrade.)
We have been calling the customers with the offending device and helping to resolve it. |
|
| said by BAINCH:
The problem was created by three Linksys BEFW11S4v4s. It has been acknowledge by Linksys and they have a fix available on their website (a firmware upgrade.)
I did a quick search for it, and can't seem to find anything. Can you post a link that explains what the issue is with this hardware?
Thx,
WizLayer |
|
BAINCHPremium,VIP,MVM
join:2003-04-02
Middletown, NY
kudos:10 | I'm away for a few days but I will see if I can look it up from here. |
|
