For the people who are interested I have uploaded some pictures of the actual nodes used for the 5ghz links http://44.144.0.14/on7lr/ The route is as it shows in tracert: 7 5 ms 5 ms 5 ms wirelessantwerpen.antwerpdatacenter.be [46.18.35.226] 8 17 ms 11 ms 9 ms vl1351-1.keyser1-3-rb1200.wirelessbelgie.ampr.org [44.144.208.30] 9 12 ms 29 ms 10 ms e13-1.keyser-rb1100-boven.wirelessbelgie.ampr.org [44.144.208.34] 10 15 ms 15 ms 16 ms e1-1.merksem1-2.wirelessbelgie.ampr.org [44.144.208.101] 11 31 ms 11 ms 25 ms 44.144.10.45 AntwerpDC -> Keyser (biggest node in the network) -> Merksem (on0an) -> Lier (on7lr) 73s Robbie ON4SAX

Tom, We have the same problems at busy sites, though most of the links are on 40mhz channels and using 20mhz bandwith, so 10mhz on either side of "free" space or 20mhz between the signals. We have started experimenting with shields on nanobridges and nanodishes and see a speed increase from 10mbit to 30mbit. Havent looked into filters or cavities yet. On the very big sites we are starting to use 24ghz equipment like the airfiber, as you can see on the "keyser" picture. However, these are still very expensive and cut in the budget. We also see that on longer links (10km+) we are having issues with rainfade on 24ghz, where the link drops entirely when a decent rain passes, and then everything gets rerouted over 5ghz links with more hops which is also not optimal. There are also problems with ubnt equipment on hamsites, as they arent shielded properly by default and it interferes with HAM rf. We try to use mini-pci boards on the routerboards there, which are in a shielded copper box inside a watertight aluminium enclosure and then use 5ghz panels or grids. I'm sorry that the camsite got passworded, it seems there was a lot of load and the sysops decided to put a password on it. I was out of the country until today without access the any datanetwork so I didn't know until today. 73s Robbie ON4SAX