andersonrobot · December 27, 2024 10:11 · Sep 24, 2023 · Sep 24, 2023 · Sep 24, 2023 · Sep 24, 2023
diff --git a/.ospf-mesh-net.md b/.ospf-mesh-net.md
@@ -1,6 +1,6 @@
 ## Enable OSPF Routing on Thunderbolt Mesh 
 # This has been deprectaed
-It is now superceded by **Openfabric Routing** [see here](/4c664734535da122f4ab2951b22b2085)
+It is now superceded by **Openfabric Routing** [see here](/4c664734535da122f4ab2951b22b2085) 
 
 ### continue at your own peril, for reference only now.
 

diff --git a/.ospf-mesh-net.md b/.ospf-mesh-net.md
@@ -1,9 +1,10 @@
-# Enable OSPF Routing on Thunderbolt Mesh 
-## This has been deprectaed
+## Enable OSPF Routing on Thunderbolt Mesh 
+# This has been deprectaed
 It is now superceded by **Openfabric Routing** [see here](/4c664734535da122f4ab2951b22b2085)
 
 ### continue at your own peril, for reference only now.
 
+## Old Gist
 This will result in an IPv4 routable mesh network that can survive any one node failure or any one cable failure.
 All the steps in this section *must be performed on each node*
 

diff --git a/.ospf-mesh-net.md b/.ospf-mesh-net.md
@@ -1,9 +1,11 @@
 # Enable OSPF Routing on Thunderbolt Mesh 
 ## This has been deprectaed
-[is now superceded by](/4c664734535da122f4ab2951b22b2085)
+It is now superceded by **Openfabric Routing** [see here](/4c664734535da122f4ab2951b22b2085)
+
+### continue at your own peril, for reference only now.
 
 This will result in an IPv4 routable mesh network that can survive any one node failure or any one cable failure.
-Alls the steps in this section *must be performed on each node*
+All the steps in this section *must be performed on each node*
 
 Please note the main section of this gist describes IPv4 on mesh. Lower down you will find additonal files that cpatures:
 1. differences if you want dual stack IPv4 / IPv6 routing (this is now what i run since writing the original gist)

diff --git a/.ospf-mesh-net.md b/.ospf-mesh-net.md
@@ -1,4 +1,7 @@
 # Enable OSPF Routing on Thunderbolt Mesh 
+## This has been deprectaed
+[is now superceded by](/4c664734535da122f4ab2951b22b2085)
+
 This will result in an IPv4 routable mesh network that can survive any one node failure or any one cable failure.
 Alls the steps in this section *must be performed on each node*
 

