Java DatagramSocket da SOCKS5 UDP Relay

Buƙatarka ta Java HTTP tana aiki ta SOCKS, amma fasalin UDP har yanzu yana aika zirga-zirga kai tsaye ko ya kasa. Saita kaddarorin SOCKS na JVM bai ba DatagramSocket aiwatar da SOCKS5 UDP ba.

API ɗin DatagramSocket yana aika da karɓar datagram da aka yi wa adireshin wuraren ƙarshen cibiyar sadarwa. Hanyarsa ta connect() tana zaɓar abokin aiki don wannan socket. Ba ta yin tattaunawar SOCKS da abokin aikin.

Hanyar SOCKS5 UDP tana buƙatar ƙarin aiki

SOCKS5 yana bayyana haɗin UDP da aka kafa a kan haɗin sarrafawa na TCP. Sannan abokin ciniki yana musayar datagram ɗin da aka lulluɓe da adireshin relay ɗin da proxy ɗin ya bayar. Kowace saƙon da aka lulluɓe yana bayyana inda za a kai shi. Aiwatar da abokin ciniki yana buƙatar sarrafa wannan tsarin da kuma tsawon rayuwar haɗin sarrafawa.

Nuna wani socket na UDP na yau da kullum zuwa tashar saurarar TCP ta proxy ɗin yana tsallake waɗannan matakai. Aika datagram ɗin albarkatun ka kai tsaye zuwa wannan adireshin ba shine maye gurbin haɗin ba.

Zaɓi ɗakin karatu ko fasalin aikace-aikace da ke goyan bayan relay ɗin SOCKS5 UDP a fili, kuma tabbatar da cibiyar sadarwa ma tana goyan bayansa. Ɗakin karatu da ke tallata goyon bayan SOCKS na iya aiwatar da TCP CONNECT kawai. Ƙayyadaddun ka'idar suna bambanta umarnin.

Relay ɗin UDP ma yana buƙatar hanya mai amfani

Haɗin TCP mai nasara zuwa proxy ɗin yana kafa hanyar sarrafawa kawai. Ganuwar wuta ko halin NAT na iya har yanzu tsoma baki da datagram ɗin da aka aika zuwa relay ɗin. Tattara wurin ƙarshen relay ɗin da aka mayar da kowane kuskuren relay kafin ka yanke shawarar cewa inda aikace-aikacen zai je ba ya kan layi.

A ƙarshe, goyon bayan jigilar SOCKS ba ya ƙara tabbacin isarwa ga UDP. Lokutan ƙarewa na aikace-aikacenka da kansu, magance asara da iyakokin girman saƙo har yanzu suna aiki bayan hanyar ta canza.