Network Engineer for Secure Proxy & Gateway Architecture

@serazummunirz

Hi There, Hope you are well. I have extensive experience in building and deploying secure proxy systems, including setting up development environments, configuring remote nodes, and ensuring failover between protocols like Hysteria2 and VLESS-Reality. With strong Linux admin skills, DevOps experience, and networking knowledge, I am well-equipped to handle the phases of this project effectively. Thanks in advance for the opportunity to working with you. Best Regards, Serazum

@tangramua

Hello,   We carefully studied the description of your project and we can confirm that we understand your needs and are also interested in your project. Our team has the necessary resources to start your project as soon as possible and complete it in a very short time.   We are 25 years in this business and our technical specialists have strong experience in Linux, Ubuntu, Network Administration, Raspberry Pi, DevOps, Network Security, Network Engineering, VPN, Network Monitoring, System Administration and other technologies relevant to your project.   Please, review our profile https://www.freelancer.com/u/tangramua where you can find detailed information about our company, our portfolio, and the client's recent reviews.   Please contact us via Freelancer Chat to discuss your project in details.    Best regards, Sales department Tangram Canada Inc.     

@iosifpeterfi

Hi, I’m Iosif Peterfi — 15+ years in Systems/DevOps, Linux, networking and security, with hands-on experience in VPN/proxy routing, firewalling, systemd and repeatable infrastructure deployments. Approach • PoC: deploy 3X-UI on a remote Ubuntu node and sing-box on Raspberry Pi; configure VLESS-Reality + Hysteria2 and validate routing/failover. • Gateway: configure TUN/transparent routing, nftables/iptables, DNS handling and startup via systemd. • QA: connect one Pi gateway to a QA server, test failover, latency, reconnect behaviour and recovery after service/network interruption. • Production: replicate hardened configs across multiple nodes, add health checks, priority/failover logic and repeatable deployment steps. • Security: least-privilege access, firewall rules, key/config protection, restricted admin panel exposure and change/rollback procedures. • Handover: documented server/Pi setup, configuration templates, troubleshooting guide and deployment checklist. Acceptance • Both protocols route correctly • Automatic failover/recovery works • Pi survives reboot/network loss without manual intervention • QA config can be reproduced on production nodes Initial PoC + QA deployment: $1440 USD (18 hours) fixed. Production rollout can be scoped after QA. Available for ongoing maintenance and expansion.

@manojmalviya93

Hi — I reviewed “Network Engineer for Secure Proxy & Gateway Architecture” and can help. From your brief: Network Engineer for Secure Proxy & Gateway Architecture Seeking an experienced network engineer to build and deploy a secure proxy system using 3X-UI (MHSanaei) on a remote server and sing-box on a Raspberry Pi client… I handle server/network monitoring, Linux/cloud ops, and AIOps-style alerting and remediation. OrcaMonitor is relevant when you need Cisco/network or server auto-remediation. Happy to align on scope, timeline, and a first milestone as soon as you are ready. Manoj, Synetal Solutions

@talhamq

As a network engineer with extensive experience in cloud computing platforms, server operating systems, and web servers, I am confident that I possess the breadth and depth of technical knowledge necessary to tackle your secure proxy and gateway architecture project. I have a solid grasp of Linux administration, including Ubuntu and Raspberry Pi OS, which will prove pivotal for setting up your desired development client environment. Furthermore, my understanding of transparent proxies, TUN interfaces, iptables, and nftables aligns perfectly with your requirements.

@SkillCrafts

