Re: Linux Newbie & Wireless

2001-09-22 Thread Ben Reser

On Sun, Sep 23, 2001 at 04:20:01AM +0200, Henrik Edlund wrote:
> (On Solaris it is "hme" instead of "eth" as a standard.)

Actually their was no standard on Solaris.  The interface name was
dependent on the driver.  hme just occurred most often because Solaris
on Sparc's generally had NICs that used the same driver.

If you run Solaris on X86 it seems like every machine has a different
naming convention...

-- 
Ben Reser <[EMAIL PROTECTED]>
http://ben.reser.org

"Before you set out for revenge dig two graves."
- Chinese Saying




Re: Linux Newbie & Wireless

2001-09-22 Thread Henrik Edlund

On Sat, 22 Sep 2001, Terrence Oblak wrote:

TO> I was planning on doing the following, again any input would be greatly
TO> appreciated:
TO>
TO> Write a script that would:
TO> 1)  Shutdown eth0 device
TO> 2)  Copy the correct ifcgf-eth0.xx script on top of
TO>  ifcgf-eth0
TO> 3)  Restart the eth0 device
TO> 4)  Restart the service to obtain a new IP address
TO>
TO> Is possible?  Or is there a better way of accomplishing what I want to do?

Easiest is to create:

ifcfg-eth0
ifcfg-eth1

And use 0 for home and 1 for work. Linux doesn't care what you call your
interfaces, you could call them "yabba32" or something, but "eth" is the
Linux "standard" naming convention. You can even have a ifcfg-eth2 for the
built-in NIC. (On Solaris it is "hme" instead of "eth" as a standard.)

-- 
Henrik Edlund <[EMAIL PROTECTED]>
http://www.edlund.org/

"You're young, you're drunk, you're in bed, you have knives; shit
happens." -- Angelina Jolie





Re: Linux Newbie & Wireless

2001-09-22 Thread Terrence Oblak

I would like to thank everyone for the replies.  It worked, my portable is 
truely portable.

I spent 4 hours researching on the internet and trying different settings.  I 
must have missed something somewhere.

I do have one more question:

I have access to a wireless network at home and at work so I was planning on 
creating two ifcgf-eth0 scripts:
1)  ifcgf-etho.home
2)  ifcgf-eth0.work

I was planning on doing the following, again any input would be greatly 
appreciated:

Write a script that would:
1)  Shutdown eth0 device
2)  Copy the correct ifcgf-eth0.xx script on top of
 ifcgf-eth0
3)  Restart the eth0 device
4)  Restart the service to obtain a new IP address

Is possible?  Or is there a better way of accomplishing what I want to do?

Thanks,

Terrence Oblak




Re: Linux Newbie & Wireless

2001-09-22 Thread Ben Reser

On Sat, Sep 22, 2001 at 08:17:08PM -0400, Anthony Procaccini wrote:
> Hmm - I wasn't aware of the hanging boot aspect of airport access. Is 
> there any way around this? I might boot into Linux at work as well. 
> If I have a network cable attached, will it still hang since it can 
> see the eth1 connection?

Actually it's not really airport that has the issue.  It's DHCP.  If
your method of getting addresses is DHCP it will attempt to get an
address.  If it can't get an address it will wait an annoyingly long
period of time till it times out.

Couple solutions turn off the ONBOOT and manually bring up the interface
ala ifup eth0

or

Just remember to disable the interface before going somewhere where you
don't have wireless.

If you use DHCP on one interface and don't disable it but have another
interface that comes up fine the one with DHCP will still hang.

-- 
Ben Reser <[EMAIL PROTECTED]>
http://ben.reser.org

"Before you set out for revenge dig two graves."
- Chinese Saying




Re: Linux Newbie & Wireless

2001-09-22 Thread Henrik Edlund

On Sat, 22 Sep 2001, Anthony Procaccini wrote:

AP> Hmm - I wasn't aware of the hanging boot aspect of airport access. Is
AP> there any way around this? I might boot into Linux at work as well.
AP> If I have a network cable attached, will it still hang since it can
AP> see the eth1 connection?

in the cfg file change to

  ONBOOT=no

and then just do "/etc/sysconfig/network-scripts/ipup eth1" when you want
wireless access.

-- 
Henrik Edlund <[EMAIL PROTECTED]>
http://www.edlund.org/

"You're young, you're drunk, you're in bed, you have knives; shit
happens." -- Angelina Jolie





Re: Linux Newbie & Wireless

2001-09-22 Thread Anthony Procaccini

>
>
>And it should work.   In the future you won't have to do either it
>should just come up when you boot.  But fair warning if you're away from
>a access point your boot will hang while it tries to get an address via
>DHCP.
>
>--
>Ben Reser <[EMAIL PROTECTED]>
>http://ben.reser.org

Hmm - I wasn't aware of the hanging boot aspect of airport access. Is 
there any way around this? I might boot into Linux at work as well. 
If I have a network cable attached, will it still hang since it can 
see the eth1 connection?

TIA!

Tony Procaccini

-- 




Re: Linux Newbie & Wireless

2001-09-22 Thread Ben Reser

On Sat, Sep 22, 2001 at 10:20:52AM -0600, Terrence Oblak wrote:
> Could someone give me detailed instructions for getting my wireless  
> connection working?  The more detailed the instructions the better, please 
> remember that Linux is very new to me, so something that might be obvious to 
> you probably isn't to me.  

Actually it's pretty easy.
Edit /etc/modules.conf
Add a line like this:
alias eth0 airport

(note you can set eth0 to whatever interface you like).
I use the following lines:
alias eth0 airport
alias eth1 gmac

That puts my airport on eth0 and my internal ethernet of my Titanium on
eth1.

Make sure you've installed wireless-tools-20-4mdk.
It's on the installation CD, just install it via:
rpm -Uvh wireless-tools-20-4mdk.ppc.rpm

Create or edit your /etc/sysconfig/network-scripts/ifcfg-eth0 (assuming
that your airport is on eth0).

Put something like the following:
DEVICE=eth0
BOOTPROTO=dhcp
NETMASK=255.255.255.0
ONBOOT=yes
WIRELESS_ENC_KEY=encryptionkeyforwep
WIRELESS_ESSID=nameofaccesspoint

For the encryption key if you're using a text password as a key use
something like this:
s:abcde

Otherwise if it's just entering the hex key.

At this point I'd probably reboot to make sure that the airport shows on
the right ethernet interface.  If you're sure it already is then you
should be able to just do: modprobe airport
Then ifup eth0

And it should work.   In the future you won't have to do either it
should just come up when you boot.  But fair warning if you're away from
a access point your boot will hang while it tries to get an address via
DHCP.

-- 
Ben Reser <[EMAIL PROTECTED]>
http://ben.reser.org

"Before you set out for revenge dig two graves."
- Chinese Saying