Server and gsm router ipsec tunnel

@marcusd39

Hello, Good morning . How are you? I hope this proposal finds you well. I'M A CERTIFIED & EXPERIENCED EXPERT This is to inform you that I have KEENLY gone through your project description, CLEARLY understood all the project requirements as instructed in your project proposal and this is to let you know that I will perfectly deliver as desired. Being in possession of all stated required skills, (Network Engineering, P2P Network, Cloud Networking and Network Administration), as this is my field of professional specialization having completed all certifications and developed adequate experience in the respective field, I hereby humbly request you to consider my bid for professional, quality and affordable services that meet all your requirements. I always guarantee timely delivery and unlimited revisions where necessary hence you are assured of utmost satisfaction when working with me. Please send me a message so that we can discuss more and seal the project. WELCOME.

@nintysix96

Treat the bid amount and timeline above as rough placeholders. We'll nail down the real numbers once we understand the full setup. So you're running a Milesight GSM router and need it talking reliably to a cloud server over IPsec, with pfSense handling the tunnel on one or both ends. The tricky part with cellular modems is the carrier-grade NAT and dynamic IP situation, which can cause tunnels to drop and not recover cleanly. We're guessing "keep connected" is the key phrase here, meaning you want this thing to stay up, not just connect once. Here's how we'd approach it: - IPsec tunnel config: Set up IKEv2 on pfSense with the right phase 1 and phase 2 settings to match what the Milesight supports, handling the dynamic IP side with aggressive mode or a DynDNS hook if needed. - Dead peer detection and keepalives: Tune DPD on the pfSense side so dropped cellular connections get detected fast and the tunnel re-establishes automatically without manual intervention. - Cloud server end: Configure the server-side IPsec responder (strongSwan or pfSense depending on your cloud setup) and open the right firewall/security group rules for UDP 500 and 4500. - Routing and NAT: Make sure traffic from behind the Milesight actually routes through the tunnel correctly and isn't leaking outside it. - Stability testing: We'll stress the connection through a few reconnect cycles to confirm the auto-recovery is solid before handing over. Once we have a quick chat about your cloud provider, the Milesight model, and what's running behind it, we'll send a short written proposal with the steps and final price. Want to jump on a quick call this week to walk through the setup? Best, 96 Studio

@markupdudes

Hello, I'm confident in setting up a robust IPSec tunnel between your Milesight GSM modem and the cloud server using pfSense. My background in Network Engineering and Network Administration ensures stable, secure connections with optimized Cloud Networking configurations. I'll handle the end-to-end setup, monitoring, and troubleshooting to keep your devices reliably connected. I propose we start with a detailed review of your current infrastructure, then proceed with configuration and testing within a week. This approach guarantees smooth deployment and lasting performance. Could you share your current pfSense version and any existing IPSec configurations to tailor the setup perfectly? Thanks,

@haseebs74

Hi, Connecting a Milesight GSM modem to a cloud server via IPsec VPN through pfSense is a network configuration task I have done before and can get working reliably. I will configure the IPsec tunnel on pfSense with the correct phase 1 and phase 2 settings to match the Milesight modem requirements, set up the GSM modem connection on the Milesight device, establish the IPsec tunnel between the modem and your cloud server and configure keepalive and auto reconnect settings so the connection stays stable and recovers automatically if the GSM link drops. I will test the full connection end to end and confirm stable connectivity before handover. You will also get a short document explaining the configuration so you can replicate it on additional modems later. One question: what cloud server platform are you using — AWS, DigitalOcean, a VPS or something else — and do you already have pfSense installed and running or starting from scratch?