Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
04-09-2002, 07:39 AM
|
#1
|
|
LQ Newbie
Registered: Apr 2002
Posts: 7
Rep:
|
connect: Network is unreachable
Ok, so I have a machine that I previously ran with 7.1, which
has an integrated network interface (a SOYO Dragon with a VIA
chip set). Anyway, when I installed 7.1, I figured the board
was so new that it would be unlikely that there was support
for the onboard network interface, so I added a NIC right from
the start and everything worked great. Now since I re installed
with 7.2 I am having some trouble. During the install 7.2
recognized the onboard interface (the 7.1 install never even
detected it), so I figured I would configure both the onboard
and the NIC. Then if the onboard worked, I would pull the NIC,
or if not, I would just use the NIC. Well now niether works. I
can ping both the lo, eth0 and eth1 (which is the NIC) but when I
ping anything else I get the message
connect: Network is unreachable
I Would love to get the onboard interface
working, but I will settle for the NIC if I have to. Any
responses are greatly appriciated.
Here is some additional info from relevent commands.
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:50:2C:00:B1:F8
inet addr:206.129.55.69 Bcast:206.129.55.79 Mask:255.255.255.240
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:
RX packets:78 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:12413 (12.1 Kb) TX bytes:168 (168.0 b)
Interrupt:11 Base address:0xec00
eth1 Link encap:Ethernet HWaddr 00:04:5A:54:45:FC
inet addr:206.129.55.68 Bcast:206.129.55.79 Mask:255.255.255.240
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:4 dropped:0 overruns:0 carrier:8
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:10 Base address:0xd000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:52 errors:0 dropped:0 overruns:0 frame:0
TX packets:52 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3444 (3.3 Kb) TX bytes:3444 (3.3 Kb)
# cat /proc/interupts
CPU0
0: 74594 XT-PIC timer
1: 533 XT-PIC keyboard
2: 0 XT-PIC cascade
5: 0 XT-PIC usb-uhci
8: 1 XT-PIC rtc
10: 9 XT-PIC eth1
11: 102 XT-PIC eth0, cmpci
12: 859 XT-PIC PS/2 Mouse
14: 24265 XT-PIC ide0
15: 2384 XT-PIC ide1
NMI: 0
LOC: 0
ERR: 0
MIS: 0
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
206.129.55.64 0.0.0.0 255.255.255.240 U 0 0 0 eth1
206.129.55.64 0.0.0.0 255.255.255.240 U 0 0 0 eth1
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
# ifup eth0
# ifup eth1
# cat /etc/modules.conf
alias parport_lowlevel parport_pc
alias eth0 via-rhine
alias eth1 tulip
alias sound-slot-0 cmpci
post-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1 || :
pre-remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S >/dev/null 2>&1 || :
alias usb-controller usb-uhci
# netstat -r
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
206.129.55.64 * 255.255.255.240 U 40 0 0 eth1
206.129.55.64 * 255.255.255.240 U 40 0 0 eth1
127.0.0.0 * 255.0.0.0 U 40 0 0 lo
|
|
|
|
04-09-2002, 09:27 AM
|
#2
|
|
Senior Member
Registered: Dec 2001
Location: The Netherlands
Distribution: Ubuntu
Posts: 1,316
Rep:
|
You are missing a default gateway. Try adding one with the route command.
|
|
|
|
04-18-2002, 12:12 AM
|
#3
|
|
LQ Newbie
Registered: Apr 2002
Posts: 7
Original Poster
Rep:
|
well I tried adding the gateway and here is where I ended up.
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
206.129.55.64 * 255.255.255.240 U 0 0 0 eth1
206.129.55.64 * 255.255.255.240 U 0 0 0 eth1
206.129.55.0 * 255.255.255.240 U 0 0 0 eth0
206.129.55.0 dragon.affoinfo 255.255.255.0 UG 0 0 0 eth0
206.129.55.0 * 255.255.255.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 206.129.55.49 0.0.0.0 UG 0 0 0 eth0
PING 206.129.55.49 (206.129.55.49) from 206.129.55.69 : 56(84) bytes of data.
From 206.129.55.69: Destination Host Unreachable
From 206.129.55.69: Destination Host Unreachable
From 206.129.55.69: Destination Host Unreachable
--- 206.129.55.49 ping statistics ---
5 packets transmitted, 0 packets received, +3 errors, 100% packet loss
so I gather I am not doing somthing correctly.
Also I can't seem to delete the ones I want to get rid of.
|
|
|
|
04-18-2002, 07:30 AM
|
#4
|
|
Member
Registered: Jun 2001
Location: (Cashville) Nashville, TN
Distribution: CentOS 4.0, Slackware 10.2,
Posts: 223
Rep:
|
R u using a manufacture router (ie. linksys, d-link) or r u using a linux box? What distro?
|
|
|
|
04-18-2002, 08:05 AM
|
#5
|
|
LQ Newbie
Registered: Apr 2002
Posts: 7
Original Poster
Rep:
|
I believe its a cisco router.
|
|
|
|
04-18-2002, 08:26 AM
|
#6
|
|
Member
Registered: Jun 2001
Location: (Cashville) Nashville, TN
Distribution: CentOS 4.0, Slackware 10.2,
Posts: 223
Rep:
|
what is the default gateway of the router?
also can u ping any other url or ip addy at ur current config?
|
|
|
|
04-18-2002, 08:51 AM
|
#7
|
|
LQ Newbie
Registered: Apr 2002
Posts: 7
Original Poster
Rep:
|
the gateway (router) address is 206.129.55.49 on my side. I don't know what it's address is externally.
the only IP adresses I can ping successfully are lo, eth0 and eth1.
I haven't even bothered with urls yet.
I'm not sure how this plays into it but our subnetmask is 255.255.255.240. route didn't seem to work when I tried to use this for the genmask.
|
|
|
|
04-18-2002, 11:17 AM
|
#8
|
|
Member
Registered: Jun 2001
Location: (Cashville) Nashville, TN
Distribution: CentOS 4.0, Slackware 10.2,
Posts: 223
Rep:
|
Alright I think this is ur problem.....when u added the default gateway u also added the word default..so when u do a route -n u get
"default 206.129.55.49". Depending on what distro ur using u need to take that out and then try it agian..I'm running a linksys router and ur config isn't to much diff from mine. R u connected to a school network or something? did u also try changing ur Genmask to 255.255.255.0 and see'n what happens?
|
|
|
|
04-18-2002, 12:13 PM
|
#9
|
|
LQ Newbie
Registered: Apr 2002
Posts: 7
Original Poster
Rep:
|
in the man pages it says you have to set up the static route to the gateway first before you can set up the default gateway route. I would assume that this would mean I would use a command like this to set up to set up routing to the local subnet.
# route add -net 206.129.55.0 genmask 255.255.255.240 dev eth0
I tried this and it didn't seem to make any diffence I still got the error:
connect: Network is unreachable
and it would not allow me to ad a default gateway at this point.
then I tried this
# route add -net 206.129.55.0 genmask 255.255.255.0 dev eth0
that seem to make it a little happier and at this point if I try to ping addresses with in the subnet, I get a message that looks something like this
[IP address] host is unreachable
where IP address was any IP within the subnet.
after that last command, even though I could not ping the gateway I was able to issue this command without error
# route add default gateway 206.129.55.49
also I think I am confused about the syntax to delete a spicific line from the routing table, I tried somthing like this and was unsuccessful
# route del 206.129.55.64
It returned an error and I think it said something like "no such process"
|
|
|
|
04-19-2002, 02:28 PM
|
#10
|
|
LQ Newbie
Registered: Apr 2002
Posts: 7
Original Poster
Rep:
|
can someone give me an example of the output of the route -n command on a system that has the routeing table set up correctly?
|
|
|
|
04-19-2002, 05:24 PM
|
#11
|
|
Member
Registered: Jun 2001
Location: (Cashville) Nashville, TN
Distribution: CentOS 4.0, Slackware 10.2,
Posts: 223
Rep:
|
Here is mine:
Destination Gateway Genmask Flags Metric Ref Use Iface
192.118.0.1 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.118.1.1 0.0.0.0 UG 0 0 0 eth0
of course those r not my real gateway/destination ip's....I'm using a linksys router w/ wireless acess point
.
|
|
|
|
04-21-2002, 10:33 AM
|
#12
|
|
LQ Newbie
Registered: Apr 2002
Posts: 7
Original Poster
Rep:
|
Ok so I think things are starting to become a little clearer. Now I understand that the subnet mask of 255.255.255.240 means that there are blocks of 16 addresses (i.e. 0-15, 16-31, 32-47...)so we have apperently been aloted two blocks by our ISP, 48-63 and 64-79. So the route for the block in which my actual address exist was set up already by the config files except for the wrong device so I tried adding this:
# route add -net xxx.xxx.xxx.64 netmask 255.255.255.240 dev eth0
then in order to talk to the gateway, which is in the first block, I tried this
#route add -net xxx.xxx.xxx.48 netmask 255.255.255.240 dev eth0
So from what I understand this should allow me to communicate with all the IP addresses within our 2 address blocks but I am still getting the message
destination host unreacheable
for all the IP's in that range  What am I missing?
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 11:42 PM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|