You really should post to a Linux newsgroup to ask this, but I find it
amazingly unlikely that Circle is causing the problem. Circle just
uses the standard write() system call to send data. The MUD never,
ever deals directly with the ethernet driver.
If I were the sysadmin I'd try using a new and *good* ethernet card
instead of a crappy $15 NE2000 clone.
Jeremy
Jeff Beers writes:
>This might not circle code causing this problem, but I'm not
>an expert on this kind of thing.
>
>We have just recently moved our mud from SunOS to Linux operating
>systems.
>
>The sysadmin that owns the site (who is new to this himself -- I think
>we are the first customer) had said that /var/log (I believe) is
>gettingthe following messages:
>
>May 22 18:18:07 mudd kernel: loading device 'eth0'...
>May 22 18:18:07 mudd kernel: ne.c:v1.10 9/23/94 Donald Becker
>(becker@cesdis.gsfc.nasa.gov)
>May 22 18:18:07 mudd kernel: NE*000 ethercard probe at 0x300: 00 60 67
>00 6d da
>May 22 18:18:07 mudd kernel: eth0: NE2000 found at 0x300, using IRQ 3.
>May 22 18:26:02 mudd kernel: eth0: bogus packet size: 32864,
status=0x21
...
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://democracy.queensu.ca/~fletcher/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/15/00 PST