Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.misc > #89224 > unrolled thread

Multi-Networking in Linux - Multiple Subnets

Started byc186282 <c186282@nnada.net>
First post2026-07-29 23:23 -0400
Last post2026-07-30 13:48 +0200
Articles 16 on this page of 116 — 15 participants

Back to article view | Back to comp.os.linux.misc

Contents

  Multi-Networking in Linux - Multiple Subnets c186282 <c186282@nnada.net> - 2026-07-29 23:23 -0400
    Re: Multi-Networking in Linux - Multiple Subnets rbowman <bowman@montana.com> - 2026-07-30 04:14 +0000
      Re: Multi-Networking in Linux - Multiple Subnets c186282 <c186282@nnada.net> - 2026-07-30 23:38 -0400
        Re: Multi-Networking in Linux - Multiple Subnets rbowman <bowman@montana.com> - 2026-07-31 05:31 +0000
        Re: Multi-Networking in Linux - Multiple Subnets Richard Kettlewell <invalid@invalid.invalid> - 2026-07-31 09:44 +0100
          Re: Multi-Networking in Linux - Multiple Subnets The Natural Philosopher <tnp@invalid.invalid> - 2026-07-31 12:19 +0100
          Re: Multi-Networking in Linux - Multiple Subnets Rich <rich@example.invalid> - 2026-08-04 03:52 +0000
            Re: Multi-Networking in Linux - Multiple Subnets c186282 <c186282@nnada.net> - 2026-08-04 00:58 -0400
              Re: Multi-Networking in Linux - Multiple Subnets Andy Burns <usenet@andyburns.uk> - 2026-08-04 08:24 +0100
              Re: Multi-Networking in Linux - Multiple Subnets The Natural Philosopher <tnp@invalid.invalid> - 2026-08-04 11:21 +0100
    Re: Multi-Networking in Linux - Multiple Subnets "Carlos E. R." <robin_listas@es.invalid> - 2026-07-30 12:37 +0200
      Re: Multi-Networking in Linux - Multiple Subnets Marc Haber <mh+usenetspam2616@zugschl.us> - 2026-07-30 13:42 +0200
        Re: Multi-Networking in Linux - Multiple Subnets "Carlos E. R." <robin_listas@es.invalid> - 2026-07-30 13:58 +0200
          Re: Multi-Networking in Linux - Multiple Subnets Robert Heller <heller@deepsoft.com> - 2026-07-30 12:14 +0000
            Re: Multi-Networking in Linux - Multiple Subnets "Carlos E. R." <robin_listas@es.invalid> - 2026-07-31 13:36 +0200
          Re: Multi-Networking in Linux - Multiple Subnets The Natural Philosopher <tnp@invalid.invalid> - 2026-07-30 13:25 +0100
            Re: Multi-Networking in Linux - Multiple Subnets "Carlos E. R." <robin_listas@es.invalid> - 2026-07-31 13:37 +0200
          Re: Multi-Networking in Linux - Multiple Subnets Marc Haber <mh+usenetspam2616@zugschl.us> - 2026-07-30 18:43 +0200
            Re: Multi-Networking in Linux - Multiple Subnets rbowman <bowman@montana.com> - 2026-07-30 19:22 +0000
              Re: Multi-Networking in Linux - Multiple Subnets Marc Haber <mh+usenetspam2616@zugschl.us> - 2026-07-30 21:53 +0200
                Re: Multi-Networking in Linux - Multiple Subnets rbowman <bowman@montana.com> - 2026-07-31 05:08 +0000
                  Re: Multi-Networking in Linux - Multiple Subnets c186282 <c186282@nnada.net> - 2026-07-31 01:16 -0400
                    Re: Multi-Networking in Linux - Multiple Subnets rbowman <bowman@montana.com> - 2026-07-31 08:00 +0000
              Re: Multi-Networking in Linux - Multiple Subnets Robert Heller <heller@deepsoft.com> - 2026-07-30 20:07 +0000
                Re: Multi-Networking in Linux - Multiple Subnets rbowman <bowman@montana.com> - 2026-07-31 05:14 +0000
            Re: Multi-Networking in Linux - Multiple Subnets "Carlos E. R." <robin_listas@es.invalid> - 2026-07-31 13:38 +0200
              Re: Multi-Networking in Linux - Multiple Subnets The Natural Philosopher <tnp@invalid.invalid> - 2026-07-31 12:46 +0100
                Re: Multi-Networking in Linux - Multiple Subnets "Carlos E. R." <robin_listas@es.invalid> - 2026-07-31 13:57 +0200
              Re: Multi-Networking in Linux - Multiple Subnets - Movistar "docs" "Carlos E. R." <robin_listas@es.invalid> - 2026-07-31 14:25 +0200
          Re: Multi-Networking in Linux - Multiple Subnets Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-30 21:18 +0000
            Re: Multi-Networking in Linux - Multiple Subnets c186282 <c186282@nnada.net> - 2026-07-30 23:50 -0400
              Re: Multi-Networking in Linux - Multiple Subnets Robert Riches <spamtrap42@jacob21819.net> - 2026-07-31 04:06 +0000
                Re: Multi-Networking in Linux - Multiple Subnets c186282 <c186282@nnada.net> - 2026-07-31 00:34 -0400
                  Re: Multi-Networking in Linux - Multiple Subnets "Carlos E. R." <robin_listas@es.invalid> - 2026-07-31 13:50 +0200
                    Re: Multi-Networking in Linux - Multiple Subnets Marc Haber <mh+usenetspam2616@zugschl.us> - 2026-07-31 14:51 +0200
                      Re: Multi-Networking in Linux - Multiple Subnets The Natural Philosopher <tnp@invalid.invalid> - 2026-07-31 14:37 +0100
                      Re: Multi-Networking in Linux - Multiple Subnets "Carlos E. R." <robin_listas@es.invalid> - 2026-08-01 14:11 +0200
                        Re: Multi-Networking in Linux - Multiple Subnets Marc Haber <mh+usenetspam2616@zugschl.us> - 2026-08-01 16:49 +0200
                          Re: Multi-Networking in Linux - Multiple Subnets The Natural Philosopher <tnp@invalid.invalid> - 2026-08-01 16:49 +0100
                            Re: Multi-Networking in Linux - Multiple Subnets rbowman <bowman@montana.com> - 2026-08-01 19:14 +0000
                              Re: Multi-Networking in Linux - Multiple Subnets The Natural Philosopher <tnp@invalid.invalid> - 2026-08-02 10:52 +0100
                                Re: Multi-Networking in Linux - Multiple Subnets rbowman <bowman@montana.com> - 2026-08-02 20:32 +0000
                                  Re: Multi-Networking in Linux - Multiple Subnets The Natural Philosopher <tnp@invalid.invalid> - 2026-08-03 12:03 +0100
                            Re: Multi-Networking in Linux - Multiple Subnets "Carlos E. R." <robin_listas@es.invalid> - 2026-08-01 22:57 +0200
                        Re: Multi-Networking in Linux - Multiple Subnets Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-01 23:43 +0000
                          Re: Multi-Networking in Linux - Multiple Subnets "Carlos E. R." <robin_listas@es.invalid> - 2026-08-02 03:48 +0200
                            Re: Multi-Networking in Linux - Multiple Subnets c186282 <c186282@nnada.net> - 2026-08-01 23:53 -0400
                              Re: Multi-Networking in Linux - Multiple Subnets The Natural Philosopher <tnp@invalid.invalid> - 2026-08-02 11:00 +0100
                            Re: Multi-Networking in Linux - Multiple Subnets Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-02 03:56 +0000
                              Re: Multi-Networking in Linux - Multiple Subnets "Carlos E. R." <robin_listas@es.invalid> - 2026-08-02 14:13 +0200
                                Re: Multi-Networking in Linux - Multiple Subnets The Natural Philosopher <tnp@invalid.invalid> - 2026-08-02 14:55 +0100
                                  Re: Multi-Networking in Linux - Multiple Subnets c186282 <c186282@nnada.net> - 2026-08-02 23:11 -0400
                                    Re: Multi-Networking in Linux - Multiple Subnets rbowman <bowman@montana.com> - 2026-08-03 16:48 +0000
                                Re: Multi-Networking in Linux - Multiple Subnets Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-02 23:02 +0000
                                  Re: Multi-Networking in Linux - Multiple Subnets "Carlos E. R." <robin_listas@es.invalid> - 2026-08-03 03:05 +0200
            Re: Multi-Networking in Linux - Multiple Subnets "Carlos E. R." <robin_listas@es.invalid> - 2026-07-31 13:43 +0200
              Re: Multi-Networking in Linux - Multiple Subnets The Natural Philosopher <tnp@invalid.invalid> - 2026-07-31 12:50 +0100
                Re: Multi-Networking in Linux - Multiple Subnets "Carlos E. R." <robin_listas@es.invalid> - 2026-07-31 14:00 +0200
              Re: Multi-Networking in Linux - Multiple Subnets Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-31 22:52 +0000
                Re: Multi-Networking in Linux - Multiple Subnets c186282 <c186282@nnada.net> - 2026-07-31 23:45 -0400
                Re: Multi-Networking in Linux - Multiple Subnets Richard Kettlewell <invalid@invalid.invalid> - 2026-08-01 12:22 +0100
                  Re: Multi-Networking in Linux - Multiple Subnets "Carlos E. R." <robin_listas@es.invalid> - 2026-08-01 14:15 +0200
                    Re: Multi-Networking in Linux - Multiple Subnets The Natural Philosopher <tnp@invalid.invalid> - 2026-08-01 14:09 +0100
                  Re: Multi-Networking in Linux - Multiple Subnets The Natural Philosopher <tnp@invalid.invalid> - 2026-08-01 14:08 +0100
                    Re: Multi-Networking in Linux - Multiple Subnets rbowman <bowman@montana.com> - 2026-08-01 19:11 +0000
        Re: Multi-Networking in Linux - Multiple Subnets Robert Heller <heller@deepsoft.com> - 2026-07-30 11:59 +0000
          Re: Multi-Networking in Linux - Multiple Subnets The Natural Philosopher <tnp@invalid.invalid> - 2026-07-30 13:32 +0100
          Re: Multi-Networking in Linux - Multiple Subnets Marc Haber <mh+usenetspam2616@zugschl.us> - 2026-07-30 18:44 +0200
            Re: Multi-Networking in Linux - Multiple Subnets The Natural Philosopher <tnp@invalid.invalid> - 2026-07-30 18:06 +0100
              Re: Multi-Networking in Linux - Multiple Subnets Marc Haber <mh+usenetspam2616@zugschl.us> - 2026-07-30 21:54 +0200
          Re: Multi-Networking in Linux - Multiple Subnets c186282 <c186282@nnada.net> - 2026-07-30 23:48 -0400
          Re: Multi-Networking in Linux - Multiple Subnets Marc Haber <mh+usenetspam2616@zugschl.us> - 2026-07-31 08:15 +0200
            Re: Multi-Networking in Linux - Multiple Subnets Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-31 06:53 +0000
              Re: Multi-Networking in Linux - Multiple Subnets Marc Haber <mh+usenetspam2616@zugschl.us> - 2026-07-31 14:52 +0200
            Re: Multi-Networking in Linux - Multiple Subnets The Natural Philosopher <tnp@invalid.invalid> - 2026-07-31 12:10 +0100
              Re: Multi-Networking in Linux - Multiple Subnets Marc Haber <mh+usenetspam2616@zugschl.us> - 2026-07-31 15:04 +0200
                Re: Multi-Networking in Linux - Multiple Subnets The Natural Philosopher <tnp@invalid.invalid> - 2026-07-31 14:42 +0100
                  Re: Multi-Networking in Linux - Multiple Subnets Marc Haber <mh+usenetspam2616@zugschl.us> - 2026-07-31 16:24 +0200
          Re: Multi-Networking in Linux - Multiple Subnets "Carlos E. R." <robin_listas@es.invalid> - 2026-07-31 14:04 +0200
            Re: Multi-Networking in Linux - Multiple Subnets Marc Haber <mh+usenetspam2616@zugschl.us> - 2026-07-31 15:06 +0200
              Re: Multi-Networking in Linux - Multiple Subnets The Natural Philosopher <tnp@invalid.invalid> - 2026-07-31 14:42 +0100
                Re: Multi-Networking in Linux - Multiple Subnets Marc Haber <mh+usenetspam2616@zugschl.us> - 2026-07-31 16:25 +0200
                  Re: Multi-Networking in Linux - Multiple Subnets The Natural Philosopher <tnp@invalid.invalid> - 2026-07-31 15:34 +0100
        Re: Multi-Networking in Linux - Multiple Subnets The Natural Philosopher <tnp@invalid.invalid> - 2026-07-30 13:24 +0100
          Re: Multi-Networking in Linux - Multiple Subnets Marc Haber <mh+usenetspam2616@zugschl.us> - 2026-07-31 08:16 +0200
            Re: Multi-Networking in Linux - Multiple Subnets The Natural Philosopher <tnp@invalid.invalid> - 2026-07-31 12:15 +0100
        Re: Multi-Networking in Linux - Multiple Subnets Andy Burns <usenet@andyburns.uk> - 2026-07-30 14:53 +0100
          Re: Multi-Networking in Linux - Multiple Subnets The Natural Philosopher <tnp@invalid.invalid> - 2026-07-30 14:59 +0100
            Re: Multi-Networking in Linux - Multiple Subnets Andy Burns <usenet@andyburns.uk> - 2026-07-30 15:06 +0100
              Re: Multi-Networking in Linux - Multiple Subnets Rich <rich@example.invalid> - 2026-07-30 14:35 +0000
          Re: Multi-Networking in Linux - Multiple Subnets Marc Haber <mh+usenetspam2616@zugschl.us> - 2026-07-30 18:46 +0200
        Re: Multi-Networking in Linux - Multiple Subnets c186282 <c186282@nnada.net> - 2026-07-30 23:45 -0400
        Re: Multi-Networking in Linux - Multiple Subnets "Carlos E. R." <robin_listas@es.invalid> - 2026-07-31 13:51 +0200
          Re: Multi-Networking in Linux - Multiple Subnets "Stanislav N. aka pztrn" <no@email.please> - 2026-07-31 17:28 +0500
          Re: Multi-Networking in Linux - Multiple Subnets Marc Haber <mh+usenetspam2616@zugschl.us> - 2026-07-31 15:07 +0200
          Re: Multi-Networking in Linux - Multiple Subnets Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-31 22:55 +0000
          Re: Multi-Networking in Linux - Multiple Subnets Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2026-08-01 15:49 +0300
            Re: Multi-Networking in Linux - Multiple Subnets "Carlos E. R." <robin_listas@es.invalid> - 2026-08-01 15:16 +0200
              Re: Multi-Networking in Linux - Multiple Subnets Marc Haber <mh+usenetspam2616@zugschl.us> - 2026-08-01 16:52 +0200
                Re: Multi-Networking in Linux - Multiple Subnets The Natural Philosopher <tnp@invalid.invalid> - 2026-08-01 16:52 +0100
                  Re: Multi-Networking in Linux - Multiple Subnets "Carlos E. R." <robin_listas@es.invalid> - 2026-08-01 23:04 +0200
                    Re: Multi-Networking in Linux - Multiple Subnets Marc Haber <mh+usenetspam2616@zugschl.us> - 2026-08-02 06:00 +0200
                      Re: Multi-Networking in Linux - Multiple Subnets c186282 <c186282@nnada.net> - 2026-08-02 00:14 -0400
                        Re: Multi-Networking in Linux - Multiple Subnets Marc Haber <mh+usenetspam2616@zugschl.us> - 2026-08-02 08:40 +0200
                          Re: Multi-Networking in Linux - Multiple Subnets The Natural Philosopher <tnp@invalid.invalid> - 2026-08-02 10:55 +0100
                          Re: Multi-Networking in Linux - Multiple Subnets Jim Jackson <jj@franjam.org.uk> - 2026-08-03 17:15 +0000
                        Re: Multi-Networking in Linux - Multiple Subnets The Natural Philosopher <tnp@invalid.invalid> - 2026-08-02 10:54 +0100
                      Re: Multi-Networking in Linux - Multiple Subnets Andy Burns <usenet@andyburns.uk> - 2026-08-02 11:33 +0100
                        Re: Multi-Networking in Linux - Multiple Subnets Nuno Silva <nunojsilva@invalid.invalid> - 2026-08-02 14:42 +0100
                          Re: Multi-Networking in Linux - Multiple Subnets Andy Burns <usenet@andyburns.uk> - 2026-08-02 15:43 +0100
                            Re: Multi-Networking in Linux - Multiple Subnets The Natural Philosopher <tnp@invalid.invalid> - 2026-08-02 20:27 +0100
                  Re: Multi-Networking in Linux - Multiple Subnets Marc Haber <mh+usenetspam2616@zugschl.us> - 2026-08-02 05:59 +0200
                    Re: Multi-Networking in Linux - Multiple Subnets The Natural Philosopher <tnp@invalid.invalid> - 2026-08-02 11:02 +0100
      Re: Multi-Networking in Linux - Multiple Subnets c186282 <c186282@nnada.net> - 2026-07-30 23:43 -0400
        Re: Multi-Networking in Linux - Multiple Subnets "Carlos E. R." <robin_listas@es.invalid> - 2026-07-31 14:28 +0200
    Re: Multi-Networking in Linux - Multiple Subnets Marc Haber <mh+usenetspam2616@zugschl.us> - 2026-07-30 13:48 +0200

