Labels

Android (1) bash (2) boost (2) C (34) C++ (2) cheatsheet (2) CLion (6) css (3) Debian (33) DL (17) Docker (2) Dreamweaver (2) Eclipse (3) fail2ban (4) git (5) GitHub (4) Hacking (3) html (8) http (1) iOS (1) iPad (1) IRC (1) Java (31) javascript (3) Linux (167) Mac (19) Machine Learning (1) mySQL (48) Netbeans (4) Networking (1) Nexus (1) OpenVMS (6) Oracle (1) Pandas (3) php (16) Postgresql (8) Python (9) raid (1) RedHat (14) Samba (2) Slackware (47) SQL (14) svn (1) tar (1) ThinkPad (1) Virtualbox (3) Visual Basic (1) Visual Studio (1) Windows (2)

Tuesday, 15 August 2023

Linux Routing Table

From route -n

 

Example;

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.29.42.103    0.0.0.0         255.255.255.255 UH    0      0        0     eth6
10.29.8.76        0.0.0.0         255.255.255.255 UH    0      0        0     eth6
10.28.10.0        0.0.0.0         255.255.255.0     U       0      0        0     eth6
192.168.8.0      0.0.0.0         255.255.254.0     U       0      0        0     eth7
23.128.16.0      0.0.0.0         255.255.240.0     U       0      0        0     eth7
 

The entries for 10.28.10.0 and 23.128.16.0 are applied automatically when, for example the following is added;  

iface eth7 inet static
address  23.128.28.20
netmask  255.255.240.0
network  23.128.16.0
#gateway  23.128.16.1

iface eth6 inet static
address 10.28.10.21
netmask 255.255.255.0
network 10.28.10.0
#gateway    10.28.10.1


Based on the above, we could read as;

Traffic destined for 10.29.42.103/32 (255.255.255.255) would be routed through the gateway 0.0.0.0 via the eth6 interface.

Traffic destined for 10.29.8.76/32 (255.255.255.255) would be routed through the gateway 0.0.0.0 via the eth6 interface.

Traffic destined for 10.28.10.0/24 (255.255.255.0) would be routed through the gateway 0.0.0.0 via the eth6 interface.

Traffic destined for 192.168.8.0/23 (255.255.254.0) would be routed through the gateway 0.0.0.0 via the eth7 interface.

Traffic destined for 23.128.16.0/20 (255.255.240.0) would be routed through the gateway 0.0.0.0 via the eth7 interface.

If there were 0.0.0.0 under the Destination column, this would indicate a Default Gateway.

I believe the below is more correct than the above for the 10.29.42.103

Destination     Gateway         Genmask             Flags Metric Ref    Use Iface
10.29.42.103    10.28.10.1    255.255.255.255 UH    0         0        0     eth6

which would read;

Traffic destined for 10.29.42.103/32 (255.255.255.255) would be routed through the gateway 10.28.10.1 via the eth6 interface. This could be achieved by ip route add 10.29.42.103/32 via 10.28.10.1 dev eth0

with the possibility of the below being more "normal";

Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.29.42.103    10.28.10.1    255.255.255.0 UH    0         0        0     eth6

which would read;

Traffic destined for 10.29.42.103/24 (255.255.255.0) would be routed through the gateway 10.28.10.1 via the eth6 interface. This could be achieved by ip route add 10.29.42.103/24 via 10.28.10.1 dev eth0
 

 

 

No comments:

Post a Comment

Note: only a member of this blog may post a comment.