Re: Wireless : best policy / pratice to start it
On Wed, Jul 26, 2006 at 04:37:50PM -0600, Rob Sims wrote:
> I just discovered network-manager{,-kde} which I now have working on my
...
> I did need to add a stanza to /etc/dbus-1/system.d/knetworkmanager.conf:
>
>
>
>
>
>
>
...which is corrected in today's sid upload.
--
Rob
signature.asc
Description: Digital signature
Re: Wireless : best policy / pratice to start it
On Mon, Jul 24, 2006 at 08:51:50PM +0200, Bruno Costacurta wrote:
> I'm looking for the best policies / practices to start wireless networking.
> Briefly I use wireless in following locations:
>
> -home:
> wpa via wpa_supplicant
>
> -public (bars..etc..):
> no wep/wpa
>
> Both works fine. Currently I start a console logged with user root to call
> ifup with related params.
> Should I used root to call ifup ?
> I would like to keep a manual connection as I do not want to automatically
> connect.
I just discovered network-manager{,-kde} which I now have working on my
orinoco based and ipw2200 based laptops with kernel 2.6.17. Makes
managing connections painless. Simply add users who need permission to
manage the interface to the netdev group and run. I don't use WPA (WEP
only), but the package depends on wpasupplicant, so WPA should be
supported.
I did need to add a stanza to /etc/dbus-1/system.d/knetworkmanager.conf:
...to match the corresponding stanza in NetworkManager.conf. The package is
not in sarge.
Connects automatically to "trusted" nets, but not untrusted.
--
Rob
signature.asc
Description: Digital signature
Re: Wireless : best policy / pratice to start it
On Mon, Jul 24, 2006 at 08:51:50PM +0200, Bruno Costacurta wrote.. > I'm looking for the best policies / practices to start wireless > networking. Briefly I use wireless in following locations: > > -home: wpa via wpa_supplicant > > -public (bars..etc..): no wep/wpa > > Both works fine. Currently I start a console logged with user root > to call ifup with related params. Should I used root to call ifup > ? I would not log in as root to start ifup. Instead use sudo. apt-cache show sudo >>> Sudo is a program designed to allow a sysadmin to give limited root privileges to users and log root activity. The basic philosophy is to give as few privileges as possible but still allow people to get their work done. Kevin -- Kevin Coyner GnuPG key: 1024D/8CE11941 http://rustybear.com/publickey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Wireless : best policy / pratice to start it
Wireless encryption is a good start, preferably 128-bit. If you have an access filter on your router to govern which machines access the network, enable it also and give the router your MAC address as its first/only entry. Not to state the obvious, but change your router's password from the default and enable blocking for any questionable ports which show up via a quick netstat -plant. I have a wireless network with two computers and these steps seem to work well for me. R. On Monday 24 July 2006 01:51 pm, Bruno Costacurta wrote: > Hello, > > I'm looking for the best policies / practices to start wireless networking. > Briefly I use wireless in following locations: > > -home: > wpa via wpa_supplicant > > -public (bars..etc..): > no wep/wpa > > Both works fine. Currently I start a console logged with user root to call > ifup with related params. > Should I used root to call ifup ? > I would like to keep a manual connection as I do not want to automatically > connect. > > Hereafter my partial file 'interface' > > (snip) > # wireless public places > iface public inet dhcp > wireless-essid any > wireless-key off > > # wireless at home using wpa > iface homewpa inet static > wpa_driver wext > wpa-conf /home/bruno/.wpa/wpa_supplicant.conf > address 192.168.1.4 > netmask 255.255.255.0 > gateway 192.168.1.1 > (snip) > > > Bye, > Bruno -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
