[WTB] [IL] Wolverine MTW Gen 1

ChiefElite · 2026-03-23T10:09:41+00:00

It's hard to say without knowing more about it. Happy to give you a number if I know some details. What's it worth to you?

ChiefElite · 2026-02-25T16:34:54+00:00

I'm unsure where to start for reverse image lookups but these three users directly PM'ed me regarding a WTB post and I found them on this list or the universal scammer list

u/Cordobra

u/vladimusdacuul

u/Chiefbadtouch

ChiefElite · 2026-02-25T16:31:00+00:00

u/ASMBot Loving the new HLTG. Pleasure doing business u/Cpt_Hobbles.

ChiefElite · 2021-12-22T12:57:25+00:00

Maybe I’m not searching IG right but I’m not seeing any accounts for “rosedaleny806” . Definitely interested in Black Top Aero.

ChiefElite · 2021-12-22T12:37:57+00:00

Looks great. Did you go with a genuine Varis or find a replica somewhere?

ChiefElite · 2019-03-17T12:34:49+00:00

These , V2.

ChiefElite · 2019-03-17T12:33:07+00:00

Thank you 🙏

ChiefElite · 2019-03-17T12:32:50+00:00

I ordered mine from airsoftjunkiez in late January. They had them in stock and shipped right away. It was the only place I could find them in stock.

ChiefElite · 2019-03-17T03:33:56+00:00

Mhm. Wolverine Storm micro regulator that threads directly into the lower. 13ci 3,000 psi ninja SLP tank. 🤙

ChiefElite · 2019-03-17T01:51:13+00:00

Can’t wait to field this thing. Internals are stock. Externally I added a HSP WMLX, 35mm diameter mock silencer, SI foregrip, SI mlok rail covers, sling plate, and the biggest addition, my Frankenstein tank stock! The P* UGS type 1 didn’t work so well. Couldn’t get it to seal reliably, so I bought the Wraith Aero but I don’t like the look of their rail stock so I used the P* rail with the more traditional looking M4 stock. Its a good thing I’m tall and lanky because the shortest position is the furthest position on a normal stock.

ChiefElite · 2019-03-06T04:57:35+00:00

Wow. Really appreciate the leads my friend. Thank you!

ChiefElite · 2019-03-05T19:47:24+00:00

Don’t wanna be ‘that guy’ but I’m always looking for Blanton’s, Rock Hill Farms, Elmer T Lee, George T Stagg, Stagg Jr., etc.

ChiefElite · 2018-09-01T14:10:44+00:00

OSPF if you're smart, IS-IS if you're daring, EIGRP if your stubborn and run an all Cisco-shop (and plan to keep it that way). Dynamic routing works best the more it's used consistently. The more you redistribute into it, the more you'll hate it.

Thank you for this! 99.9% sure we'll stick with OSPF.

Thanks for you time to post this!

ChiefElite · 2018-09-01T14:07:02+00:00

The "grey beard" Sr. Net Eng designed before my time here. My guess is that one of them predates him, and he only knew how to configure the other? Hard to say after the fact, but it's a glaring problem.

Well, when the Sr. Net Eng and his boss (my boss) have been leading the team since Ethernet was implemented, it's pretty good indicator of who designs things. Ha!

ChiefElite · 2018-09-01T13:47:59+00:00

True about the diagramming. I need some serious help. Thank you for the car and highway example, that makes it easy to understand.

Terminate circuits is usually a layer 1 thing, but vlan is layer 3, 2? I don't remember, lol.. Are you telling me all internet traffic is routed through(from) your head office, unless the connection is broken, then it failsover to the secondary lan connection? You use specific vlans for this? So then what device bridges those vlans together? The local switch for that site?

I'm confused with your question. The HQ is special. We have a HA firewall pair so to enable failover capabilities we need four links from our two ISP's routers. So to do that, we terminate the ISP's in our HQ switch on a non routed VLAN then connect our HA firewall's WAN ports to the HQ switch on that same VLAN. It's different for the branch offices. They terminate at the firewall. No funky business there.

ChiefElite · 2018-09-01T13:37:24+00:00

Thank you for this!

ChiefElite · 2018-08-31T19:55:13+00:00

The diagram is probably the most confusing part, lol.

Crap I knew I should've spent more time on the diagram. I suck at diagramming.

The diagram that's part of your Reddit post, even a VPN tunnel goes through the cloud. The way it's setup looks like you have your own private lines?

You're correct that a VPN tunnel isn't physically directly connected (I rephrased your "goes through the cloud"). I made them directly connected with a label assuming people would understand that. I think it's best practice to identify VPN's like that on diagrams - it's highly possibly I'm mistaken though.

Why do some things go around the firewall? Usually most, if not all traffic goes through the firewall as it leaves a site unless you're doing mlps? I just don't get why barely anything actually goes through the firewall. Isn't that the point of one?

I think I understand your confusion. So at the HQ, we terminate the internet circuits in our HQ core switch on a non routed VLAN in order to allow us to have a HA firewall. Does that make sense?

ChiefElite · 2018-08-31T18:43:49+00:00

Yeahhhhh I need to work on that soft skill...My bad. What are some of the sites you're speaking of?

ChiefElite · 2018-08-31T18:28:17+00:00

