AdguardTeam/AdGuardHome

SOCKS proxy

Open

#3,796 opened on Nov 2, 2021

View on GitHub
 (7 comments) (10 reactions) (0 assignees)Go (34,000 stars) (2,333 forks)batch import
P3: Mediumexternal libsfeature requesthelp wanted

Description

Following #3795 as well as #391 and some other issues. This probably will mean that the dnsproxy module will need to implement the proxy first.

Related to #1228.

Contributor guide

Tech stack
go
Domain
backend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Go programming languageSOCKS proxy protocolUnderstanding of DNS and proxy concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Start by familiarizing yourself with the dnsproxy module in the AdGuardHome repository. Read the referenced issues (#3795, #391, #1228) to understand the context and any prior discussions. Research how SOCKS proxies work and consider using existing Go libraries for SOCKS protocol support. The implementation likely involves modifying the proxy logic to route traffic through a SOCKS proxy. Look for any maintainer comments on this issue for additional guidance.
SOCKS proxy · AdguardTeam/AdGuardHome#3796 | Good First Issue