Saita proxy na IPv6 SOCKS5 a cikin Telethon 1.45

Yi amfani da backend ɗin python-socks da Telethon ya rubuta don literal ɗin proxy na IPv6 kuma ka bambanta wannan mai sauraro da zaɓin Telegram da use_ipv6 ke yi.

Proxy na iya saurare a kan IPv6 yayin da yake ɗaukar haɗi zuwa uwar garken Telegram a wata iyali ta adireshi. Ka ɗauki ƙarshen proxy da ƙarshen Telegram daban.

Don Telethon 1.45, idan akwai dogaro da aka rubuta python-socks[asyncio] a cikin muhallin aikace-aikacen:

from telethon import TelegramClient

client = TelegramClient(
    'existing-session', api_id, api_hash,
    proxy={
        'proxy_type': 'socks5',
        'addr': '2001:db8::10',
        'port': 1080,
        'rdns': True,
    },
)

Ka maye gurbin adireshin IPv6 da tashar jiragen ruwa na takardar da ainihin mai sauraro. Filin adireshin literal ne ba tare da baka ba, domin tashar jiragen ruwa riga wata ƙima ce daban. Ana buƙatar baka yayin shigar da adireshin IPv6 cikin authority na URL.

Ka ƙara filayen username da password don asusun SOCKS idan an buƙata. Asusun SOCKS5 ya bambanta da API ID, API hash da session na Telegram.

use_ipv6=True yana sarrafa zaɓin Telethon na adireshin uwar garken Telegram. Ba shi ne maɓallin da ke mai da sunan mai masaukin proxy na IPv6 zuwa ingantaccen adireshin sauraro ba.

Ka duba backend ɗin da ainihin mai fassarar Python ke da shi lokacin da tsohon muhalli ya gaza a kan IPv6. Import a wani muhallin kama-da-wane baya canza wannan tsari. Hanyoyin haɗin proxy na MTProto suna amfani da wata tuple mai ɗauke da sirri; wannan wani tsari ne daban.

Labarai masu alaƙa