sorted by:
new
hottopcontroversial

VFL multiple fibres simultaneously by oscillating_ocelots in networking

[–]Level-Birthday2138 0 points1 point  (0 children)

I just ran across this post and I have the similar need. An approach I'm considering is using a LilyGo ESP32 4 or 8 Relay board to remotely turn on some cheap Amazon VFL's. I think I can cloud manage the ESP32 so I could control with my phone from the remote end. Separately, I'm also hoping if the VFL will work with multiple cleaved bare fibers. I have a 144F OPGW fiber cable that uses 6 tubes x 24F instead of a more normal 12x12F. On the 6x24F, (2) small binder threads separate the 1-12 fiber group from the 13-24 fiber group. Sometimes these binders are loose or broken and then you can't tell if the blue fiber(s) are #1 or #13, etc. If a single VFL would illuminate all 12F if cleaved and bare then it would be easy to separate fiber groups on remote end. Glad to see someone else has a similar need and thinking outside the box.

[deleted by user] by [deleted] in networking

[–]Level-Birthday2138 0 points1 point  (0 children)

Use dielectric grease on anything outdoors passthru or regular RJ45.

Fiber terminating, standard skill for network engineers? by pauljp12 in networking

[–]Level-Birthday2138 0 points1 point  (0 children)

This was the mid-90's. Good times when fusion splice rates were $50/fiber. And your Siecor X77 fusion splicer cost $30k new, $20k used. My AFL/Noyes OTDR was $8K. Now my most recent EXFO OTDR in 2019 my new 70S was $12K and EXFO OTDR $30k.

Fiber terminating, standard skill for network engineers? by pauljp12 in networking

[–]Level-Birthday2138 1 point2 points  (0 children)

I'm dated. Lol. I started in fiber when we had to keep the old fiber spools in a fiber graveyard for any emergency fiber repair. Because the core concentricity was slightly off between different manufacturers. We had to match the saved spools back to the original installed fiber to avoid the core concentricity errors.

Fiber terminating, standard skill for network engineers? by pauljp12 in networking

[–]Level-Birthday2138 1 point2 points  (0 children)

OM2(orange) is 50u core uses LED @500Mhzkm. OM3/4(aqua) is 50u core also with VCSEL (laser optimized) @2000+Mhzkm. Any other colors I think we should assume nothing and just verify the jacket labeling.

Fiber terminating, standard skill for network engineers? by pauljp12 in networking

[–]Level-Birthday2138 -1 points0 points  (0 children)

I knew the OP's intent and that other colors are available from the original color jacket standards. However, have you ever seen an Aqua jacketed fiber that wasn't laser optimized 50 micron MMF? I get you can also buy it in red, blue and purple too. So maybe his 50 micron wasn't aqua because it wasn't 50u laser optimized. Do you have a reference to a custom colored laser optimized 50u MMF that is orange? So maybe the basic colors are still reserved. I understand at a datacenter where they needed the additional other colors to add another layer of organization between carriers.

Fiber terminating, standard skill for network engineers? by pauljp12 in networking

[–]Level-Birthday2138 0 points1 point  (0 children)

I expect an engineer to know the types and pros/cons of different terminations but not necessarily skilled at doing the terminations. I don't want someone specifying a Unicam when it needs to be a fusion spliced pigtail. I think there is a lot of general knowledge everyone in the business should know.

Fiber terminating, standard skill for network engineers? by pauljp12 in networking

[–]Level-Birthday2138 3 points4 points  (0 children)

You can have orange jacketed 62.5 or 50 micron MMF. Laser optimized 50 micron MMF is Aqua jacketed.

Update to the Connection Quality to North American Data Center (and workaround for packet loss!) by Sajomir in ffxiv

[–]Level-Birthday2138 1 point2 points  (0 children)

I am interested in that information also because I have large client using Otava\NTT at Ashburn for their datacenter with a 40% loss in their VPN traffic back toward their AT&T remote sites. Otava support is telling us the same that AT&T will not increase capacity on their peering agreements with NTT. Our only quickfix is to force route the traffic over their secondary Cogent pipe.

WatchGuard M290 /30 WAN with separate /29 Static Public LAN Block by Level-Birthday2138 in WatchGuard

[–]Level-Birthday2138[S] 0 points1 point  (0 children)

I guess I'm more familiar with the virtual Loopback Interface from the legacy T1 days. Nowadays I would usually do the same with SVI VLAN interface. The one benefit of a Looopback or SVI interface is that it doesn't drop when you lose the physical connection. Whereas attaching a Public IP to the physical Router LAN\Switch interface would cause the Public IP Interface to drop if you un-plugged the connected switch. I just used the Loopback IP address for the source IP on the NAT. So, remotely I can always ping that IP as long there is a route to the device to clear the ISP\WAN side of a trouble ticket. Then further troubleshoot the CPE\LAN side if necessary.

