- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Help?! It's Monday!!! Route command screwy?
Operating System - HP-UX
1821400
Members
3063
Online
109633
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
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
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО02-11-2002 06:37 AM
тАО02-11-2002 06:37 AM
Help?! It's Monday!!! Route command screwy?
What's wrong with the following picture?
lg1nfs0 root /home/tgfurnis # netstat -arn
Routing tables
Dest/Netmask Gateway Flags Refs Use Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 3644 lo0 4136
192.168.50.2 192.168.50.2 UH 0 41406 lan0 4136
192.168.50.0 192.168.50.2 U 2 0 lan0 1500
127.0.0.0 127.0.0.1 U 0 0 lo0 4136
lg1nfs0 root /home/tgfurnis # route add default 192.168.50.1
add net default: gateway 192.168.50.1: Network is unreachable
lg1nfs0 root /home/tgfurnis # ping 192.168.50.1
PING 192.168.50.1: 64 byte packets
64 bytes from 192.168.50.1: icmp_seq=0. time=2. ms
???
----192.168.50.1 PING Statistics----
1 packets transmitted, 1 packets received, 0% packet loss
round-trip (ms) min/avg/max = 2/2/2
In other words, there's a route to 192.168.50.0 through the lan0 interface on 192.168.50.2. In fact that works - I am connected to the system from 192.168.50.1. But the system has no default route and I can't seem to add one - it should be defaulting out to 192.168.50.1, but if I attempt to add a default route there, I get "192.168.50.1 network unreachable". That's obviously not true, since I'm connected from there. Am I doing something wrong?
And if not, any suggestions on a workaround? I'm not sure yet how or why the system lost its default route, would like to avoid rebooting or completely restarting networking until next weekend if possible, but I need to get stuff routed through 192.168.50.1...
lg1nfs0 root /home/tgfurnis # netstat -arn
Routing tables
Dest/Netmask Gateway Flags Refs Use Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 3644 lo0 4136
192.168.50.2 192.168.50.2 UH 0 41406 lan0 4136
192.168.50.0 192.168.50.2 U 2 0 lan0 1500
127.0.0.0 127.0.0.1 U 0 0 lo0 4136
lg1nfs0 root /home/tgfurnis # route add default 192.168.50.1
add net default: gateway 192.168.50.1: Network is unreachable
lg1nfs0 root /home/tgfurnis # ping 192.168.50.1
PING 192.168.50.1: 64 byte packets
64 bytes from 192.168.50.1: icmp_seq=0. time=2. ms
???
----192.168.50.1 PING Statistics----
1 packets transmitted, 1 packets received, 0% packet loss
round-trip (ms) min/avg/max = 2/2/2
In other words, there's a route to 192.168.50.0 through the lan0 interface on 192.168.50.2. In fact that works - I am connected to the system from 192.168.50.1. But the system has no default route and I can't seem to add one - it should be defaulting out to 192.168.50.1, but if I attempt to add a default route there, I get "192.168.50.1 network unreachable". That's obviously not true, since I'm connected from there. Am I doing something wrong?
And if not, any suggestions on a workaround? I'm not sure yet how or why the system lost its default route, would like to avoid rebooting or completely restarting networking until next weekend if possible, but I need to get stuff routed through 192.168.50.1...
Hockey PUX?
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-11-2002 06:41 AM
тАО02-11-2002 06:41 AM
Re: Help?! It's Monday!!! Route command screwy?
D'oh! Forgot the extra "1" on the end of the route command. No longer an issue. :-(
Hockey PUX?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-11-2002 06:42 AM
тАО02-11-2002 06:42 AM
Re: Help?! It's Monday!!! Route command screwy?
Show us your route add command.
live free or die
harry
live free or die
harry
Live Free or Die
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-11-2002 06:43 AM
тАО02-11-2002 06:43 AM
Re: Help?! It's Monday!!! Route command screwy?
The ole user error. You are right, it must be a monday!
live free or die
harry
live free or die
harry
Live Free or Die
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP