Re: outgoing tcp port 25 blocked? how to prove it?

Marco Moock <mm+usenet-es@dorfdsl.de> writes:

On 18.10.2024 um 15:03 Uhr Lesley Esen wrote:
>

%sudo tcptraceroute -n -p 25 srv1.dorfdsl.de
Selected device ena0, address 172.26.5.226, port 25 for outgoing
packets Tracing the path to srv1.dorfdsl.de (82.139.196.13) on TCP
port 80 (http), 30 hops max

>
This traceroute implementation uses -p for the source port.
Dest is 80, so you check the wrong thing. Look at the manpage (I don't
have FreeBSD here) for the destination port to set.

Thanks.  That makes sense.  The output now makes sense.  Completely
blocked right from the first hop.  Perhaps AWS did not actually unblock
outbound tcp 25; perhaps they unblocked only inbound tcp 25.

%tcptraceroute -n srv1.dorfdsl.de 25
Selected device ena0, address 172.26.5.226, port 22831 for outgoing packets
Tracing the path to srv1.dorfdsl.de (82.139.196.13) on TCP port 25 (smtp), 30 hops max
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
Destination not reached
%