RFC 1918 usage in Internet routes - was: Re: Swinog Post RFC1918 IP's on BBCS and Cable based Services - swinog

16 Aug 2016


      Hello Sunrise,
many thanks for your (anonymous) feedback.
<Offtopic>
Ok, I have not seen this other discussion - and simply I do NOT want to
start this "relegious" discussion about it.
For me personally it is "bad behaviour" to use RFC1918 in internet public
based services / routes.
For sure others CAN do, because it is not strictly forbidden.
This is for me also a general "problem" according RFC's:
what is "MUST" and what is "SHOULD"....
So I stop it here.
</Offtopic>
Back to my case:
Here see the traces which use RFC1918 in your backbone.
So you assign it ! Or may send me an introduction why I am wrong.
May I missed something.
Many thanks in advance,
Best Regards
Stephan
remark:
192.168.12.254 is your CPE / Fritzbox
/root: traceroute local.ch
traceroute to local.ch (185.101.119.163), 64 hops max, 40 byte packets
 1  192.168.12.254 (192.168.12.254)  0.826 ms  0.650 ms  0.559 ms
 2  10.136.71.241 (10.136.71.241)  18.020 ms  18.421 ms  18.051 ms
 3  172.16.19.146 (172.16.19.146)  22.824 ms  22.594 ms  20.392 ms
 4  172.16.19.145 (172.16.19.145)  20.397 ms  23.046 ms  22.561 ms
 5  194.230.108.185 (194.230.108.185)  18.058 ms  19.911 ms  19.526 ms
 6  * * *
 7  * * *
 8  oer02pe05.ge1-0-19.bb.sunrise.net (212.161.250.138)  20.847 ms
    oer02pe05.ge1-0-0.bb.sunrise.net (212.161.250.134)  22.801 ms  22.368 ms
 9  195.141.229.234 (195.141.229.234)  22.636 ms  22.517 ms  22.724 ms
10  * * *
11  * * *
(snip)
/root: traceroute -I local.ch
traceroute to local.ch (185.101.119.163), 64 hops max, 48 byte packets
 1  192.168.12.254 (192.168.12.254)  0.682 ms  0.543 ms  0.506 ms
 2  10.136.71.241 (10.136.71.241)  18.382 ms  20.533 ms  17.602 ms
 3  172.16.19.146 (172.16.19.146)  22.372 ms  22.011 ms  22.478 ms
 4  172.16.19.145 (172.16.19.145)  21.672 ms  21.664 ms  22.113 ms
 5  194.230.108.185 (194.230.108.185)  19.564 ms  19.532 ms  19.533 ms
 6  * * *
 7  * * *
 8  oer02pe05.ge1-0-19.bb.sunrise.net (212.161.250.138)  22.131 ms  22.230
ms  21.965 ms
 9  195.141.229.234 (195.141.229.234)  21.793 ms  22.007 ms  21.611 ms
10  * * *
11  * * *
(snip)
...
tracert local.ch
Routenverfolgung zu local.ch [185.101.119.163]
über maximal 30 Hops:
  1    <1 ms    <1 ms     1 ms  192.168.12.254
  2    18 ms    17 ms    18 ms  10.136.71.241
  3    23 ms    22 ms    22 ms  172.16.19.146
  4    23 ms    23 ms    22 ms  172.16.19.145
  5    24 ms    20 ms    20 ms  194.230.108.185
  6     *        *        *     Zeitüberschreitung der Anforderung.
  7     *        *        *     Zeitüberschreitung der Anforderung.
  8    87 ms    85 ms    83 ms  oer02pe05.ge1-0-19.bb.sunrise.net
[212.161.250.138]
  9    87 ms    86 ms    79 ms  195.141.229.234
 10     *        *        *     Zeitüberschreitung der Anforderung.
 11     *        *        *     Zeitüberschreitung der Anforderung.
(snip)
Inbound:
(snip)
....
 6  e1-19.c-r1.es34.nine.ch (5.148.160.143)  12.509 ms  11.148 ms  11.102 ms
 7  194.230.36.32 (194.230.36.32)  1.271 ms  1.261 ms  1.214 ms
 8  * * *
 9  zur01are02.et-10-3-0.bb.sunrise.net (195.141.217.155)  1.355 ms  1.225
ms  1.088 ms
10  * * *
11  * * *
12  * * *
13  adsl-84-227-50-245.adslplus.ch (84.227.50.245)  22.971 ms  23.458 ms
23.962 ms
2016-08-16 13:44 GMT+02:00 peering peering@sunrise.net:
...
Hi
Based on the current post at the swinog mailing list and a previous one
which discussed the topic in detail. In fact there is no obligation to not
use private IP Addresses for internet based Services.
Therefore be aware, that the seen RFC1918 Addresses has not been assigned
by sunrise.
Many Thanks for your understanding