Date: Thu, 18 Sep 2003 17:34:54 -0000 From: Josh Paetzel <friar_josh@webwarrior.net> To: "Edwin D. Vinas" <edwin_vinas@yahoo.com> Cc: freebsd-questions@freebsd.org Subject: Re: Network Problem on FreeBSD-4.8 : Cannot ping LAN hosts Message-ID: <20030918173319.GO27665@tcbug.org> In-Reply-To: <20030918170415.44168.qmail@web60208.mail.yahoo.com> References: <20030918164438.GM27665@tcbug.org> <20030918170415.44168.qmail@web60208.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Sep 18, 2003 at 10:04:15AM -0700, Edwin D. Vinas wrote: > hi josh, > > see dmesg, ifconfig and netstat below... hope you can help me now. -edwin > > IFCONFIG > > dc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > > inet 192.168.0.6 netmask 0xffffff00 broadcast 192.168.0.255 > > inet6 fe80::280:adff:fe00:591a%dc0 prefixlen 64 scopeid 0x1 > > ether 00:80:ad:00:59:1a > > media: Ethernet autoselect (100baseTX) > > status: active Nothing wrong here. > > DMESG > > dc0: <Davicom DM9102A 10/100BaseTX> port 0xd000-0xd0ff mem 0xef000000-0xef0000ff irq 11 at device 9.0 on pci0 > > dc0: Ethernet address: 00:80:ad:00:59:1a > > miibus0: <MII bus> on dc0 > > ukphy0: <Generic IEEE 802.3u media interface> on miibus0 > > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto There's your NIC being detected. > > ad0: UDMA ICRC error reading fsbn 0 (ad0 bn 0; cn 0 tn 0 sn 0) retrying > > ad0: UDMA ICRC error reading fsbn 0 (ad0 bn 0; cn 0 tn 0 sn 0) retrying > > ad0: UDMA ICRC error reading fsbn 0 (ad0 bn 0; cn 0 tn 0 sn 0) retrying > > ad0: UDMA ICRC error reading fsbn 0 (ad0 bn 0; cn 0 tn 0 sn 0) falling back to PIO mode > This isn't so good, looks like your hard drive is sick, although I doubt that has anything to do with your network troubles. > NETSTAT -rn > > Routing tables > > Internet: > > Destination Gateway Flags Refs Use Netif Expire > > default 192.168.0.1 UGSc 0 0 dc0 > > 127.0.0.1 127.0.0.1 UH 0 0 lo0 > > 192.168.0 link#1 UC 1 0 dc0 > > 192.168.0.1 link#1 UHLW 1 3 dc0 > You've got the correct gateway here, and it appears to be up as well. > > I can browse the web using all the WinXPs but I cannot access the web via FreeBSD. > > FreeBSD's IP address follows the 192.198.0.x format just like the other WinXPs. > > When I check the FreeBSD, i can see its IP address and Subnet Mask etc via "ifconfig". > > I can even change the IP address+ Gateway (which is WinXP2's IP add) using > > ifconfig or /stand/sysinstall. I even manually edited rc.conf, and even changed the > > setting to DHCP etc etc etc. > > > > My diagnosis tells that I cannot ping any WinXP machine in the LAN. But I can ping myself (FreeBSD) locally. When I run "netstat -rn", It seems the network card is ok. > > When I run "tcpdump", I didn't show any output. By the way, this network card is CNet PRO200. I was thinking it was not recognize or supported by the FreeBSD-4.8. When I checked "FreeBSD-4.8's Hardware Compatibility Lit", I didn't see any "CNet PRO200" but I saw a "CNet/PRO" which I suppose are just the same. So, I recompiled my Kernel again just in case FreeBSD didn't recognize this newly installed Cnet LAN card. But, nothing changed after Kernel recompilation. (But I did not change any option in the Generic kernel; just re-compiled it). > > > > The output when I ping WinXP3: "ping: sendto: Host is down". > > It's not true coz Im typing this email right in the WinXP3 machine. I cannot also ping FreeBSD's IP add from the WinXP internet sharing server. The dmesg shows the following: pci0 (vendor=0x1106 dev=0x3059) at 17.5 irq 5. > > > > By the way, this machine where FreeBSD is installed also has WinXP which works fine when in Windows. So Im sure my LAN card is really ok. It's only a problem of FreeBSD. > > > > > > What should I do? I don't want to make FreeBSD machine as my Internet sharing server as of now (although its the best option). Im testing/running a Unix program that needs to be connected to the Internet via Windows XP gateway. > > > > Please help me make my FreeBSD be part of my LAN.... > > > > -Edwin > > > > > > The output of dmesg and ifconfig would be helpful in diagnosing this. I suppose > that's major PITA though considering you're LAN isn't working. At the very least, > the first entry that comes up with ifconfig would be very helpful. > > Josh > Two things come to mind. One is that you don't have correct nameservers in /etc/resolv.conf. The other is that your WinXP box has it's native firewall turned on and is not playing nicely with FreeBSD. Other than that, from what I can tell everything looks ok on the FreeBSD side of things, but I agree it's odd that the same box with WinXP on it can access the network and internet just fine. One last thing I can recommend is to try arp -a and see if you are connected below the TCP level. You should get an output similar to: (10.0.0.1) at 00:02:b3:c0:a9:c9 on xl0 [ethernet] Sorry I can't be of more help but it looks like you've configured FreeBSD correctly. Josh
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030918173319.GO27665>