Pinging win from FreeBSD

kenneth topp
1999-10-17T18:22:49Z

Alex,

It could be an arp problem...  Perhaps you can run a tcpdump command (as
root on the freebsd box) and watch what traffic is going on.  This
strictly isn't a samba problem, and the fact that the bsd box shows up in
network neighborhood should point you to test the tcp/ip failure.  Can you
telnet (from microsoft to bsd)?  Websurf?  Is microsoft box's internet
connection messing things up?

See the ping/arp section below to try to track things down.  After that,
other things to try is checking routes, and the cables (did you make them
yourself?)

And after one last check of your message: the pn0 device has an mac
address of 87:ff:87:ff:87:ff.  That's wrong, and scary.  If you changed
that for your posting, then okay.  If that's really the output I'd check
for duplicate mac addresses.  ethernet was designed with no two machines
on the same subnet having the same mac address.  If you can change the mac
address on both machines, and changed them to the same adress, we've found
the problem.

Kenneth


--[ mini ping/arp tutorial/debugging ]--
I'd look at arp first, then routes, then wiring.  do and 'arp -a'
(both
boxes), see if you have the other machine listed.  If not then confirm the
failure with tcpdump output not like this (running on box2):

10:59:40.507825 eth0 > arp who-has box1 tell box2 (0:60:97:a1:ed:a3)
10:59:40.508137 eth0 < arp reply box1 is-at 0:60:97:a4:b7:3c
(0:60:97:a1:ed:a3)
10:59:40.508178 eth0 > box2 > b0x1: icmp: echo request
10:59:40.508541 eth0 < box1 > box2: icmp: echo reply

If a machine considers itself on the same subnet as another machine then
the machine puts out and arp request to get the mac address of the other
machine (first line).  Then there is a response with the mac address
(second line), then the ping goes out on the subnet (third line), and
ofcouse the actual response (fourth line).  If it stops after line one,
then box2 isn't getting the response from box1 (or box1 isn't getting
the
request from box2).  If it skips the first two lines, then the arp is one
the machine (arp -a), which would happen for subsequent pings in a working
scenerio _or_ the machines don't consider themselves on the same subnet.
With the 'arp' command you can delete entries.
--[ end mini ]--


On Mon, 18 Oct 1999 ATeslik@aol.com wrote:

> Hello Samba folks,
>
>             I thought you might be able to help me.
>  I have 2 machines, 1 is FreeBSD, 1 is win95. They can't ping each
other, but
> the bsd box comes up in Network Nieghborhood when Samba is active.
What's
> going on? Is it not possible to ping a windows machine from a unix box?
They
> are on the same hub via UTP. IPs are 192.168.1.x and netmasks are same
> (255.255.255.0). No ipfw or routed running. Does anyone out there have a
> small network like this that mabye I can bounce a few questions off you?
> Heres some output to look at:
>
> >> 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 1500
> ppp0: 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!
>
> Alex
> <ateslik@aol.com>
>