Page 6 of 6 — ← Prev page 1 2 3 4 5 [6]

#89411

From"Carlos E. R." <robin_listas@es.invalid>
Date2026-08-01 23:04 +0200
Message-ID<nd75arF4quU5@mid.individual.net>
In reply to#89396
On 2026-08-01 17:52, The Natural Philosopher wrote:
> On 01/08/2026 15:52, Marc Haber wrote:
>> "Carlos E. R." <robin_listas@es.invalid> wrote:
>>> So, stop saying that `192.168.0.0/16` is wrong, or that 172.16/12
>>> is wrong.
>>
>> I never did.
>>
>> I said that it is stupid to use that for a single network.
>>
>> You're supposed to cut yourself an appropriately sized piece from 
>> those ranges,
> 
> Says who?
> 
>> and hope that you'll never have to connect to a network that uses the
>> same piece,
> 
> Hardly likely in a soho/domestic situation
> 
>> and that you can reduce that probability
> 
> which is already infinitesimal
> 
>> by choosing small pieces and neither the obvious ones nor the ones
>> you know that everyone else uses.
>>
> Since its a private network there is no everyone else
> 
>> Greetings Marc
> 

Conceivable, it is possible that at some point in time I might need to 
connect to an VPN. I'll cross that bridge when/if needed.

