Hi everyone! I'm new to the forum and pretty new to managing network infrastructure like this, so I'm hoping for a bit of a walkthrough. 😅
I’m setting up a CloudGen VPN tunnel for a data pipeline project, following Barracuda’s official admin guide. I’ve reached the part about enabling a specific compression protocol, and the documentation says to set a configuration flag called `compression-level` in the advanced tunnel settings.
The problem is, I’m in my CloudGen Firewall admin interface (v9.0.1), and I simply cannot find that flag anywhere in the VPN tunnel configuration menus. I’ve checked under:
* **VPN Service > IPsec Tunnels > [My Tunnel]**
* The "Advanced" tab within the tunnel config
* Even the raw configuration file view
It’s just not there. Has anyone else run into this? I’m wondering if:
* The documentation is for a different firmware version?
* The flag has been renamed or moved to a totally different section?
* This feature is now enabled by default and the flag is deprecated?
I want to make sure my tunnel is optimized, especially for moving larger datasets. Could someone point me to where this setting lives now, or clarify if I even need to worry about it? A step-by-step on what you did would be incredibly helpful!
Thanks in advance – really excited to learn from this community.
Hey, welcome to the forum! You've definitely hit on a common snag - the docs and the UI don't always stay in sync. I ran into this exact thing a few months back.
You're on the right track with your guesses. In version 9.x, that specific `compression-level` flag was removed from the UI because the compression protocol you're referencing (IPcomp) is actually kind of deprecated for most modern use. It can sometimes add overhead instead of helping. The feature is still in the engine, but it's not recommended for new tunnels, especially for data pipelines.
For moving larger datasets, I'd focus more on the MTU settings and making sure your Phase 2 SA (Security Association) lifetimes are tuned for sustained traffic. Check the "IKE" tab in your tunnel config for those SA settings. What's on the other end of your tunnel, if you don't mind me asking? That can change the tuning approach.
Happy testing!
Yes, that sync issue between docs and the live UI is such a pain point. It really trips up adoption when the official guide doesn't match what people see.
You're spot on about IPcomp being deprecated. I'd add that even if you could set it via CLI, enabling it on a modern, high-bandwidth data pipeline tunnel can actually trigger Path MTU issues. The compression processing can fragment packets in a way that just breaks things. Been there, chased that ghost for a day.
I'm curious, user1348, when you mention tuning SA lifetimes for sustained traffic - have you found a sweet spot for something like a constant database sync? I've seen the default timeouts cause renegotiation hiccups during big transfers.