Book a demo

Cut patent&paper research from weeks to hours with PatSnap Eureka AI!

Try now
VPN Technology Holdings v. Rubicon Communications | pfSense VPN Patent | PatSnap
Explore in Eureka
Case ID1:24-cv-01191
FiledOct 2024
ClosedMar 2025
Patent Litigation

VPN Technology Holdings v. Rubicon Communications: Dismissed With Prejudice in 157 Days

VPN Technology Holdings asserted US7844718B2 — covering remote VPN client configuration — against Rubicon Communications, maker of pfSense open-source firewall and router software. The parties jointly stipulated to dismissal with prejudice in under six months, with each side bearing its own costs, suggesting a pre-trial resolution without a public damages figure.

Resolution time
157days
157 days — resolved faster than the median W.D. Tex. patent case, suggesting early settlement or licence
Patents asserted
1
US7844718B2 — pfSense VPN client configuration via OpenVPN, IPsec, and WireGuard protocols
Outcome
Dismissed with Prejudice
Dismissed with prejudice by joint stipulation — plaintiff cannot refile the same claims
Cost ruling
Own Costs
Each party bears its own attorneys’ fees, expenses, and costs — no fee-shifting order
Published by PatSnap Insights Team · Verified by PatSnap Eureka Data
Case overview

pfSense VPN Patent Dispute Ends in Joint Dismissal With Prejudice

On 4 October 2024, VPN Technology Holdings, LLC filed suit against Rubicon Communications LLC in the Western District of Texas before Judge Alan D. Albright, asserting US7844718B2. The complaint targeted pfSense — Rubicon’s widely used open-source firewall and router platform — specifically the OpenVPN wizard and integrated support for VPN client configuration protocols including OpenVPN, IPsec, and WireGuard.

The case closed on 10 March 2025 when the court granted the parties’ joint motion and stipulation of dismissal pursuant to Federal Rule of Civil Procedure 41(a)(1)(A)(ii). The dismissal was entered with prejudice, permanently barring VPN Technology Holdings from re-asserting the same claims against Rubicon. Notably, each party was ordered to bear its own attorneys’ fees, expenses, and costs — a neutral cost structure consistent with a negotiated resolution rather than a litigated judgment.

A 157-day resolution is considerably faster than the typical W.D. Tex. patent case trajectory under Judge Albright, suggesting the parties reached a private agreement — potentially a licence, covenant not to sue, or business arrangement — shortly after filing. The joint and unopposed nature of the motion, combined with the with-prejudice designation, indicates a deliberate, structured exit. The financial terms, if any, remain confidential and are not disclosed in the public record.

Case at a glance
Case no.1:24-cv-01191
CourtTexas Western
JudgeAlan D Albright
FiledOctober 4, 2024
ClosedMarch 10, 2025
Duration157 days
OutcomeDismissed with Prejudice
Verdict causeInfringement Action
BasisDismissed with Prejudice
Prior Art Intelligence
See what prior art exists on this patent.
Eureka scans millions of patents and papers to surface prior art that may have invalidated these claims before costly litigation begins.
Check Prior Art
Case data sourced from PACER / Texas Western District Court via PatSnap Eureka Litigation Intelligence Explore similar cases ↗
Case timeline

Filing to Dismissed with Prejudice in 157 days

157 days — resolved faster than the median W.D. Tex. patent case, suggesting early settlement or licence

Case timeline: Complaint filed OCT 4 2024, DEC–JAN — 157 days total Horizontal timeline showing the three key events in VPN Technology Holdings, LLC v Rubicon Communications LLC from filing to resolution. Source: PACER, Texas Western District Court. OCT 4 2024 Complaint filed Pre-trial proceedings MAR 10 2025 Dismissed with Prejudice 157 DAYS TOTAL
Dismissal terms

Dismissed with prejudice: what the joint stipulation means for both parties

Legal mechanism

Rule 41 joint stipulation ends the case permanently

A dismissal under Federal Rule of Civil Procedure 41(a)(1)(A)(ii) requires the signed agreement of all parties who have appeared. Once filed and granted, a with-prejudice designation operates as a final adjudication on the merits, extinguishing the plaintiff’s right to refile the same claims against the same defendant in any court. Judge Albright granted the motion noting its joint and unopposed nature — a routine but legally conclusive step.

Permanent bar on refiling
Plaintiff outcome

VPN Technology Holdings permanently relinquishes US7844718B2 claims vs. Rubicon