As it is, I don't see what I can do considering that I absolutely must 
keep the 192.168.1.* range almost intact. I might use a smaller NET, 
like a /18 prefix instead of a /16

-- 
Cheers,
        Carlos E.R.
        ES🇪🇸, EU🇪🇺;

[toc] | [prev] | [next] | [standalone]

#89432

FromMarc Haber <mh+usenetspam2616@zugschl.us>
Date2026-08-02 06:00 +0200
Message-ID<114mfd5$2dmco$1@news1.tnib.de>
In reply to#89411
"Carlos E. R." <robin_listas@es.invalid> wrote:
>As it is, I don't see what I can do considering that I absolutely must 
>keep the 192.168.1.* range almost intact. I might use a smaller NET, 
>like a /18 prefix instead of a /16

/24 is still to big, but still sensible and what most people do.

But you can of course make sure that everybody who takes a look at
your network will immediately know that you're clueless.

I'm done with this part of the discussion.

-- 
----------------------------------------------------------------------------
Marc Haber         |   " Questions are the         | Mailadresse im Header
Rhein-Neckar, DE   |     Beginning of Wisdom "     | 
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 6224 1600402

[toc] | [prev] | [next] | [standalone]

#89435

Fromc186282 <c186282@nnada.net>
Date2026-08-02 00:14 -0400
Message-ID<KR-dnY2VRtXvWfP3nZ2dnZfqnPWdnZ2d@giganews.com>
In reply to#89432
On 8/2/26 00:00, Marc Haber wrote:
> "Carlos E. R." <robin_listas@es.invalid> wrote:
>> As it is, I don't see what I can do considering that I absolutely must
>> keep the 192.168.1.* range almost intact. I might use a smaller NET,
>> like a /18 prefix instead of a /16
> 
> /24 is still to big, but still sensible and what most people do.

   Sorry, but /24 is now TOO SMALL for a lot of
   businesses, and hard to ORGANIZE for smaller
   entities. Workstations, servers, net-connected
   devices, IOT shit ... /24 isn't BIG enough
   anymore.

   But NOT smooth easy way to like make ".0.x"
   and ".1.x" look like one big smooth network.

> But you can of course make sure that everybody who takes a look at
> your network will immediately know that you're clueless.
> 
> I'm done with this part of the discussion.

   Might be a good thing .... :-)

   I'm interested in the DEAD PRACTICAL considerations,
   not "philosophic" or 25-year-old "assumptions".

[toc] | [prev] | [next] | [standalone]

#89441

FromMarc Haber <mh+usenetspam2616@zugschl.us>
Date2026-08-02 08:40 +0200
Message-ID<114moog$2ebrv$1@news1.tnib.de>
In reply to#89435
c186282 <c186282@nnada.net> wrote:
>On 8/2/26 00:00, Marc Haber wrote:
>> "Carlos E. R." <robin_listas@es.invalid> wrote:
>>> As it is, I don't see what I can do considering that I absolutely must
>>> keep the 192.168.1.* range almost intact. I might use a smaller NET,
>>> like a /18 prefix instead of a /16
>> 
>> /24 is still to big, but still sensible and what most people do.
>
>   Sorry, but /24 is now TOO SMALL for a lot of
>   businesses, and hard to ORGANIZE for smaller
>   entities. Workstations, servers, net-connected
>   devices, IOT shit ... /24 isn't BIG enough
>   anymore.

I am talking about people like you who can barely type an IP address
without accidents.

>   But NOT smooth easy way to like make ".0.x"
>   and ".1.x" look like one big smooth network.

/23 or if you insist /20.

No one with a sane mind will run a /18 in a single broadcast domain.

>> I'm done with this part of the discussion.
>
>   Might be a good thing .... :-)
>
>   I'm interested in the DEAD PRACTICAL considerations,
>   not "philosophic" or 25-year-old "assumptions".

I am horrified by the fact that I seem to be the only person with a
networking background here.

-- 
----------------------------------------------------------------------------
Marc Haber         |   " Questions are the         | Mailadresse im Header
Rhein-Neckar, DE   |     Beginning of Wisdom "     | 
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 6224 1600402

[toc] | [prev] | [next] | [standalone]

#89453

FromThe Natural Philosopher <tnp@invalid.invalid>
Date2026-08-02 10:55 +0100
Message-ID<114n47a$ccdc$5@dont-email.me>
In reply to#89441
On 02/08/2026 07:40, Marc Haber wrote:
> I am horrified by the fact that I seem to be the only person with a
> networking background here.

