From owner-freebsd-current Tue Feb 2 11:13:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19617 for freebsd-current-outgoing; Tue, 2 Feb 1999 11:13:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA19605 for ; Tue, 2 Feb 1999 11:13:30 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id OAA05271; Tue, 2 Feb 1999 14:20:13 -0500 From: Bill Paul Message-Id: <199902021920.OAA05271@skynet.ctr.columbia.edu> Subject: Re: problem with vr0 To: clkao@CirX.ORG (Chia-liang Kao) Date: Tue, 2 Feb 1999 14:20:11 -0500 (EST) Cc: current@FreeBSD.ORG In-Reply-To: <199902021826.CAA00553@genius.cirx.org> from "Chia-liang Kao" at Feb 3, 99 02:26:52 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Chia-liang Kao had to walk into mine and say: > > I have problem with my newly bought D-link DFE530TX on my -current > (which is very new). > > I have tested my NIC using the master/slave mode program came with my > NIC with my room mate. And the results show the NIC work correctly. > > The most strange thing is that I can see the ethernet address of the > other ip, see the following infomation. But I can't get the interface > to work at all. ARRRRGHHHH!!! I really don't want to get mad at you personally, but this is really starting to annoy me. Virtually every time anybody reports a problem, the only thing they ever say is "it doesn't work." WHAT DOESN'T WORK EXACTLY!?! Describe the problem(s)!! Show us examples!! Show us error messages!! Does it catch fire?! Does it spit pea soup at you and speak in tongues?! Does it lie around the house all day and refuse to cut its hair and get a job!? WHAT!! You have not explained exactly what is going wrong. You have not explained what it is that you're trying to do which isn't working. You have not explained how you came to the conclusion that the card "isn't working." Show us what happens if you type 'ping 192.168.100.1'. Don't attempt to paraphrase the error messages: quote them exactly. Does ping not illustrate the problem accurately? Fine: choose another example and show us the results. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message