By agreeing to a with-prejudice dismissal, VPN Technology Holdings forfeits any future infringement action against Rubicon Communications under US7844718B2 for the same accused products and conduct. This is a meaningful concession for a patent assertion entity whose leverage depends on the credibility of future enforcement. Whether the dismissal reflects a commercial settlement, licence fee, or strategic withdrawal is not disclosed in the public record.

Claims extinguished vs. Rubicon
Defendant outcome

Rubicon exits with prejudice — pfSense development continues

For Rubicon Communications, the with-prejudice dismissal provides the strongest available protection short of a court judgment of non-infringement or invalidity: the same plaintiff cannot reassert the same patent claims against the same conduct. pfSense’s VPN configuration features — including the OpenVPN wizard, IPsec, and WireGuard support — are no longer exposed to this specific claim. The own-costs order avoids any fee liability for Rubicon.

Protected against re-assertion
Commercial implications

Open-source VPN platforms remain a patent assertion target

This case is consistent with a broader pattern of PAEs asserting VPN configuration patents against open-source network infrastructure vendors. A sub-six-month resolution before any claim construction or merits ruling leaves US7844718B2 with no public validity or infringement analysis — meaning the patent retains its presumption of validity and could still be asserted against other VPN platform operators, cloud router vendors, or managed service providers using similar configurations.

US7844718B2 remains enforceable
Legal analysis based on PACER docket records for case 1:24-cv-01191 and PatSnap Eureka litigation intelligence Search PatSnap Eureka ↗
Parties and representation

Full party and counsel information

RoleNameTypeDetail
PlaintiffVPN Technology Holdings, LLCCompanyPatent assertion entity — holder of US7844718B2 covering remote VPN client configuration technologySearch in Eureka ↗
DefendantRubicon Communications LLCCompanyRubicon Communications LLC — developer of pfSense open-source firewall and router platformSearch in Eureka ↗
Plaintiff counselM. Scott FullerAttorneyCounsel for VPN Technology Holdings, LLCSearch in Eureka ↗
Plaintiff counselRandall T. GarteiserAttorneyCounsel for VPN Technology Holdings, LLCSearch in Eureka ↗
Plaintiff counselRene A. VazquezAttorneyCounsel for VPN Technology Holdings, LLCSearch in Eureka ↗
Plaintiff law firmGarteiser Honea PLLCLaw FirmRepresenting VPN Technology Holdings, LLCSearch in Eureka ↗
Plaintiff law firmSinergia Technology Law Group, PLLCLaw FirmRepresenting VPN Technology Holdings, LLCSearch in Eureka ↗
Defendant counselDwayne Keith GoetzelAttorneyCounsel for Rubicon Communications LLCSearch in Eureka ↗
Defendant law firmKowert, Hood, Munyon, Rankin & Goetzel, PCLaw FirmRepresenting Rubicon Communications LLCSearch in Eureka ↗
Presiding judgeJudge Alan D AlbrightJudgeTexas Western District CourtSearch in Eureka ↗
Official verdict

Official order — verbatim text

“Before the Court is the Parties’ Joint Motion and Stipulation of Dismissal pursuant to Federal Rule of Civil Procedure 4(a)(1)(A)(ii). ECF No. 14. Noting the Motion’s joint and unopposed nature, the Court hereby GRANTS the Joint Motion and Stipulation and ORDERS that all claims asserted or that could have been asserted in this suit by Plaintiff are hereby DISMISSED WITH PREJUDICE, with each party to bear their own attorneys’ fees, expenses, and costs”
Source: PACER Docket, Case 1:24-cv-01191, Texas Western District Court

The court’s order adopts the parties’ agreed language verbatim, granting dismissal of ‘all claims asserted or that could have been asserted’ — broad language that sweeps in any related theories VPN Technology Holdings might otherwise have reserved. The with-prejudice designation and mutual cost-bearing structure are consistent with a negotiated exit: neither side obtained a public merits ruling, but Rubicon secures a permanent bar against re-assertion of these claims. The absence of any fee-shifting under 35 U.S.C. § 285 suggests neither party pressed an ‘exceptional case’ argument to conclusion.

PACER case 1:24-cv-01191 · Public docket record Explore in Eureka ↗
Patent at issue

US7844718B2 — Remote VPN Client Configuration for Network Appliances

Publication No.US7844718B2
Application No.US11/709355
Patent details
ProductRemote access VPN client configuration via OpenVPN, IPsec, and WireGuard on firewall/router platforms
Cited in actionOctober 4, 2024

