As far as we are thinking about possible evolutions, we can also add new criteria. Ability to change link "weight" according to link quality (or other parameters) may be an intesring thing.
Well, as soon as something is changed in the protocol you lose the big advantage of running standard protocols available in standard firmware, see the AMPR RIP thing.
I don't know if BGP has some "weight" parameter. OSPF has. It can not change the weight dynamically, but it's possible to change that weight by an external script. That's nice, and that's the reason why we choose OSPF for our "internal" network.
I have considered doing similar things in BGP (adjusting prepend or local-pref dynamically based on SNMP monitoring of the link). We have not experimented with OSPF yet, I read in many places that it has problems with scaling when the CPU power on routers is limited (like on old RB750s)
Rob
Well, as soon as something is changed in the protocol you lose the big advantage of running standard protocols available in standard firmware, see the AMPR RIP thing.
Not changing the protocol, but finding the right protocol that can accomodate with link quality and weight.
I have considered doing similar things in BGP (adjusting prepend or local-pref dynamically based on SNMP monitoring of the link). We have not experimented with OSPF yet, I read in many places that it has problems with scaling when the CPU power on routers is limited (like on old RB750s)
I don't know Mikrotik. We are using OpenWRT, mostly on TP-Link or GL-Inet cheap routers. The border routers are Debian VMs, with potentially unlimited CPU. And my OSPF network does not have a size which can disturb a CPU, even on a $20 hardware :-)
This is an interesing purpose, anyway. Maybe it's better to keep two separate routing policies : - one protocol for external/internet, which should be BGP - another protocol for internal routing, which can be GBP, or something else But this only applies for networks build around a regional/local gateway. For a standalone endpoint (such as current IP-IP user), there's no distinction between "internal" and "external" routing, there's only one routing policy.
Then, the question becomes : - Is it better to keep full mesh / standalone endpoints (such as current IP-IP) ? But if so, how to handle Plug and Play and NAT traversal ? - Or is it better to have small local gateways managed by skilled teams, and end-users connecting to those gateways with simpler PnP VPN systems ?
We choosed the second option, with fully home-made design (OpenWRT, OpenVPN, OSPF), because it best suited our needs, and because we are an island, with few inter-connects with the rest of the world.
It seems lots of people in the world are using similar designs, with a central gateway and enpoints connecting to it via VPNs. Maybe we just have to share our experiences, and adopt some kind of "standardized" rules for our gateways ?
73 de TK1BI
On 21/07/19 19:46, Toussaint OTTAVI via 44Net wrote:
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
You (and some others) are sending blank messages to the list. Suggest you use plain text.
I saw that. Messages are readable on Android, but appears blank in Thunderbird. When we answer, the answer remains blank (but the text is readable in the message source)
Will check...
Envoyé depuis mon smartphone Samsung Galaxy.
Envoyé depuis mon smartphone Samsung Galaxy.
-------- Message d'origine -------- De : Tony Langdon via 44Net 44net@mailman.ampr.org Date : 21/07/2019 11:57 (GMT+01:00) À : 44net@mailman.ampr.org Cc : Tony Langdon vk3jed@vkradio.com Objet : Re: [44net] Time to restructure the network?
On 21/07/19 19:46, Toussaint OTTAVI via 44Net wrote:
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
You (and some others) are sending blank messages to the list. Suggest you use plain text.
-- 73 de Tony VK3JED/VK3IRL http://vkradio.com
Greetings Toussaint et al.
I'm seeing exactly the same, Android vs Thunderbird on W8.1
Best regards. Tom - SP2L
Le 21/07/2019 à 11:56, Tony Langdon via 44Net a écrit :
You (and some others) are sending blank messages to the list. Suggest you use plain text.
Funny, even your answer was blank text on Thunderbird. I had to get the text in the message source.
I switched my Thunderbird to plain text (I thought it was already set, but it was not).
Let's see if this text is readable. And sorry for the inconvenience.
On 21/07/19 21:31, Toussaint OTTAVI via 44Net wrote:
Le 21/07/2019 à 11:56, Tony Langdon via 44Net a écrit :
You (and some others) are sending blank messages to the list. Suggest you use plain text.
Funny, even your answer was blank text on Thunderbird. I had to get the text in the message source.
I switched my Thunderbird to plain text (I thought it was already set, but it was not).
Let's see if this text is readable. And sorry for the inconvenience.
Loud and clear now. :)
Actually, Tony, this appears to be a mailing list problem. The text they are sending is in an included subpart, but it's being presented in the wrong order by the relaying software. It's there, but you have to dig for it.
While I'm troubleshooting this and trying to adjust the mailman software to stop relaying almost-blank messages, if the posters will turn off their plain-and-html dual posting options and, as you say, use plaintext only, the messages will come through plainly. - Brian
On Sun, Jul 21, 2019 at 07:56:17PM +1000, Tony Langdon via 44Net wrote:
On 21/07/19 19:46, Toussaint OTTAVI via 44Net wrote:
You (and some others) are sending blank messages to the list. Suggest you use plain text.
-- 73 de Tony VK3JED/VK3IRL http://vkradio.com
-
Brian Kantor -
Rob Janssen -
SP2L -
Tony Langdon -
Toussaint OTTAVI