Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 16 Oct 1999 20:17:59 -0400
From:      Christopher Michaels <ChrisMic@clientlogic.com>
To:        "'ATeslik@aol.com'" <ATeslik@aol.com>
Cc:        freebsd-questions@freebsd.org
Subject:   RE: can't ping win95 machine
Message-ID:  <6C37EE640B78D2118D2F00A0C90FCB4401105CFD@site2s1>

next in thread | raw e-mail | index | archive | help
Can the FreeBSD machine ping itself?

Do you have IPFIREWALL compiled into your kernel?

-Chris

> -----Original Message-----
> From:	ATeslik@aol.com [SMTP:ATeslik@aol.com]
> Sent:	Saturday, October 16, 1999 7:35 PM
> To:	bright@wintelcom.net
> Cc:	freebsd-questions@freebsd.org
> Subject:	Re: can't ping win95 machine
> 
> In a message dated 10/16/1999 4:12:46 PM Pacific Daylight Time, 
> bright@wintelcom.net writes:
> 
> << On Sat, 16 Oct 1999 ATeslik@aol.com wrote:
>  
>  > In a message dated 10/16/1999 1:53:51 PM Pacific Daylight Time, 
>  > ChrisMic@clientlogic.com writes:
>  > 
>  > << It may help us if you can provied the output of a couple things.
>  >  
>  > >> ifconfig -a
>  > 
>  > pn0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> inet 
>  > 192.168.1.3 netmask 0xffffff00 broadcast 192.168.1.255
>  >     ether 87:ff:87:ff:87:ff     
>  >     media: autoselect (10baseT/UTP <half-duplex>)
>  >     supported media: autoselect 100baseT4 100baseTX <full-duplex>
>  >     100baseTX <half-duplex> 100baseTX 10baseT/UTP <full-duplex> 
> 10baseT/UTP 
>  >     <half-duplex> 10baseT/UTP
>  > lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
>  > tun0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500ppp0: 
>  > flags=8010<POINTOPOINT,MULTICAST> mtu 1500
>  > lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
>  >     inet 127.0.0.1 netmask 0xff000000 
>  > 
>  > 
>  > I'm using a linksys LNE100TXII NIC with the "pn" (PNIC) driver in my 
> kernel.
>  > 
>  > >> ping <windows-ip>
>  > 
>  > PING 192.168.1.2 (192.168.1.2): 56 data bytes---
>  > ping: sendto: Host is down
>  > ping: sendto: Host is down
>  > 192.168.1.2 ping statistics ---6 packets transmitted, 0 packets
> received, 
>  > 100% packet loss
>  > 
>  > >> ping <freebsd-ip> (from the windows machine).
>  > 
>  > 
>  > Pinging 192.168.1.3 with 32 bytes of data:
>  > 
>  > Request timed out.
>  > Request timed out.
>  > Request timed out.
>  > Request timed out.
>  > 
>  > If theres anymore input I can offer, let me know! At this point I'll do
> 
> just 
>  > about anything to get this working. Thanks again!
>  
>  >>>Can you telnet or ftp?  With a stock FreeBSD install i'm suspecting
> that
>  >>>some software on the win95 machine may be tripping you up.
>  
> You know, I thought so too! When I was trying Linux a while back I could.
> For 
> some reason though, I can't with FreeBSD. Tried CuteFTP and Simple Telnet.
> 
> Nothing.
> 
>  >>>I also noticed that the pn0 is saying "full duplex" since you are
>  >>>on a hub it should be set to half-duplex:
>  
>  >>>ifconfig pn0 mediaopt half-duplex
>  
>  >>>then try again.
> 
> I tried this, got an error:
> SIOCSIFMEDIA: Device not configured
> then I noticed that my card is set:
> media: autoselect (10baseT/UTP <half-duplex>)
> I think those other settings are just options on the card, but it is
> actually 
> set half-duplex.
>  
> >>>you may want to put that at the end of your ifconfig line
>  >>>in /etc/rc.conf.
>  
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-questions" in the body of the message


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6C37EE640B78D2118D2F00A0C90FCB4401105CFD>