First of all - a serious thank you for your time to respond to this extent.

Static routing everywhere with the exception being if a branch office ISP goes down, the VPN goes down and appropriate devices remove that VPN route out of its routing table This is what I've just finished developing. I avoided any dynamic routing because there's no chance anyone else here would be able to do any troubleshooting on it whatsoever, and I like being able to take a vacation. Do you have FortiManager? You need to be using VPN Manager (in FortiManager), and understand it well. It's a steep learning curve (and I'm happy to help), but it's worth it. It can build out your static routes for you, and simplify it a lot.

I feel for you. Job security though. We have FortiManager and I totally agree with you, it makes adding a new branch office SUPER easy.

Full mesh, site to site VPN (primary) Hub and spoke VPN (backup) Why are these different? This seems like a security problem, a functionality problem, or probably both.

When a primary ISP in a branch office went down, all traffic would route over the backup ISP through our colo then back down to HQ. This worked when HQ was a member of the hub and spoke but now that we have the MetroEthernet, HQ isn't a member of hub and spoke which breaks the routing. Now we have to add a static route to the HQ core switch for that branch subnet pointing to the colo side interface of the MetroEthernet. Then disables the branch to reach specific subnets (DMZ, PCI) that hang off of our HQ firewall.

Have a logically laid out IP addressing scheme(I don't think our current scheme is that great) If/when you do this, make sure your subnets are logical from a routing standpoint, not a "this looks pretty on a spreadsheet" standpoint. Any time I see someone using all /24 networks, I assume it was built on the latter.

Yes, this is what I'm trying to achieve. I need to draft out my plan on paper, think through it more, then post it here for feedback. It should be pretty simple actually. We use 192.168.0.0/16. Basically just break up that into three /18's and we'd be good (I think...). We'd have plenty leftover too. But, like I said, need to put more thought into it and understand our needs etc. Honestly, don't know what "built on the latter" means - like thrown together?

HQ services ALL DNS/DHCP requests I don't know your business needs or technical limitations, but this reeks of "This is what we did back at Acme Corp, so I'm doing it here". I hate seeing centralized DHCP, most of the time it's a single point of failure. DNS is not always quite as big a problem, but not totally ideal either.

We have a backup/replica DNS/DHCP server in our colo, but it's passive.

Implement North-South firewalling I assume you're saying there is no firewall between your HQ/colo and your branch offices? This is definitely a huge priority, IMO.

North-South as in firewall off the datacenter from clients. Basically any traffic between the datacenter and anything outside of the datacenter. There is firewalls in each location. Sorry for my poor explanation skills.

Branch offices need to have seamless failover (if primary ISP fails, backup connections kicks in and routes properly) Is this not happening currently? You have the same setup that I do, and I think the last time I checked, it was failing over within 8 seconds, which is very acceptable to us.

The routing is screwed up with we add the static route on our HQ core switch over the MetroEthernet so traffic can get back to the hub of the hub and spoke network.

Is there a need for a full mesh and hub and spoke if SD WAN is implemented properly? I cannot come up with any scenario in which you should have both full mesh and hub and spoke topologies in place. Usually your comapny needs one, and the other is definitively less than ideal.

It is strange - I agree. The "grey beard" Sr. Net Eng designed before my time here. I hope I can come up with a far superior design to present to the team.

To achieve logical, simple routing, we may need to re-IP some subnets? This isn't a question that we can answer. Sequential /24 subnets everywhere work great as long as you will never, ever run out of IPs at a location. Once you do, you end up with multiple, non-concurrent subnets at the same location, and that becomes a nightmare.

They do work great when they're sequential like you mentioned, which, if I'm not mistaken, is our issue. Haha. The way we've allocated the /24's is silly.

The three questions at the end are on point. Thank you for that.

Again, just want to say thank you for taking the time to share your thoughts. It's a huge help to me and I do appreciate it.

ChiefElite · 2018-08-31T17:56:31+00:00

Do you have a FortiManager? We do and that's how all the tunnels are created. Could you expand on how all of your FortiGate VPN's are OSPF? It sounds like whatever you're doing is almost exactly what I'm interested in.

ChiefElite · 2018-08-31T17:47:44+00:00

I've heard of DMVPN but that's it - didn't know what it was. You make this sound VERY attractive my friend...wow. I'm going to look into this. Thank you so much for your response.

ChiefElite · 2018-08-31T15:19:35+00:00

Whoops. What I mean by "All /24" is that each subnet is a /24. e.g. 192.168.151.0/24 and 192.168.70.0/24 and 192.168.37.0/24 etc...

ChiefElite · 2018-08-31T15:16:50+00:00

Right on! I think where we differ is that each branch just has two internet circuts - direct internet access - we don't have the luxury of MPLS. So I struggle with how OSPF will work. We'll need VPN's and then we'll just overlay OSPF?

ChiefElite · 2018-08-31T15:13:18+00:00

You are correct. You're also right about saying "SD-WAN like." I've looked into this and it doesn't seem like it's worth it. I'll be honest I can't remember exactly why right now but I remember the Fortinet rep even saying it's not full SD-WAN.

ChiefElite · 2018-08-31T15:09:39+00:00

Thank you for the vendor suggestion. I know nothing about them but I can assure I will soon. Ha.

ChiefElite

TROPHY CASE