Re: Network Problem on FreeBSD-4.8 : Cannot ping LAN hosts

2003-10-19 Thread Edwin D. Vinas
hi josh,

thanks for the advise. it's the FIREWALL thing that
don't allow my FreeBSD to access the Internet Sharing
in the Windows XP. Now, its ok already. I just
unchecked the option that Restricts IP hosts from
Internet (external) to access the Internet Sharing
Machine or something like that. Now its working. It
really is not a problem with my FreeBSD LAN card or
other configurations. It's the WindowsXP trick!

-edwin



--- Josh Paetzel [EMAIL PROTECTED] wrote:
 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=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST
 mtu 1500
  
  inet 192.168.0.6 netmask 0xff00 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 0xef00-0xefff 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 

Re: Network Problem on FreeBSD-4.8 : Cannot ping LAN hosts

2003-10-19 Thread Josh Paetzel
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=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
 
 inet 192.168.0.6 netmask 0xff00 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 0xef00-0xefff 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

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Network Problem on FreeBSD-4.8 : Cannot ping LAN hosts

2003-09-18 Thread Josh Paetzel
On Thu, Sep 18, 2003 at 09:06:19AM -0700, Edwin D. Vinas wrote:
 Hi,
  
 I've stumbling with all the mailing lists about this problem and I hope somebody 
 will give a kind advise. Here's my LAN setup:
 
 |   |  ||  |
 WinXP1  WinXP2   WinXP3   WinXP4   FreeBSD
  
 WinXP3 is my Internet Sharing Machine connected to my ISP.
 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 unknown card (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
 
 
 best regards,
 
 \___\__\___/__/ Edwin D. Vi?as http://edwin.ontheweb.com
  \___\__\_/__/  Electronics and Communications Engineer
   \___\__\___/__/   Mobile: +639202612660
\___\__\_/__/E-mail: [EMAIL PROTECTED]
 PH  \___\_/ The Brain is as vast as the Universe.
 

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

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Network Problem on FreeBSD-4.8 : Cannot ping LAN hosts

2003-09-18 Thread Edwin D. Vinas
hi josh,
 
see dmesg, ifconfig and netstat below... hope you can help me now. -edwin
 
IFCONFIG

dc0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500

inet 192.168.0.6 netmask 0xff00 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

lp0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500

faith0: flags=8002BROADCAST,MULTICAST mtu 1500

lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384

inet6 ::1 prefixlen 128 

inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 

inet 127.0.0.1 netmask 0xff00 

ppp0: flags=8010POINTOPOINT,MULTICAST mtu 1500

sl0: flags=c010POINTOPOINT,LINK2,MULTICAST mtu 552


DN

dc0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500

inet 192.168.0.6 netmask 0xff00 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

lp0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500

faith0: flags=8002BROADCAST,MULTICAST mtu 1500

lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384

inet6 ::1 prefixlen 128 

inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 

inet 127.0.0.1 netmask 0xff00 

ppp0: flags=8010POINTOPOINT,MULTICAST mtu 1500

sl0: flags=c010POINTOPOINT,LINK2,MULTICAST mtu 552

DMESG

Copyright (c) 1992-2003 The FreeBSD Project.

Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994

The Regents of the University of California. All rights reserved.

FreeBSD 4.8-RELEASE #0: Fri Feb 18 21:38:56 PHT 2000

[EMAIL PROTECTED]:/usr/src/sys/compile/CNETPRO

Timecounter i8254 frequency 1193182 Hz

CPU: AMD Duron(tm) processor (699.51-MHz 686-class CPU)

Origin = AuthenticAMD Id = 0x631 Stepping = 1

Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR

AMD Features=0xc044RSVD,AMIE,DSP,3DNow!

real memory = 268369920 (262080K bytes)

avail memory = 255897600 (249900K bytes)

Preloaded elf kernel kernel at 0xc051d000.

Pentium Pro MTRR support enabled

md0: Malloc disk

Using $PIR table, 7 entries at 0xc00fdf00

npx0: math processor on motherboard

npx0: INT 16 interface

pcib0: Host to PCI bridge on motherboard

pci0: PCI bus on pcib0

agp0: VIA Generic host to PCI bridge mem 0xe800-0xebff at device 0.0 on pci0

pcib1: PCI to PCI bridge (vendor=1106 device=b099) at device 1.0 on pci0

pci1: PCI bus on pcib1

pci1: NVidia model 0110 graphics accelerator at 0.0 irq 10

dc0: Davicom DM9102A 10/100BaseTX port 0xd000-0xd0ff mem 0xef00-0xefff 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

isab0: PCI to ISA bridge (vendor=1106 device=3074) at device 17.0 on pci0

isa0: ISA bus on isab0

atapci0: VIA 8233 ATA100 controller port 0xd400-0xd40f at device 17.1 on pci0

ata0: at 0x1f0 irq 14 on atapci0

ata1: at 0x170 irq 15 on atapci0

uhci0: VIA 83C572 USB controller port 0xd800-0xd81f irq 11 at device 17.2 on pci0

usb0: VIA 83C572 USB controller on uhci0

usb0: USB revision 1.0

uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1

uhub0: 2 ports with 2 removable, self powered

uhci1: VIA 83C572 USB controller port 0xdc00-0xdc1f irq 11 at device 17.3 on pci0

usb1: VIA 83C572 USB controller on uhci1

usb1: USB revision 1.0

uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1

uhub1: 2 ports with 2 removable, self powered

uhci2: VIA 83C572 USB controller port 0xe000-0xe01f irq 11 at device 17.4 on pci0

usb2: VIA 83C572 USB controller on uhci2

usb2: USB revision 1.0

uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1

uhub2: 2 ports with 2 removable, self powered

pci0: unknown card (vendor=0x1106, dev=0x3059) at 17.5 irq 5

fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0

fdc0: FIFO enabled, 8 bytes threshold

fd0: 1440-KB 3.5 drive on fdc0 drive 0

atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0

atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0

kbd0 at atkbd0

psm0: PS/2 Mouse irq 12 on atkbdc0

psm0: model IntelliMouse, device ID 3

vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0

sc0: System console at flags 0x100 on isa0

sc0: VGA 16 virtual consoles, flags=0x300

sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0

sio0: type 16550A

sio1 at port 0x2f8-0x2ff irq 3 on isa0

sio1: type 16550A

ppc0: Parallel port at port 0x378-0x37f irq 7 on isa0

ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode

plip0: PLIP network interface on ppbus0

lpt0: Printer on ppbus0

lpt0: Interrupt-driven port

ppi0: Parallel I/O on ppbus0

ad0: 29325MB Maxtor 6E030L0 [59582/16/63] at ata0-master UDMA100

acd0: DVD-ROM DVD-ROM DVD-16X6S at ata0-slave PIO4

Mounting root from ufs:/dev/ad0s2a

ad0: UDMA ICRC error reading fsbn 0 (ad0 bn 0;