Finding my WLAN IP address.

[David Vincent]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>> | feisty at feisty-laptop:~$ ifconfig
>> | eth0      Link encap:Ethernet  HWaddr 00:15:C5:C8:13:D1
>> |           UP BROADCAST MULTICAST  MTU:1500  Metric:1
> ...
>> | eth1      Link encap:Ethernet  HWaddr 00:18:DE:98:C7:34
>> |           UP BROADCAST MULTICAST  MTU:1500  Metric:1
> ...
>> | eth0:avah Link encap:Ethernet  HWaddr 00:15:C5:C8:13:D1
>> |           inet addr:169.254.8.89  Bcast:169.254.255.255 
>> |           Mask:255.255.0.0
>> |           UP BROADCAST MULTICAST  MTU:1500  Metric:1
>> |           Interrupt:22
> 
>> according to this your connected via eth0 ethernet.  not wireless.
>> unplug and give ifdown eth0 and then ifup ath0 a shot, see what happens.
> 
> It doesn't really show that.  Because it didn't get any connection on eth0
> or eth1, avahi set up a pseudo-connection - that's just the same address
> that Windows will give you if you have no connection.

It's called an "APIPA" address, Automatic Private IP Address.
169.254.x.y is a range Microsoft reserved for use for an OS which is
unable to contact a DHCP server.

In this way, machines which use this method can be hooked up to a hub or
switch and they will automatically choose IP addresses in the same
subnet and be able to talk and share their resources.

Note there are about 64516 IPs in that pool so while they do choose
random IPs there is a chance that they will choose the same IP and
create issues, however that chance is pretty low.

Weird one Dotan!  Your computer shouldn't be talking on the network but
we all received that email....do you have one of those new Quantum NICs
with the Flux Capacitor?

- -d
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH4S/wfpRzWFIV0XMRAuvhAJ0WwYUISWXb7Igyc1x1qjp2c2WZ0ACeMF9d
Hw88IzR9d6qfNUoFBBLgbpI=
=Lzol
-----END PGP SIGNATURE-----