Script took 296 seconds to run.
Sent 45 emails in this run.
OSPF Routers: 641
Routers with issues: 116
Total issues: 268
Routers not linked to a node: 27
Script took 491 seconds to run.
Sent 9 emails in this run.
OSPF Routers: 645
Routers with issues: 116
Total issues: 253
Routers not linked to a node: 18
Great someone linked some routers to nodes.
A friend of mine has been disconnected since before the weekend already. Her node (butterflychick) connects to Mammon2. The radio itself is connected, but there is no throughput. Could this possibly be related to what is happening here?
This is nothing related to this.
I asked ButterflyChick to open a separate thread related to her connection issues, as that whole area seems to be down.
Stop hijacking popular threads 
EDIT: Use this thread, http://www.ctwug.za.net/showthread.php?5813-Koeiklap-13-254-down-replacing-rb-this-week&p=47641#post47641
Script took 155 seconds to run.
Sent 9 emails in this run.
OSPF Routers: 647
Routers with issues: 102
Total issues: 238
Routers not linked to a node: 9
Great improvement there. 100 to go.
Should already be 100 now. Added a new router last night, your script run before I was done with all the new configs.
Ran WMS script on:
172.18.7.60
172.18.7.62
172.18.89.14
So we should be at 100 or below 100.
I wonder if you can link a router to an admin and see who’s routers are not compliant?
Script took 138 seconds to run.
Sent 6 emails in this run.
OSPF Routers: 646
Routers with issues: 86
Total issues: 195
Routers not linked to a node: 6
1 Like
Yes you seem to have done it.
This is what this script does. It links routers to wind nodes and emails the node admins with the issues.
Script took 171 seconds to run.
Sent 35 emails in this run.
OSPF Routers: 644
Routers with issues: 84
Total issues: 197
Routers not linked to a node: 6
We are getting there! Thanks Spin for the time and effort 
, By the way do you have some kind of automated system which sends the mails for you or do you send it manually? I know it would probably take some time to send all of those mails.
All automated. See I posted this in wrong thread. Edit: Moved
Script took 71 seconds to run.
Sent 5 emails in this run.
OSPF Routers: 644
Routers with issues: 84
Total issues: 197
Routers not linked to a node: 6
Script took 65 seconds to run. (logging into 636 routers!!)
Sent 0 emails in this run.
OSPF Routers: 636
Routers with issues: 81
Total issues: 194
Routers not linked to a node: 6
We’ve come down lots, but the 1 Nov deadline is not far.
Is there a way to see what IP are still not compliant and/or what admin has been assigned to said range via the wiki page?
The following RBs have no wind entries at all. If someone can figure out exactly to who they belong and contact those people it would be great.
The rest of the rbs are being mailed via wind every couple of days so people must not want to keep their wug connections anymore. :rolleyes:
Even some of these below are receiving emails on nodes where a subnet range matches one of these ips. Some someone aught to have received an email on some of these.
172.18.16.14
172.18.22.125
172.18.26.253
172.18.26.254
172.18.89.75
172.18.226.254
172.18.240.250
172.18.252.38
172.18.252.218
172.18.16.14 - Kingpin
172.18.22.125 - WireIce
172.18.26.253 - Should be remove off of WUG as it doesnt even have a wiki asigned entry
172.18.26.254 - Should be remove off of WUG as it doesnt even have a wiki asigned entry
172.18.89.75 - JypelsOude - Skouperd
172.18.226.254 - KM (should really break this down more in the wiki)
172.18.240.250 - Stolla
172.18.252.38 - OSPF (cant find route to this ip. Still active?)
172.18.252.218 - OSPF (cant find route to this ip. Still active?)
Guess if the range is assigned to your name its your responsibility?
172.18.89.75 is in Skouperd’s range, but if you look at the body of the OSPF ID in the LSA DB, it shows:
flags=
link-type=Transit id=172.18.60.33 data=172.18.60.33 metric=10
link-type=Transit id=172.18.60.1 data=172.18.60.8 metric=1
172.18.60.33 is a network range out of Jypel’s /24, so we should probably have a look around there. However if you do a traceroute to it…it goes to link-moontop.jypels.ctwug.za.net. Probably where we should look for that one.
Edit: Actually all of those belong to the moontop rbs.
Edit2: Alright so 172.18.89.75 is on rb7.moontop, and should be changed to 172.18.59.8
The problem is, ctwug/ctwug works on it, but I can see radius is disabled. Someone will have to ask Moonfruit to fix.
172.18.16.14 updated to 172.18.110.14 on kingpin–oom-norman RB.