Re: internode/iinet/tpg ipv4 bogons in route
Damon Permezel via linux-aus <[email protected]>
| Newsgroups | gmane.linux.australia |
|---|---|
| Message-ID | <O_mZHEevoBl5Y2oal1JeMizCguxGjqmDv7w4jf28tbtPkqJn3-g-JXGH9RrObZe9NdzlPEiT55_a7TnmF7STwygAtC8354aZlzK6wU4tR6k=@zepherin.com> |
That makes sense. With a point-to-point link, you would not want to consume globally routable addresses. Sent with Proton Mail secure email. ------- Original Message ------- On Tuesday, June 14th, 2022 at 14:50, Paul Gear via linux-aus <[email protected]> wrote: > On 14/6/22 14:41, Andrew Pam via linux-aus wrote: > > > On 14/6/22 14:38, Rob Kearey via linux-aus wrote: > > > > > This is incredibly common practice, for all sorts of reasons. > > > > Yes, many ISPs use private addresses internally and they will show up > > as routing hops. Not at all unusual. > > > > Very normal; Internode use 10.0.0.0/8 on their PPPoE concentrators: > > # ip addr ls dev ppp0 > 16: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1492 qdisc > > pfifo_fast state UNKNOWN group default qlen 3 > link/ppp > inet 150.101.178.79 peer 10.20.26.119/32 scope global ppp0 > valid_lft forever preferred_lft forever > inet6 fe80::1106:d625:b69f:eb2a/10 scope link > valid_lft forever preferred_lft forever > > > _______________________________________________ > linux-aus mailing list > [email protected] > http://lists.linux.org.au/mailman/listinfo/linux-aus > > To unsubscribe from this list, send a blank email to > linux-aus-unsubscribe-cunTk1MwBs8iFSDQTTA3OBCuuivNXqWP@public.gmane.org _______________________________________________ linux-aus mailing list [email protected] http://lists.linux.org.au/mailman/listinfo/linux-aus To unsubscribe from this list, send a blank email to linux-aus-unsubscribe-cunTk1MwBs8iFSDQTTA3OBCuuivNXqWP@public.gmane.org
publickey - dap-2nJC94JhJR5Wk0Htik3J/[email protected] - 0x2DD13951.asc
(application/pgp-keys, 721 B)
-----BEGIN PGP PUBLIC KEY BLOCK----- Version: OpenPGP.js v4.10.10 Comment: https://openpgpjs.org xjMEYDF6TBYJKwYBBAHaRw8BAQdA5/JsHmrrULLsuThgA6aZNNj0FI82TO32 s/a3IHvZFT3NI2RhcEB6ZXBoZXJpbi5jb20gPGRhcEB6ZXBoZXJpbi5jb20+ wo8EEBYKACAFAmAxekwGCwkHCAMCBBUICgIEFgIBAAIZAQIbAwIeAQAhCRBP myeREN9D8xYhBC3ROVGYflxrN8MuqU+bJ5EQ30PzlCIA/2PI8BzZW+OqXOPp 8ATH0sac9n5uMTP0BZqoB55/7N/0AQC7J7nrkbjMFWeAsnC29aGW3hqOoAzF rBchkTGA17avB844BGAxekwSCisGAQQBl1UBBQEBB0CVws4QkocA/AJhL7V1 mIrEWeC7mXX1ubpdk3eATFypfQMBCAfCeAQYFggACQUCYDF6TAIbDAAhCRBP myeREN9D8xYhBC3ROVGYflxrN8MuqU+bJ5EQ30PzJQAA/0RaKDwZsrGX7qjH MG31KNuLe2xaD+Lb0f9Fu+eOYZLAAP9SYA8uRqJspP1XggxYZZRBtP4ZIxMU bSlIigxgz2xNBw== =jm2d -----END PGP PUBLIC KEY BLOCK-----
signature.asc
(application/pgp-signature, 249 B)
-----BEGIN PGP SIGNATURE----- Version: ProtonMail wnUEARYKAAYFAmKoX8IAIQkQT5snkRDfQ/MWIQQt0TlRmH5cazfDLqlPmyeR EN9D822eAP9SvJphI58qjOGOu23X6CUJM2ZcWnmfQ+aKXk+6pl1GJwEAhd5h fFkZqi8rUIgFkWDL2Jw7u4ofy7ho5JeXxQ4uQwA= =LeiI -----END PGP SIGNATURE-----