From owner-freebsd-questions Thu Feb 5 15:17:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20949 for questions-outgoing; Thu, 5 Feb 1998 15:17:47 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from second.dialup.access.net (lsmarso.dialup.access.net [166.84.254.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20763 for ; Thu, 5 Feb 1998 15:15:36 -0800 (PST) (envelope-from lsmarso@panix.com) Received: (from lsmarso@localhost) by second.dialup.access.net (8.8.8/8.8.8) id RAA00321 for freebsd-questions@freebsd.org; Thu, 5 Feb 1998 17:33:00 -0500 (EST) (envelope-from lsmarso) Message-ID: <19980205173256.24272@panix.com> Date: Thu, 5 Feb 1998 17:32:56 -0500 From: "Larry S. Marso" To: freebsd-questions@FreeBSD.ORG Subject: 3com 3C589D and zp0 vs. ep0 Mail-Followup-To: freebsd-questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe questions" I would appreciate any assistance you can offer unwinding the following problem. In summary: using the 3com 3C589D, I can't get IP aliasing to work using the ep0 driver, whereas it works *perfectly* with the zp0 driver. I am running a home LAN with a FreeBSD 3.0-current (sources cvsup'd about Feb. 1st) server and FreeBSD RELENG_2_2 (cvsup'd Feb. 3rd) laptop client. My primary objective is ISDN access permitting the laptop to take advantage of the high speed serial port card on the server, as well as having backup drives and secondary compiler. On the laptop, I'm using the 3Com Etherlink III3C589D-TP card. I get very different, and in each case unsatisfactory results with either the zp0 or ep0 driver on the laptop. ^^^^^^^^^^ Under zp0, unless I have the gateway server connected to the net, sendmail and retrieving vi sessions jam on laptop startup until ^C (because it believes gateway is accessible?). Also, it take a couple of *minutes* to get a prompt back from server for a telnet session. (ftp and ping responses are immediate). *Suspending* a session and attempting to restart brings back the X-windows view, but my laptop is completely locked up (and, of course, you wouldn't expect the card to come back to life after it's powered down). A mount_nfs of either machine's drives works fine on the other. Most importantly, IP aliasing works under zp0, accomplishing my major objective. ^^^^^^^^^^^ Under ep0, curiously, I get an immediate response telnetting to the server. Suspending and restarting a session works fine, another major objective. A mount_nfs again works fine for either machine. However, for the life of me, *****I can't get IP aliasing to work*****. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ For starters, ep0 does not seem properly ifconfig'd using the default values. This is how I've configured my rc.conf: pccard_enable="YES" # Set to YES if you want to configure PCCARD devices. pccard_mem="DEFAULT" # If pccard_enable=YES, this is card memory address. pccard_ifconfig="ep0" # Specialized pccard ethernet configuration (or NO). ... network_interfaces="lo0 ep0 zp0" # List of network interfaces (lo0 is loopback). ifconfig_lo0="inet 127.0.0.1" # default loopback device configuration. ifconfig_ep0="inet 192.168.1.2 netmask 255.255.255.0" ifconfig_zp0="inet 192.168.1.2 netmask 255.255.255.0" My pccard.conf entry is: # 3Com Etherlink III 3C589B, 3C589C card "3Com Corporation" "3C589D" config 0x1 "ep0" 10 insert echo 3Com Etherlink III inserted insert /etc/pccard_ether ep0 link0 -link1 remove echo 3Com Etherlink III removed remove /sbin/ifconfig ep0 delete I'm wondering if there's a problem with my ifconfig specification? ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ With these settings, I get an ifconfig -a result that suggests ep0 was not properly configured: ep0: flags=a843 mtu 1500 ether 00:60:08:92:98:0f Something seems wrong with the /etc/pccard_ether script, which results in: # /etc/pccard_ether ep0 link0 -link1 ifconfig: ep0: bad value So, I issue a more complete ifconfig statement: ifconfig ep0 inet 192.168.1.1 netmask 255.255.255.0 link0 -link1 which results in the following ifconfig -a output: ep0: flags=9843 mtu 1500 inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255 ether 00:60:08:92:98:0f This is the point where I make the observations above, about telnet, ping and ftp working fine to the server, but there's no IP aliasing. For comparison, this is the output of ifconfig -a for zp0 which follows immediately after bootup: zp0: flags=1843 mtu 1500 inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255 ether 00:60:08:92:98:0f Subtle difference. I don't know how to interpret the presence of "MULTICAST" in the ep0 entry, or the meaning of the varying flags= numbers. As I said above, IP aliasing works like a charm. Here is some additional background. First, a show route under user PPP at the server level: PPP ON lsmarso> show route Destination Gateway Flags Netif default 166.84.0.124 UGSc tun0 127.0.0.1 127.0.0.1 UH lo0 166.84.0.124 166.84.254.60 UH tun0 192.168.1/24 link#1 UC ed0 192.168.1.2 00:60:08:92:98:0f UHLW ed0 (That's before prompting the nameserver). Looks the same for zp0 and ep0. What else can I report? The message reported on startup of each respective driver: zp0: aui/bnc/utp address 00:60:08:92:98:0f vs. ep0: utp/bnc[*UTP*] address 00:60:08:92:98:0f Again, there's a difference there, but I don't know how to interpret it. Thank you for any assistance you can offer. -- Larry S. Marso lsmarso@panix.com