AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
How to read netbalancer2/12/2023 ![]() Perhaps it helps to figure out what is wrong with failoverd. But I am working my day job for pretty long hours and I have volunteer work on weekends until late spring so anything more than a few minutes is too much time for me at the moment. It has been over a year since I looked at either the ZS scripts or the documentation on Linux iptables and routing, so I’ll have to get back up to speed. (Sorry about the weird display of the snippet from the diff, this bulletin board code does not seem to like a string of less than characters.) Iptables -t mangle -A NB_FO_PRE -p icmp -icmp-type echo-request -d $IPP -j MARK -set-mark 1$GW b14 is using a TOS indication on the ping packet whilst my patch classifies the ping using IP Tables… There are to merge conflicts in the file that look the same: The conflicting changes in failoverd have to do with the logic for issuing pings our of the desired interface. How many and what type of WAN interfaces do you have and have you noticed issues with either detecting a WAN failure or recovering from a failure? If you need help wit the patch let me know. I used the pre-patched files from a b13 installation and this seems to work If anyone using my patch has experience with that problem perhaps we can figure out what I did wrote: Too many other irons in the fire…īy the way, if I recall correctly, Fulvio’s hesitation on incorporating my patch into his code base was issues with falsely declaring an interface as failed. Unfortunately, I can’t say how long it will be before I can get time to look at this. ![]() But I will have to wrap my head around how the ip tables and rules work again before I can make my mind up about the conflicts in failoverd.Įnd result: I don’t think it is safe to apply the b12 QoS/Netbalancer patch to b14. The conflicts in fw_initrules are straight forward. My first cut at applying the changes in the kerbynet.cgi/scripts modified by the QoS/Netbalancer patch indicate two things:Ģ) There are merge conflicts in failoverd and fw_initrules Good news the current patch/fix can still be used. ![]() Quick update: from my initial testing it looks as though the QoS/Netbalancer patch/fix has NOT been included in this update. ![]()
0 Comments
Read More
Leave a Reply. |