HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- routing basic explanation
Operating System - Linux
1827990
Members
2241
Online
109973
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
Forums
Discussions
Discussions
Discussions
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
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
11-10-2004 04:21 PM
11-10-2004 04:21 PM
routing basic explanation
Hi all,
bellow is a part o routing table
Destination Gateway Genmask Iface
10.0.0.0 0.0.0.0 255.255.255.0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 eth1
0.0.0.0 10.0.0.5 0.0.0.0 eth0
my question is concerning to qateway 0.0.0.0,
what does 0.0.0.0 mean ? There is no gateway ?
Or is there relation between 0.0.0.0 gateway and 0.0.0.0 destination ? (in sence all packets to 10.0.0.0 network go via 0.0.0.0 gw so the destination is also 0.0.0.0)
many thanks
M.
bellow is a part o routing table
Destination Gateway Genmask Iface
10.0.0.0 0.0.0.0 255.255.255.0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 eth1
0.0.0.0 10.0.0.5 0.0.0.0 eth0
my question is concerning to qateway 0.0.0.0,
what does 0.0.0.0 mean ? There is no gateway ?
Or is there relation between 0.0.0.0 gateway and 0.0.0.0 destination ? (in sence all packets to 10.0.0.0 network go via 0.0.0.0 gw so the destination is also 0.0.0.0)
many thanks
M.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-10-2004 05:52 PM
11-10-2004 05:52 PM
Re: routing basic explanation
"Destination 0.0.0.0" line speaks about default gateway - it means, all destinations which doesn't covered by other rules.
and "gateway 0.0.0.0" means - this box has "direct connection" to this network - in other words, there is ethX in such network.
and "gateway 0.0.0.0" means - this box has "direct connection" to this network - in other words, there is ethX in such network.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-11-2004 06:42 AM
11-11-2004 06:42 AM
Re: routing basic explanation
thanksand default GW is a router with interface to my network that handle all packets going through ?does it follow that all packets which are not going through default gw are packets to my network and are handled via ARP many thanks M.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-11-2004 09:38 AM
11-11-2004 09:38 AM
Re: routing basic explanation
Ok, a bit of a network/netmask lesson.
The 'destination' is supposed to be the stub of a network address of which to match against the destination address of IP packets that pass through the routing table.
Using the bit-mask of the 'genmask' value, it takes a given path if there is a match.
0.0.0.0/0.0.0.0 works as a default route for the simple reason that *ALL* destination addresses match it.
As packets filter through from the top of the routing table, as they match they get sent down different paths. If all other routes didn't match, the default is taken.
So using your routing table lets set up an example:
Destination address: 192.168.1.32
Packet hits the first route. 10.0.0.0/255.255.255.0. This is not a match.
Packet hits the second route. 192.168.1.0/255.255.255.0. This is a match (the first 3 bytes fully match). The routing table says to send it via the interface 'eth1' (as there is no gateway, it just sends it to the wire). At this point, ARP tables etc. are used.
Packet never hits third route.
Destination address: 10.3.1.9
Packet hits first route. As the genmask is '255.255.255.0', the first 3 bytes have to match. Packet does not match this rule.
Packet hits second route. Doesn't match.
Packet hits thrid route. As this is the default route, it forwards the packet to the machine '10.0.0.5' via eth0.
This making sense? :)
The 'destination' is supposed to be the stub of a network address of which to match against the destination address of IP packets that pass through the routing table.
Using the bit-mask of the 'genmask' value, it takes a given path if there is a match.
0.0.0.0/0.0.0.0 works as a default route for the simple reason that *ALL* destination addresses match it.
As packets filter through from the top of the routing table, as they match they get sent down different paths. If all other routes didn't match, the default is taken.
So using your routing table lets set up an example:
Destination address: 192.168.1.32
Packet hits the first route. 10.0.0.0/255.255.255.0. This is not a match.
Packet hits the second route. 192.168.1.0/255.255.255.0. This is a match (the first 3 bytes fully match). The routing table says to send it via the interface 'eth1' (as there is no gateway, it just sends it to the wire). At this point, ARP tables etc. are used.
Packet never hits third route.
Destination address: 10.3.1.9
Packet hits first route. As the genmask is '255.255.255.0', the first 3 bytes have to match. Packet does not match this rule.
Packet hits second route. Doesn't match.
Packet hits thrid route. As this is the default route, it forwards the packet to the machine '10.0.0.5' via eth0.
This making sense? :)
One long-haired git at your service...
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
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP