Do you have fragile.mshome.net in the /etc/hosts file?
To ping using fragile.mshome.net you would need a DSN server
to resolve that name to an internal IP address.
Look in the ports collection for djbdns
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of
Thanks;
I checked with ifconfig, and fragile's IP is actually 192.168.0.224,
and I put this in the hosts file.
Now, I can ping and ssh into fragile using the IP address, but
pinging fragile still assumes 192.168.0.116 is it's IP - so does
the fault now lie with the other machines on the
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Phil Cooper
Sent: Wednesday, June 29, 2005 7:43 PM
To: freebsd-questions@freebsd.org
Subject: Ping and general network weirdness
Hi everybody;
Not doing too well with my first freeBSD install. I
Here's the output, thanks for such a quick reply.
$ netstat -rn
Routing tables
Internet:
DestinationGatewayFlagsRefs Use Netif
Expire
default192.168.0.1UGS 00rl0
127.0.0.1 127.0.0.1 UH 1
It depends where fragile is mapped to the IP. If it's only in the hosts
file, the other machines have no way of knowing, and will probably fail
to resolve 'fragile' to an IP. If it's in DNS somewhere, you just need
to correct the DNS record.
Try pinging by IP?
On Thu, 2005-06-30 at 01:10
As far as I know, not knowing much, doesn't the win XP box which
connects to the net do all the DHCP and local DNS when XP's internet
connection sharing is turned on? Which it is. It's at 192.168.0.1,
which netstat is correctly reporting as the default gateway...
So is it a case of working
, 2005 7:10 PM
To: freebsd-questions@freebsd.org
Subject: Re: Ping and general network weirdness
Thanks;
I checked with ifconfig, and fragile's IP is actually 192.168.0.224,
and I put this in the hosts file.
Now, I can ping and ssh into fragile using the IP address, but
pinging
XP can offer all the DNS it is aware of, but unless you updated a DNS
server somewhere with fragile-192.168.1.204, it can't resolve. You
have to do more than setting a hostname to make it resolve on the
network. If you are obtaining the IP address on fragile dynamically
anyway (via DHCP), you
If you haven't explicitly set fragile-192.168.1.204 in a DNS
server, it
won't resolve from any other machine unless you put it in that
machines
host file as well (windows has one, but the path eludes me right now).
On Thu, 2005-06-30 at 01:23 +0100
Fixed - all the machines can see it
