From: Don Raikes <don.raikes@oracle.com>
To: "Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>
Subject: RE: /etc/network/interfaces
Date: Thu, 13 Jun 2013 10:08:03 -0700 (PDT) [thread overview]
Message-ID: <8a1ee7c5-ed29-4c7d-babe-cbcb0c4a3cae@default> (raw)
In-Reply-To: <20130613061700.GB12774@jdc.jasonjgw.net>
Ok, so I haven't looked at wpasupplicant yet, but is there any kind of quick and dirty tutorial on how to get debian up and running on a wireless network?
I have both wired and wireless connections here, and would like ot be able to use the wireless when I move from office to office (actually from my home office to the family room :-) ).
-----Original Message-----
From: Jason White [mailto:jason@jasonjgw.net]
Sent: Wednesday, June 12, 2013 11:17 PM
To: speakup@linux-speakup.org
Subject: Re: /etc/network/interfaces
Gregory Nowak <greg@gregn.net> wrote:
> It's been a while since I had access to multiple networks. From what I
> recall, each connection requires its own wlan0 configuration block
> (I.E. you can't have multiple network configurations for the same wlan
> interface). You also can't have multiple wlan0 interfaces defined at
> the same time, or you'll get an error.
>
My recollection is that you can label the connections in the interfaces file, and then bring up the right connection manually with the ifup command.
> My quick and dirty work around was to comment out the network I didn't
> want to use, and to uncomment the one I did. If you don't want to play
> with commenting and uncommenting your interfaces file every time you
> want to connect to a different network, then wpasupplicant can be
> configured to connect to multiple networks, and to prefer one over
> another if they are both in range. Have a look at the wpa_supplicant,
> and wpa_supplicant.conf man pages. Oh yes, and from what I recall,
> wpasupplicant does integrate nicely with your interfaces file.
It's the right tool to use for wireless networks, especially if they're using WPa 2, as they should be for security reasons.
_______________________________________________
Speakup mailing list
Speakup@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
/etc/network/interfaces Doug Smith
` /etc/network/interfaces Gregory Nowak
` /etc/network/interfaces Jason White
` Don Raikes [this message]
` /etc/network/interfaces Gregory Nowak
` /etc/network/interfaces Jason White
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8a1ee7c5-ed29-4c7d-babe-cbcb0c4a3cae@default \
--to=don.raikes@oracle.com \
--cc=speakup@linux-speakup.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).