I ran a networking company installing TCP/IP and email over the whole of 
britain for some years.
But I dont suppose that counts


-- 
"The most difficult subjects can be explained to the most slow witted 
man if he has not formed any idea of them already; but the simplest 
thing cannot be made clear to the most intelligent man if he is firmly 
persuaded that he knows already, without a shadow of doubt, what is laid 
before him."

    - Leo Tolstoy

[toc] | [prev] | [next] | [standalone]

#89516

FromJim Jackson <jj@franjam.org.uk>
Date2026-08-03 17:15 +0000
Message-ID<slrn1171j5v.mop.jj@iridium.wf32df>
In reply to#89441
>
> No one with a sane mind will run a /18 in a single broadcast domain.
>

Indeed. In fact I found it quite a handfull running a large IPv4 /22 
with about ~600 active machines on one LAN with IPv4 was quite something.

We were introducing IPv6, but I retired before the traffic was mostly 
IPv6. But IPv6's design can make it possible to run LANs with a lot more 
active machines, as instead of broadcast, it makes use of Multicast services.

[toc] | [prev] | [next] | [standalone]

#89452

FromThe Natural Philosopher <tnp@invalid.invalid>
Date2026-08-02 10:54 +0100
Message-ID<114n44n$ccdc$4@dont-email.me>
In reply to#89435
On 02/08/2026 05:14, c186282 wrote:
> Sorry, but /24 is now TOO SMALL for a lot of
>    businesses, and hard to ORGANIZE for smaller
>    entities. Workstations, servers, net-connected
>    devices, IOT shit ... /24 isn't BIG enough
>    anymore.

It is however about the largest manageable lump of machines on one network

You really don't want broadcasts going to 10,000 machines


-- 
"The most difficult subjects can be explained to the most slow witted 
man if he has not formed any idea of them already; but the simplest 
thing cannot be made clear to the most intelligent man if he is firmly 
persuaded that he knows already, without a shadow of doubt, what is laid 
before him."

    - Leo Tolstoy

[toc] | [prev] | [next] | [standalone]

#89462

FromAndy Burns <usenet@andyburns.uk>
Date2026-08-02 11:33 +0100
Message-ID<nd8klnFcldqU2@mid.individual.net>
In reply to#89432
Marc Haber wrote:

> I'm done with this part of the discussion.

That's the 2nd time you've promised that ...

[toc] | [prev] | [next] | [standalone]

#89469

FromNuno Silva <nunojsilva@invalid.invalid>
Date2026-08-02 14:42 +0100
Message-ID<114nhge$gvl6$3@dont-email.me>
In reply to#89462
On 2026-08-02, Andy Burns wrote:

> Marc Haber wrote:
>
>> I'm done with this part of the discussion.
>
> That's the 2nd time you've promised that ...

Maybe there was a collision in the medium and the first attempt was
aborted. Are we sure the thread is set to full-duplex in a full-duplex
capable medium? And not on a shared medium?

-- 
Nuno Silva

[toc] | [prev] | [next] | [standalone]

#89472

FromAndy Burns <usenet@andyburns.uk>
Date2026-08-02 15:43 +0100
Message-ID<nd93a7Fev4pU1@mid.individual.net>
In reply to#89469
Nuno Silva wrote:

> Andy Burns wrote:
> 
>> Marc Haber wrote:
>>
>>> I'm done with this part of the discussion.
>>
>> That's the 2nd time you've promised that ...
> 
> Maybe there was a collision in the medium and the first attempt was
> aborted. Are we sure the thread is set to full-duplex in a full-duplex
> capable medium? And not on a shared medium?
I think it's more of an impedance mismatch between those who recognise 
that other people have similar levels of knowledge to their own, and 
people who assume their own knowledge is superior to everyone else's.

[toc] | [prev] | [next] | [standalone]

#89475

FromThe Natural Philosopher <tnp@invalid.invalid>
Date2026-08-02 20:27 +0100
Message-ID<114o5ni$o5pq$1@dont-email.me>
In reply to#89472
On 02/08/2026 15:43, Andy Burns wrote:
> I think it's more of an impedance mismatch between those who recognise 
> that other people have similar levels of knowledge to their own, and 
> people who assume their own knowledge is superior to everyone else's.

...whereas in fact it's often far worse...

-- 
"I am inclined to tell the truth and dislike people who lie consistently.
This makes me unfit for the company of people of a Left persuasion, and 
all women"

[toc] | [prev] | [next] | [standalone]

#89431

FromMarc Haber <mh+usenetspam2616@zugschl.us>
Date2026-08-02 05:59 +0200
Message-ID<114mfb5$2dm15$1@news1.tnib.de>
In reply to#89396
The Natural Philosopher <tnp@invalid.invalid> wrote:
>On 01/08/2026 15:52, Marc Haber wrote:
>> "Carlos E. R." <robin_listas@es.invalid> wrote:
>>> So, stop saying that `192.168.0.0/16` is wrong, or that 172.16/12
>>> is wrong.
>> 
>> I never did.
>> 
>> I said that it is stupid to use that for a single network.
>> 
>> You're supposed to cut yourself an appropriately sized piece from 
>> those ranges,
>
>Says who?

Everybody with a remote clue about networking.

-- 
----------------------------------------------------------------------------
Marc Haber         |   " Questions are the         | Mailadresse im Header
Rhein-Neckar, DE   |     Beginning of Wisdom "     | 
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 6224 1600402

[toc] | [prev] | [next] | [standalone]

#89455

FromThe Natural Philosopher <tnp@invalid.invalid>
Date2026-08-02 11:02 +0100
Message-ID<114n4iv$ccdc$7@dont-email.me>
In reply to#89431
On 02/08/2026 04:59, Marc Haber wrote:
> The Natural Philosopher <tnp@invalid.invalid> wrote:
>> On 01/08/2026 15:52, Marc Haber wrote:
>>> "Carlos E. R." <robin_listas@es.invalid> wrote:
>>>> So, stop saying that `192.168.0.0/16` is wrong, or that 172.16/12
>>>> is wrong.
>>>
>>> I never did.
>>>
>>> I said that it is stupid to use that for a single network.
>>>
>>> You're supposed to cut yourself an appropriately sized piece from
>>> those ranges,
>>
>> Says who?
> 
> Everybody with a remote clue about networking.
> 
I don't. And I have more than a remote clue

You are confusing rote learnt rules with technical feasibility and 
individual freedoms

Rules are for the guidance of wise men and the obedience of fools


-- 
“when things get difficult you just have to lie”

― Jean Claud Jüncker

[toc] | [prev] | [next] | [standalone]

#89282

Fromc186282 <c186282@nnada.net>
Date2026-07-30 23:43 -0400
Message-ID<tbicncpMNbd3hPH3nZ2dnZfqnPidnZ2d@giganews.com>
In reply to#89234
On 7/30/26 06:37, Carlos E. R. wrote:
> On 2026-07-30 05:23, c186282 wrote:
>> Normal - you connect yer box to "THE Network",
>> some dot address.
>>
>> But what if you want it to see MULTIPLE subnets ...
>> 192.168.0.x and 192.168.1.x or more ???
> 
> Laicolasse:~ # ifconfig
> eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
>          inet 192.168.2.9  netmask 255.255.0.0  broadcast 192.168.255.255
>          inet6 fe80::f6a8:A:B:C  prefixlen 64  scopeid 0x20<link>
>          ether f4:*:*:*:*:01  txqueuelen 1000  (Ethernet)
>          RX packets 23204  bytes 20795150 (19.8 MiB)
>          RX errors 0  dropped 1  overruns 0  frame 0
>          TX packets 11818  bytes 1882795 (1.7 MiB)
>          TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> 

   Seems hopeful ... I'll try it out ! :-)

   Umm ... is it the "netmask" that makes multi-subnets
   more easily accessible ???

   Don't use IPV6.