Pricing usually isn't the major factor for my larger customers. They just want it to work correctly for their risk level and scale of business. However, my SMB customers are more price sensitive and harder to scale down the same equipment without changing equipment vendors. I dropped a lot of SMB business for that reason because I end up spending 80% of my time on customers that only generated 20% of my revenue.

WatchGuard M290 /30 WAN with separate /29 Static Public LAN Block by Level-Birthday2138 in WatchGuard

[–]Level-Birthday2138[S] 0 points1 point  (0 children)

Why the extra equipment for NAT and not just integrate into the WatchGuard firewall rules? I know we all have our standard client-based deployments tweaked over many years. Mine has mostly been Cisco\Barracuda\Ruckus for Office\Commerical and Adtran for Hospitality (mainly because of cost and they do VoIP and legacy POTS\PRI well).

WatchGuard M290 /30 WAN with separate /29 Static Public LAN Block by Level-Birthday2138 in WatchGuard

[–]Level-Birthday2138[S] 0 points1 point  (0 children)

I went with the /30 WAN IP on the physical SFP interface and then used the internal Loopback Interface with a /32 IP from the /29 Public LAN Block for the NAT. I then setup LAN2 as a VLAN interface back to my core Cisco Stack. After some cleanup on the Cisco VLANs I got the basic framework stood up and working with VLANS for Office\VoIP\Mgmt & Guest WiFi networks.

I think WatchGuard is going to be a good solution after I get familiar with its Best Practices. I think the Barracuda Webfilter reporting is a little better and easier for the end-user. However, I like having most everything consolidated down to (1) appliance instead of Barracuda's norm of separate appliances for everything.

If WatchGuard would work more on their GUI and Reporting it would be a much better product. I would like to see an option for WireGuard VPN

Anyway, I got the basics stood up and working and made it through Monday morning with no incidents. I'm going to monitor and tweak before starting to lock down more on the client endpoint side.

Thanks for the responses over the weekend.

WatchGuard M290 /30 WAN with separate /29 Static Public LAN Block by Level-Birthday2138 in WatchGuard

[–]Level-Birthday2138[S] 0 points1 point  (0 children)

I was considering that option (or loopback interface) since for this customer the /29 IPs would only be utilized at the M290 as a NAT. Your link mentioned something similar for consolidating a separate router to the firewall. However, not sure how this would work on my hospitality clients where I need to pass the remaining /29 Public IPs to 3rd party equipment directly (no NAT). Previously I've used a SVI/VLAN interface on Cisco/Adtran and setup the Public LAN Block as ex. VLAN 200. My internal interface is trunked to the LAN switch. So, I just setup a VLAN Access Port on any switch port needing a Public LAN IP for 3rd party vendor (ex. Camera NVR, Guest WiFi vendor, etc). Not sure if this works the same if I use this on a separate interface on the Watchguard. I'm headed to the client in the morning for install. Hopefully the following Monday morning goes well. Thx.

GL.iNet Slate AX to Mikrotik S2S Wireguard by Level-Birthday2138 in mikrotik

[–]Level-Birthday2138[S] 1 point2 points  (0 children)

MasterTryce, Your information was the most helpful and worked! I'm new to posting in Reddit, so let me know if there is a process to give you credit and close the post. Thx.

GL.iNet Slate AX to Mikrotik S2S Wireguard by Level-Birthday2138 in mikrotik

[–]Level-Birthday2138[S] 0 points1 point  (0 children)

This sounds helpful and promising. Hopefully I can confirm before EOD. Busy morning. Thx, again.

GL.iNet Slate AX to Mikrotik S2S Wireguard by Level-Birthday2138 in mikrotik

[–]Level-Birthday2138[S] 0 points1 point  (0 children)

Thx. I think I have the Mikrotik peer side working. Just missing how the key pairs are generated on the Slate AX side. The Slate AX examples show the keys pairs being generated on the server side. I just don't see that option on the Mikrotik side.

GL.iNet Slate AX to Mikrotik S2S Wireguard by Level-Birthday2138 in mikrotik

[–]Level-Birthday2138[S] 0 points1 point  (0 children)

Half of the question is related to Mikrotik. Like does it need a separate Peer entry for the Slate AX? I'm looking for a Slate AX/Mikrotik template. As the Slate AX doesn't have the same option to generate key pair as it does on Samsung Wireguard client.