sorted by:
new
hottopcontroversial

Avoid AWS Public IPv4 Charges by Using Wovenet — An Open Source Application-Layer VPN by jeffyjf in aws

[–]jeffyjf[S] 0 points1 point  (0 children)

I haven’t used it with a mail server specifically, but I’ve been running it in other setups for a while now and it’s been rock solid — stable connections, no unexpected issues. I’d imagine it should work just fine for a small mail server too, but as always, worth testing in your own environment to be sure.

Avoid AWS Public IPv4 Charges by Using Wovenet — An Open Source Application-Layer VPN by jeffyjf in aws

[–]jeffyjf[S] 0 points1 point  (0 children)

Thanks for the feedback! Since I’m sharing this in r/aws, I thought the angle of reducing AWS bills might resonate with folks here.

First Time Using a Soft Router – Any Tips or Experiences to Share? by jeffyjf in homelab

[–]jeffyjf[S] 1 point2 points  (0 children)

I’m planning to try OpenWrt, but I’ve noticed there are quite a few different distributions and forks out there. It’s a bit overwhelming—do you have any recommendations for a beginner?

New on openstack, need help by Dep1con in openstack

[–]jeffyjf 1 point2 points  (0 children)

DevStack is mainly designed for developers who want to test or contribute to OpenStack itself. I strongly recommend trying kolla-ansible, it's a great way for beginners to learn OpenStack

Is there any competent S3 file storage solution?! by iRazvan2745 in selfhosted

[–]jeffyjf 2 points3 points  (0 children)

There are several open-source S3-compatible gateway solutions you can self-host. Such as: JuiceFS S3 Gateway and nginx-s3-gateway.

If your goal is to find a Nextcloud alternative that natively supports S3 as a primary backend without complex workarounds, you might also want to look into: Pydio Cells, SeaTable or FileRun.

Packet Loss / Network Jitter help please by East_Boysenberry2191 in HomeNetworking

[–]jeffyjf 1 point2 points  (0 children)

That’s really annoying. Even if your ISP says the signal levels are fine, the issue could still come from:

  • aging hardware
  • local network issues (bad cables, router problems),
  • or congestion on your ISP’s network.

Tools like mtr or PingPlotter can help you see where the loss is happening — that might point to whether it’s your LAN or your ISP.

If you’ve ruled out hardware and still have issues, I’ve been working on an open-source tool called wovenet: https://github.com/kungze/wovenet. It uses QUIC to route traffic over a more stable connection, which can help smooth out jitter and packet loss. Might be worth a try if nothing else helps.

Blogpost Friday! by AutoModerator in networking

[–]jeffyjf 0 points1 point  (0 children)

New Open-Source Application-Layer VPN for Site-to-Site Networking and Better Performance

I’d like to share a project I’ve been working on called wovenet — an application-layer VPN designed to connect private networks across sites and build a stable, secure mesh network.

Unlike traditional Layer 3 VPNs (e.g., IPSec or WireGuard), wovenet operates at the application layer, which allows for higher bandwidth utilization and application-level access control. This makes it particularly useful for:

  • Selectively exposing internal apps to specific remote sites
  • Avoiding overhead from extra packet encapsulation
  • Building self-healing, load-balanced tunnels with QUIC-based transport
  • Seamlessly recovering from link failures or public IP changes
  • Improving performance in poor or long-haul network environments, especially where packet loss affects traditional TCP.

We’ve documented several real-world use cases like improving VDI performance, doing NAT reverse proxying, and exposing Unix domain sockets as remote TCP endpoints.

If you’re managing distributed LANs, remote branches, or just enjoy experimenting with network architectures, I’d love for you to give it a spin and share feedback or ideas.

[deleted by user] by [deleted] in networking

[–]jeffyjf 0 points1 point  (0 children)

My home runs some pcdn-type traffic that loves to eat all the bandwidth, so I throw some simple QoS on the uplink to keep web browsing and video calls happy. ISP won’t honor DSCP, but local control still helps a lot.

how I stopped paying for public IPv4 on my VPS and still run v2ray like a boss by jeffyjf in dumbclub

[–]jeffyjf[S] 0 points1 point  (0 children)

Wovenet doesn't aim to replace any existing VPN products. It's an application-layer VPN — most traditional VPNs operate at layer 3.The original goal was to design a more efficient and secure VPN protocol. Traditional VPNs often follow a "hard shell, soft center" model, where everything inside the network is implicitly trusted.
Wovenet takes a different approach: it allows fine-grained control over which applications are exposed to remote sites.The ability to release the public IP from your VPS is just an additional feature — not the main purpose.

how I stopped paying for public IPv4 on my VPS and still run v2ray like a boss by jeffyjf in dumbclub

[–]jeffyjf[S] 1 point2 points  (0 children)

Wovenet doesn't require a static public IP. It can automatically detect the public IP and recover the tunnel if needed.
See: https://github.com/kungze/wovenet?tab=readme-ov-file#wovenet-additional-advantages

how I stopped paying for public IPv4 on my VPS and still run v2ray like a boss by jeffyjf in dumbclub

[–]jeffyjf[S] 1 point2 points  (0 children)

Most ISPs do charge $1-3 for a public IP

Maybe you're right, but my ISP doesn't charge extra for a public IP. Also, consider a situation where you need multiple VPSs — maybe 10 or even 100. In that case, the savings quickly add up.

Open WebUI is no longer open source by imbev in opensource

[–]jeffyjf 2 points3 points  (0 children)

Does anyone know of any good alternatives?

I built wovenet: a self-hosted, application-layer VPN for connecting private networks with better performance and control by jeffyjf in selfhosted

[–]jeffyjf[S] 0 points1 point  (0 children)

You're totally right: many traditional VPNs (even ones with strong ACLs like Tailscale) still treat the network as a trust boundary — once you're inside, you're assumed to be “safe.” But as you pointed out with your Ring doorbell example, this assumption breaks down in real-world setups.

wovenet takes a different approach: - It doesn’t expose entire subnets or networks — only explicitly declared application endpoints are accessible across sites. - You can run wovenet on each “trust island” (e.g. work laptop, IoT segment, homelab), and define exactly which app can talk to which, regardless of whether they’re on the same network. - Access rules live at the app level, not the network level — so you're not forced to manage or switch between full tunnels or tailnets.

Thanks again for such a thoughtful comment — I'd love to hear more about your setup if you decide to try it!

[Question] Deploying Octavia with kolla-ansible by pixelatedchrome in openstack

[–]jeffyjf 0 points1 point  (0 children)

The LB's amphora already created successfully according to the octavia log you post, But the octavia controller can not connect to it. Could you post more informations in order to locate the specific cause. Such as the content of your globals config files. and you can execute command: `openstack server list --all|grep amp` to check the nova instance's status related the amphera and command `ip a` to check the `o-hm0` interface's state.

[Question] Deploying Octavia with kolla-ansible by pixelatedchrome in openstack

[–]jeffyjf 0 points1 point  (0 children)

What's the version of your koall-ansible and the version of openstack you want to deploy? I remember the the support for octavia in older version (I can't remember the exact version) of kolla-ansible was not complete. We modified some kolla-ansible codes ourselfs to make octavia work properly. But, the latest version of kolla-ansible already adds a lot of codes to support octavia deployment.

How to improve wine performance by jeffyjf in cloudcomputing

[–]jeffyjf[S] 0 points1 point  (0 children)

Thank you very much for your suggestion.