diff --git a/dual-stack-ospf.md b/dual-stack-ospf.md
@@ -18,7 +18,7 @@ iface lo:6 inet static
 ## Enable IPv4 and IPv6 forwarding
 1. use `nano /etc/sysctl.conf` to open the file
 2. uncomment `#net.ipv6.conf.all.forwarding=1` (remove the # symbol)
-3. uncomment `#3net.ipv4.ip_forward=1` (remove the # symbol)
+3. uncomment `#net.ipv4.ip_forward=1` (remove the # symbol)
 4. save the file
 
 ## FRR Setup

diff --git a/.ospf-mesh-net.md b/.ospf-mesh-net.md
@@ -6,7 +6,7 @@ Please note the main section of this gist describes IPv4 on mesh. Lower down you
 1. differences if you want dual stack IPv4 / IPv6 routing (this is now what i run since writing the original gist)
 2. opernfabric instead of OSPF (to do)
 
-[this gist is part of this series](scyto/76e94832927a89d977ea989da157e9dc)
+[this gist is part of this series](/76e94832927a89d977ea989da157e9dc)
 
 ## Key Parameters
 Key Information Used

diff --git a/.ospf-mesh-net.md b/.ospf-mesh-net.md
@@ -12,6 +12,10 @@ Please note the main section of this gist describes IPv4 on mesh. Lower down you
 Key Information Used
 Note i used the 10.x IPv4 space as this is not used anywhere else on my network YMMV
 
+lo = loopback
+en05/06 - these are the thunderbolt ports
+
+
 **Node l:**
 - lo:0 = 10.0.0.81/32
 - en05 = 10.0.0.5/30

diff --git a/.ospf-mesh-net.md b/.ospf-mesh-net.md
@@ -1,9 +1,9 @@
-# Enable IPv4 OSPF Routing on Thunderbolt Mesh 
-This will result in a routable mesh network that can survive any one node failure or any one cable failure.
+# Enable OSPF Routing on Thunderbolt Mesh 
+This will result in an IPv4 routable mesh network that can survive any one node failure or any one cable failure.
 Alls the steps in this section *must be performed on each node*
 
-Please note the main section of this gist descrives IPv4 on mesh. Lower down you will find additonal files that cpatures:
-1. differences if you want dual stack IPv4 / IPv6 routing
+Please note the main section of this gist describes IPv4 on mesh. Lower down you will find additonal files that cpatures:
+1. differences if you want dual stack IPv4 / IPv6 routing (this is now what i run since writing the original gist)
 2. opernfabric instead of OSPF (to do)
 
 [this gist is part of this series](scyto/76e94832927a89d977ea989da157e9dc)

diff --git a/dual-stack-ospf.md b/dual-stack-ospf.md
@@ -1,5 +1,7 @@
 This supplement is if you want dual stack IPv4 abd IPv6
 
+Note id you are doing CEPH it should be either IPv4 or IPv6 for all the monitors, MDS and daemons - do not try and dual stack it, depite the docs implying it is ok my findsing on quincy are is it is funky....  so stick yp IPv4 or IPv6 - it is possible to switch ceph back and forth - but be very careful.... it will be scary (tl;dr pick one)
+
 ## Create an IPv6 loopback
 In /etc/network/intefaces you will want an IPv6 loopback for IPv6 seperate from IPv4.
 My best pactice is to use the same number in the last hextet as the last octet from IPv4 - makes things easy to remember)

diff --git a/dual-stack-ospf.md b/dual-stack-ospf.md
@@ -13,11 +13,13 @@ iface lo:6 inet static
 
 ...
 ````
-## Enable IPv6 forwarding
-Using IPv4 to take advantage of not needing to use addresses - does make things simpler 
--  uncomment `#net.ipv6.ip_forward=1` using `nano /etc/sysctl.conf` (remove the # symbol and save the file)
-
+## Enable IPv4 and IPv6 forwarding
+1. use `nano /etc/sysctl.conf` to open the file
+2. uncomment `#net.ipv6.conf.all.forwarding=1` (remove the # symbol)
+3. uncomment `#3net.ipv4.ip_forward=1` (remove the # symbol)
+4. save the file
 
+## FRR Setup
 This is the content for FRR - rememvber to increment the router-ids on each node you use this on where you see X
 
 edit the frr daemons file to change `ospf6d=no` to `ospf6d=yes` and  `ospfd=no` to `ospfd=yes`

diff --git a/dual-stack-ospf.md b/dual-stack-ospf.md
@@ -1,5 +1,6 @@
 This supplement is if you want dual stack IPv4 abd IPv6
 
+## Create an IPv6 loopback
 In /etc/network/intefaces you will want an IPv6 loopback for IPv6 seperate from IPv4.
 My best pactice is to use the same number in the last hextet as the last octet from IPv4 - makes things easy to remember)
 
@@ -12,10 +13,17 @@ iface lo:6 inet static
 
 ...
 ````
+## Enable IPv6 forwarding
+Using IPv4 to take advantage of not needing to use addresses - does make things simpler 
+-  uncomment `#net.ipv6.ip_forward=1` using `nano /etc/sysctl.conf` (remove the # symbol and save the file)
 
 
 This is the content for FRR - rememvber to increment the router-ids on each node you use this on where you see X
 
+edit the frr daemons file to change `ospf6d=no` to `ospf6d=yes` and  `ospfd=no` to `ospfd=yes`
+
+This is the config to issue in vtysh - note if you are moving from a pure IPv4 configu youy might want to stop the serice and delete the frr config file before doing this to reset the config. 
+
 ```
 ip forwarding
 ipv6 forwarding

diff --git a/dual-stack-ospf.md b/dual-stack-ospf.md
@@ -51,3 +51,4 @@ interface en06
  exit
 !
 ```
+to do: speed up faiover by plaing with deadtime, hello time etc.
diff --git a/dual-stack-ospf.md b/dual-stack-ospf.md
@@ -1,5 +1,19 @@
 This supplement is if you want dual stack IPv4 abd IPv6
 
+In /etc/network/intefaces you will want an IPv6 loopback for IPv6 seperate from IPv4.
+My best pactice is to use the same number in the last hextet as the last octet from IPv4 - makes things easy to remember)
+
+so PVE1 would look like this, increment the last digit of the IP for each subsequent node.
+```
+...
+auto lo:6
+iface lo:6 inet static
+        address fc00::81/128
+
+...
+````
+
+
 This is the content for FRR - rememvber to increment the router-ids on each node you use this on where you see X
 
 ```

diff --git a/ospf-mesh-net.md → .ospf-mesh-net.md b/ospf-mesh-net.md → .ospf-mesh-net.md
diff --git a/_dual-stack-ospf.md → dual-stack-ospf.md b/_dual-stack-ospf.md → dual-stack-ospf.md
diff --git a/.dual-stack-ospf.md → _dual-stack-ospf.md b/.dual-stack-ospf.md → _dual-stack-ospf.md
diff --git a/dual-stack-ospf.md → .dual-stack-ospf.md b/dual-stack-ospf.md → .dual-stack-ospf.md
diff --git a/dual-stack-ospf.md b/dual-stack-ospf.md
@@ -0,0 +1,39 @@
+This supplement is if you want dual stack IPv4 abd IPv6
+
+This is the content for FRR - rememvber to increment the router-ids on each node you use this on where you see X
+
+```
+ip forwarding
+ipv6 forwarding
+!
+router ospf
+ ospf router-id 0.0.0.X
+ log-adjacency-changes
+ exit
+!
+router ospf6
+ ospf6 router-id 0.0.0.1
+ log-adjacency-changes
+ timers throttle spf 100 200 5000
+ exit
+!
+interface lo
+ ip ospf area 0
+ ipv6 ospf6 area 0
+ exit
+!
+interface en05
+ ip ospf area 0
+ ip ospf network broadcast
+ ipv6 ospf6 area 0
+ ipv6 ospf6 network broadcast
+ exit
+!
+interface en06
+ ip ospf area 0
+ ip ospf network broadcast
+ ipv6 ospf6 area 0
+ ipv6 ospf6 network broadcast
+ exit
+!
+```
diff --git a/ospf-mesh-net.md b/ospf-mesh-net.md
@@ -2,6 +2,10 @@
 This will result in a routable mesh network that can survive any one node failure or any one cable failure.
 Alls the steps in this section *must be performed on each node*
 
+Please note the main section of this gist descrives IPv4 on mesh. Lower down you will find additonal files that cpatures:
+1. differences if you want dual stack IPv4 / IPv6 routing
+2. opernfabric instead of OSPF (to do)
+
 [this gist is part of this series](scyto/76e94832927a89d977ea989da157e9dc)
 
 ## Key Parameters

diff --git a/ospf-mesh-net.md b/ospf-mesh-net.md
@@ -2,7 +2,7 @@
 This will result in a routable mesh network that can survive any one node failure or any one cable failure.
 Alls the steps in this section *must be performed on each node*
 
-[this is part of this series](scyto/76e94832927a89d977ea989da157e9dc)
+[this gist is part of this series](scyto/76e94832927a89d977ea989da157e9dc)
 
 ## Key Parameters
 Key Information Used

diff --git a/ospf-mesh-net.md b/ospf-mesh-net.md
@@ -2,6 +2,8 @@
 This will result in a routable mesh network that can survive any one node failure or any one cable failure.
 Alls the steps in this section *must be performed on each node*
 
+[this is part of this series](scyto/76e94832927a89d977ea989da157e9dc)
+
 ## Key Parameters
 Key Information Used
 Note i used the 10.x IPv4 space as this is not used anywhere else on my network YMMV

diff --git a/ospf-mesh-net.md b/ospf-mesh-net.md
@@ -87,12 +87,12 @@ interface lo
 !
 interface en05
  ip ospf area 0
- ip ospf network point-to-multipoint
+ ip ospf network broadcast
  exit
 !
 interface en06
  ip ospf area 0
- ip ospf network point-to-multipoint
+ ip ospf network broadcast
  exit
 !
 

diff --git a/ospf-mesh-net.md b/ospf-mesh-net.md
@@ -4,7 +4,7 @@ Alls the steps in this section *must be performed on each node*
 
 ## Key Parameters
 Key Information Used
-Note my IPv6 addresses ad redacted using x for the network portion. I used addresses from my actual IPv6 range. You will need to determine the IP addresses for your environement. The NET bellow can be reused with no modification
+Note i used the 10.x IPv4 space as this is not used anywhere else on my network YMMV
 
 **Node l:**
 - lo:0 = 10.0.0.81/32

diff --git a/ospf-mesh-net.md b/ospf-mesh-net.md
@@ -135,16 +135,27 @@ C>* 10.0.0.81/32 is directly connected, lo, 12:15:09
 O>* 10.0.0.82/32 [110/10] via 10.0.0.10, en06, weight 1, 00:53:41
 O>* 10.0.0.83/32 [110/10] via 10.0.0.6, en05, weight 1, 00:53:11
 C>* 192.168.1.0/24 is directly connected, vmbr0, 12:15:06
-
 ```
-Check networking with `lldpctl` you should see something like this, where you will see the two other nodes (note you may also see other devices on your network that are over the 2.5gbe proxmox management interface).
-
+and lastly `ip route`
 ```
-I HAVE NO VALID EXAMPLE AT THIS POINT AS OSPF NOT WORKING
--------------------------------------------------------------------------------
+root@pve1:~# ip route
+default via 192.168.1.1 dev vmbr0 proto kernel onlink 
+10.0.0.4/30 dev en05 proto kernel scope link src 10.0.0.5 
+10.0.0.8/30 dev en06 proto kernel scope link src 10.0.0.9 
+10.0.0.12/30 nhid 53 proto ospf metric 20 
+        nexthop via 10.0.0.6 dev en05 weight 1 
+        nexthop via 10.0.0.10 dev en06 weight 1 
+10.0.0.82 nhid 54 via 10.0.0.10 dev en06 proto ospf metric 20 
+10.0.0.83 nhid 33 via 10.0.0.6 dev en05 proto ospf metric 20 
+192.168.1.0/24 dev vmbr0 proto kernel scope link src 192.168.1.81 
 ```
 
-You can now test the network by pinging FC00:: addresses of the other nodes (don't ping the node your on, and by pulling cables and seeing if it works).  Note routing changes can take 15s to take effect, I am not sure how to speed up that detection - but it will be an FRR conf setting or config setting I assume.  This is for future research task.
+##Testing Example
+You can now test the network by pinging the IPv4 loopback addresses of the other nodes.  For example ping (using my IPs defined earlier):
+- `ping 10.0.0.81`
+- `ping 10.0.0.82`
+- `ping 10.0.0.83`
+
+Now pull one of the TB cables and repeat the test.
 
-## Testing Example
-<to be written>
+You should still be able to ping all nodes!!
diff --git a/ospf-mesh-net.md b/ospf-mesh-net.md
@@ -102,21 +102,41 @@ interface en06
 7. save the configu with `write memory`
 8. show the configure applied correctly with `show running-config` - note the order of the items will be different to how you entered them and thats ok.  (If you made a mistake i found the easiest way was to edt `/etc/frr/frr.conf` - but be careful if you do that.)
 9. use the command `exit` to leave setup
-10. rpeat steps 1 to 10 on the other 3 nodes
+10. repeat steps 1 to 9 on the other 3 nodes
 11. once you have configured all 3 nodes issue the command `vtysh -c "show ip ospf neighbor"` you will see:
 ```
-pve2# show ipv ospf neighbor
-Neighbor ID     Pri    DeadTime    State/IfState         Duration I/F[State]
+root@pve1:~# vtysh -c "show ip ospf neighbor"
+
+Neighbor ID     Pri State           Up Time         Dead Time Address         Interface                        RXmtL RqstL DBsmL
+0.0.0.2           1 Full/DROther    52m26s            33.951s 10.0.0.10       en06:10.0.0.9                        0     0     0
+0.0.0.3           1 Full/DROther    51m56s            33.444s 10.0.0.6        en05:10.0.0.5                        0     0     0
 
 ```
-10. now issue the command `show ip route` and you will see:
+10. now issue the command `vtysh -c "show ip route"` and you will see:
 ```
-pve2# show ip route
-<I GET ONLY NORMAL ROUTES - NO OSPF BASED ONES >
+root@pve1:~# vtysh -c "show ip route"
+Codes: K - kernel route, C - connected, S - static, R - RIP,
+       O - OSPF, I - IS-IS, B - BGP, E - EIGRP, N - NHRP,
+       T - Table, v - VNC, V - VNC-Direct, A - Babel, F - PBR,
+       f - OpenFabric,
+       > - selected route, * - FIB route, q - queued, r - rejected, b - backup
+       t - trapped, o - offload failure
+
+C>* 10.0.0.4/30 is directly connected, en05, 00:53:16
+O>* 10.0.0.5/32 [110/0] is directly connected, en05, weight 1, 00:53:16
+O   10.0.0.6/32 [110/10] via 10.0.0.6, en05 inactive, weight 1, 00:53:11
+C>* 10.0.0.8/30 is directly connected, en06, 00:53:46
+O>* 10.0.0.9/32 [110/0] is directly connected, en06, weight 1, 00:53:46
+O   10.0.0.10/32 [110/10] via 10.0.0.10, en06 inactive, weight 1, 00:53:41
+O>* 10.0.0.13/32 [110/10] via 10.0.0.10, en06, weight 1, 00:53:32
+O>* 10.0.0.14/32 [110/10] via 10.0.0.6, en05, weight 1, 00:53:11
+O   10.0.0.81/32 [110/0] is directly connected, lo, weight 1, 12:15:09
+C>* 10.0.0.81/32 is directly connected, lo, 12:15:09
+O>* 10.0.0.82/32 [110/10] via 10.0.0.10, en06, weight 1, 00:53:41
+O>* 10.0.0.83/32 [110/10] via 10.0.0.6, en05, weight 1, 00:53:11
+C>* 192.168.1.0/24 is directly connected, vmbr0, 12:15:06
 
 ```
-10. Exit the shell with `Exit`
-
 Check networking with `lldpctl` you should see something like this, where you will see the two other nodes (note you may also see other devices on your network that are over the 2.5gbe proxmox management interface).
 
 ```

diff --git a/ospf-mesh-net.md b/ospf-mesh-net.md
@@ -19,7 +19,7 @@ Note my IPv6 addresses ad redacted using x for the network portion. I used addre
 - ospf router-id = 0.0.0.2
 
 **Node 3:**
-- lo:0 = 10.0.0.82/32
+- lo:0 = 10.0.0.83/32
 - en05 = 10.0.0.14/30
 - en06 = 10.0.0.6/30
 - ospf router-id = 0.0.0.3

diff --git a/ospf-mesh-net.md b/ospf-mesh-net.md
@@ -14,14 +14,14 @@ Note my IPv6 addresses ad redacted using x for the network portion. I used addre
 
 **Node 2:**
 - lo:0 = 10.0.0.82/32
-- en05 = 10.0.0.13/30
-- en06 = 10.0.0.17/30
+- en05 = 10.0.0.10/30
+- en06 = 10.0.0.13/30
 - ospf router-id = 0.0.0.2
- 
+
 **Node 3:**
-- lo:0 = 10.0.0.83/32
-- en05 = 10.0.0.21/30
-- en06 = 10.0.0.25/30
+- lo:0 = 10.0.0.82/32
+- en05 = 10.0.0.14/30
+- en06 = 10.0.0.6/30
 - ospf router-id = 0.0.0.3
 
 ## Enable IPv4 forwarding
@@ -32,7 +32,7 @@ Using IPv4 to take advantage of not needing to use addresses - does make things
 doing this means we don't have to give each thunderbolt a manual IPv6 addrees and that these addresses stay constant no matter what
 Add the following to each node using `nano /etc/network/interfaces`
 
-This should go uder the `auto lo` section and for each node the X should be 1, 2 or 3 depending on the node 
+This should go uder the `auto lo` section and for each node the X should be 1, 2 or depending on the node 
 
 ```
 auto lo:0
@@ -87,12 +87,12 @@ interface lo
 !
 interface en05
  ip ospf area 0
- ip ospf network point-to-point
+ ip ospf network point-to-multipoint
  exit
 !
 interface en06
  ip ospf area 0
- ip ospf network point-to-point
+ ip ospf network point-to-multipoint
  exit
 !
 
@@ -103,11 +103,7 @@ interface en06
 8. show the configure applied correctly with `show running-config` - note the order of the items will be different to how you entered them and thats ok.  (If you made a mistake i found the easiest way was to edt `/etc/frr/frr.conf` - but be careful if you do that.)
 9. use the command `exit` to leave setup
 10. rpeat steps 1 to 10 on the other 3 nodes
-
-
-### I HAVE NEVER GOT THIS WORKING BELOW THIS POINT - NOT SURE WHY
-
-12. once you have configured all 3 nodes issue the command `show ip ospf neighbor` you will see:
+11. once you have configured all 3 nodes issue the command `vtysh -c "show ip ospf neighbor"` you will see:
 ```
 pve2# show ipv ospf neighbor
 Neighbor ID     Pri    DeadTime    State/IfState         Duration I/F[State]

diff --git a/ospf-mesh-net.md b/ospf-mesh-net.md
@@ -32,7 +32,7 @@ Using IPv4 to take advantage of not needing to use addresses - does make things
 doing this means we don't have to give each thunderbolt a manual IPv6 addrees and that these addresses stay constant no matter what
 Add the following to each node using `nano /etc/network/interfaces`
 
-This should go uder the `auto lo` section and for each node the X should be 1, 2 or depending on the node 
+This should go uder the `auto lo` section and for each node the X should be 1, 2 or 3 depending on the node 
 
 ```
 auto lo:0

diff --git a/ospf-mesh-net.md b/ospf-mesh-net.md
@@ -17,9 +17,9 @@ Note my IPv6 addresses ad redacted using x for the network portion. I used addre
 - en05 = 10.0.0.13/30
 - en06 = 10.0.0.17/30
 - ospf router-id = 0.0.0.2
-
+ 
 **Node 3:**
-- lo:0 = 10.0.0.82/32
+- lo:0 = 10.0.0.83/32
 - en05 = 10.0.0.21/30
 - en06 = 10.0.0.25/30
 - ospf router-id = 0.0.0.3

diff --git a/ospf-mesh-net.md b/ospf-mesh-net.md
@@ -124,45 +124,7 @@ pve2# show ip route
 Check networking with `lldpctl` you should see something like this, where you will see the two other nodes (note you may also see other devices on your network that are over the 2.5gbe proxmox management interface).
 
 ```
-root@pve1:~# lldpctl
--------------------------------------------------------------------------------
-LLDP neighbors:
--------------------------------------------------------------------------------
-Interface:    en05, via: LLDP, RID: 1, Time: 0 day, 12:32:30
-  Chassis:     
-    ChassisID:    mac 48:21:0b:56:a5:d8
-    SysName:      pve2.mydomain.com
-    SysDescr:     Debian GNU/Linux 12 (bookworm) Linux 6.2.16-6-pve #1 SMP PREEMPT_DYNAMIC PMX 6.2.16-7 (2023-08-01T11:23Z) x86_64
-    MgmtIP:       192.168.1.82
-    MgmtIface:    4
-    MgmtIP:       fc00::2
-    MgmtIface:    1
-    Capability:   Bridge, on
-    Capability:   Router, on
-    Capability:   Wlan, on
-    Capability:   Station, off
-  Port:        
-    PortID:       mac 02:99:94:7c:11:48
-    PortDescr:    en06
-    TTL:          120
--------------------------------------------------------------------------------
-Interface:    en06, via: LLDP, RID: 3, Time: 0 day, 12:31:58
-  Chassis:     
-    ChassisID:    mac 48:21:0b:58:9c:45
-    SysName:      pve3.mydomain.com
-    SysDescr:     Debian GNU/Linux 12 (bookworm) Linux 6.2.16-6-pve #1 SMP PREEMPT_DYNAMIC PMX 6.2.16-7 (2023-08-01T11:23Z) x86_64
-    MgmtIP:       192.168.1.83
-    MgmtIface:    4
-    MgmtIP:       fc00::3
-    MgmtIface:    1
-    Capability:   Bridge, on
-    Capability:   Router, on
-    Capability:   Wlan, on
-    Capability:   Station, off
-  Port:        
-    PortID:       mac 02:32:15:c8:5d:d4
-    PortDescr:    en05
-    TTL:          120
+I HAVE NO VALID EXAMPLE AT THIS POINT AS OSPF NOT WORKING
 -------------------------------------------------------------------------------
 ```
 

diff --git a/ospf-mesh-net.md b/ospf-mesh-net.md
@@ -77,7 +77,7 @@ Note: the X should be the number of the node you are working on, so for my stetu
 ip forwarding
 !
 router ospf
- ospf router-id 0.0.0.3
+ ospf router-id 0.0.0.X
  log-adjacency-changes
  exit
 !
No results found