1.3.7 -- UDP problems?

Mike Shaver (shaver@neon.ingenia.com)
Fri, 7 Jul 1995 05:08:53 -0400 (EDT)

I just did a double-upgrade (to ELF(*) and 1.3.7), and discovered that
named "broke". Actually, I think UDP broke...

I'm getting:
Jul 7 04:11:26 neon kernel: UDP: bad checksum. From 86753756:1435 to 86753756:53 ulen 51
Jul 7 04:14:07 neon kernel: UDP: bad checksum. From 86753756:53 to 86753756:1441 ulen 191
Jul 7 04:14:21 neon kernel: UDP: bad checksum. From 86753756:53 to 86753756:1444 ulen 191
Jul 7 04:14:26 neon kernel: UDP: bad checksum. From 86753756:53 to 86753756:1447 ulen 191
Jul 7 04:14:34 neon kernel: UDP: bad checksum. From 86753756:53 to 86753756:1451 ulen 99
Jul 7 04:14:42 neon kernel: UDP: bad checksum. From 86753756:1457 to 86753756:53 ulen 51
Jul 7 04:14:47 neon kernel: UDP: bad checksum. From 86753756:1457 to 86753756:53 ulen 51
Jul 7 04:15:16 neon kernel: UDP: bad checksum. From 86753756:1465 to 86753756:53 ulen 39
Jul 7 04:15:23 neon kernel: UDP: bad checksum. From 86753756:53 to 86753756:1467 ulen 191

That's me talking to me...

I stepped back to an a.out 1.3.6, and it's gone away.

Just FYI,
Mike

(*) Almost totally painless. I had all the a.out libs in
/usr/i486-linuxaout/lib already, and then it was just a matter of
installing the slackware ELF beta over top of what I had. Other than
a null emacs binary, it was incredibly smooth. Kudos to Patrick.
(And HJ et al., of course...)

-- 
#> Mike Shaver (shaver@ingenia.com)                                   <#
#> Technical specialist, pedant, packetsmith                          <#
#>                                 Ingenia Communications Corporation <#
#>               Research, Development, Support and Sleep Deprivation <#
#>                    Packets crafted, bugs found, rebellions quelled <#