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

Groups > linux.debian.user > #245732 > unrolled thread

What should I put inside the file called wlan0?

Back to article view | Back to linux.debian.user

Contents

  What should I put inside the file called wlan0? Stella Ashburne <rewefie@gmx.com> - 2022-02-28 19:50 +0100
    Re: What should I put inside the file called wlan0? <tomas@tuxteam.de> - 2022-02-28 20:20 +0100
      Re: What should I put inside the file called wlan0? Stella Ashburne <rewefie@gmx.com> - 2022-02-28 21:00 +0100
        Re: What should I put inside the file called wlan0? tomas@tuxteam.de - 2022-02-28 21:30 +0100
          Re: What should I put inside the file called wlan0? Stella Ashburne <rewefie@gmx.com> - 2022-02-28 22:50 +0100
        Re: What should I put inside the file called wlan0? <tomas@tuxteam.de> - 2022-02-28 21:30 +0100
          Re: What should I put inside the file called wlan0? Stella Ashburne <rewefie@gmx.com> - 2022-02-28 22:50 +0100
            Re: What should I put inside the file called wlan0? tomas@tuxteam.de - 2022-03-01 07:40 +0100
              Re: What should I put inside the file called wlan0? Brian <ad44@cityscape.co.uk> - 2022-03-01 13:20 +0100
                Re: What should I put inside the file called wlan0? Stella Ashburne <rewefie@gmx.com> - 2022-03-01 15:30 +0100
                  Re: What should I put inside the file called wlan0? Brian <ad44@cityscape.co.uk> - 2022-03-01 16:00 +0100
              Re: What should I put inside the file called wlan0? Stefan Monnier <monnier@iro.umontreal.ca> - 2022-03-01 15:20 +0100
                Re: What should I put inside the file called wlan0? <tomas@tuxteam.de> - 2022-03-01 15:50 +0100
        Re: What should I put inside the file called wlan0? Tim Woodall <debianuser@woodall.me.uk> - 2022-03-01 13:20 +0100
          Re: What should I put inside the file called wlan0? <tomas@tuxteam.de> - 2022-03-01 13:30 +0100
            Re: What should I put inside the file called wlan0? David Wright <deblis@lionunicorn.co.uk> - 2022-03-01 15:40 +0100
              Re: What should I put inside the file called wlan0? <tomas@tuxteam.de> - 2022-03-01 15:50 +0100
          Re: What should I put inside the file called wlan0? Stella Ashburne <rewefie@gmx.com> - 2022-03-01 15:40 +0100
            Re: What should I put inside the file called wlan0? Tim Woodall <debianuser@woodall.me.uk> - 2022-03-01 15:50 +0100
              Re: What should I put inside the file called wlan0? Greg Wooledge <greg@wooledge.org> - 2022-03-01 16:00 +0100
                Re: What should I put inside the file called wlan0? Tim Woodall <debianuser@woodall.me.uk> - 2022-03-01 16:40 +0100
                  wikis: moin-moin : plain text (was: Re: What should I put inside the file called wlan0?) rhkramer@gmail.com - 2022-03-03 14:50 +0100
                    Re: wikis: moin-moin : plain text (was: Re: What should I put inside  the file called wlan0?) Greg Wooledge <greg@wooledge.org> - 2022-03-03 15:00 +0100
                    Re: wikis: moin-moin : plain text (was: Re: What should I put inside  the file called wlan0?) Tim Woodall <debianuser@woodall.me.uk> - 2022-03-03 15:50 +0100
        Re: What should I put inside the file called wlan0? David Wright <deblis@lionunicorn.co.uk> - 2022-03-01 17:30 +0100
          Re: What should I put inside the file called wlan0? Stella Ashburne <rewefie@gmx.com> - 2022-03-02 09:10 +0100
            Re: What should I put inside the file called wlan0? Brian <ad44@cityscape.co.uk> - 2022-03-02 19:00 +0100
              Re: What should I put inside the file called wlan0? Stella Ashburne <rewefie@gmx.com> - 2022-03-03 09:00 +0100
                Re: What should I put inside the file called wlan0? Tim Woodall <debianuser@woodall.me.uk> - 2022-03-03 12:30 +0100
                  Re: What should I put inside the file called wlan0? Stella Ashburne <rewefie@gmx.com> - 2022-03-03 19:30 +0100
                    Re: What should I put inside the file called wlan0? Brian <ad44@cityscape.co.uk> - 2022-03-03 19:50 +0100
                      Re: What should I put inside the file called wlan0? Stella Ashburne <rewefie@gmx.com> - 2022-03-03 20:00 +0100
              Re: What should I put inside the file called wlan0? David Wright <deblis@lionunicorn.co.uk> - 2022-03-03 17:00 +0100
                Re: What should I put inside the file called wlan0? Stella Ashburne <rewefie@gmx.com> - 2022-03-03 19:50 +0100
                  Re: What should I put inside the file called wlan0? <tomas@tuxteam.de> - 2022-03-03 21:00 +0100
                  Re: What should I put inside the file called wlan0? David Wright <deblis@lionunicorn.co.uk> - 2022-03-08 16:20 +0100
              Re: What should I put inside the file called wlan0? Stella Ashburne <rewefie@gmx.com> - 2022-03-03 19:40 +0100
                Re: What should I put inside the file called wlan0? Brian <ad44@cityscape.co.uk> - 2022-03-03 19:50 +0100
                  Re: What should I put inside the file called wlan0? Brian <ad44@cityscape.co.uk> - 2022-03-03 20:00 +0100
                  Re: What should I put inside the file called wlan0? Stella Ashburne <rewefie@gmx.com> - 2022-03-03 20:00 +0100
            Re: What should I put inside the file called wlan0? David Wright <deblis@lionunicorn.co.uk> - 2022-03-08 16:20 +0100
    Re: What should I put inside the file called wlan0? Brian <ad44@cityscape.co.uk> - 2022-02-28 21:10 +0100
      Re: What should I put inside the file called wlan0? Stella Ashburne <rewefie@gmx.com> - 2022-02-28 21:20 +0100
        Re: What should I put inside the file called wlan0? Brian <ad44@cityscape.co.uk> - 2022-03-01 00:20 +0100
          Re: What should I put inside the file called wlan0? Stella Ashburne <rewefie@gmx.com> - 2022-03-01 06:10 +0100
            Re: What should I put inside the file called wlan0? Markus Schönhaber <debian-user@list-post.mks-mail.de> - 2022-03-01 09:00 +0100
              Re: What should I put inside the file called wlan0? Stella Ashburne <rewefie@gmx.com> - 2022-03-01 12:10 +0100
          Re: What should I put inside the file called wlan0? <tomas@tuxteam.de> - 2022-03-01 07:50 +0100
    Re: What should I put inside the file called wlan0? Nicolas George <george@nsup.org> - 2022-02-28 22:20 +0100
      Re: What should I put inside the file called wlan0? Ash Joubert <ash@transient.nz> - 2022-02-28 23:50 +0100
        Re: What should I put inside the file called wlan0? Brian <ad44@cityscape.co.uk> - 2022-03-01 00:50 +0100
          Re: What should I put inside the file called wlan0? Curt <curty@free.fr> - 2022-03-01 10:30 +0100
          Re: What should I put inside the file called wlan0? Ash Joubert <ash@transient.nz> - 2022-03-01 22:20 +0100
        Re: What should I put inside the file called wlan0? Stella Ashburne <rewefie@gmx.com> - 2022-03-01 06:10 +0100
      Re: What should I put inside the file called wlan0? Brian <ad44@cityscape.co.uk> - 2022-03-01 00:50 +0100
        Re: What should I put inside the file called wlan0? Nicolas George <george@nsup.org> - 2022-03-01 10:50 +0100

