Unable to access any of the ctwug.za.net sites from withing the Wug network but am able to access it from the ‘outside’ world.
Tracert results to wind.ctwug.za.net from within the CTwug network ends on centrifuge.ctwug.za.net (172.18.1.11).
Audi still works though.
As far as I know, that is the correct IP for centrifuge, you can check the status’ of all services here: https://status.ctwug.za.net/
Thanks @JellyBean, everything seems to be fine again now so not sure what happened.
1 Like
I experimented with something. Wanted to do it on the WUG as I wanted to be sure it works and I didn’t think anyone would notice. Currently tunnels to services are openvpn tunnels. We have tunnels from wug side to centrifuge and tunnels from other services to centrifuge. Actually a mess to set up and lots of inefficiencies.
I experimented with replacing it with tinc. Prettly nifty little VPN app. Basically you tell it about a few hosts and make it connect to one or two of them. And you tell it witch network this is supposed represent. It will then start figuring out stuff and making shortcuts.
I did a network where I had a wug side server (say A) connecting to C (centrifuge) and I had a another service obliquity (call it B) connecting to C. The software so once A-C connected and B-C connected the software automatically figures out that all three are on the same network and makes a connection between A-B as well.
I ran it in switch mode so effectively to the host OS it appears if it’s on a switch with all the other devices. Then I tested if OSPF ran over it. It also automatically tries to make sure that A/B/C have ports available and figures out how to get through firewalls.
It took a bit longer than I expected but it worked reasonably well. So I’d be switching at some point.
2 Likes
always working hard to improve things! Thanks @spin
2 Likes