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.
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.
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
Dismissed with prejudice: what the joint stipulation means for both parties
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 refilingVPN 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. RubiconRubicon 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-assertionOpen-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 enforceableFull party and counsel information
| Role | Name | Type | Detail |
|---|---|---|---|
| Plaintiff | VPN Technology Holdings, LLC | Company | Patent assertion entity — holder of US7844718B2 covering remote VPN client configuration technologySearch in Eureka ↗ |
| Defendant | Rubicon Communications LLC | Company | Rubicon Communications LLC — developer of pfSense open-source firewall and router platformSearch in Eureka ↗ |
| Plaintiff counsel | M. Scott Fuller | Attorney | Counsel for VPN Technology Holdings, LLCSearch in Eureka ↗ |
| Plaintiff counsel | Randall T. Garteiser | Attorney | Counsel for VPN Technology Holdings, LLCSearch in Eureka ↗ |
| Plaintiff counsel | Rene A. Vazquez | Attorney | Counsel for VPN Technology Holdings, LLCSearch in Eureka ↗ |
| Plaintiff law firm | Garteiser Honea PLLC | Law Firm | Representing VPN Technology Holdings, LLCSearch in Eureka ↗ |
| Plaintiff law firm | Sinergia Technology Law Group, PLLC | Law Firm | Representing VPN Technology Holdings, LLCSearch in Eureka ↗ |
| Defendant counsel | Dwayne Keith Goetzel | Attorney | Counsel for Rubicon Communications LLCSearch in Eureka ↗ |
| Defendant law firm | Kowert, Hood, Munyon, Rankin & Goetzel, PC | Law Firm | Representing Rubicon Communications LLCSearch in Eureka ↗ |
| Presiding judge | Judge Alan D Albright | Judge | Texas Western District CourtSearch in Eureka ↗ |
Official order — verbatim text
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.
US7844718B2 — Remote VPN Client Configuration for Network Appliances
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.
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.
Run a freedom-to-operate analysis on US7844718B2 to assess your product’s exposure
Run FTO in Eureka →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.
Related patent case — similar technology
Comparable case in the same technology domain. Patent holder and defendant reached resolution after proceedings.
SettledRelated infringement action — same court
Comparable “pfSense” software, an open-source firewall and router platform which includes integrated support for the configuration of VPN clients on the remote devices by supporting protocols such as OpenVPN, IPsec, and WireGuard The OpenVPN wizard in pfSense software performs the setting up of a remote access VPN for mobile clients-adjacent infringement action. Patent enforcement dynamics analysed in depth.
Active · District CourtRelated invalidity challenge — appellate outcome
Combined invalidity and infringement action in the same technology space. Decided after substantive proceedings.
DecidedVPN Technology Holdings, LLC’s broader IP enforcement history
VPN Technology Holdings, LLC’s full litigation history covering prior enforcement, licensing activity, and inter partes review proceedings.
Portfolio viewWhat 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.
Judge Albright’s docket patterns amplify early settlement pressure
W.D. Tex. under Judge Albright is known for aggressive scheduling that compresses defendant discovery timelines and increases early settlement leverage for plaintiffs. Companies receiving demand letters referencing this docket should factor in the structural litigation asymmetry when evaluating response strategy.
PAE enforcement chains: who else may be in the crosshairs
VPN Technology Holdings, LLC is a holding entity with no disclosed operating products — consistent with a PAE model. Identifying the patent’s full prosecution history, prior assignments, and any related continuation applications is critical for assessing whether other VPN configuration claims remain pending and who else may face assertion.
VPN v Rubicon — key questions answered
Dismissed with prejudice means the court entered a final termination of all claims VPN Technology Holdings asserted or could have asserted against Rubicon Communications under US7844718B2. The plaintiff is permanently barred from refiling the same patent claims against the same defendant. The dismissal was entered by joint stipulation under Rule 41(a)(1)(A)(ii).
US7844718B2 (application US11/709355) covers technology for configuring VPN clients on remote devices, particularly in the context of network appliance and router platforms. In this case, it was asserted against pfSense’s OpenVPN wizard and integrated VPN protocol support including OpenVPN, IPsec, and WireGuard. No claim construction order was issued in this case.
The 157-day resolution — significantly faster than the W.D. Tex. median — is consistent with an early private resolution, which may include a licence, covenant not to sue, or other commercial arrangement. The joint and unopposed nature of the dismissal motion suggests both parties agreed on terms before any substantive litigation milestones such as a Markman hearing or claim construction briefing.
No. A with-prejudice dismissal by joint stipulation carries no merits ruling on validity or infringement. The patent retains its statutory presumption of validity. No court has found US7844718B2 invalid or not infringed in this proceeding. Other parties offering similar VPN configuration features cannot rely on this dismissal as a defence.
The court’s order specifies that each party bears its own attorneys’ fees, expenses, and costs. No fee-shifting was ordered under 35 U.S.C. § 285 (which requires a finding of an ‘exceptional case’). This mutual cost-bearing structure is typical of negotiated dismissals and does not reflect any judicial finding regarding the merit or frivolousness of the claims.
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.
PatSnap Eureka searches patents and litigation data to answer instantly.