> ...
> 
>> Has anybody made this work ? The adapter
>> must not see just ONE subnet, but a LIST
>> of subnets and translate one to another
>> seamlessly.
> 
> Works for me as above :-)

   Encouraging.

   I'll try some experiments.

[toc] | [prev] | [next] | [standalone]

#89337

From"Carlos E. R." <robin_listas@es.invalid>
Date2026-07-31 14:28 +0200
Message-ID<nd3inoFi6v5U7@mid.individual.net>
In reply to#89282
On 2026-07-31 05:43, c186282 wrote:
> On 7/30/26 06:37, Carlos E. R. wrote:
>> On 2026-07-30 05:23, c186282 wrote:
>>> Normal - you connect yer box to "THE Network",
>>> some dot address.
>>>
>>> But what if you want it to see MULTIPLE subnets ...
>>> 192.168.0.x and 192.168.1.x or more ???
>>
>> Laicolasse:~ # ifconfig
>> eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
>>          inet 192.168.2.9  netmask 255.255.0.0  broadcast 192.168.255.255
>>          inet6 fe80::f6a8:A:B:C  prefixlen 64  scopeid 0x20<link>
>>          ether f4:*:*:*:*:01  txqueuelen 1000  (Ethernet)
>>          RX packets 23204  bytes 20795150 (19.8 MiB)
>>          RX errors 0  dropped 1  overruns 0  frame 0
>>          TX packets 11818  bytes 1882795 (1.7 MiB)
>>          TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>>
> 
>    Seems hopeful ... I'll try it out ! :-)
> 
>    Umm ... is it the "netmask" that makes multi-subnets
>    more easily accessible ???
> 
>    Don't use IPV6.
> 
>> ...
>>
>>> Has anybody made this work ? The adapter
>>> must not see just ONE subnet, but a LIST
>>> of subnets and translate one to another
>>> seamlessly.
>>
>> Works for me as above :-)
> 
>    Encouraging.
> 
>    I'll try some experiments.

It is not kosher, but it works for me. It is not multi-subnets, it is a 
bigger net.

> 


-- 
Cheers,
        Carlos E.R.
        ES🇪🇸, EU🇪🇺;

[toc] | [prev] | [next] | [standalone]

#89236

FromMarc Haber <mh+usenetspam2616@zugschl.us>
Date2026-07-30 13:48 +0200
Message-ID<114fdmc$1tsbb$1@news1.tnib.de>
In reply to#89224
c186282 <c186282@nnada.net> wrote:
>Has anybody made this work ?

Of course, hundreds of times. But your intention is not clear, and
your track history doesn't motivate me very much to help.

Which basic networking literature did you already read?

Greetings
Marc

