ping www.sun.com ===>> unknown host www.sun.com: What 1 cmd fixes it?
David Combs
it down; brought it up, and I get this.
No change in cables; other computers on same modem-thing
browse just fine.
To tell the truth, I'd had the machine "up" ever since
a friend (now unreachable) got me all set up. That recent
takeing-down was the FIRST time down since way back then.
(Yes, is the same machine with the not turning on if
usb hub was plugged in -- have been spending time
using a different machine.)
Anyway, looks like I should have (or he should have had me)
add some critical command or two into a script!
What do you suppose that one or two commands I need to
give (then add to script!) to make it work ok.
Uses ethernet cable to get to the router, and yes I did
wiggle the plugs at each end.
----
Oh, just to make sure, is there any way to query the
router from the computer, or send something to it,
that will simply show that the computer IS connected
to it?
Thanks!
David
Richard B. Gilbert
I'd ping something else!! I just tried pinging that address myself and
got no response.
Richard B. Gilbert
ping 192.168.0.1
This does require that the network cable from your computer is plugged
into your router or that there is some indirect connection; e.g. through
a switch. If the connection is direct and correctly made both the
interface on your computer and the router should display a "Link Light".
This tells you that your computer and the router are correctly connected
to each other, that both devices are powered on, etc, etc.
It also requires that your software be configured correctly.
hume.sp...@bofh.ca
> Oh, just to make sure, is there any way to query the
> router from the computer, or send something to it,
> that will simply show that the computer IS connected
> to it?
Yes, ping.
However, "unknown host" seems to indicate that perhaps your nameservice
is broken. That MIGHT be because the entire network is broken, but perhaps
not.
First, ping the router.
Then, ping the nameservers listed in /etc/resolv.conf.
Then, use 'nslookup' to check if a known host will resolve, like www.sun.com.
If nslookup works, check /etc/nsswitch.conf.
--
Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/
hume.sp...@bofh.ca
> I'd ping something else!! I just tried pinging that address myself and
> got no response.
Even if the remote site is down, you'll get a "no response" error...
NOT a "unknown host" error, as the original poster said he saw.
Oscar del Rio
> All was working fine (firefox browsing, etc) when I took
> it down; brought it up, and I get this.
>
> No change in cables; other computers on same modem-thing
> browse just fine.
>
> To tell the truth, I'd had the machine "up" ever since
> a friend (now unreachable) got me all set up. That recent
> takeing-down was the FIRST time down since way back then.
post the output of:
# ifconfig -a
# netstat -rn
# cat /etc/resolv.conf
# grep dns /etc/nsswitch.conf
I suspect the default gateway was not made "permanent" and got lost on
reboot. If that the case, the 1 cmd to fix it would be
route -p add default ###.###.###.###
where ###... is your router's IP address.
David Combs
Richard B. Gilbert <rgilb...@comcast.net> wrote:
>Ping the router e.g.:
>ping 192.168.0.1
>
>This does require that the network cable from your computer is plugged
>into your router or that there is some indirect connection; e.g. through
>a switch. If the connection is direct and correctly made both the
>interface on your computer and the router should display a "Link Light".
>This tells you that your computer and the router are correctly connected
>to each other, that both devices are powered on, etc, etc.
>
>It also requires that your software be configured correctly.
1: ping 192.168.0.1 gives
ICMP host unreachable from gateway localhost (127.0.0.1)
for icmp from localhost (127.0.0.1) to 192.168.0.1
and then in a loop keeps outputting those two lines until I ^C it.
NOTE: ping localhost says localhost is alive (or something like that)
( ping 192.168.0.1 gives
^^^^^^^^^^^ is this the right thing to ping for ALL machines,
and if not, where do I find the one for MY computer? )
2: lights are on at both ends.
AND, when I unplug the cable from the router, the
light on the sun goes OFF (as it should, according to
what you're saying, yes?)
3: ipconfig -i says everything is running:
lo0: ... <UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> ...
inet 127.0.0.1 netmask ff000000
BGE0: ... <BROADCAST, RUNNING, MULTICAST, IPv4>
inet 0.0.0.0 netmask 0
THANKS for info on the link-light. First I've heard of it, esp as
a check on each end being connected and working.
I also tried ping www.truthout.com; said "unknown <something, I forget>".
Thanks!
David
Paul Gress
> 1: ping 192.168.0.1 gives
> ICMP host unreachable from gateway localhost (127.0.0.1)
> for icmp from localhost (127.0.0.1) to 192.168.0.1
> and then in a loop keeps outputting those two lines until I ^C it.
>
> NOTE: ping localhost says localhost is alive (or something like that)
>
Different routers have different addresses. Mine has 192.168.1.1. Then
also it can be changed manually. So the fist thing to check is the command
netstat -rn
This will show the default route (to the router) and it's address, if
the network is working.
>
> ( ping 192.168.0.1 gives
> ^^^^^^^^^^^ is this the right thing to ping for ALL machines,
> and if not, where do I find the one for MY computer? )
>
See above
> 2: lights are on at both ends.
>
> AND, when I unplug the cable from the router, the
> light on the sun goes OFF (as it should, according to
> what you're saying, yes?)
>
> 3: ipconfig -i says everything is running:
> lo0: ... <UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> ...
> inet 127.0.0.1 netmask ff000000
> BGE0: ... <BROADCAST, RUNNING, MULTICAST, IPv4>
> inet 0.0.0.0 netmask 0
>
>
Not really. inet has an address of 0.0.0.0
My ifconfig -a
/usr/sbin/ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu
8232 index 1
inet 127.0.0.1 netmask ff000000
rge0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500
index 3
inet 0.0.0.0 netmask ff000000
iwh0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500
index 5
inet 192.168.1.206 netmask ffffff00 broadcast 192.168.1.255
I'm on my laptop with opensolaris, so iwh0 is my wireless network
interface and rge0 is my wired interface. rge0 has no address, also no
wire. iwh0 is assigned 192.168.1.206 by my router.
The command netstat -rn
Routing Table: IPv4
Destination Gateway Flags Ref Use Interface
-------------------- -------------------- ----- ----- ---------- ---------
default 192.168.1.1 UG 1 456 iwh0
192.168.1.0 192.168.1.206 U 1 14 iwh0
127.0.0.1 127.0.0.1 UH 6 201 lo0
My router is 192.168.1.1
Paul
hume.sp...@bofh.ca
> BGE0: ... <BROADCAST, RUNNING, MULTICAST, IPv4>
> inet 0.0.0.0 netmask 0
"0.0.0.0" is definitely not right. Is this interface supposed to be
statically configured, or use DHCP?
What does /etc/hostname.bge0 contain?
Richard B. Gilbert
> In article <xoudnXcs9v10AZfW...@giganews.com>,
> Richard B. Gilbert <rgilb...@comcast.net> wrote:
>
>> Ping the router e.g.:
>> ping 192.168.0.1
>>
>> This does require that the network cable from your computer is plugged
>> into your router or that there is some indirect connection; e.g. through
>> a switch. If the connection is direct and correctly made both the
>> interface on your computer and the router should display a "Link Light".
>> This tells you that your computer and the router are correctly connected
>> to each other, that both devices are powered on, etc, etc.
>>
>> It also requires that your software be configured correctly.
>
> 1: ping 192.168.0.1 gives
> ICMP host unreachable from gateway localhost (127.0.0.1)
> for icmp from localhost (127.0.0.1) to 192.168.0.1
> and then in a loop keeps outputting those two lines until I ^C it.
>
> NOTE: ping localhost says localhost is alive (or something like that)
>
>
> ( ping 192.168.0.1 gives
> ^^^^^^^^^^^ is this the right thing to ping for ALL machines,
> and if not, where do I find the one for MY computer? )
No, it's only correct if your network is using RFC-1918 private network
addresses. These addresses are NOT routeable. See RFC-1918
http://www.faqs.org/rfcs/rfc1918.html
Ask your network manager to tell you the net mask for your network.
It's probably 255.255.255.0 but using a mask that's "probably right" is
not a good idea! Find out what's correct and then use it.
<snip>
There are several books on the subject of Networks. "TCP/IP Network
Administration" by Craig Hunt is a good one. If your library does not
have a copy, I'm sure that Amazon, http://www.amazon.com/, either has it
or can get it.
David Combs
---- ok, here it is:
>
> netstat -rn
Routing Table: IPv4
Destination Gateway Flags Ref Use Interface
-------------------- -------------------- ----- ----- ---------- ---------
127.0.0.1 127.0.0.1 UH 31 675313 lo0
>
>
> ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
bge0: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 0.0.0.0 netmask 0
>
>
> cat /etc/resolv.conf
DOMAIN BRUSSELSPROUTS
nameserver 167.206.251.129
nameserver 167.206.251.130
> grep dns /etc/nsswitch.conf
# /etc/nsswitch.dns:
# DNS service expects that an instance of svc:/network/dns/client be
hosts: files dns
ipnodes: files dns
>
> whoami
dkc
David Combs
<hume.sp...@bofh.ca> wrote:
>David Combs <dkc...@panix.com> wrote:
>> Oh, just to make sure, is there any way to query the
>> router from the computer, or send something to it,
>> that will simply show that the computer IS connected
>> to it?
>
>Yes, ping.
>
>However, "unknown host" seems to indicate that perhaps your nameservice
>is broken. That MIGHT be because the entire network is broken, but perhaps
>not.
>
>First, ping the router.
How do you do that?
>
>Then, ping the nameservers listed in /etc/resolv.conf.
ping 167.206.251.129
Host unreachable from gateway localhost (127.0.0.1)
For icmp from ....
Host unreachable from gateway localhost (127.0.0.1)
For icmp from ....
Host unreachable from gateway localhost (127.0.0.1)
For icmp from ....
Host unreachable from gateway localhost (127.0.0.1)
For icmp from ....
^C
Then same thing but for ....130
ping 167.206.251.130
ditto for its output, but with 130 instead of 129.
David
hume.sp...@bofh.ca
ping <IP>. But you'd have to know what your router is, first.
Are you behind a little NAT box, like a DLink or something? Should your
machine be statically configured, or acquiring via DHCP? I asked before
in a different followup.
Richard B. Gilbert
> In article <hee768$gf$2...@Kil-nws-1.UCIS.Dal.Ca>,
> <hume.sp...@bofh.ca> wrote:
>> David Combs <dkc...@panix.com> wrote:
>>> Oh, just to make sure, is there any way to query the
>>> router from the computer, or send something to it,
>>> that will simply show that the computer IS connected
>>> to it?
>> Yes, ping.
>>
>> However, "unknown host" seems to indicate that perhaps your nameservice
>> is broken. That MIGHT be because the entire network is broken, but perhaps
>> not.
>>
>> First, ping the router.
>
>
> How do you do that?
You say:
ping 127.0.0.1
or whatever IP address you have configured the router to use.
Note that the router has TWO IP addresses. One is for the outside world
to use. This address will be assigned by your Internet Provider. The
other is the router's address on your local network. The latter is the
one you ping to test the ability of your computer to talk to the router.
Your local network is probably using one of the RFC-1918 address families;
"3. Private Address Space
The Internet Assigned Numbers Authority (IANA) has reserved the
following three blocks of the IP address space for private internets:
10.0.0.0 - 10.255.255.255 (10/8 prefix)
172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
192.168.0.0 - 192.168.255.255 (192.168/16 prefix)"
Read more: http://www.faqs.org/rfcs/rfc1918.html
Oscar del Rio
>> netstat -rn
>
> Routing Table: IPv4
> Destination Gateway Flags Ref Use Interface
> -------------------- -------------------- ----- ----- ---------- ---------
> 127.0.0.1 127.0.0.1 UH 31 675313 lo0
missing default gateway. The gateway was probably added manually before
the reboot, without making it permanent.
>> ifconfig -a
> bge0: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
> inet 0.0.0.0 netmask 0
Missing IP address and netmask. You will not get anywhere with 0.0.0.0
The IP address was probably added manually with ifconfig, again without
saving it.
We have no way to know what your IP address, netmask and gateway are
supposed to be. You will have to figure that out perhaps by checking the
settings of other machines in your local network.
EXAMPLE - IF and only IF your network settings were to be
IP: 192.168.12.34
Netmask: 255.255.0.0
Gateway: 192.168.1.2
# vi /etc/hosts
192.168.12.34 YOURCOMPUTERNAME
# vi /etc/netmasks
192.168.0.0 255.255.0.0
# echo 192.168.12.34 > /etc/hostname.bge0
# ifconfig bge0 192.168.12.34 netmask + broadcast + up
# route -p add default 192.168.1.2
That should fix it. No need to reboot but you might want to reboot
anyway to make sure the settings got saved properly.
David Combs
Here's SOME of the info we keep around about the local network:
(This was given to me just a few hours ago.)
dns servers:
167.206.3.152
167.206.7.4
^---- maybe that's a 2, but probably a 7. (Hard to read the writing.)
default gateway: 192.168.1.1
david (me) 192.168.1.205
Does that help?
If so, please tell me what files to update.
THANKS!
David
Paul Gress
These are the DNS servers for Cablevision from Hicksville NY.
> default gateway: 192.168.1.1
Thats from the router, the default route.
>
>
> david (me) 192.168.1.205
>
Looks like a static IP address.
> Does that help?
>
> If so, please tell me what files to update.
Here goes:
Put in your /etc/hosts an line entry:
192.168.1.205 My_computer_hostname
where "My_computer_hostname" is the actual name for your computer.
Put in a/the file /etc/defaultrouter the entry:
192.168.1.1
Put in a/the file /etc/resolv.conf the entry:
nameserver 167.206.3.152
nameserver 167.206.7.4
Create an empty file /etc/hostname.bge0
# touch /etc/hostname.bge0
This will auto configure for all the above entries upon reboot so you do
not need to do "route -p add default 192.168.1.1".
Now either reboot or enter:
# route -p add default 192.168.1.1
Hope this helps.
Paul
hume.sp...@bofh.ca
> If so, please tell me what files to update.
Just before doing what Paul suggested, it might be worthwhile to try the
following:
/sbin/ifconfig bge0 auto-dhcp start
... and see what happens.
Barry OGrady
You appear to have the gateway set to localhost 127.0.0.1.
You need to change it to the router ip.
>
>
>Then same thing but for ....130
>
>ping 167.206.251.130
>
>ditto for its output, but with 130 instead of 129.
>
>
>
>
>
>David
>
>
>
>
>
>
>
>
>
>
>>
>>Then, use 'nslookup' to check if a known host will resolve, like www.sun.com.
>>
>>If nslookup works, check /etc/nsswitch.conf.
>>
>>--
>>Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/
>
=-=-=
Barry
http://members.iinet.net.au/~barry.og
David Combs
what line in it, do I change?
(The paper I was given says "default gateway 192.168.1.1".)
I mean, I gave the above command:
>>ping 167.206.251.129
and it came back with:
>>
>>Host unreachable from gateway localhost (127.0.0.1)
>>For icmp from ....
>>Host unreachable from gateway localhost (127.0.0.1)
...
Where did it get that 127.0.0.1 from?
>
>>
>>
>>Then same thing but for ....130
>>
>>ping 167.206.251.130
>>
>>ditto for its output, but with 130 instead of 129.
>>
>>
>>
>>
>>
>>David
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>>
>>>Then, use 'nslookup' to check if a known host will resolve, like www.sun.com.
>>>
>>>If nslookup works, check /etc/nsswitch.conf.
>>>
>>>--
>>>Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/
>>
>
>=-=-=
>Barry
>http://members.iinet.net.au/~barry.og
Much thanks from embarrassingly know-nothing David
Paul Gress
>>
> Really stupid question, but how do I do that? ie, what file, and maybe
> what line in it, do I change?
>
> (The paper I was given says "default gateway 192.168.1.1".)
>
> I mean, I gave the above command:
>
> >>ping 167.206.251.129
>
> and it came back with:
>
>>> Host unreachable from gateway localhost (127.0.0.1)
>>> For icmp from ....
>>> Host unreachable from gateway localhost (127.0.0.1)
> ...
>
> Where did it get that 127.0.0.1 from?
>
>
>
That is your default route. Set all the files I from the instructions I
send the other day, it should work. It will change your default gateway
or default route to 192.168.1.1.
Paul
David Combs
THANK YOU!!!!
THAT DID IT!!!!
THANKS!!!!
Question: do I have to do that by hand each time I boot up?
Or, is there some place I can put it, so that it happens
automatically?
(Remember, this is solaris-10, so the booting-up init-file stuff
is all different, I think.)
Thanks!
David
David Combs
Deliberate top-post:
Paul Hume, whose post came immediately after yours, and which
I had not yet seen when I 10 minutes ago followed-up to you,
suggested that I try doing:
/sbin/ifconfig bge0 auto-dhcp start
and see what happened.
Blow me over, everything (well, ping and firefox) seems to work.
(but ping on www.sun.com didn't, but did on eg www.truthout.org,
and www.booktv.org. Humm -- maybe I should try something
that I have NEVER gone to on that computer, just to make
sure it's not an old copy or something. Wait, I'll be
right back.
...
Yep, it does.
THEREFORE THIS NEXT QUESION: And I'll ask you the same question
I asked him (who knows when he'll see it?):
So, whenever I boot up, do I have to type in that start
command by hand?
Or is there somewhere that I can put it so that it will
get executed automatically (if it hasn't already "started")?
And, again, I'm using solaris-10, which has some totally new
way of starting up, without using all those init-file scripts?
THANKS!
David
All this stuff here (below, bottom placed), I could just
delete it in this followup, but to keep your suggestions
alive, existing, I'll leave them there.
Thanks!
In article <4b0dfb6b$0$22532$607e...@cv.net>,
Richard B. Gilbert
> In article <4bq0h5duqqik8cci7...@4ax.com>,
> Barry OGrady <god_fre...@hotmail.com> wrote:
>> On Wed, 25 Nov 2009 05:05:57 +0000 (UTC), dkc...@panix.com (David
>> Combs) wrote:
>>
>>> In article <hee768$gf$2...@Kil-nws-1.UCIS.Dal.Ca>,
>>> <hume.sp...@bofh.ca> wrote:
>>>> David Combs <dkc...@panix.com> wrote:
>>>>> Oh, just to make sure, is there any way to query the
>>>>> router from the computer, or send something to it,
>>>>> that will simply show that the computer IS connected
>>>>> to it?
>>>> Yes, ping.
>>>>
>>>> However, "unknown host" seems to indicate that perhaps your nameservice
>>>> is broken. That MIGHT be because the entire network is broken, but perhaps
>>>> not.
>>>>
>>>> First, ping the router.
>>>
>>> How do you do that?
You type "ping 192.168.0.1"!
The "dotted decimal" number is an IP address which may or may not
designate something on your home network.
I suspect that you would do best to seek professional help. Your local
Office Max might be able to help you out. Don't be surprised if you get
a bill for two or three hundred bucks for making a house call, teaching
Networking 101, etc.
<snip>
Your local community college may offer such a course.
hume.sp...@bofh.ca
> Question: do I have to do that by hand each time I boot up?
> Or, is there some place I can put it, so that it happens
> automatically?
Your bge0 interface is being plumbed, so /etc/hostname.bge0 must exist.
To make the interface use DHCP, just "touch /etc/dhcp.bge0".
Check to make sure that /etc/hostname.bge0 contains, though. Is it empty?
I tend not to trust the hostname handed out by DHCP (this is purely personal
preference), so I also put the hostname I want the machine to use for itself
into /etc/nodename. ie: "echo kimji > /etc/nodename".
> (Remember, this is solaris-10, so the booting-up init-file stuff
> is all different, I think.)
Not at all. It's just fired through SMF, like everything else. The
SMF service is svc:/network/physical:default, and it calls the script
/lib/svc/method/net-physical, which you can read to see the logic used.
Once you touch that /etc/dhcp.bge0 file, you should even be able to do a
"svcadm restart network/physical" and it should properly restart the
interface, pulling in the DNS servers and default route and all that.
Paul Gress
> Deliberate top-post:
>
> Paul Hume, whose post came immediately after yours, and which
> I had not yet seen when I 10 minutes ago followed-up to you,
> suggested that I try doing:
>
> /sbin/ifconfig bge0 auto-dhcp start
>
> and see what happened.
>
> Blow me over, everything (well, ping and firefox) seems to work.
>
> (but ping on www.sun.com didn't, but did on eg www.truthout.org,
> and www.booktv.org. Humm -- maybe I should try something
> that I have NEVER gone to on that computer, just to make
> sure it's not an old copy or something. Wait, I'll be
> right back.
>
> ...
>
> Yep, it does.
>
>
>
>
> THEREFORE THIS NEXT QUESION: And I'll ask you the same question
> I asked him (who knows when he'll see it?):
>
> So, whenever I boot up, do I have to type in that start
> command by hand?
>
> Or is there somewhere that I can put it so that it will
> get executed automatically (if it hasn't already "started")?
>
> And, again, I'm using solaris-10, which has some totally new
> way of starting up, without using all those init-file scripts?
>
>
>
> delete it in this followup, but to keep your suggestions
> alive, existing, I'll leave them there.
>
>
> Thanks!
>
>
>
>
Dave,
The command "/sbin/ifconfig bge0 auto-dhcp start" I believe will not
work through another reboot.
What this command did was start DHCP, which is basically a dynamic
address assignment. In other words, it assigned you the next free
address on the router. So there is a very good chance you don't have
192.168.1.205 assigned as your IP address. If you have any equipment
communicating to your computer using 192.168.1.205 it won't work.
You can find out your ip address assigned by the router by entering the
following command:
netstat -rn
Here is the output from my computer:
# netstat -rn
Routing Table: IPv4
Destination Gateway Flags Ref Use Interface
-------------------- -------------------- ----- ----- ---------- ---------
default 192.168.1.1 UG 1 456 iwh0
192.168.1.0 192.168.1.206 U 1 14 iwh0
127.0.0.1 127.0.0.1 UH 6 201 lo0
My assigned IP address by the router is 192.168.1.206.
There are two ways to get IP 192.168.1.206 assigned to you. One way is
as I've explained in a previous e-mail (also attached below) or have the
router setup to reserve an IP address based on the MAC ID of your
computer NIC (Network Interface Card), your IT department should know
how to set up the Router for this.
Any way, I think the best option is to configure your computer for a
static IP address as shown below.
Paul