<div dir="ltr"><br><br><div class="gmail_quote">On Sun, Aug 29, 2010 at 11:40 AM, Nadav Har'El <span dir="ltr"><<a href="mailto:nyh@math.technion.ac.il">nyh@math.technion.ac.il</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
On Sun, Aug 29, 2010, shimi wrote about "Re: Can there be an Ethernet Switch that doesn't work with Linux???":<br>
<div class="im"><br>
</div><div class="im">
> It could be that there's an Ethernet negotiation problem, in such a way that<br>
> your MAC doesn't get registered on the switch (?). Not necessarily a Linux<br>
> problem. Maybe a NIC problem, or an Ethernet cable problem. Of course that<br>
> with a Hub that would work anyways, because a Hub broadcasts to all ports,<br>
> regardless of negotiation...<br>
<br>
</div>Like I said on a previous mail, the speed negotiation works. The guess that<br>
the switch has a bug and forgets my computer's MAC address makes sense, but<br>
how come it forgets the Linux computer's and remembers the Windows one? :(<br>
<div class="im"><br><br></div></blockquote><div><br>I didn't mention 'speed' in my message.<br><br>I don't have really deep knowledge in this, but what I do know (and of course stand to be corrected...), is that part of 'switching', when an Ethernet link goes up, both sides "announce" their MACs to the other end; This data is then stored, and used to decide to which physical port should the Ethernet frame be sent. That's what SWITCHing is all about. <br>
<br>What I was suggesting is that something went wrong there, this is regardless to speed, MDI-X, etc. etc. and perhaps the wrong MAC was registered, or something similar. That would cause traffic destined to your MAC to not arrive to your port. Theoretically it fits ;)<br>
<br>-- Shimi <br></div></div><br></div>