P.S., here my lab router (not anybody needs a network that complex.
neither do I):
|[1/4990]mh@prom:~ $ ip addr
|1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
|    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
|    inet 127.0.0.1/8 scope host lo
|       valid_lft forever preferred_lft forever
|    inet6 ::1/128 scope host noprefixroute 
|       valid_lft forever preferred_lft forever
|2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
|    link/ether 00:0d:b9:41:c9:ec brd ff:ff:ff:ff:ff:ff
|    altname enx000db941c9ec
|    inet6 fe80::20d:b9ff:fe41:c9ec/64 scope link proto kernel_ll 
|       valid_lft forever preferred_lft forever
|3: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
|    link/ether 00:0d:b9:41:c9:ed brd ff:ff:ff:ff:ff:ff
|    altname enx000db941c9ed
|    inet6 fe80::20d:b9ff:fe41:c9ed/64 scope link proto kernel_ll 
|       valid_lft forever preferred_lft forever
|4: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
|    link/ether 00:0d:b9:41:c9:ee brd ff:ff:ff:ff:ff:ff
|    altname enx000db941c9ee
|    inet6 fe80::20d:b9ff:fe41:c9ee/64 scope link proto kernel_ll 
|       valid_lft forever preferred_lft forever
|5: int181: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
|    link/ether d6:90:72:70:53:35 brd ff:ff:ff:ff:ff:ff
|    inet 192.168.181.112/24 brd 192.168.181.255 scope global int181
|       valid_lft forever preferred_lft forever
|    inet 192.168.181.254/32 scope global int181
|       valid_lft forever preferred_lft forever
|    inet6 2a01:238:43fa:bc81::70:100/64 scope global 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::1/64 scope link 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::d490:72ff:fe70:5335/64 scope link proto kernel_ll 
|       valid_lft forever preferred_lft forever
|6: int182: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
|    link/ether 8e:e3:a1:db:0e:ca brd ff:ff:ff:ff:ff:ff
|    inet 192.168.182.254/24 brd 192.168.182.255 scope global int182
|       valid_lft forever preferred_lft forever
|    inet6 2001:16b8:a9ad:bec2::70:100/64 metric 256 scope global dynamic mngtmpaddr 
|       valid_lft 6093sec preferred_lft 2493sec
|    inet6 2a01:238:43fa:bc82::70:100/64 scope global 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::1/64 scope link 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::8ce3:a1ff:fedb:eca/64 scope link proto kernel_ll 
|       valid_lft forever preferred_lft forever
|7: int183: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
|    link/ether 16:3a:85:53:3e:c4 brd ff:ff:ff:ff:ff:ff
|    inet 192.168.183.254/24 brd 192.168.183.255 scope global int183
|       valid_lft forever preferred_lft forever
|    inet6 2001:16b8:a9ad:bec3::70:100/64 metric 256 scope global dynamic mngtmpaddr 
|       valid_lft 6093sec preferred_lft 2493sec
|    inet6 2a01:238:43fa:bc83::70:100/64 scope global 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::1/64 scope link 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::143a:85ff:fe53:3ec4/64 scope link proto kernel_ll 
|       valid_lft forever preferred_lft forever
|8: int184: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
|    link/ether 6e:8c:51:bc:71:c8 brd ff:ff:ff:ff:ff:ff
|    inet 192.168.184.254/24 brd 192.168.184.255 scope global int184
|       valid_lft forever preferred_lft forever
|    inet6 2001:16b8:a9ad:bec4::70:100/64 metric 256 scope global dynamic mngtmpaddr 
|       valid_lft 6093sec preferred_lft 2493sec
|    inet6 2a01:238:43fa:bc84::70:100/64 scope global 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::1/64 scope link 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::6c8c:51ff:febc:71c8/64 scope link proto kernel_ll 
|       valid_lft forever preferred_lft forever
|9: int185: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
|    link/ether e6:67:04:7f:d2:51 brd ff:ff:ff:ff:ff:ff
|    inet 192.168.185.254/24 brd 192.168.185.255 scope global int185
|       valid_lft forever preferred_lft forever
|    inet6 2001:16b8:a9ad:bec5::70:100/64 metric 256 scope global dynamic mngtmpaddr 
|       valid_lft 6093sec preferred_lft 2493sec
|    inet6 2a01:238:43fa:bc85::70:100/64 scope global 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::1/64 scope link 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::e467:4ff:fe7f:d251/64 scope link proto kernel_ll 
|       valid_lft forever preferred_lft forever
|10: int186: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
|    link/ether 92:f0:ec:6c:09:36 brd ff:ff:ff:ff:ff:ff
|    inet 192.168.186.254/24 brd 192.168.186.255 scope global int186
|       valid_lft forever preferred_lft forever
|    inet6 2001:16b8:a9ad:bec6::70:100/64 metric 256 scope global dynamic mngtmpaddr 
|       valid_lft 6093sec preferred_lft 2493sec
|    inet6 2a01:238:43fa:bc86::70:100/64 scope global 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::1/64 scope link 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::90f0:ecff:fe6c:936/64 scope link proto kernel_ll 
|       valid_lft forever preferred_lft forever
|11: int187: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
|    link/ether 7e:71:8b:db:97:7f brd ff:ff:ff:ff:ff:ff
|    inet 192.168.187.254/24 brd 192.168.187.255 scope global int187
|       valid_lft forever preferred_lft forever
|    inet6 2001:16b8:a9ad:bec7::70:100/64 metric 256 scope global dynamic mngtmpaddr 
|       valid_lft 6093sec preferred_lft 2493sec
|    inet6 2a01:238:43fa:bc87::70:100/64 scope global 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::1/64 scope link 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::7c71:8bff:fedb:977f/64 scope link proto kernel_ll 
|       valid_lft forever preferred_lft forever
|12: int188: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
|    link/ether a6:3a:3a:5e:12:be brd ff:ff:ff:ff:ff:ff
|    inet 192.168.188.254/24 brd 192.168.188.255 scope global int188
|       valid_lft forever preferred_lft forever
|    inet6 2001:16b8:a9ad:bec8::70:100/64 metric 256 scope global dynamic mngtmpaddr 
|       valid_lft 6093sec preferred_lft 2493sec
|    inet6 2a01:238:43fa:bc88::70:100/64 scope global 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::1/64 scope link 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::a43a:3aff:fe5e:12be/64 scope link proto kernel_ll 
|       valid_lft forever preferred_lft forever
|13: int189: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
|    link/ether e2:85:3f:b2:47:a4 brd ff:ff:ff:ff:ff:ff
|    inet 192.168.189.254/24 brd 192.168.189.255 scope global int189
|       valid_lft forever preferred_lft forever
|    inet6 2001:16b8:a9ad:bec9::70:100/64 metric 256 scope global dynamic mngtmpaddr 
|       valid_lft 6093sec preferred_lft 2493sec
|    inet6 2a01:238:43fa:bc89::70:100/64 scope global 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::1/64 scope link 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::e085:3fff:feb2:47a4/64 scope link proto kernel_ll 
|       valid_lft forever preferred_lft forever
|14: int191: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
|    link/ether b6:96:e4:95:6f:9c brd ff:ff:ff:ff:ff:ff
|    inet 192.168.191.254/24 brd 192.168.191.255 scope global int191
|       valid_lft forever preferred_lft forever
|    inet6 2a01:238:43fa:bc91::70:100/64 scope global 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::1/64 scope link 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::b496:e4ff:fe95:6f9c/64 scope link proto kernel_ll 
|       valid_lft forever preferred_lft forever
|15: int192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
|    link/ether f6:41:8b:b2:87:59 brd ff:ff:ff:ff:ff:ff
|    inet 192.168.192.254/24 brd 192.168.192.255 scope global int192
|       valid_lft forever preferred_lft forever
|    inet6 2001:16b8:a9ad:bed2::70:100/64 metric 256 scope global dynamic mngtmpaddr 
|       valid_lft 6093sec preferred_lft 2493sec
|    inet6 2a01:238:43fa:bc92::70:100/64 scope global 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::1/64 scope link 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::f441:8bff:feb2:8759/64 scope link proto kernel_ll 
|       valid_lft forever preferred_lft forever
|16: int193: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
|    link/ether fa:7a:1a:45:ac:a2 brd ff:ff:ff:ff:ff:ff
|    inet 192.168.193.254/24 brd 192.168.193.255 scope global int193
|       valid_lft forever preferred_lft forever
|    inet6 2a01:238:43fa:bc93::70:100/64 scope global 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::1/64 scope link 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::f87a:1aff:fe45:aca2/64 scope link proto kernel_ll 
|       valid_lft forever preferred_lft forever
|17: int194: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
|    link/ether 26:81:13:21:3e:d1 brd ff:ff:ff:ff:ff:ff
|    inet 192.168.194.254/24 brd 192.168.194.255 scope global int194
|       valid_lft forever preferred_lft forever
|    inet6 2a01:238:43fa:bc94::70:100/64 scope global 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::1/64 scope link 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::2481:13ff:fe21:3ed1/64 scope link proto kernel_ll 
|       valid_lft forever preferred_lft forever
|18: int195: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
|    link/ether fa:af:a9:ed:5d:51 brd ff:ff:ff:ff:ff:ff
|    inet 192.168.195.254/24 brd 192.168.195.255 scope global int195
|       valid_lft forever preferred_lft forever
|    inet6 2a01:238:43fa:bc95::70:100/64 scope global 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::1/64 scope link 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::f8af:a9ff:feed:5d51/64 scope link proto kernel_ll 
|       valid_lft forever preferred_lft forever
|19: int196: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
|    link/ether 6e:03:93:ed:93:67 brd ff:ff:ff:ff:ff:ff
|    inet 192.168.196.254/24 brd 192.168.196.255 scope global int196
|       valid_lft forever preferred_lft forever
|    inet6 2a01:238:43fa:bc96::70:100/64 scope global 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::1/64 scope link 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::6c03:93ff:feed:9367/64 scope link proto kernel_ll 
|       valid_lft forever preferred_lft forever
|20: int198: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
|    link/ether 56:da:f6:fe:ec:0b brd ff:ff:ff:ff:ff:ff
|    inet6 2a01:238:43fa:bc98::70:100/64 scope global 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::1/64 scope link 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::54da:f6ff:fefe:ec0b/64 scope link proto kernel_ll 
|       valid_lft forever preferred_lft forever
|21: per281: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
|    link/ether 72:a6:b9:cf:a0:65 brd ff:ff:ff:ff:ff:ff
|    inet 192.168.221.254/24 brd 192.168.221.255 scope global per281
|       valid_lft forever preferred_lft forever
|    inet6 2a01:238:43fa:bcb1::70:100/64 scope global 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::70a6:b9ff:fecf:a065/64 scope link proto kernel_ll 
|       valid_lft forever preferred_lft forever
|22: per851: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
|    link/ether 12:bf:64:5d:fa:03 brd ff:ff:ff:ff:ff:ff
|    inet 172.22.51.17/24 brd 172.22.51.255 scope global per851
|       valid_lft forever preferred_lft forever
|    inet6 fe80::10bf:64ff:fe5d:fa03/64 scope link proto kernel_ll 
|       valid_lft forever preferred_lft forever
|23: unt381: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
|    link/ether 8a:2f:3f:e4:64:9b brd ff:ff:ff:ff:ff:ff
|    inet 192.168.251.241/24 brd 192.168.251.255 scope global unt381
|       valid_lft forever preferred_lft forever
|    inet6 2001:16b8:a9ad:be00:882f:3fff:fee4:649b/64 scope global dynamic mngtmpaddr noprefixroute 
|       valid_lft 6933sec preferred_lft 3333sec
|    inet6 fdce:4a40:8870:0:882f:3fff:fee4:649b/64 scope global dynamic mngtmpaddr noprefixroute 
|       valid_lft 6933sec preferred_lft 3333sec
|    inet6 2a01:238:43fa:bc8e::70:100/64 scope global 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::70:100/64 scope link 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::882f:3fff:fee4:649b/64 scope link proto kernel_ll 
|       valid_lft forever preferred_lft forever
|24: unt382: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
|    link/ether e2:9c:36:40:f7:cd brd ff:ff:ff:ff:ff:ff
|    inet 192.168.252.241/24 brd 192.168.252.255 scope global unt382
|       valid_lft forever preferred_lft forever
|    inet6 2a01:238:43fa:bc8f::70:100/64 scope global 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::e09c:36ff:fe40:f7cd/64 scope link proto kernel_ll 
|       valid_lft forever preferred_lft forever
|25: unt383: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
|    link/ether ce:1a:b9:cd:51:f3 brd ff:ff:ff:ff:ff:ff
|    inet 192.168.253.241/24 brd 192.168.253.255 scope global unt383
|       valid_lft forever preferred_lft forever
|    inet6 2a01:238:43fa:bc8c::70:100/64 scope global 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::cc1a:b9ff:fecd:51f3/64 scope link proto kernel_ll 
|       valid_lft forever preferred_lft forever
|26: vlan194@enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master int194 state UP group default qlen 1000
|    link/ether 00:0d:b9:41:c9:ec brd ff:ff:ff:ff:ff:ff
|27: vlan187@enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master int187 state UP group default qlen 1000
|    link/ether 00:0d:b9:41:c9:ec brd ff:ff:ff:ff:ff:ff
|28: vlan183@enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master int183 state UP group default qlen 1000
|    link/ether 00:0d:b9:41:c9:ec brd ff:ff:ff:ff:ff:ff
|29: vlan189@enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master int189 state UP group default qlen 1000
|    link/ether 00:0d:b9:41:c9:ec brd ff:ff:ff:ff:ff:ff
|30: vlan188@enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master int188 state UP group default qlen 1000
|    link/ether 00:0d:b9:41:c9:ec brd ff:ff:ff:ff:ff:ff
|31: vlan193@enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master int193 state UP group default qlen 1000
|    link/ether 00:0d:b9:41:c9:ec brd ff:ff:ff:ff:ff:ff
|32: vlan186@enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master int186 state UP group default qlen 1000
|    link/ether 00:0d:b9:41:c9:ec brd ff:ff:ff:ff:ff:ff
|33: vlan192@enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master int192 state UP group default qlen 1000
|    link/ether 00:0d:b9:41:c9:ec brd ff:ff:ff:ff:ff:ff
|34: vlan196@enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master int196 state UP group default qlen 1000
|    link/ether 00:0d:b9:41:c9:ec brd ff:ff:ff:ff:ff:ff
|35: vlan182@enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master int182 state UP group default qlen 1000
|    link/ether 00:0d:b9:41:c9:ec brd ff:ff:ff:ff:ff:ff
|36: vlan195@enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master int195 state UP group default qlen 1000
|    link/ether 00:0d:b9:41:c9:ec brd ff:ff:ff:ff:ff:ff
|37: vlan198@enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master int198 state UP group default qlen 1000
|    link/ether 00:0d:b9:41:c9:ec brd ff:ff:ff:ff:ff:ff
|38: vlan191@enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master int191 state UP group default qlen 1000
|    link/ether 00:0d:b9:41:c9:ec brd ff:ff:ff:ff:ff:ff
|39: vlan181@enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master int181 state UP group default qlen 1000
|    link/ether 00:0d:b9:41:c9:ec brd ff:ff:ff:ff:ff:ff
|40: vlan184@enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master int184 state UP group default qlen 1000
|    link/ether 00:0d:b9:41:c9:ec brd ff:ff:ff:ff:ff:ff
|41: vlan185@enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master int185 state UP group default qlen 1000
|    link/ether 00:0d:b9:41:c9:ec brd ff:ff:ff:ff:ff:ff
|42: vlan383@enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master unt383 state UP group default qlen 1000
|    link/ether 00:0d:b9:41:c9:ee brd ff:ff:ff:ff:ff:ff
|43: vlan382@enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master unt382 state UP group default qlen 1000
|    link/ether 00:0d:b9:41:c9:ee brd ff:ff:ff:ff:ff:ff
|44: vlan381@enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master unt381 state UP group default qlen 1000
|    link/ether 00:0d:b9:41:c9:ee brd ff:ff:ff:ff:ff:ff
|45: vlan281@enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master per281 state UP group default qlen 1000
|    link/ether 00:0d:b9:41:c9:ed brd ff:ff:ff:ff:ff:ff
|46: vlan851@enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master per851 state UP group default qlen 1000
|    link/ether 00:0d:b9:41:c9:ed brd ff:ff:ff:ff:ff:ff
|48: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master int181 state UNKNOWN group default qlen 1000
|    link/ether fe:54:00:5f:3e:74 brd ff:ff:ff:ff:ff:ff
|    inet6 fe80::fc54:ff:fe5f:3e74/64 scope link proto kernel_ll 
|       valid_lft forever preferred_lft forever
|49: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master int181 state UNKNOWN group default qlen 1000
|    link/ether fe:54:00:9b:79:71 brd ff:ff:ff:ff:ff:ff
|    inet6 fe80::fc54:ff:fe9b:7971/64 scope link proto kernel_ll 
|       valid_lft forever preferred_lft forever
|50: vnet2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master int181 state UNKNOWN group default qlen 1000
|    link/ether fe:54:00:88:82:99 brd ff:ff:ff:ff:ff:ff
|    inet6 fe80::fc54:ff:fe88:8299/64 scope link proto kernel_ll 
|       valid_lft forever preferred_lft forever
|52: zg2vpn: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
|    link/none 
|    inet 10.8.0.112/24 brd 10.8.0.255 scope global zg2vpn
|       valid_lft forever preferred_lft forever
|    inet6 2a01:238:43fa:bc02::70:100/64 scope global 
|       valid_lft forever preferred_lft forever
|    inet6 fe80::ba5:2e95:9e65:f750/64 scope link stable-privacy proto kernel_ll 
|       valid_lft forever preferred_lft forever
|[2/4944]mh@prom:~ $ ip route
|default via 192.168.251.254 dev unt381 proto static 
|10.8.0.0/24 dev zg2vpn proto kernel scope link src 10.8.0.112 
|10.200.1.0/24 via 172.22.51.1 dev per851 proto static 
|10.200.32.0/19 via 172.22.51.1 dev per851 proto static 
|10.242.0.0/23 via 172.22.51.1 dev per851 proto static 
|10.242.4.0/23 via 172.22.51.1 dev per851 proto static 
|81.92.173.224/29 via 10.8.0.1 dev zg2vpn proto static 
|81.92.173.227 via 10.8.0.1 dev zg2vpn metric 200 
|172.16.0.0/18 via 172.22.51.1 dev per851 proto static 
|172.22.0.0/16 via 172.22.51.1 dev per851 proto static 
|172.22.51.0/24 dev per851 proto kernel scope link src 172.22.51.17 
|192.168.0.0/20 via 172.22.51.1 dev per851 proto static 
|192.168.32.0/19 via 172.22.51.1 dev per851 proto static 
|192.168.181.0/24 dev int181 proto kernel scope link src 192.168.181.112 
|192.168.182.0/24 dev int182 proto kernel scope link src 192.168.182.254 
|192.168.183.0/24 dev int183 proto kernel scope link src 192.168.183.254 
|192.168.184.0/24 dev int184 proto kernel scope link src 192.168.184.254 
|192.168.185.0/24 dev int185 proto kernel scope link src 192.168.185.254 
|192.168.186.0/24 dev int186 proto kernel scope link src 192.168.186.254 
|192.168.187.0/24 dev int187 proto kernel scope link src 192.168.187.254 
|192.168.188.0/24 dev int188 proto kernel scope link src 192.168.188.254 
|192.168.189.0/24 dev int189 proto kernel scope link src 192.168.189.254 
|192.168.191.0/24 dev int191 proto kernel scope link src 192.168.191.254 
|192.168.192.0/24 dev int192 proto kernel scope link src 192.168.192.254 
|192.168.193.0/24 dev int193 proto kernel scope link src 192.168.193.254 
|192.168.194.0/24 dev int194 proto kernel scope link src 192.168.194.254 
|192.168.195.0/24 dev int195 proto kernel scope link src 192.168.195.254 
|192.168.196.0/24 dev int196 proto kernel scope link src 192.168.196.254 
|192.168.196.128/28 via 192.168.196.111 dev int196 proto static 
|192.168.221.0/24 dev per281 proto kernel scope link src 192.168.221.254 
|192.168.251.0/24 dev unt381 proto kernel scope link src 192.168.251.241 
|192.168.252.0/24 dev unt382 proto kernel scope link src 192.168.252.241 
|192.168.253.0/24 dev unt383 proto kernel scope link src 192.168.253.241 
|[4/4934]mh@prom:~ $ ip -6 route
|2001:16b8:a9ad:be00::/64 dev unt381 proto ra metric 1024 expires 6925sec pref medium
|2001:16b8:a9ad:bec2::/64 dev int182 proto kernel metric 256 expires 6085sec pref medium
|2001:16b8:a9ad:bec3::/64 dev int183 proto kernel metric 256 expires 6085sec pref medium
|2001:16b8:a9ad:bec4::/64 dev int184 proto kernel metric 256 expires 6085sec pref medium
|2001:16b8:a9ad:bec5::/64 dev int185 proto kernel metric 256 expires 6085sec pref medium
|2001:16b8:a9ad:bec6::/64 dev int186 proto kernel metric 256 expires 6085sec pref medium
|2001:16b8:a9ad:bec7::/64 dev int187 proto kernel metric 256 expires 6085sec pref medium
|2001:16b8:a9ad:bec8::/64 dev int188 proto kernel metric 256 expires 6085sec pref medium
|2001:16b8:a9ad:bec9::/64 dev int189 proto kernel metric 256 expires 6085sec pref medium
|2001:16b8:a9ad:bed2::/64 dev int192 proto kernel metric 256 expires 6085sec pref medium
|unreachable 2001:16b8:a9ad:bec0::/58 dev lo proto dhcp metric 1024 pref medium
|2001:16b8:a9ad:be00::/56 nhid 1454718517 via fe80::b2f2:8ff:fe64:9ec6 dev unt381 proto ra metric 1024 expires 1525sec pref medium
|2a01:238:43fa:bc02::/64 dev zg2vpn proto kernel metric 256 pref medium
|2a01:238:43fa:bc81::/64 dev int181 proto kernel metric 256 pref medium
|2a01:238:43fa:bc82::/64 dev int182 proto kernel metric 256 pref medium
|2a01:238:43fa:bc83::/64 dev int183 proto kernel metric 256 pref medium
|2a01:238:43fa:bc84::/64 dev int184 proto kernel metric 256 pref medium
|2a01:238:43fa:bc85::/64 dev int185 proto kernel metric 256 pref medium
|2a01:238:43fa:bc86::/64 dev int186 proto kernel metric 256 pref medium
|2a01:238:43fa:bc87::/64 dev int187 proto kernel metric 256 pref medium
|2a01:238:43fa:bc88::/64 dev int188 proto kernel metric 256 pref medium
|2a01:238:43fa:bc89::/64 dev int189 proto kernel metric 256 pref medium
|2a01:238:43fa:bc8c::/64 dev unt383 proto kernel metric 256 pref medium
|2a01:238:43fa:bc8e::/64 dev unt381 proto kernel metric 256 pref medium
|2a01:238:43fa:bc8f::/64 dev unt382 proto kernel metric 256 pref medium
|2a01:238:43fa:bc91::/64 dev int191 proto kernel metric 256 pref medium
|2a01:238:43fa:bc92::/64 dev int192 proto kernel metric 256 pref medium
|2a01:238:43fa:bc93::/64 dev int193 proto kernel metric 256 pref medium
|2a01:238:43fa:bc94::/64 dev int194 proto kernel metric 256 pref medium
|2a01:238:43fa:bc95::/64 dev int195 proto kernel metric 256 pref medium
|2a01:238:43fa:bc96:6f::/80 via 2a01:238:43fa:bc96::6f:100 dev int196 proto static metric 1024 pref medium
|2a01:238:43fa:bc96:16f::/80 via 2a01:238:43fa:bc96::6f:100 dev int196 proto static metric 1024 pref medium
|2a01:238:43fa:bc96::/64 dev int196 proto kernel metric 256 pref medium
|2a01:238:43fa:bc98::/64 dev int198 proto kernel metric 256 pref medium
|unreachable 2a01:238:43fa:bc80::/59 dev lo proto static metric 1024 pref medium
|2a01:238:43fa:bcb1::/64 dev per281 proto kernel metric 256 pref medium
|unreachable 2a01:238:43fa:bcb0::/62 dev lo proto static metric 1024 pref medium
|fdce:4a40:8870::/64 dev unt381 proto ra metric 1024 expires 6925sec pref medium
|fdce:4a40:8870::/64 nhid 1454718517 via fe80::b2f2:8ff:fe64:9ec6 dev unt381 proto ra metric 1024 expires 1525sec pref medium
|fe80::/64 dev enp1s0 proto kernel metric 256 pref medium
|fe80::/64 dev int181 proto kernel metric 256 pref medium
|fe80::/64 dev int182 proto kernel metric 256 pref medium
|fe80::/64 dev int183 proto kernel metric 256 pref medium
|fe80::/64 dev int184 proto kernel metric 256 pref medium
|fe80::/64 dev int185 proto kernel metric 256 pref medium
|fe80::/64 dev int186 proto kernel metric 256 pref medium
|fe80::/64 dev int187 proto kernel metric 256 pref medium
|fe80::/64 dev int188 proto kernel metric 256 pref medium
|fe80::/64 dev int189 proto kernel metric 256 pref medium
|fe80::/64 dev int191 proto kernel metric 256 pref medium
|fe80::/64 dev int192 proto kernel metric 256 pref medium
|fe80::/64 dev int193 proto kernel metric 256 pref medium
|fe80::/64 dev int194 proto kernel metric 256 pref medium
|fe80::/64 dev int195 proto kernel metric 256 pref medium
|fe80::/64 dev int196 proto kernel metric 256 pref medium
|fe80::/64 dev int198 proto kernel metric 256 pref medium
|fe80::/64 dev enp3s0 proto kernel metric 256 pref medium
|fe80::/64 dev unt381 proto kernel metric 256 pref medium
|fe80::/64 dev unt382 proto kernel metric 256 pref medium
|fe80::/64 dev unt383 proto kernel metric 256 pref medium
|fe80::/64 dev enp2s0 proto kernel metric 256 pref medium
|fe80::/64 dev per281 proto kernel metric 256 pref medium
|fe80::/64 dev per851 proto kernel metric 256 pref medium
|fe80::/64 dev vnet0 proto kernel metric 256 pref medium
|fe80::/64 dev vnet1 proto kernel metric 256 pref medium
|fe80::/64 dev vnet2 proto kernel metric 256 pref medium
|fe80::/64 dev zg2vpn proto kernel metric 256 pref medium
|fec0:0:0:ffff::1 via 2a01:238:43fa:bc81::a4:100 dev int181 proto static metric 1024 pref medium
|fec0:0:0:ffff::2 via 2a01:238:43fa:bc8e::9:100 dev unt381 proto static metric 1024 pref medium
|fec0:0:0:ffff::3 via 2a01:238:43fa:bc81::a4:100 dev int181 proto static metric 1024 pref medium
|default nhid 1454718517 via fe80::b2f2:8ff:fe64:9ec6 dev unt381 proto ra metric 1024 expires 1525sec pref medium
|[5/4927]mh@prom:~ $ 
-- 
----------------------------------------------------------------------------
Marc Haber         |   " Questions are the         | Mailadresse im Header
Rhein-Neckar, DE   |     Beginning of Wisdom "     | 
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 6224 1600402

[toc] | [prev] | [standalone]

Page 6 of 6 — ← Prev page 1 2 3 4 5 [6]

Back to top | Article view | comp.os.linux.misc

csiph-web