From owner-freebsd-current@FreeBSD.ORG Sun Oct 19 12:40:04 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AEB8716A4B3 for ; Sun, 19 Oct 2003 12:40:04 -0700 (PDT) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 97C1D43F75 for ; Sun, 19 Oct 2003 12:40:02 -0700 (PDT) (envelope-from slave-mike@rv1.dynip.com) Received: from duron.rv1.dynip.com (c-66-177-119-177.se.client2.attbi.com[66.177.119.177]) by comcast.net (rwcrmhc11) with ESMTP id <2003101919400101300p7vbce>; Sun, 19 Oct 2003 19:40:01 +0000 Received: from rv1.dynip.com (localhost [127.0.0.1]) by duron.rv1.dynip.com (8.12.10/8.12.10) with ESMTP id h9JJdxHh000929; Sun, 19 Oct 2003 15:40:00 -0400 (EDT) (envelope-from slave-mike@rv1.dynip.com) Message-ID: <3F92E88F.6020802@rv1.dynip.com> Date: Sun, 19 Oct 2003 15:39:59 -0400 From: slave-mike User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: slave-mike References: <3F9097DD.1090500@rv1.dynip.com> <20031018161032.T35407@carver.gumbysoft.com> <3F92093F.9070008@rv1.dynip.com> <3F922269.1020909@rv1.dynip.com> <3F9223D5.9050501@rv1.dynip.com> In-Reply-To: <3F9223D5.9050501@rv1.dynip.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: mjoyner Subject: -march athlon breaks my networking was: ip stack broken? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Oct 2003 19:40:04 -0000 I realized that my /etc/make.conf was set to use -O0 -march athlon for kernel builds. After removing the COPTS and CPU stuff form /etc/make.conf my kernel's networking now works fine. Any clue as to why -march athlon breaks my networking? slave-mike wrote: > FYI: here is the output from ifconfig, arp -an, ipv4 routing tables > while running the 5.1-RELEASE kernel. > > dc0: flags=8943 mtu 1500 > inet6 fe80::2c0:f0ff:fe48:7562%dc0 prefixlen 64 scopeid 0x1 > inet 192.168.0.2 netmask 0xffffff00 broadcast 192.168.0.255 > ether 00:c0:f0:48:75:62 > media: Ethernet autoselect (100baseTX ) > status: active > ? (10.255.255.255) at ff:ff:ff:ff:ff:ff on vmnet1 permanent [ethernet] > ? (192.168.0.0) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] > ? (192.168.0.1) at 00:a0:c5:e6:58:00 on dc0 [ethernet] > ? (192.168.0.253) at 00:06:25:54:2a:20 on dc0 [ethernet] > ? (192.168.0.255) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] > > netstat -rn > Routing tables > > Internet: > Destination Gateway Flags Refs Use Netif Expire > default 192.168.0.1 UGSc 8 0 dc0 > 10 link#4 UC 1 0 vmnet1 > 10.255.255.255 ff:ff:ff:ff:ff:ff UHLWb 2 58 vmnet1 > 127.0.0.1 127.0.0.1 UH 11 3250 lo0 > 192.168.0.0 ff:ff:ff:ff:ff:ff UHLWb 0 9 dc0 => > 192.168.0 link#1 UC 4 0 dc0 > 192.168.0.1 00:a0:c5:e6:58:00 UHLW 9 8 dc0 332 > 192.168.0.2 127.0.0.1 UGHS 0 5 lo0 > 192.168.0.253 00:06:25:54:2a:20 UHLW 0 1 dc0 1057 > 192.168.0.255 ff:ff:ff:ff:ff:ff UHLWb 4 147 dc0 > > > slave-mike wrote: > >> Follows is my arp table entries and interface while running a -current >> kernel. >> >> My system can see the default gateway etc, and appears to be >> transmitting packets (based on activity of hub lights), but does not >> seem to be receiving them back or knowing they are received back >> beyond the arp/rarp packets or it just plain eats them. :) >> >> 192.168.0.1 is my default gw >> >> I have tried both fxp0 and dc0. >> I have tried both with and without vmnet being loaded. >> >> ? (10.255.255.255) at ff:ff:ff:ff:ff:ff on vmnet1 permanent [ethernet] >> ? (192.168.0.0) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] >> ? (192.168.0.1) at 00:a0:c5:e6:58:00 on dc0 [ethernet] >> ? (192.168.0.253) at 00:06:25:54:2a:20 on dc0 [ethernet] >> ? (192.168.0.255) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] >> >> dc0: flags=8943 mtu 1500 >> inet6 fe80::2c0:f0ff:fe48:7562%dc0 prefixlen 64 scopeid 0x1 >> inet 192.168.0.2 netmask 0xffffff00 broadcast 192.168.0.255 >> ether 00:c0:f0:48:75:62 >> media: Ethernet autoselect (100baseTX ) >> status: active >> >> >> mjoyner wrote: >> >>> It works fine with a 5.1 kernel. >>> >>> Doug White wrote: >>> >>>> On Fri, 17 Oct 2003, mjoyner wrote: >>>> >>>> >>>>> When I use a current kernel, my system will obtain an ip address via >>>>> dhclient, but thereafter, it cannot see the network. >>>>> >>>>> I have tried switching ethernet cards. (used both a dc0 and an fxp0) >>>>> Am currently using a 5.1-RELEASE kernel to have network access. >>>>> >>>>> Advice? >>>> >>>> >>>> >>>> >>>> >>>> Perhaps your DHCP server is handing out bogus info? >>>> >>> >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to >>> "freebsd-current-unsubscribe@freebsd.org" >> >> >> >> ------------------------------------------------------------------------ >> >> ? (10.255.255.255) at ff:ff:ff:ff:ff:ff on vmnet1 permanent [ethernet] >> ? (192.168.0.0) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] >> ? (192.168.0.1) at 00:a0:c5:e6:58:00 on dc0 [ethernet] >> ? (192.168.0.253) at 00:06:25:54:2a:20 on dc0 [ethernet] >> ? (192.168.0.255) at ff:ff:ff:ff:ff:ff on dc0 permanent [ethernet] >> >> dc0: flags=8943 mtu 1500 >> inet6 fe80::2c0:f0ff:fe48:7562%dc0 prefixlen 64 scopeid 0x1 >> inet 192.168.0.2 netmask 0xffffff00 broadcast 192.168.0.255 >> ether 00:c0:f0:48:75:62 >> media: Ethernet autoselect (100baseTX ) >> status: active >> > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"