# [EMAIL PROTECTED] / 2003-11-09 19:00:28 -0500:
> At 05:29 PM 11/9/2003, Luke Kearney wrote:
>
> >OK I think I see the problem. Your winblows machines are on a different
> >network to the FBSD machine. Change FBSD to 192.168.0.7 and all should
> >be just fine.
>
> Very cool Luke; this worked and my FBSD box now can ping my Windoz boxes
> and vice versa.
>
> >There is no route to host for the other machines because
> >as far as FBSD is concerned the other machines should be on a different
> >wire.
>
> So that third node on the IP addr represents what, the switch?
no, it's the subnet. ok, this is not a helpful answer. in one of
your previous post, you wrote:
192.168.0.1 (win-xp)
192.168.0.150 (win-95)
192.168.7.7 (freebsd-4.8/mini)
192.168.0.3 (win-98)
192.168.0.160 (win-95)
Destination Gateway Flags Refs Use Netif Expire
127.0.0.1 127.0.0.1 UH 0 0 lo0
192.168.7 link#1 UC 1 0 ep0
192.168.7.7 00:20:af:4d:24:b7 UHLW 0 1 lo0
#ifconfig -a
ep0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.7.7 netmask 0xffffff00 broadcast 192.168.7.255
ether 00:20:af:4d:24:b7
media: Ethernet 10baseT/UTP
lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
faith0: flags=8002<BROADCAST,MULTICAST> mtu 1500
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000
ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
sl0: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 552
the netmask in the ifconfig output is important, because the host
uses its ip address and the netmask to figure out where it should be
sending packets for a given ip. it does so by "masking" the ip
address with the netmask: the bits that are turned on in the mask
cover "local" (in the network sense) part of the address;
inet 192.168.7.7 netmask 0xffffff00
or the equivalent
inet 192.168.7.7 netmask 255.255.255.0
means 192.168.7 is the part common to all hosts on the network, and
there are 256 distinct addresses on the network (254 hosts, 0 for
the address of the network, 255 for the broadcast address).
addresses that are local (on the same wire) can be sent the packets
directly, foreign addresses (on a different network) require passing
the traffic through a box connected to the foreign logical network.
you had no route configured for the 192.168.0/24 network, hence the
error.
> IOW you're saying since all the other boxes on the LAN are
> 192.168.0.nnn the FBSD box needed to be as well?
given the netmask you use, yes. or you could change the mask on all
hosts to, say, 255.255.0.0.
--
If you cc me or remove the list(s) completely I'll most likely ignore
your message. see http://www.eyrie.org./~eagle/faqs/questions.html
_______________________________________________
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
