sshuttle connection drops with TCP Previous Segment not Captured

Open
#677 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
centos

Research direction

The report identifies sshuttle on CentOS 7 and a Wireshark warning, but names no source file, test, or entry point. Start by reproducing the drops and determining whether they originate in sshuttle or the network stack; done would require a confirmed cause and a clearly scoped fix or configuration change.

Written by the indexing model from the issue text.

Description

Hello, Im running sshuttle

sshuttle-0-8.20120810git9ce2fa0.el7.noarch

on Centos 7 x64 servers, routing 3 networks over this connection

network A > network B > network C

on C, I'm getting drops every few minutes, dont see any issues on sshuttle or syslog, (all servers in this setup have same MTU setting on ifaces)

running wireshark on this interface, I see these messages

"TCP previous segment not captured"

image

Wondering if anyone ran into this issue, not sure if this is a sysctl setting or network stack bug on my end.

thank you.

Dominant language
Python
Stars
13.6k
Forks
795
Avg merge
8h 49m
Merged PRs (30d)
12

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sshuttle/sshuttle

All issues in sshuttle/sshuttle

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.