Categories
Cat 8 Leviton system
Category: Uncategorized
Categories
The new age of case studies
After the recent filing of Ubiquiti vs Cambium, Winncom, and BLIP networks the question of case studies has come up. One of the pieces of complaints is a case study Blip Networks did on Cambium Elevate.
What changes do you think will be forthcoming in future case studies? Should end users who do the case study require more terms from the manufacturer they are doing the case study to protect themselves? Are we going to see actual legal documents for any case studies to be done? Or are companies just not going to want to do case studies for fear of opening themselves up for retaliation?
I am interested to know your thoughts.
The following are results from a series of tests of AGLcom’s parabolic dish antennas on an existing link that is 5.7 miles long. The link typically passes 80-90Mbs with a TX capacity of 140 Mbs and radios used are Ubiquiti AF5X operating at 5218 Mhz. A full PDF with better Readability can be downloaded here..
The tests were taken in stages:
- 1) The normal performance of the link was recorded.
- 2) The 2′ dish at one end, B, was replaced with the AGLcom, C, dish and the link reestablished.The link performance was recorded.
- 3) The 2′ dish at the other end, A, was replaced with the AGLcom, D, dish and the link reestablished. The link performance was recorded.
- 4) The setting on the AF5xs were adjusted to optimize the link performance with data recorded.
- 5) The 2′ dish, B was put back in the link and the performance was recorded.
- 6) The ACLcom C was put back into place.
The tables below do not follow the test order as the third line of data was actually the last test performed.
Antennas:
A-Jirous JRC-29EX MIMO
B-Jirous JRC-29EX MIMO C-AGLcom – PS-6100-30-06-DP D-AGLcom – PS-6100-29-06-DP-UHP
Results:
Table 1 is the signal strength results of the various dishes on the link. The first line, A-B, is the original Jirous to Jirous. A is the first two columns of the link and are the A side and the last two columns are the B side on the link. What is of interest is that exchanging B to C in the second line brought the signal deviation between the channels to only 1db and 0 db as seen in Table 2. The third line was a result of replacing the horn on the A dish and optimizing the setting on the AF5X radios. This changed the signal by around 7db and improved the link capacity, Table 3. Clearly, the A dish had a problem with the original horn.
In the fourth line, D-B, the signal strength improved as well at the signal deviation on the two channels, Table 2 first two columns. This link was not optimized. The fifth line, D-C is both AGLcom dishes which improved the bandwidth, Table 3, and the signal deviations, Table 2. The final line, D-C, was the previous line optimized. The signal strengths moved closer together and the bandwidth improved.
Link Ch0 Ch1 Ch0 Ch1
- A-B -73 -76
- A-C -73 -74
A*-C -64 -66
- D-B -63 -62
- D-C -62 -62
D*-C -60 -60
-70 -74 -71 -71 -65 -66 -59 -59 -58 -58 -61 -61
Signal Strength (* optimized data) Table 1
Table 2 has four data columns, the first two being the measured results and the latter two being the measured difference from theory. The Jirous and AF5X calculators were used for the theory signals. Clearly the signal approached the theoritical limit with the optimization and with the change of dishes. The optimization improved the signal by ~9db for the link that we replaced the horn on the Jirous and by ~2db for the AGLcom link.
Link dSig dSig A-B 3 4 A-C 1 0 A*-C 2 1 D-B -1 0 D-C 0 0 D*-C 0 0
dSig dSig -16.5 -17.4 -17.0 -15.0 -8.0 -9.0 -13.3 -5.3 -7.0 -4.3 -5.0 -6.0
Signal strength variation from theory Table 2
The band width improvement was more obvious, Table 3, from 22 Mbs to 39 Mbs for the RX and 144 Mbs to 141 Mbs TX for the link with the horn replacement. The bandwidth improvement for the optimization of the AGLcom link was from 61Mbs to 66Mbs RX and from 211Mbs to 267Mbs for TX.
The bandwidth improvement from the original, optimized link to the AGLcom link is from 61Mbs RX to 67Mbs and from 210Mbs TX to 267Mbs. There is a clear improvement for the AGLcom link over the Jirous link.
Link BW-RX
- A-B 22.5
- A-C 39.0
A*-C 60.9
- D-B 61.4
- D-C 60.6
D*-C 66.6
BW-TX 144.6 141.4 210.0 211.0 215.0 267.6
Table 3
Conclusions:
The data supports a measurable improvement in both signal strength and bandwidth with the use of the AGLcom dishes. However, it is difficult to quantify the improvement. The Jirous dishes were identical whereas the AGLcom dishes were not. One of the jirous dishes was under performing initially but was repaired for the last tests. Additional testing is needed to provide accurate data analysis and performance comparison. The best performance tests would involve identical AGLcom dishes, ideally two links, one each of both types of dishes.
One of the things I see startup wisps do wrong is their use of phone numbers. This is one of those details that is often overlooked but is critical. It’s critical not only for tracking but also for the sanity of everyone involved. Let’s identify where many WISPs go wrong.
The typical startup wisp is a type A go-getter. This is what Entrepreneurs are by default. Once they have a plan they jump head over heels in. Many may start with a simple phone number, but when they call a customer if they are on their way to do an install or something they end up using their phone number. The problem is customers keep this cell phone. If the office is closed they start texting or calling any number they have. Some customers will be respectful of boundaries, but many will not. If they are getting packet loss at 3 am they are calling and texting. This problem compounds as you grow and you have multiple installers involved. You want customer issues tracked in some sort of ticket/CRM system. You also don’t want your employees ahev to answer customer texts or calls after hours if they aren’t being paid. It’s one of the quickest ways for employees to get burnt out or say the incorrect things.
So how do you solve this? The simple buzzword answer is unified communications. One of the easiest and cheapest is Google Voice. With Google Voice and others, you have a primary number. This is the number you give out to clients. They call this and it rings another phone or phones. This can be an extension on the VOIP system it is a part of, another number, and/or cell phones. Depending on the level of sophistication it can ring all the programmed numbers at once, or ring one, and move on to the next one. If no one answers it drops the caller into voice mail. With Google voice, the programmed numbers are all rang at once.
The inbound ringing is pretty standard. The “trick” for the WISP is the outgoing calling. You want to be able to call a customer and have it come up as the main number’s caller ID, not your cell phone. Most PBX systems can be set up to do this with the extensions attached to them. Cell phone calls are a little more complicated. The way Google Voice solves this is through the use of forwarding numbers, You bring up the app, enter a number and it actually calls a different number. Behind the scenes, it is using this forwarding number to “spoof” your number to the person you are calling. Your phone is not calling the other party directly. Your phone calls this forwarding number behind the scenes and works it all out on the backend.
Other vendors have Apps which do similar functions. Asterisk has their DISA function. Once you have these functions setup it boils down to training and processes. Your installers need to remember to use the app or the function when calling customers. As the company grows, a way to help this situation is for employees to not use personal cell phones. If a company provides a cell phone the employee can customize voicemail, or even forward no answers to the help desk should a customer get the cell phone.
Hope this helps one of the glaring issues a startup faces.
Recently I attended the Cambium Roadshow 2018. Some notes.
-Epmp 3000 expected to be here in September. 4×4 Mimo product. Early marketing should be coming in the next couple of weeks.
-820C pricing is getting aggressive.
-Mikrotik Open beta Elevate is out. Ability to elevate Mikrotik units.
Force 300
-second radio can be used as management access or a realtime spectrum analyzer
-No more java client for the analyzer
-65k packets per second
-About 10% throughput at the sector in a legacy network. Future software updates can lessen this.
-Dynamic spectrum capability
-Future vision is to have CNMaestro be aware of spectrum. This opens up the ability to view channels and interference on a network level.
450 Product Line
-Channel sizes have increased to 30 and 40mhz
-450b radios Integrated (17dBi for $299) and high gain (24dBi for $349)
-New processor
-4.9-5.925 GHZ
-Single gigabit port
-30 volt power supply, polarity Agnostic
-450 3.65 will be SaS compliant
cnArcher
-iPhone app should be here soon.
-Ability to push configs from the App
450M
-8×8 mimo due to physical size. 12×12 or 16×16 would mean a very large product
-Integrated 90 degree sector
-Direct DC power
-SFP port
-Current SMs will connect
MTIN Family of web-sites
www.mtin.net
www.j2sw.com
www.indycolo.net
www.startawisp.info
Categories
Winbox brute Force
You really should not have your winbox port open to anything but a management network, but if you need a script to help with brute force on the Mikrotik.
add action=drop chain=input comment="drop winbox brute forcers" dst-port=8291 \
protocol=tcp src-address-list=winbox_blacklist
add action=add-src-to-address-list address-list=winbox_blacklist \
address-list-timeout=1w3d chain=input connection-state=new dst-port=8291 \
protocol=tcp src-address-list=winbox_stage3
add action=add-src-to-address-list address-list=winbox_stage3 \
address-list-timeout=1m chain=input connection-state=new dst-port=8291 \
protocol=tcp src-address-list=winbox_stage2
add action=add-src-to-address-list address-list=winbox_stage2 \
address-list-timeout=1m chain=input connection-state=new dst-port=8291 \
protocol=tcp src-address-list=winbox_stage1
add action=add-src-to-address-list address-list=winbox_stage1 \
address-list-timeout=1m chain=input connection-state=new dst-port=8291 \
protocol=tcp
add action=drop chain=forward comment="drop WINBOX brute downstream" dst-port=8291 \
protocol=tcp src-address-list=winbox_blacklist
Of course changing your Winbox port number and disallowing access from anything but trusted Ip addresses is one of the best ways.
Categories
What is a BGP Confederation?
In network routing, BGP confederation is a method to use Border Gateway Protocol (BGP) to subdivide a single autonomous system (AS) into multiple internal sub-AS’s, yet still advertise as a single AS to external peers. This is done to reduce the number of entries in the iBGP routing table. If you are familiar with breaking OSPF domains up into areas, BGP confederations are not that much different, at least from a conceptual view.
And, much like OSPF areas, confederations were born when routers had less CPU and less ram than they do in today’s modern networks. MPLS has superseded the need for confederations in many cases. I have seen organizations, who have different policies and different admins break up their larger networks into confederations. This allows each group to go their own directions with routing policies and such.
if you want to read the RFC:https://tools.ietf.org/html/rfc5065
Categories
A little fun on a Friday
Dug this out of the archives. A little word search fun for a Friday.
Categories
Quanta LB4M
Do you have a Quanta Lb4M and are looking for software? Check out this site:
https://puck.nether.net/~jared/lb4m/
I will grab these files and if this site ever disappears will mirror them if anyone asks. Until then use the above link.
You must be logged in to post a comment.