Deutsch English Français Italiano |
<uumhr4$o1bc$1@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!weretis.net!feeder8.news.weretis.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: William Unruh <unruh@invalid.ca> Newsgroups: alt.os.linux.ubuntu,comp.sys.raspberry-pi,alt.os.linux.mageia Subject: Re: Where to get the sources (openconnect) ? Followup-To: alt.os.linux.mageia Date: Thu, 4 Apr 2024 15:43:33 -0000 (UTC) Organization: A noiseless patient Spider Lines: 37 Message-ID: <uumhr4$o1bc$1@dont-email.me> References: <uueuq5$2kqfh$1@dont-email.me> <uuf01e$2lb63$1@dont-email.me> <kiWON.134011$Vrtf.36559@fx39.iad> <uui04k$3f9re$1@dont-email.me> <uukasm$304p$1@dont-email.me> <7ivPN.86565$mMj7.8864@fx01.iad> Injection-Date: Thu, 04 Apr 2024 15:43:33 +0200 (CEST) Injection-Info: dont-email.me; posting-host="c44298ec159bafce9d07f7565fef719d"; logging-data="787820"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX190T/f4tLcvN5R7ibzyhsSZ" User-Agent: slrn/1.0.3 (Linux) Cancel-Lock: sha1:sa+fLJH9V0KFGJPvx4otLsXyK/E= Bytes: 2755 On 2024-04-04, Bud Frede <frede@mouse-potato.com> wrote: > Marco Moock <mm+usenet-es@dorfdsl.de> writes: > >> On 02.04.2024 um 22:16 Uhr William Unruh wrote: >> >>> ?? 192.168.x.x is non-routable. >> >> It is routable, but won't be routed on the internet. >> You can of course route it through a tunnel like here. > > I always say that the RFC 1918 addresses are "not normally publicly > routed." :-) > > As you say, they definitely _are_ routable, or a whole lot of home and > corporate networks would not be functional. The key word is "publicly". Ie, once you get away from directly attached networks (or internal routers you have specially set up within your organization) and some outside router needs to be involved to get the packet from here to there, then that router has no idea which of the millions of networks with 192.168. to send the packet to. In the case in question, there are two networks with the same 192.168. network addresses. As mentioned the locally attached network should get the nod. The claim is that it is not. Of course this is going by tun to remote vpn. So if the local 192.168. addresses are being set up so that those packets still get delivered through tun, then the "localy attached network" could well be the remote one. Answer, tell your local machine to deliver all 192.168 stuff not to tun but to a local router which knows about your local 192.168. > > I saw a video not too long ago that pointed out that the use of these > addresses and NAT was made widespread by the Cisco PIX. It was a pretty > interesting look back at something new that now seems commonplace and > ordinary. > >