Your requirement for a robust, automatically failing-over proxy system mirrors my recent work on a similar distributed network architecture, where I successfully implemented failover logic between different VPN protocols to ensure continuous connectivity for a critical service. I'm confident I can achieve a similar seamless experience for your 3X-UI and sing-box deployment. My approach will involve a phased implementation starting with a Proof of Concept. I'll leverage `sing-box`'s advanced routing and protocol configuration capabilities, specifically focusing on its ability to define multiple outbound protocols and implement sophisticated fallback rules. For the Raspberry Pi client, I'll script the installation and configuration of `sing-box`, ensuring it dynamically monitors the VLESS-Reality and Hysteria2 connections to the remote server. On the server-side, I'll configure `3X-UI` to manage user access and ensure optimal routing to the sing-box clients. To ensure a perfect fit, could you clarify the desired latency tolerance for the failover event? Also, what are your primary concerns regarding ongoing monitoring and alerting for this setup? I'm eager to discuss these details and how my expertise can deliver a highly resilient proxy solution for your needs.

@Hrolgar

Routing between VLESS-Reality and Hysteria2 means choosing which one is the default path. Reality is TCP and blends in under DPI but stalls on lossy links. Hysteria2 is UDP and fast but is the first thing a strict network drops. I'd make Reality primary and let a sing-box urltest group fall over to Hysteria2, then cut each protocol in turn in the PoC to confirm the switch. My rate is 70 USD per hour. It holds if I get SSH to the Pi and the servers, so no hardware work is needed. It also assumes the PoC is one 3X-UI node and one sing-box client, with multi-node rollout billed separately, and that you supply the VPS nodes plus the domain and certificate details Reality needs. If any of that differs, I'll re-quote before starting. Do you want the Pi to proxy the whole LAN through TUN, or only selected devices via nftables rules?

@mcollinscalz

Hello, Building a resilient, high-availability proxy gateway requires robust protocol orchestration, precise nftables/TUN routing, and low-latency failover logic between VLESS-Reality and Hysteria2. As a Network & Systems Engineer, I can architect and deploy your 3X-UI to Raspberry Pi proxy architecture from PoC to production. How I Will Execute Your Architecture: Server Infrastructure: Deploy and secure 3X-UI (MHSanaei) on Ubuntu nodes, configuring VLESS-Reality (SNI camouflage) and Hysteria2 (UDP/QUIC optimization for lossy networks). Raspberry Pi Gateway: Configure sing-box on Raspberry Pi OS in TUN/transparent proxy mode using nftables for local network traffic redirection, systemd auto-restart, and automatic health-check failover between nodes. Staged Deployment: Drive a structured 3-phase rollout (PoC -> QA validation -> Multi-node Production HA) backed by Ansible configuration playbooks for easy node scaling. Deliverables: Production-ready 3X-UI server configurations & sing-box JSON configs Ansible automation scripts for multi-node deployment Step-by-step setup, failover testing, and maintenance documentation I am experienced with anti-censorship protocols, ARM hardware optimization, and modern proxy routing. I am ready to start Phase 1 immediately! Best regards,

@patricko098

You're not just hiring a freelancer. You're choosing the outcome. I've successfully built a secure proxy architecture for a major global client, implementing a multi-protocol gateway that utilized both VLESS and custom tunneling solutions. This project greatly enhanced the client's network reliability and reduced downtime by 40%. My work with top-tier companies like Google and Amazon has honed my skills in delivering high-stakes projects under pressure, ensuring that I meet demanding client expectations. My background in Linux administration and networking, particularly with Ubuntu and Raspberry Pi, aligns perfectly with your project needs. With hands-on experience in infrastructure automation and configuration management, I'm equipped to tackle the multi-phase approach you've outlined, from development to production deployment. I understand your goals of establishing a secure, efficient, and scalable proxy system. My approach will include a detailed PoC to test failover capabilities, followed by rigorous QA to ensure real-world readiness, ultimately deploying a robust production environment with high availability. Reliable execution and proactive communication are my cornerstones. I'll ensure seamless updates and problem-solving throughout the project, delivering a solution that continues to provide value beyond launch. I am confident that my expertise and strategic approach make me the ideal choice for your project. The strongest projects succeed because they start with the right plan, process, and execution. Regards, Patrick O'Flaherty.

@amadorjay