Page 1 of 3  [1] 2 3  Next page →

#245732 — What should I put inside the file called wlan0?

I quote from Debian Wiki (https://wiki.debian.org/WiFi/HowToUse) :

"Restrict the permissions of /etc/network/interfaces, to prevent pre-shared key (PSK) disclosure (alternatively use a separate config file such as /etc/network/interfaces.d/wlan0 on newer Debian versions): "

What should I put in the file called wlan0? Said wiki does not provide examples.

Best regards.

Stella

[toc] | [next] | [standalone]

#245736

[Multipart message — attachments visible in raw view] — view raw

On Mon, Feb 28, 2022 at 07:49:32PM +0100, Stella Ashburne wrote:
> I quote from Debian Wiki (https://wiki.debian.org/WiFi/HowToUse) :
> 
> "Restrict the permissions of /etc/network/interfaces, to prevent pre-shared key (PSK) disclosure (alternatively use a separate config file such as /etc/network/interfaces.d/wlan0 on newer Debian versions): "
> 
> What should I put in the file called wlan0? Said wiki does not provide examples.

man 5 interfaces provides the relevant bits: by default, the files
in interfaces.d are (textually) included in interfaces. So each
of those files can basically have a "snippet" of what you would
put in interfaces (to avoid losing sanity, whole stanzas seem
recommendable).

So if you have this in your /etc/network/interfaces somewhere:

  ...
  ## Bahn ICE
  iface wlan0 inet dhcp
    wireless-essid WIFIonICE
    wireless-mode Auto
  ...

(it's actually my current setting, BTW :) you could swap that
out to some file under interfaces.d.

Cheers
-- 
t

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

#245738

Dearie,

Thanks for your reply.

> Sent: Tuesday, March 01, 2022 at 3:10 AM
> From: tomas@tuxteam.de
> To: debian-user@lists.debian.org
> Subject: Re: What should I put inside the file called wlan0?
>
>
> So if you have this in your /etc/network/interfaces somewhere:
>
>   ...
>   ## Bahn ICE
>   iface wlan0 inet dhcp
>     wireless-essid WIFIonICE
>     wireless-mode Auto
>   ...
>
> (it's actually my current setting, BTW :) you could swap that
> out to some file under interfaces.d.

The contents of my current /etc/network/interfaces file are:

# The primary network interface
allow-hotplug wlp3s0
iface wlp7s0 inet static
        wpa-ssid JupiterRising
        wpa-psk {a long string of alphanumeric characters}
        address 192.168.1.99/24
        gateway 192.168.1.1
        # dns-* options are implemented by the resolvconf package, if installed
        dns-nameservers 1.1.1.1 8.8.8.8

Are you saying that I can cut out the above contents and paste them into a file called wlp7s0 (whose path is /etc/network/interfaces.d/)?

Best regards.

Stella

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

#245742

[Multipart message — attachments visible in raw view] — view raw

On Mon, Feb 28, 2022 at 09:20:07PM +0100, tomas@tuxteam.de wrote:

[...]

> (in Debian, at least) /etc/network/interfaces is only root-readable. So

This is wrong (note to self: double-check things. Gah). Sorry for any
confusion.

Cheers
-- 
t

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

#245746

Dearie

> Sent: Tuesday, March 01, 2022 at 4:21 AM
> From: tomas@tuxteam.de
> To: debian-user@lists.debian.org
> Subject: Re: What should I put inside the file called wlan0?
>
> On Mon, Feb 28, 2022 at 09:20:07PM +0100, tomas@tuxteam.de wrote:
>
> [...]
>
> > (in Debian, at least) /etc/network/interfaces is only root-readable. So
>
If that's the case, why would Debian Wiki recommend to chmod as follows?

# chmod 0600 /etc/network/interfaces

(source: https://wiki.debian.org/WiFi/HowToUse)

Best regards.

Stella

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

#245743

[Multipart message — attachments visible in raw view] — view raw

On Mon, Feb 28, 2022 at 08:59:03PM +0100, Stella Ashburne wrote:
> Dearie,
> 
> Thanks for your reply.
> 
> > Sent: Tuesday, March 01, 2022 at 3:10 AM
> > From: tomas@tuxteam.de
> > To: debian-user@lists.debian.org
> > Subject: Re: What should I put inside the file called wlan0?
> >
> >
> > So if you have this in your /etc/network/interfaces somewhere:
> >
> >   ...
> >   ## Bahn ICE
> >   iface wlan0 inet dhcp
> >     wireless-essid WIFIonICE
> >     wireless-mode Auto
> >   ...
> >
> > (it's actually my current setting, BTW :) you could swap that
> > out to some file under interfaces.d.
> 
> The contents of my current /etc/network/interfaces file are:
> 
> # The primary network interface
> allow-hotplug wlp3s0
> iface wlp7s0 inet static
>         wpa-ssid JupiterRising
>         wpa-psk {a long string of alphanumeric characters}
>         address 192.168.1.99/24
>         gateway 192.168.1.1
>         # dns-* options are implemented by the resolvconf package, if installed
>         dns-nameservers 1.1.1.1 8.8.8.8
> 
> Are you saying that I can cut out the above contents and paste them into a file called wlp7s0 (whose path is /etc/network/interfaces.d/)?

That's how I read that man page, yes (disclaimer: I haven't actually
tried).

However, if I remember your original post correctly, there were security
reasons mentioned (about a possibly world readable /etc/network/interfaces,
and splitting out an .../interfaces.d/wlan0 as a fix), Note that by default
(in Debian, at least) /etc/network/interfaces is only root-readable. So
this wouldn't be the reason you'd want to do the split (there are other
valid reasons, though).

Cheers
-- 
t

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

#245747

Dearie

> Sent: Tuesday, March 01, 2022 at 4:20 AM
> From: tomas@tuxteam.de
> To: debian-user@lists.debian.org
> Subject: Re: What should I put inside the file called wlan0?
>
>
> However, if I remember your original post correctly, there were security
> reasons mentioned (about a possibly world readable /etc/network/interfaces,
> and splitting out an .../interfaces.d/wlan0 as a fix), Note that by default
> (in Debian, at least) /etc/network/interfaces is only root-readable. So
> this wouldn't be the reason you'd want to do the split (there are other
> valid reasons, though).
>
According to Debian Wiki WiFi How To Use (https://wiki.debian.org/WiFi/HowToUse), the reason for doing the split is:

(sic) Restrict the permissions of /etc/network/interfaces, to prevent pre-shared key (PSK) disclosure

Best regards.

Stella

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

#245769

[Multipart message — attachments visible in raw view] — view raw

On Mon, Feb 28, 2022 at 10:43:52PM +0100, Stella Ashburne wrote:
> Dearie

[...]

> According to Debian Wiki WiFi How To Use (https://wiki.debian.org/WiFi/HowToUse), the reason for doing the split is:
> 
> (sic) Restrict the permissions of /etc/network/interfaces, to prevent pre-shared key (PSK) disclosure

I see. As others have already noted in this thread, your WiFi PSK
isn't usually a high-value secret; besides, if someone has access
to your computer, she typically has more valuable things to look
for.

One might construct scenarios: having a quick look at your laptop
in the bar while you are in the restroom, then stealing your bandwidth
(or doing nasty things from your access point's IP). But hey.

That said, you're your network's boss, so it's on you to decide.
There might be reasons to not reveal it (or, let's be realistic, to
make access to it a bit more difficult).

Cheers
-- 
t

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

#245780

On Tue 01 Mar 2022 at 07:35:20 +0100, tomas@tuxteam.de wrote:

> On Mon, Feb 28, 2022 at 10:43:52PM +0100, Stella Ashburne wrote:
> > Dearie
> 
> [...]
> 
> > According to Debian Wiki WiFi How To Use (https://wiki.debian.org/WiFi/HowToUse), the reason for doing the split is:
> > 
> > (sic) Restrict the permissions of /etc/network/interfaces, to prevent pre-shared key (PSK) disclosure
> 
> I see. As others have already noted in this thread, your WiFi PSK
> isn't usually a high-value secret; besides, if someone has access
> to your computer, she typically has more valuable things to look
> for.

/e/n/i may contain PSKs for networks other than the home network;
friens, relatives, work etc. A user, having been trusted with them,
may see it as an obligation not to make *them* easily accessible.

-- 
Brian.

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

#245784

Dearie

> Sent: Tuesday, March 01, 2022 at 8:13 PM
> From: "Brian" <ad44@cityscape.co.uk>
> To: debian-user@lists.debian.org
> Subject: Re: What should I put inside the file called wlan0?
>
>
> /e/n/i may contain PSKs for networks other than the home network;
> friens, relatives, work etc. A user, having been trusted with them,
> may see it as an obligation not to make *them* easily accessible.
>
> --
By /e/n/i did you mean /etc/network/interfaces or /etc/network/interfaces.d  ?

Best regards.

Stella

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

#245790

On Tue 01 Mar 2022 at 15:25:52 +0100, Stella Ashburne wrote:

> Dearie
> 
> > Sent: Tuesday, March 01, 2022 at 8:13 PM
> > From: "Brian" <ad44@cityscape.co.uk>
> > To: debian-user@lists.debian.org
> > Subject: Re: What should I put inside the file called wlan0?
> >
> >
> > /e/n/i may contain PSKs for networks other than the home network;
> > friens, relatives, work etc. A user, having been trusted with them,
> > may see it as an obligation not to make *them* easily accessible.
> >
> > --
> By /e/n/i did you mean /etc/network/interfaces or /etc/network/interfaces.d  ?

The first.

-- 
Brian.

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

#245783

tomas@tuxteam.de [2022-03-01 07:35:20] wrote:
> I see.  As others have already noted in this thread, your WiFi PSK
> isn't usually a high-value secret; besides, if someone has access
> to your computer, she typically has more valuable things to look
> for.

OTOH, by putting barriers only at those places where we can think
of attack scenarios we end up with rampant security issues, because
attacks are more diverse/creative than we can ever be.

[ Of course, the dual is that by providing the information only where
  we can think of scenarios where it's justified, we end up with an
  unusably restrictive system.  Again because we lack creativity.  ]


        Stefan

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

#245787

[Multipart message — attachments visible in raw view] — view raw

On Tue, Mar 01, 2022 at 09:11:46AM -0500, Stefan Monnier wrote:
> tomas@tuxteam.de [2022-03-01 07:35:20] wrote:
> > I see.  As others have already noted in this thread, your WiFi PSK
> > isn't usually a high-value secret; besides, if someone has access
> > to your computer, she typically has more valuable things to look
> > for.
> 
> OTOH, by putting barriers only at those places where we can think
> of attack scenarios we end up with rampant security issues, because
> attacks are more diverse/creative than we can ever be.

Definitely. 

I think the most important thing to keep around is "context matters", which
more or less corresponds to what secuity buffs call "threat model". What
kind of stuff are you trying to defend against?

 - Is it only your home's access point's secret key what is at stake, or
   your friend's, workplace's, etc?

 - Are you defending against your computer "at rest" being stolen (in
   which case perhaps a full disk encryption might Just Do (TM) or are
   you defending against some javascript-vectored trojan coming in
   via your browser (or some macro through some *cough* text processing
   software)?

And so on. Security can be very amusing :-)

This permission based securisation carries over many things from the
good ol' times of real multiuser systems. Now of course it's one road
bump more: should my browser ask me for my password I'd tend to kill
it right away; most folks wouldn't be that cruel :-)

Cheers
-- 
t

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

#245779

On Mon, 28 Feb 2022, Stella Ashburne wrote:

> Dearie,
>
> Thanks for your reply.
>
>> Sent: Tuesday, March 01, 2022 at 3:10 AM
>> From: tomas@tuxteam.de
>> To: debian-user@lists.debian.org
>> Subject: Re: What should I put inside the file called wlan0?
>>
>>
>> So if you have this in your /etc/network/interfaces somewhere:
>>
>>   ...
>>   ## Bahn ICE
>>   iface wlan0 inet dhcp
>>     wireless-essid WIFIonICE
>>     wireless-mode Auto
>>   ...
>>
>> (it's actually my current setting, BTW :) you could swap that
>> out to some file under interfaces.d.
>
> The contents of my current /etc/network/interfaces file are:
>
> # The primary network interface
> allow-hotplug wlp3s0
> iface wlp7s0 inet static
>        wpa-ssid JupiterRising
>        wpa-psk {a long string of alphanumeric characters}
>        address 192.168.1.99/24
>        gateway 192.168.1.1
>        # dns-* options are implemented by the resolvconf package, if installed
>        dns-nameservers 1.1.1.1 8.8.8.8
>
> Are you saying that I can cut out the above contents and paste them into a file called wlp7s0 (whose path is /etc/network/interfaces.d/)?
>

Yes, but you need to have this in /e/n/i

source-directory /etc/network/interfaces.d

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

#245781

[Multipart message — attachments visible in raw view] — view raw

On Tue, Mar 01, 2022 at 12:16:44PM +0000, Tim Woodall wrote:
> On Mon, 28 Feb 2022, Stella Ashburne wrote:

[...]

> > # The primary network interface
> > allow-hotplug wlp3s0
> > iface wlp7s0 inet static
> >        wpa-ssid JupiterRising
> >        wpa-psk {a long string of alphanumeric characters}
> >        address 192.168.1.99/24
> >        gateway 192.168.1.1
> >        # dns-* options are implemented by the resolvconf package, if installed
> >        dns-nameservers 1.1.1.1 8.8.8.8
> > 
> > Are you saying that I can cut out the above contents and paste them into a file called wlp7s0 (whose path is /etc/network/interfaces.d/)?
> > 
> 
> Yes, but you need to have this in /e/n/i
> 
> source-directory /etc/network/interfaces.d

That's correct. This line is by default there on (sufficiently recent)
Debians (yes, this time I double-checked ;-)

Cheers
-- 
t

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

#245785

On Tue 01 Mar 2022 at 13:22:37 (+0100), tomas@tuxteam.de wrote:
> On Tue, Mar 01, 2022 at 12:16:44PM +0000, Tim Woodall wrote:
> > On Mon, 28 Feb 2022, Stella Ashburne wrote:
> 
> [...]
> 
> > > # The primary network interface
> > > allow-hotplug wlp3s0
> > > iface wlp7s0 inet static
> > >        wpa-ssid JupiterRising
> > >        wpa-psk {a long string of alphanumeric characters}
> > >        address 192.168.1.99/24
> > >        gateway 192.168.1.1
> > >        # dns-* options are implemented by the resolvconf package, if installed
> > >        dns-nameservers 1.1.1.1 8.8.8.8
> > > 
> > > Are you saying that I can cut out the above contents and paste them into a file called wlp7s0 (whose path is /etc/network/interfaces.d/)?
> > > 
> > 
> > Yes, but you need to have this in /e/n/i
> > 
> > source-directory /etc/network/interfaces.d
> 
> That's correct. This line is by default there on (sufficiently recent)
> Debians (yes, this time I double-checked ;-)

I think you need to triple-check then. The Debian default line is

  source /etc/network/interfaces.d/*

which relaxes the restrictions on filename patterns that are
read by source-directory /etc/network/interfaces.d.

Cheers,
David.

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

#245788

[Multipart message — attachments visible in raw view] — view raw

On Tue, Mar 01, 2022 at 08:37:15AM -0600, David Wright wrote:

[...]

> I think you need to triple-check then. The Debian default line is

(note to self: triple-check next time ;-)

Cheers
-- 
t

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

#245786

Dearie

Thanks for your clarification.

> Sent: Tuesday, March 01, 2022 at 8:16 PM
> From: "Tim Woodall" <debianuser@woodall.me.uk>
> To: "Stella Ashburne" <rewefie@gmx.com>
> Cc: debian-user@lists.debian.org
> Subject: Re: What should I put inside the file called wlan0?
>
> On Mon, 28 Feb 2022, Stella Ashburne wrote:
>
> > Dearie,
> >
> > Thanks for your reply.
> >
> >> Sent: Tuesday, March 01, 2022 at 3:10 AM
> >> From: tomas@tuxteam.de
> >> To: debian-user@lists.debian.org
> >> Subject: Re: What should I put inside the file called wlan0?
> >
> >
> > Are you saying that I can cut out the above contents and paste them into a file called wlp7s0 (whose path is /etc/network/interfaces.d/)?
> >
>
> Yes, but you need to have this in /e/n/i
>

Did you mean /etc/network/interfaces AND /etc/network/interfaces.d/wlp3s0 each must have the following contents:

# The primary network interface
allow-hotplug wlp3s0
iface wlp3s0 inet static
       wpa-ssid JupiterRising
       wpa-psk {a long string of alphanumeric characters}
       address 192.168.1.99/24
       gateway 192.168.1.1
       # dns-* options are implemented by the resolvconf package, if installed
       dns-nameservers 1.1.1.1 8.8.8.8


> source-directory /etc/network/interfaces.d
>
What did you mean by source-directory /etc/network/interfaces.d ? I am a bit confused.

Best regards.

Stella

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

#245789

On Tue, 1 Mar 2022, Stella Ashburne wrote:

> Dearie
>
> Thanks for your clarification.
>
>> Sent: Tuesday, March 01, 2022 at 8:16 PM
>> From: "Tim Woodall" <debianuser@woodall.me.uk>
>> To: "Stella Ashburne" <rewefie@gmx.com>
>> Cc: debian-user@lists.debian.org
>> Subject: Re: What should I put inside the file called wlan0?
>>
>> On Mon, 28 Feb 2022, Stella Ashburne wrote:
>>
>>> Dearie,
>>>
>>> Thanks for your reply.
>>>
>>>> Sent: Tuesday, March 01, 2022 at 3:10 AM
>>>> From: tomas@tuxteam.de
>>>> To: debian-user@lists.debian.org
>>>> Subject: Re: What should I put inside the file called wlan0?
>>>
>>>
>>> Are you saying that I can cut out the above contents and paste them into a file called wlp7s0 (whose path is /etc/network/interfaces.d/)?
>>>
>>
>> Yes, but you need to have this in /e/n/i
>>
>
> Did you mean /etc/network/interfaces AND /etc/network/interfaces.d/wlp3s0 each must have the following contents:
>
> # The primary network interface
> allow-hotplug wlp3s0
> iface wlp3s0 inet static
>       wpa-ssid JupiterRising
>       wpa-psk {a long string of alphanumeric characters}
>       address 192.168.1.99/24
>       gateway 192.168.1.1
>       # dns-* options are implemented by the resolvconf package, if installed
>       dns-nameservers 1.1.1.1 8.8.8.8
>
>
>> source-directory /etc/network/interfaces.d
>>
> What did you mean by source-directory /etc/network/interfaces.d ? I am a bit confused.
>
> Best regards.
>
> Stella
>
>
>

My /etc/network/interfaces has:
# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d


and then in /etc/network/interfaces.d I have a separate file for each
interface I want to configure.

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

#245791

On Tue, Mar 01, 2022 at 02:42:29PM +0000, Tim Woodall wrote:
> My /etc/network/interfaces has:
> # interfaces(5) file used by ifup(8) and ifdown(8)
> # Include files from /etc/network/interfaces.d:
> source-directory /etc/network/interfaces.d

Did you write this file yourself, or are you using something other
than Debian?  Just curious.

unicorn:~$ grep interfaces /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*

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

Page 1 of 3  [1] 2 3  Next page →

Back to top | Article view | linux.debian.user

csiph-web