FTP over TLS explicit, not working on JioFiber

[Lolita_Magnum]

FTP over TLS via Port 21. I get the following error.

Connection failed.
ERR:: 504 Command not implemented for that parameter

Support has been useless, they instead raise IN ACT Alarm. The engineer has no clue what FTP is.
Is this a known issue? Is there any workaround? Jio says the issue has been raised to NOC, but it doesn't seem like there are gonna bother with it.

 

[ishanjain28]

@Lolita_Magnum Does this work on other ISPs? Looks like this error happens if the target server doesn't support the featureset.

 

[Lolita_Magnum]

Yes, it works just fine with other ISPs. It even works on JioFiber if I use a VPN.
I have already enquired the webmaster about the featureset thing, and the issue is on the ISP end.
Running the same FTP on a nonprivileged port, ie. not 21. Fixes the issue but this causes various of my devices to not be able to use FTP.

 

[JB701]

maybe they are hijacking outgoing ftp port.

try obtaining certificate of the ip on both jio and on diff isp and see if they match.

you can use Binaries - OpenSSLWiki

openssl s_client -starttls ftp -connect test.rebex.net:21 -showcerts

replace test.rebex.net with your ftp server

 

[Lolita_Magnum]

@JB701
White on other ISPs or VPN.

CONNECTED(000001B0)
depth=2 C = US, O = Internet Security Research Group, CN = ISRG Root X1
verify error:num=20:unable to get local issuer certificate
verify return:1
depth=1 C = US, O = Let's Encrypt, CN = R3
verify return:1
depth=0 CN = <server-name-here-redacted>
verify return:1
---
Certificate chain
 0 s:CN = <server-name-here-redacted>
   i:C = US, O = Let's Encrypt, CN = R3
   a: pKEY: rsaEncryption, 2048 (bit); sigalg: RSA-SHA256
   v:NotBefore: May 23 10:41:15 2022 GMT; NotAfter: Aug 21 10:41:14 2022 GMT

On JioFiber

CONNECTED(000001C4)
B0320000:error:0A00010B:SSL routines:ssl3_get_record:wrong version number:ssl\record\ssl3_record.c:355:
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 73 bytes and written 331 bytes
Verification: OK
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
---

I'm guessing this is a hijack, do share, what it means.

 

[JB701]

yes, they are likely have their own ftp server or smthn which they're redirecting all outgoing port 21 connections to (because a connection is indeed being made). their ftp server doesn't have tls so that's why it showed the error for you along with no cert when using openssl.

most likely some error by whoever configured the network.

 

[Lolita_Magnum]

Why are they doing this lol, what did ftp do to them.

 

[havoc]

@Lolita_Magnum what's your plan?
Do you get good international speeds? In comparison to Airtel is it better or not? In terms of routing, international speeds etc.

 

[Lolita_Magnum]

@havoc It's the 999_150Mbps Plan. I'm getting ~155-170Mbps on it.
Peering is better than airtel, but international speeds never hit the maximum capacity of my plan but were always above 100Mbps on Multi and about ~70-90Mbps on single threads, uploads are a lot worse. Airtel has consistent max performance anywhere I could think of.

Single-Threaded Performance on Jio. (150Mbps)

https://ultra.cc/network-tools/speedtest/3abaa785-c561-4dad-ab52-8fd19fb8e484

Single-Threaded Performance on Airtel. (100Mbps)

https://ultra.cc/network-tools/speedtest/4fab303a-a19f-4524-a2d1-2c89931aebca

Single-Threaded when Downloading from Hetzner on Jio.

It does well enough for the Server(s) I use. So, I'm okay with this provider.

The only con is FTP over TLS port 21 is hijacked by Jio. They still have a resolution in progress but I do not see it anytime soon.

 

[lkyrajpurohit]

Now issue resolved by Jio.