Hi there, The challenge lies in ensuring automatic protocol failover between VLESS-Reality and Hysteria2 while maintaining secure routing through the proxy system. It’s crucial to first establish a solid proof of concept to verify that the routing and failover mechanisms are functioning correctly on the Raspberry Pi client gateway. I can set up the client environment with 3X-UI on the server and deploy sing-box locally for initial testing. After that, we can move to QA deployment with real-world testing to ensure performance. Given your requirements, how do you envision the monitoring process for the deployed network? Looking forward to discussing the details in chat.

@ahmadraza001912

Your brief describes a three-phase rollout: a local proof of concept, a single QA server with the Raspberry Pi gateway, then multiple production nodes with high availability. I would structure the work the same way. First, I would build the proof of concept with sing-box on a development client, using selector and urltest outbounds to test automatic failover between VLESS-Reality and Hysteria2. I would then script the 3X-UI installation and inbound configuration so every server node is deployed identically. This keeps QA and production consistent and makes new nodes quick to add. My background is Linux and Ubuntu administration, systemd services, Docker, Nginx and Cloudflare, with production deployments handled carefully to avoid disruption. I would deliver the server setup, tuned Raspberry Pi configs, and clear setup documentation with hand-off notes. I am open to ongoing maintenance after launch. As a next step, I can send a short phase-one plan with a test checklist once you confirm the Raspberry Pi model and the target server provider. Which Raspberry Pi model and OS version will the gateway run on, and do you already have the server nodes provisioned?

@sufyanasmat38

Hi, I understand the project, and we can build the gateway architecture with reliable failover, secure routing, systemd services, firewall rules, TUN based traffic handling, and repeatable Linux deployments across Raspberry Pi and remote servers. We can structure the setup so QA and production configurations remain consistent and easy to maintain, with monitoring, troubleshooting, and clear deployment documentation included. Relevant Linux, Raspberry Pi, networking, DevOps, and infrastructure work is available in our portfolio. 1. Should failover happen automatically based on connectivity and health checks, or only when the active tunnel becomes unavailable? 2. Will the Raspberry Pi operate as the network gateway for other devices, or only handle its own traffic? 3. How many production nodes and Raspberry Pi gateways do you expect in the final deployment?

@samnangy4

Hello, I hope your week is going well. I've set up proxy and gateway stacks like this before, and 3X-UI with sing-box is familiar territory. Having delivered multiple similar builds, the failure mode that matters most here isn't the initial setup, it's what happens when a node dies at 2am and the Pi has to swing across cleanly. One recent build paired sing-box on a Pi 4 gateway with a remote panel, using a urltest outbound plus a fallback chain so VLESS-Reality and Hysteria2 could hand off automatically. The tricky part was TUN mode on ARM, where timing under load kept breaking the health check before I tuned the intervals properly. Getting that stable took longer than the server side did. For a start, I'd get the PoC running with systemd units for sing-box on the Pi, tproxy rules via nftables, and a scripted node config generator so QA and production servers stay repeatable. Probably the cleanest path is Ansible for the node deployment, since you'll want parity across environments. Before I map out the failover logic, it'd help to compare notes on the Pi model and Raspberry Pi OS version you're targeting, and whether Hysteria2 is meant as primary or backup. Could we hop on a short call this week? Looking forward to hearing from you, Samnang

@selaaf

a pi gateway that flips between vless-reality and hysteria2 on its own, backed by your 3x-ui servers, is something i can set up for you from poc through to production i can do this for you, and i'm comfortable with linux, systemd and nftables on both ubuntu and pi os i'll stay on it through each phase until the failover behaves the way you want, and sort out any bugs that show up after how many production nodes and pi gateways are you planning for the final rollout? i can keep supporting it after deployment too Sela

@tkashi466

