Re: bge driver internal routing issues?
Thanks for the that, we've just packed down the machines to move them I will endeavour to test this as soon as I have access to them again. However I think I did try disabling checksum off loading but not a 100% sure so will need to check. Steve - Original Message - From: "David Malone" <[EMAIL PROTECTED]> On Sun, Aug 28, 2005 at 09:06:47PM +0100, Steven Hartland wrote: Having a really odd problem here where udp queries to servers running on machines with bge cards dont respond via ip address that are being bound on: Can you run "tcpdump -s 0 -vvv port 1234" on the client (replace port 1234 with the port number for the service). See if tcpdump shows a reply packet, and if it does see if the checksum is reported OK. It could be that the checksum offloading on the bge card is busted. (You could also check "netstat -s" on the client to see if it shows many bad checksums in the UDP section.) This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bge driver internal routing issues?
On Sun, Aug 28, 2005 at 09:06:47PM +0100, Steven Hartland wrote: > Having a really odd problem here where udp queries to > servers running on machines with bge cards dont respond > via ip address that are being bound on: Can you run "tcpdump -s 0 -vvv port 1234" on the client (replace port 1234 with the port number for the service). See if tcpdump shows a reply packet, and if it does see if the checksum is reported OK. It could be that the checksum offloading on the bge card is busted. (You could also check "netstat -s" on the client to see if it shows many bad checksums in the UDP section.) David. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
bge driver internal routing issues?
Having a really odd problem here where udp queries to servers running on machines with bge cards dont respond via ip address that are being bound on: qop1# ifconfig bge0: flags=8843 mtu 1500 options=1a inet 217.41.254.99 netmask 0xff80 broadcast 217.41.254.127 ether 00:e0:81:63:9c:0a media: Ethernet autoselect (100baseTX ) status: active bge1: flags=8802 mtu 1500 options=1a ether 00:e0:81:63:9c:09 media: Ethernet autoselect (none) status: no carrier lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff00 qop1# sockstat |grep 8478 mpukgame ucc-bin42425 66 udp4 *:8478*:* mpukgame ucc-bin42424 66 udp4 *:8478*:* qop1# qstat -uns 127.0.0.1:8478 -noportoffset ADDRESS PLAYERS MAP RESPONSE TIMENAME 127.0.0.1:8478 0/10 CTF-Cybrosis][ 42 / 0 CTFGame i25 :: CTF #1 qop1# qstat -uns 217.41.254.99:8478 -noportoffset ADDRESS PLAYERS MAP RESPONSE TIMENAME 217.41.254.99:8478 no response FreeBSD qop1.event.multiplay.co.uk 5.4-RELEASE-p2 FreeBSD 5.4-RELEASE-p2 #5: Tue Jun 21 13:28:12 UTC 2005 [EMAIL PROTECTED]:/.usr/i386/src/sys/i386/compile/MPUK_SINGLE_200HZ i386 Running the exact same test on a machine with an em driver has no problems. No idea where to start with this one any pointers appreciated. Steve This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
