Hello, I've been having some difficulty with getting my gateway set up and I think I tracked the culprit down. I did a dmesg and found out that I am getting an invalid checksum from one of my NIC's. It doesn't appear to be an interrupt problem. What could be causing this? Also, what is this exception 16 error when checking 386/387 coupling? Is this something to be worried about? I've included excerpts from the dmesg to help. By the way, I am using Caldera Open Server 2.4 on a 300mhz P2 w/128mb RAM. The NIC's are a 3Com 3c5905 and the other is a Netgear FA310TX. Any and all help is appreciated. ... Page-cache hash table entries: 32768 (order: 5, 131072 bytes) VFS: Diskquotas version dquot_6.4.0 initialized Checking 386/387 coupling... OK, FPU using exception 16 error reporting. Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX ... uhci_control_thread at 88814eb8 3c59x.c:v0.99H 11/17/98 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html eth0: 3Com 3c905C Tornado at 0x6400, ***INVALID CHECKSUM 002f*** 00:01:02:82:e6:77, IRQ 10 8K byte-wide RAM 5:3 Rx:Tx split, autoselect/Autonegotiate interface. MII transceiver found at address 24, status 7809. Enabling bus-master transmits and whole-frame receives. tulip.c:v0.91g-ppc 7/16/99 becker at cesdis.gsfc.nasa.gov eth1: Lite-On 82c168 PNIC rev 32 at 0x6800, 00:A0:CC:59:0F:57, IRQ 9. eth1: MII transceiver #1 config 3000 status 7829 advertising 01e1. Thanks, Dan