Samo ulećem da potvrdim da na SBB-u ne radi Sputnik news, a zašto i kako - ne znam.
Na Telekomu radi.
Telekom:
PING rs.sputniknews.com (178.248.237.242): 56 data bytes
Reply from 178.248.237.242: bytes=56 ttl=58 time=75.6ms seq=0
Reply from 178.248.237.242: bytes=56 ttl=58 time=73.6ms seq=1
Reply from 178.248.237.242: bytes=56 ttl=58 time=73.8ms seq=2
Reply from 178.248.237.242: bytes=56 ttl=58 time=79.8ms seq=3
--- rs.sputniknews.com ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 73.6/75.7/79.8 ms
traceroute to rs.sputniknews.com (178.248.237.242), 30 hops max, 38 byte packets[IPV4-ICMP]
1 100.71.128.1 (100.71.128.1) 16.720 ms 21.431 ms 19.695 ms
2 212.200.178.209 (212.200.178.209) 19.964 ms 19.590 ms 19.721 ms
3 192.168.26.17 (192.168.26.17) 19.741 ms 19.798 ms 19.538 ms
4 212.200.13.114 (212.200.13.114) 18.815 ms 20.329 ms 19.411 ms
5 212.200.5.38 (212.200.5.38) 39.740 ms 39.568 ms 39.869 ms
6 109.92.231.197 (109.92.231.197) 79.565 ms 79.935 ms 79.400 ms
7 178.248.237.242 (178.248.237.242) 79.733 ms 79.703 ms 73.685 ms
Traceroute Complete.
curl -I -v
https://rs.sputniknews.com
* Trying 178.248.237.242:443...
* TCP_NODELAY set
* Connected to rs.sputniknews.com (178.248.237.242) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
* ALPN, server accepted to use http/1.1
* Server certificate:
* subject: C=RU; ST=Moskva; O=Russia Today; OU=IT; CN=*.sputniknews.com
* start date: Oct 6 00:00:00 2021 GMT
* expire date: Oct 22 23:59:59 2022 GMT
* subjectAltName: host "rs.sputniknews.com" matched cert's "*.sputniknews.com"
* issuer: C=RU; ST=Moscow; L=Moscow; O=RU-Center (\U0417\U0410\U041E \U0420\U0435\U0433\U0438\U043E\U043D\U0430\U043B\U044C\U043D\U044B\U0439 \U0421\U0435\U0442\U0435\U0432\U043E\U0439 \U0418\U043D\U0444\U043E\U0440\U043C\U0430\U0446\U0438\U043E\U043D\U043D\U044B\U0439 \U0426\U0435\U043D\U0442\U0440); CN=RU-CENTER High Assurance Services CA 2
* SSL certificate verify ok.
> HEAD / HTTP/1.1
> Host: rs.sputniknews.com
> User-Agent: curl/7.68.0
> Accept: */*
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< Server: QRATOR
Server: QRATOR
< Date: Sun, 27 Mar 2022 20:02:48 GMT
Date: Sun, 27 Mar 2022 20:02:48 GMT
< Content-Type: text/html; charset=utf-8
Content-Type: text/html; charset=utf-8
< Connection: keep-alive
Connection: keep-alive
< Keep-Alive: timeout=15
Keep-Alive: timeout=15
< Set-Cookie: sputnik_rs=6240c2e8cd2ab09c1c877ef0; expires=Wed, 26-Mar-2025 20:02:48 GMT; path=/; domain=.rs.sputniknews.com; HttpOnly
Set-Cookie: sputnik_rs=6240c2e8cd2ab09c1c877ef0; expires=Wed, 26-Mar-2025 20:02:48 GMT; path=/; domain=.rs.sputniknews.com; HttpOnly
< Expires: Thu, 19 Nov 1981 08:52:00 GMT
Expires: Thu, 19 Nov 1981 08:52:00 GMT
< Cache-Control: public
Cache-Control: public
< Pragma: no-cache
Pragma: no-cache
< Set-Cookie: ab_subscriber=a; expires=Mon, 27-Mar-2023 20:02:48 GMT; path=/; domain=.rs.sputniknews.com
Set-Cookie: ab_subscriber=a; expires=Mon, 27-Mar-2023 20:02:48 GMT; path=/; domain=.rs.sputniknews.com
<
* Connection #0 to host rs.sputniknews.com left intact
SBB:
PING rs.sputniknews.com (178.248.237.242): 56 data bytes
64 bytes from 178.248.237.242: seq=0 ttl=56 time=42.146 ms
64 bytes from 178.248.237.242: seq=1 ttl=56 time=40.122 ms
64 bytes from 178.248.237.242: seq=2 ttl=56 time=40.650 ms
64 bytes from 178.248.237.242: seq=3 ttl=56 time=39.856 ms
64 bytes from 178.248.237.242: seq=4 ttl=56 time=39.508 ms
--- rs.sputniknews.com ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 39.508/40.456/42.146 ms
traceroute rs.sputniknews.com
traceroute to rs.sputniknews.com (178.248.237.242), 30 hops max, 38 byte packets
1 192.168.0.1 (192.168.0.1) 0.427 ms 0.499 ms 0.353 ms
2 cable-178-149-120-1.dynamic.sbb.rs (178.149.120.1) 12.643 ms 16.152 ms 11.193 ms
3 po-he-m-1-po3.sbb.rs (89.216.4.228) 18.903 ms 16.838 ms 17.377 ms
4 bg-ne-m-0-be113.sbb.rs (89.216.6.168) 13.500 ms 18.423 ms 16.306 ms
5 bg-tp-r-1-hg7-1.sbb.rs (89.216.5.228) 29.286 ms 22.999 ms 22.195 ms
6 5-2-1.ear1.Budapest1.Level3.net (212.133.21.229) 21.873 ms 25.932 ms 23.933 ms
7 * * *
8 highloadlab-ic332444-ffm-b4.ip.twelve99-cust.net (80.239.160.193) 42.301 ms 34.397 ms 32.953 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17^C
Telekom BGP:
flags: * = Valid, > = Selected, I = via IBGP, A = Announced, S = Stale
origin: i = IGP, e = EGP, ? = Incomplete
flags destination gateway lpref med aspath origin
I 178.248.236.0/23 212.200.5.9 85 0 197068 i
success.
SBB BGP:
show ip bgp 178.248.237.242
BGP routing table entry for 178.248.236.0/23
Paths: (3 available, best #1, table Default-IP-Routing-Table)
Not advertised to any peer
3356 197068 197068 197068
212.133.21.229 (metric 3) from 89.216.7.253 (89.216.7.253)
Origin IGP, metric 0, localpref 100, valid, internal, best
Community: 31042:10100
Last update: Wed Mar 23 01:22:14 2022
1299 197068 197068 197068
62.115.162.68 (metric 3) from 89.216.15.205 (89.216.15.205)
Origin IGP, localpref 100, valid, internal
Community: 31042:10100
Last update: Wed Mar 23 01:21:35 2022
1299 197068 197068 197068
213.248.99.157 (metric 3) from 89.216.15.193 (89.216.15.193)
Origin IGP, localpref 100, valid, internal
Community: 31042:10100
Last update: Wed Mar 23 01:21:35 2022
Deluje mi da je problem peering, ali nisam uspeo da ukapiram koja je bitna razlika između SBB-a i Telekom-a na tu temu.