US7844718B2 (application no. US11/709355) covers technology for configuring VPN clients on remote devices within a network appliance or router platform context. The patent addresses the automated or wizard-driven setup of remote access VPN sessions — the core functionality targeted in pfSense’s OpenVPN wizard. As a granted B2 patent, it has survived initial examination and carries a statutory presumption of validity under 35 U.S.C. § 282, a presumption that was never challenged on the merits in this proceeding.

VPN configuration automation is commercially significant across enterprise networking, managed security services, and open-source router platforms. pfSense is deployed by ISPs, managed service providers, and enterprise IT teams globally, making Rubicon a high-visibility target. Because no IPR petition or invalidity ruling appears in the public record for this case, US7844718B2 remains a live enforcement asset. Vendors offering similar VPN wizard or automated client provisioning features — whether on hardware appliances or software-defined networks — face analogous exposure.

Patent data sourced from USPTO via PatSnap Eureka patent database Search patent records in Eureka ↗
Freedom to operate

Should your team run an FTO against US7844718B2?

Any organisation developing, distributing, or integrating VPN client configuration features — particularly wizard-driven or automated setup flows for OpenVPN, IPsec, or WireGuard — should consider a formal freedom-to-operate analysis against US7844718B2. This is especially relevant for open-source network appliance developers, MSPs bundling VPN configuration tools, cloud router vendors, and SD-WAN platform providers operating in similar technical territory to pfSense.

PatSnap Eureka’s FTO Search Agent can map the claim scope of US7844718B2 against your product’s technical architecture, identify prior art that could support an invalidity argument, and surface any continuation or divisional applications in the same family that may carry broader or narrower claims. Eureka also monitors the patent’s assignment history and any pending litigation to give your IP team real-time enforcement intelligence before you receive a demand letter.

PatSnap Eureka FTO Search

Run a freedom-to-operate analysis on US7844718B2 to assess your product’s exposure

Run FTO in Eureka →
Related litigation

Similar VPN and Network Security Patent Cases in W.D. Texas

Explore related patent infringement actions in the VPN, firewall, and network configuration space litigated before the Western District of Texas.

🔍
Access 40+ similar cases in PatSnap Eureka
VPN Technology Holdings, LLC patent enforcement history, Texas Western case history, VPN Technology Holdings, LLC’s full IP portfolio, and comparable case analysis
VPN protocol patent suitspfSense-adjacent casesPAE filings in W.D. Tex.Network security dismissals
Unlock similar cases in Eureka →
Strategic implications

What this case signals for the VPN and network security IP landscape

A swift, quiet dismissal in W.D. Tex. rarely means the patent is dead — it often means the defendant paid to make it go away.

Early W.D. Tex. dismissals often signal a licence, not a victory

A 157-day timeline with no claim construction hearing and a joint with-prejudice dismissal is a strong indicator that Rubicon resolved the matter commercially rather than litigating to judgment. Teams operating pfSense or similar VPN platforms should treat this as a signal that US7844718B2 is being actively enforced, not retired.

US7844718B2 carries no public invalidity ruling — risk persists for others

Because the case ended before any substantive merits ruling, there is no Markman order, no summary judgment, and no IPR disposition in the record. Any competitor or vendor offering OpenVPN, IPsec, or WireGuard configuration wizards on a network appliance or software platform should assess their own exposure independently.

🔒
Full strategic analysis in PatSnap Eureka
Unlock gated insights on PAE enforcement patterns in the VPN and network security sector from this W.D. Tex. district court case.
Licensing risk signalsRelated patent familyEnforcement chain analysis
Unlock full analysis →
Analysis powered by PatSnap Eureka Litigation Intelligence Explore in Eureka ↗
Frequently asked questions

VPN v Rubicon — key questions answered

Still have questions? PatSnap Eureka can answer them instantly from patent and litigation data. Ask Eureka ↗
PatSnap Eureka

Track VPN patent enforcement before your product is targeted

US7844718B2 remains enforceable with no public invalidity ruling on record. PatSnap Eureka lets you monitor this patent’s litigation history, claim scope, and family continuations — and run an FTO before a demand letter arrives.

Ask anything about this case.
PatSnap Eureka searches patents and litigation data to answer instantly.
Powered by PatSnap Eureka
Link copied to clipboard

Related Litigation Cases

Help us improve this page

Found incorrect or outdated information? Let us know and we'll get it fixed.