- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: weird route
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2003 09:13 PM
12-14-2003 09:13 PM
weird route
Can somebody explain it to me the following and what action do I have to make?
[root]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.9.200.51 gatekeeper 255.255.255.255 UGH 0 0 0 lo
192.9.200.97 gatekeeper 255.255.255.255 UGH 0 0 0 lo
192.9.200.134 gatekeeper 255.255.255.255 UGH 0 0 0 lo
192.9.200.167 gatekeeper 255.255.255.255 UGH 0 0 0 lo
192.9.200.212 gatekeeper 255.255.255.255 UGH 0 0 0 lo
192.9.200.3 gatekeeper 255.255.255.255 UGH 0 0 0 lo
192.9.200.81 gatekeeper 255.255.255.255 UGH 0 0 0 lo
192.9.200.49 gatekeeper 255.255.255.255 UGH 0 0 0 lo
192.9.200.66 gatekeeper 255.255.255.255 UGH 0 0 0 lo
192.9.200.82 gatekeeper 255.255.255.255 UGH 0 0 0 lo
192.9.200.99 gatekeeper 255.255.255.255 UGH 0 0 0 lo
192.9.200.48 gatekeeper 255.255.255.255 UGH 0 0 0 lo
192.9.200.67 gatekeeper 255.255.255.255 UGH 0 0 0 lo
192.9.200.164 gatekeeper 255.255.255.255 UGH 0 0 0 lo
192.9.200.68 gatekeeper 255.255.255.255 UGH 0 0 0 lo
192.9.200.117 gatekeeper 255.255.255.255 UGH 0 0 0 lo
192.9.200.146 gatekeeper 255.255.255.255 UGH 0 0 0 lo
192.9.200.179 gatekeeper 255.255.255.255 UGH 0 0 0 lo
192.9.200.178 gatekeeper 255.255.255.255 UGH 0 0 0 lo
192.9.200.53 gatekeeper 255.255.255.255 UGH 0 0 0 lo
192.9.200.177 gatekeeper 255.255.255.255 UGH 0 0 0 lo
192.9.200.5 gatekeeper 255.255.255.255 UGH 0 0 0 lo
192.9.200.129 gatekeeper 255.255.255.255 UGH 0 0 0 lo
192.9.200.26 gatekeeper 255.255.255.255 UGH 0 0 0 lo
169.254.251.26 gatekeeper 255.255.255.255 UGH 0 0 0 lo
This is the firstime I see this when I run the route command on the shell of redhat 7.1.
Hope you could help me on this.
Regards,
LAT
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2003 09:23 PM
12-14-2003 09:23 PM
Re: weird route
This is nothing strange. Those are the machines and hosts your Linux box knows. First is the others box address, third the maks (255.255.255.255 means that all are individual boxes, and your router don't know the network related), gatekeeper is your gateway name, what is strange is lo at the end, meaning that all those are to be reached through your loopback interface, that is to say that all these are seen as your own machine... Nothing wrong with it aprat from the fact that it won't help you reach any machine on the net.
Maybe could you run a 'neat' to set your NIC up properly ?
hth
J
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2003 09:26 PM
12-14-2003 09:26 PM
Re: weird route
route del -host 192.9.2.51 to delete this host, and same for the others.
hth
J
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2003 10:09 PM
12-14-2003 10:09 PM
Re: weird route
You seem to have a netmask of 255.255.255.255. It makes for an exciting network but probably isn't what you want. I think this might be the reason you have a route for each machine because you don't actually have a network you can route to.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-15-2003 10:54 AM
12-15-2003 10:54 AM
Re: weird route
Your machine can be told to ignore such requests (thus not populating your routing table like this) faily simply.
As it is, a populated routing table like this isn't going to hurt, but it's not terribly efficint (a network route, or default route pointed correctly would be more efficient).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2003 08:49 AM
12-16-2003 08:49 AM
Re: weird route
I too think, you have a netmask of 255.255.255.255, which doesnt make a lot of sense, for there is no ip part for the computer left, there should be at least one bit left for the computer address. I wonder, how it works at all. So every new address has to be addressed via gateway, even the host is in the same net.
greetings,
Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2003 02:06 PM
12-16-2003 02:06 PM
Re: weird route
Post up an example or two and I'll recommend changes.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com