Re: [Madwifi-users] A few problems

[Josh (N. A. <no...@gn...>]

Andrew Findlay wrote:
> Maybe a change in the structure of the network scripts will be needed in
> the longer term. You have only one wireless interface, but it is used
> in several different environments. If those environments have ESSID
> broadcast turned on, the scripts could work out which config to used
> based on that. Unfortunately, some people have got the idea that turning
> off ESSID broadcast is good for security, so this will not always work.

Personally I have a script that I run whenever I change locations.  It 
prompts me for my current location and acts accordingly:

laptop {root} [08:17:14] <~> ./changeloc.sh
Select your location:

0) Home
1) Work
2) essidany

Choose between 0 and 2 [0] -> 1

You choose your option, and it will do iwconfig with the right 
parameters for your location as well as whatever modprobes, dhclient, 
ntp restart, etc. are required.

If your wireless card is a PCMCIA, you can also use the
'cardctl scheme'.

Ideally you should be able to un-suspend your laptop and have it 
auto-figure out where you are and react accordingly, but I haven't put 
the work into figuring out the right way to do this yet.


>>2) The other problem I have is not directly related to madwifi. It has
>>got to do with XServer. When I connect to my university wireless
>>network the dhcp server assigns a hostname to my  laptop. But when I
>>go home and start my laptop ( I don't shutdown my laptop, I put it to
>>sleep using /proc/acpi/sleep interface) at home and connect to my home
>>wireless network the hostname is no longer valid. As a result the
>>XServer doesn't start any new windows. I get the following error when
>>I try to open anything:
>>Xlib: connection to ":0.0" refused by server
>>Xlib; Client is not authorized to connect to Server
>>Gtk-Warning **: cannot open display: :0

This is a silly redhat thing.  My solution:

1) hostname laptop
2) vi /etc/sysconfig/network (change hostname to 'laptop' in this file)
3) vi /etc/hosts (add 'laptop' to the list of hostnames for 127.0.0.1)

Of course you can use any name you want instead of 'laptop'.

You could also use 'xhost +' to disable access control so that a client 
from any hostname can connect, but you might not like that level of 
insecurity.

Yet another way would be to put the possible hostnames in the access 
control list by doing 'xhost +<hostname>'.  Thus even with access 
control enabled those hostnames would e allowed to connect.

I think you can also do 'xhost +<username>' to allow you to connect from 
any hostname as long as your username is right, but that might require 
identd.

-- 
Josh "Norm" Audette <no...@gn...>
Visit http://www.gnurple.net