From owner-freebsd-questions@FreeBSD.ORG Sun Mar 25 02:21:24 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5065716A405 for ; Sun, 25 Mar 2007 02:21:24 +0000 (UTC) (envelope-from ray@stilltech.net) Received: from mail.geekdelivery.com (s205-206-56-226.ab.hsia.telus.net [205.206.56.226]) by mx1.freebsd.org (Postfix) with ESMTP id 0612113C468 for ; Sun, 25 Mar 2007 02:21:23 +0000 (UTC) (envelope-from ray@stilltech.net) Received: from [192.168.0.102] ([70.65.134.12]) by media32.ca (mail.geekdelivery.com) (MDaemon.PRO.v8.1.3.R) with ESMTP id md50000036172.msg for ; Sat, 24 Mar 2007 19:19:53 -0700 From: Ray To: freebsd-questions@freebsd.org Date: Sat, 24 Mar 2007 20:20:53 -0600 User-Agent: KMail/1.9.5 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200703242020.53269.ray@stilltech.net> X-MDRemoteIP: 70.65.134.12 X-Return-Path: ray@stilltech.net X-MDaemon-Deliver-To: freebsd-questions@freebsd.org X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) X-Spam-Report: * -4.7 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] X-Spam-Status: No, score=-4.7 required=3.0 tests=BAYES_00 autolearn=ham version=3.0.4 X-Spam-Level: X-Spam-Processed: mail.geekdelivery.com, Sat, 24 Mar 2007 19:19:55 -0700 X-MDAV-Processed: mail.geekdelivery.com, Sat, 24 Mar 2007 19:19:57 -0700 Subject: Re: order of enet interface drivers X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ray@stilltech.net List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Mar 2007 02:21:24 -0000 On Saturday 24 March 2007 8:38 pm, jekillen wrote: > Hello; > I have two identical intel interface cards installed > in a ASUS N2M32 pro motherboard. The os version > is 6.2 GENERIC running on AMD64, socket AM2. > The motherboard has dual interfaces that use Marvell > drivers. I cannot use these with this version of FreeBSD I'm working on a similar board. have you looked at: http://www.se.hiroshima-u.ac.jp/~shigeaki/software/freebsd-nfe.html I'm having success with this approach. Ray > as yet. So I got two Intel interface cards that work in > PCIe slots. Because of the hardware component situation > on this motherboard I cannot use the interfaces in PCIe lane > one slots as on of these slots is blocked, physically, and the > card will not fit. So I am using the two PCIe lane 16 slots. > I modified rc.conf (see PS at bottom) to bring up the interfaces at > boot. > They both come up and running with network addressess > assigned, as em0 an em1. > The problem: > I can ping em0 from local host and connect to ftp and ssh > from the inside network, all is well > I cannot ping em1. > ifconfig shows it up and running, with no carrier, I.E. no > network cable attached but I should be able to ping it > from local host, yes? no? Yes. > Here is the obvious question > the order of interfaces listed by ifconfig is > em0 > fwe0 > em1 > the question is: > Is it possible that fwe is blocking em1? > I have fwe0 down and took it out of > rc.conf so it does not come up on boot > but still shows up in this order with ifconfig. > If this is possible, how do I tell the system to > load fwe0 after em1 or not at all to see if I can ping it successfully? > copied from ifconfig output: > em0: flags=8843 mtu 1500 > options=b > inet 192.168.1.16 netmask 0xffffff00 broadcast 192.168.1.255 > ether 00:15:17:19:2c:89 > media: Ethernet autoselect (100baseTX ) > status: active > fwe0: flags=108802 mtu 1500 > options=8 > ether 02:11:d8:bf:40:d4 > ch 1 dma -1 > em1: flags=8843 mtu 1500 > options=b > inet 192.168.1.17 netmask 0xffffff00 broadcast 192.168.1.255 > ether 00:15:17:19:2a:b7 > media: Ethernet autoselect > status: no carrier > ping results: > am2# ping -c 1 em1 > ping: cannot resolve em1: Host name lookup failure > am2# ping -c 1 192.168.1.17 > PING 192.168.1.17 (192.168.1.17): 56 data bytes > > --- 192.168.1.17 ping statistics --- > 1 packets transmitted, 0 packets received, 100% packet loss > am2# > Any clues? > Jeff K (being necessarily philosophical at this point) > PS I say I edited rc.conf to make network changes > because I got the syntax correct for doing this. It > does work, not with commands, just variable/value assignments > JK > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org"