0000234: Wop29 sometimes gives ''MAC checksum'' error
All Projects | CNI | DZB | equalizer | IVC/ADC | LFFE | MFFE | Puma | Puma 2 | RFI | RT | submission | system time | Tadu | Time/LO | TMS | VLBI

Main | My View | View Issues | Change Log | Docs
  

Viewing Issue Simple Details [ Jump to Notes ] [ Issue History ] [ Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0000234 [TMS] minor random 08-02-10 10:40 29-11-10 08:21
Reporter Arno Schoenmakers View Status public  
Assigned To Teun Grit
Priority normal Resolution open  
Status closed  
Summary 0000234: Wop29 sometimes gives ''MAC checksum'' error
Description Ik werk met Putty op de wop29. Ik krijg vrij vaak een melding ''Received packet has incorrect MAC address" en dan stopt mijn putty sessie ermee. Is er iets mis met de netwerkkaart van wop29, of de switchpoort waar deze in zit? Ik krijg dit niet bij andere systemen waar ik mee werk.

  Groeten, Arno

Opm: Bevestigd door waarnemers.
Additional Information HW:
- Als dit wop29 netwerk is, verwacht je veel data errors in de DZB readout data. AS: wellicht heeft het te maken met domeinovergang; wop29 is dzb domein, wij werken vanuit ASTRON domein.
- TG: meerdere netwerk snelheden in 1 domein..? (zie Notes)
Attached Files

- Relationships

- Notes
(0000248)
Arno Schoenmakers
08-02-10 10:40

 Het zou belasting kunnen zijn.
Wat te denken van 10Mbps, 100Mbps en 1Gbps op 1 netwerk segment?
Mogelijk worden pakketjes gecorrupeerd? We zouden eens moeten scannen.
 
Teun

>>> Arno Schoenmakers 4-2-2010 11:57 >>>
Onwaarschijnlijk, want

- Ik gebruik al Putty versie 0.60...
- Ik heb het probleem niet met wop28 en wop30, die precies hetzelfde OS hebben


  A.

>>> On Donderdag 4 Februari 2010 at 11:36, <grit@astron.nl> wrote:
> Arno,Vervang je Putty versie eens (PuTTY version 0.52 or better) Wop29 blijft
> nog wel even op Suse10.1.Groeten, Teun A.7.1 Why do I see Incorrect MAC
> received on packet?
> One possible cause of this that used to be common is a bug in old SSH-2
> servers distributed by ssh.com. (This is not the only possible cause; see
> section 10.12 (
> http://tartarus.org/~simon/putty-snapshots/htmldoc/Chapter10.html#errors-crc [^]
> ) in the documentation.) Version 2.3.0 and below of their SSH-2 server
> constructs Message Authentication Codes in the wrong way, and expects the
> client to construct them in the same wrong way. PuTTY constructs the MACs
> correctly by default, and hence these old servers will fail to work with it.
> If you are using PuTTY version 0.52 or better, this should work
> automatically: PuTTY should detect the buggy servers from their version
> number announcement, and automatically start to construct its MACs in the
> same incorrect manner as they do, so it will be able to work with them.
> If you are using PuTTY version 0.51 or below, you can enable the workaround
> by going to the SSH panel and ticking the box labelled Imitate SSH2 MAC
> bug. It's possible that you might have to do this with 0.52 as well, if a
> buggy server exists that PuTTY doesn't know about.
> In this context MAC stands for Message Authentication Code. It's a
> cryptographic term, and it has nothing at all to do with Ethernet MAC (Media
> Access Control) addresses.
>
>>>> Arno Schoenmakers 4-2-2010 11:19 >>>
> Received packet has incorrect MAC address
 
(0000320)
Arno Schoenmakers
29-11-10 08:21

 Onduidelijk wat dit veroorzaakt. We blijven het zien, maar het is nu niet oplosbaar.
 

- Issue History
Date Modified Username Field Change
08-02-10 10:40 Arno Schoenmakers New Issue
08-02-10 10:40 Arno Schoenmakers Note Added: 0000248
08-02-10 10:40 Arno Schoenmakers Assigned To  => Teun Grit
08-02-10 10:40 Arno Schoenmakers Status new => assigned
08-02-10 10:40 Arno Schoenmakers Description Updated
08-02-10 10:40 Arno Schoenmakers Additional Information Updated
29-11-10 08:21 Arno Schoenmakers Note Added: 0000320
29-11-10 08:21 Arno Schoenmakers Status assigned => closed