Hi, I can help build the 3X-UI sing-box gateway architecture across your PoC, QA, and production phases, with a strong focus on reliable routing, protocol failover, and repeatable deployments. I understand the requirements around **VLESS-Reality, Hysteria2, TUN/transparent proxying, iptables/nftables, systemd, ARM/Raspberry Pi, and multi-node infrastructure**, including testing and troubleshooting across environments. I can deliver a clean, documented deployment with configuration consistency and a clear path for scaling and long-term maintenance.

@mirimera

I’ve deployed Linux proxy gateways on Raspberry Pi hardware with systemd-managed routing, transparent TUN interfaces, and multi-node failover. For this project, the key is using sing-box outbound selection with health checks and deterministic fallback between VLESS-Reality and Hysteria2, so the gateway recovers cleanly when a route degrades. I’ll build the 3X-UI server setup on Ubuntu, configure hardened node profiles, and create repeatable Raspberry Pi OS services and firewall rules. I’ll validate DNS, LAN routing, protocol switching, and restart persistence during the proof of concept before promoting the same configuration through QA and production. You’ll receive clear deployment documentation and maintainable configs for future nodes. Thanks, Kittipong

@julianm260

With my broad experience as an Electronics Engineer, specializing in Raspberry Pi and embedded systems, I bring a unique perspective to the Network Engineering role. I have consistently showcased the ability to implement complex solutions underpinned by Linux system administration capabilities that precisely align with your project's primary requirements. My skill set distinctly complements the scope of this mission, including familiarity with iptables, nftables, routing architectures, and transparent proxies/TUN interfaces. I have successfully delivered numerous projects end-to-end, specifically focusing on high-power electronic design and distribution systems. My cause-and-effect mindset aligns well with the troubleshooting demands inherent in network engineering. Furthermore, my craftsmanship is characterized by stringent adherence to safety, reliability, and performance standards - attributes that will be invaluable for ensuring the utmost safety and cutting-edge performance of your gateway architecture across every phase. What makes me stand out is not only my resume but rather my commitment to continued learning and growth within the industry. This project presents an excellent opportunity for me to bolster my expertise in networking tools on ARM/Raspberry Pi hardware while delivering on exemplary quality along the way. The potential for long-term support and maintenance after deployment further intrigues me - it provides a chance to ensure all changes are documented appropriately and future-proofed optimizations can be implemented. Choose me for profound expertise in tangibleizing complex designs into robust, optima

@samvela2

Hello, I am an experienced Electronic Engineer specializing in Network Security, Linux, Raspberry Pi, Network Engineering, Ubuntu, DevOps, VPN, Network Monitoring, System Administration and Network Administration. I can handle the complete development process from schematic design and component selection to PCB layout, firmware integration, testing, and troubleshooting. I work with industry-standard tools such as Altium Designer, KiCad, EasyEDA, Proteus, and MATLAB to deliver reliable and production-ready solutions. My focus is always on accuracy, performance, manufacturability, and clear documentation throughout the project. I am ready to discuss your requirements and provide a high-quality engineering solution that meets your technical goals, budget, and timeline. Thanks.

@bohdan38

Hello, Your project requires a reliable secure proxy architecture spanning 3X-UI servers, sing-box Raspberry Pi gateways, and automatic failover between VLESS-Reality and Hysteria2. The key challenge is making transparent routing, resilience, and repeatable deployment work consistently across development, QA, and production. I would build the proof of concept first, configure the remote nodes and ARM gateway, then validate TUN or transparent proxy routing, systemd services, firewall rules, health checks, and protocol failover. The deployment will be structured for repeatability across Ubuntu and Raspberry Pi OS, with clear configuration separation for each environment. Similar work includes Linux networking, proxy and gateway automation, infrastructure troubleshooting, and production API or service deployments involving secure routing and high availability. I can also document the operational workflow so future nodes and gateways can be added safely. I will deliver the first working milestone within 7 days, including tested configurations, deployment notes, and findings from real gateway testing. The remaining rollout can then proceed predictably across QA and production. Best regards, Bohdan