[LBo] Link-local.

[Geoff Jones]

Lonnie Mullenix wrote 
> >From my experience, I would assume that the system is using the>
> 192.X.x.X address for the network.  I have Never gotten  any sort of
> connection with the 169.x.x.x IP addresses.  As Billy mentioned, with a
> windows system you would be getting the 'limited or no connectivity'
> with the 169.x.x.x address and in six plus years of running various
> Linux distros, I do not recall ever running into the 169.x.x.x address
> scheme.
>
> So, that leads to a couple of questions.  Does that Debian box have
> wireless capabilities?  Does the Debian box have two or more NIC cards
> installed?

1] No, the deb box is not wireless + 2] It only has 1 nic card .

I think you're right that it's using 192.x.x.x for network connection [ which 
loads all my settings in /etc/fstab ] - but I also get a warning from 
Zonealarm, on the other box, that " Firewall blocked internet access to your 
computer [ Netbios Datagram ] from 169.254.95.93". So it seems to me that the 
169.x.x.x ip is also trying to network ?

Do the below provide further info :- ???

1] "ip addr show" gives:-
1: lo: <LOOPBACK> mtu 16436 qdisc noqueue
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:0f:ea:19:01:2b brd ff:ff:ff:ff:ff:ff
    inet 169.254.95.93/16 brd 169.254.255.255 scope link eth0
    inet 192.168.1.102/24 brd 192.168.1.255 scope global eth0
    inet6 fe80::20f:eaff:fe19:12b/64 scope link
       valid_lft forever preferred_lft forever

2] "ifconfig" gives:-
eth0      Link encap:Ethernet  HWaddr 00:0F:EA:19:01:2B
          inet addr:169.254.95.93  Bcast:169.254.255.255  Mask:255.255.0.0
          inet6 addr: fe80::20f:eaff:fe19:12b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:48741 errors:0 dropped:0 overruns:0 frame:0
          TX packets:61748 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:10631459 (10.1 MiB)  TX bytes:7671898 (7.3 MiB)
          Interrupt:193 Base address:0xe400

3] "ip route show" gives:-
192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.102
169.254.0.0/16 dev eth0  proto kernel  scope link  src 169.254.95.93
default via 192.168.1.1 dev eth0

My main question is where does 169.x.x.x get configured when I already have a 
dhcp server that can handle a simple home network [ - initially I suspected 
the 169.x.x.x address on the local network was some sort of attack!].

Any further enlightenment appreciated,

Geoff.