<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1276" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><SPAN
style="mso-fareast-font-family: 'MS Mincho'"><SPAN
class=740490518-03042004><FONT face="Courier New" size=2>All the below was true
as of yesterday, but today, once again, things happened a little
differently. It's very strange that driverloader never behaves the same
way twice, especially after a re-boot.</FONT></SPAN></SPAN></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><SPAN
style="mso-fareast-font-family: 'MS Mincho'"><SPAN
class=740490518-03042004><FONT face="Courier New"
size=2></FONT></SPAN></SPAN> </P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><SPAN
style="mso-fareast-font-family: 'MS Mincho'"><SPAN
class=740490518-03042004><FONT face="Courier New" size=2>I noticed that my modem
responds to the iwlist scan with a mode of "Auto", which I dont recall seeing
anywhere else. Root of the problem?</FONT></SPAN></SPAN></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><SPAN
style="mso-fareast-font-family: 'MS Mincho'"><SPAN
class=740490518-03042004><FONT face="Courier New"
size=2>----------------------------</FONT></SPAN></SPAN></P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><SPAN
style="mso-fareast-font-family: 'MS Mincho'"><SPAN
class=740490518-03042004></SPAN></SPAN><SPAN
style="mso-fareast-font-family: 'MS Mincho'"><SPAN
class=740490518-03042004></SPAN></SPAN><SPAN
style="mso-fareast-font-family: 'MS Mincho'"><FONT face="Courier New"
size=2></FONT></SPAN> </P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><SPAN
style="mso-fareast-font-family: 'MS Mincho'"><FONT face="Courier New"
size=2></FONT></SPAN> </P>
<P class=MsoPlainText style="MARGIN: 0in 0in 0pt"><SPAN
style="mso-fareast-font-family: 'MS Mincho'"><FONT face="Courier New"><FONT
size=2>It has been a long strange road to get this D-link card working, but
for<BR>the benefit of all, here is how I can <SPAN
class=740490518-03042004>"</SPAN>reliably<SPAN class=740490518-03042004>"</SPAN>
get a link to my 2Wire<BR>wireless DSL modem (SBC DSL service).<SPAN
style="mso-spacerun: yes"> </SPAN>I am using Mandrake 10CE with
the<BR>stock Kernel 2.6.3-4 from the download disks, but with many updates
from<BR>the updates list.<BR><BR>It usually happens that since eth0 is attempted
on boot (driverloader<BR>aliased to eth0 in modules.conf), and inevitably an IP
is NEVER grabbed<BR>on boot, I usually pull the card out of the slot to boot so
I dont waste<BR>the minute or two the boot process hangs and I can get to the
parts that<BR>work.<SPAN style="mso-spacerun: yes"> </SPAN><BR><BR>After
booting, pop in card, open up a console, give an iwlist scan, if<BR>it finds my
modem, then an ifup eth0 usually gets me going.<SPAN
style="mso-spacerun: yes"> </SPAN>Today I had<BR>an unusual message after
the ifup eth0:<BR>--------------------------<BR>[root@localhost robert]# ifup
eth0<BR>Determining IP information for eth0...SIOCADDRT: File exists<BR><SPAN
style="mso-spacerun: yes"> </SPAN>done.<BR>--------------------------<BR>What
is the SIOCADDRT?<SPAN style="mso-spacerun: yes"> </SPAN>I've never gotten
that output before.<BR><BR>Other issues:<SPAN style="mso-spacerun: yes">
</SPAN>if the iwlist scan doesnt find the modem, I change the<BR>mode to Ad-hoc
which causes the 'Link' to go green, then issue and ifup<BR>eth0 which will NOT
get an IP from the modem, so now change back to the<BR>Managed mode, and re-scan
which usually now finds the modem, then an<BR>ifup eth0 gets me connects (and
without the SIOCADDRT message from<BR>above).<BR><BR>If any combination of the
above doesnt work, I ifdown, remove card and<BR>begin again.<SPAN
style="mso-spacerun: yes"> </SPAN>Usually I get an ip, but sometimes it
can take a while<BR><BR>Here is my ifconfig-eth0
file:<BR>DEVICE=eth0<BR>BOOTPROTO=dhcp<BR>ONBOOT=yes<BR>ESSID=2WIRE360<BR>MODE=Managed<BR>HWADDR=00:05:5d:98:1d:32<BR>MII_NOT_SUPPORTED=yes<BR>WIRELESS_ENC_KEY=""<BR>NEEDHOSTNAME=yes<BR><BR><BR>This
is the output of the iwlist scan immediately after boot and card<BR>insertion
(found on first try):<BR>[root@localhost robert]# iwlist scan<BR>lo<SPAN
style="mso-spacerun: yes">
</SPAN>Interface doesn't support scanning : Operation not
supported<BR><BR>eth0<SPAN
style="mso-spacerun: yes"> </SPAN>Scan completed
:<BR><SPAN
style="mso-spacerun: yes">
</SPAN>Cell 01 - Address: 00:D0:9E:EF:1F:D1<BR><SPAN
style="mso-spacerun: yes">
</SPAN>ESSID:"2WIRE360"<BR><SPAN
style="mso-spacerun: yes">
</SPAN>Mode:Managed<BR><SPAN
style="mso-spacerun: yes">
</SPAN>Frequency:2.437GHz<BR><SPAN
style="mso-spacerun: yes">
</SPAN>Quality:1/1<SPAN style="mso-spacerun: yes"> </SPAN>Signal level:-82
dBm<SPAN style="mso-spacerun: yes"> </SPAN>Noise level:-200 dBm<BR><SPAN
style="mso-spacerun: yes">
</SPAN>Encryption key:off<BR><SPAN
style="mso-spacerun: yes">
</SPAN>Bit Rate:1Mb/s<BR><SPAN
style="mso-spacerun: yes">
</SPAN>Bit Rate:2Mb/s<BR><SPAN
style="mso-spacerun: yes">
</SPAN>Bit Rate:5.5Mb/s<BR><SPAN
style="mso-spacerun: yes">
</SPAN>Bit Rate:11Mb/s<BR><SPAN
style="mso-spacerun: yes">
</SPAN>Bit Rate:22Mb/s<BR><SPAN
style="mso-spacerun: yes">
</SPAN>Extra:bcn_int=100<BR><BR><BR>One issue that I am not sure about is how
the setup software for the<BR>windows based D-link card and the modem work to
set the host name.<SPAN style="mso-spacerun: yes"> </SPAN>In<BR>windows
(and when I used a Xircom wired lan card) my computer was given<BR>a name other
than localhost.<SPAN style="mso-spacerun: yes"> </SPAN>I booted into
windows and went to the<BR>modem's configuration interface and changed the
computer name to local<BR>host.<SPAN style="mso-spacerun: yes"> </SPAN>I
cant say for sure if this had any effect, but there is less<BR>confusion and
opportunities for breakage as far as I can tell.<BR><BR>Robert F<?xml:namespace
prefix = o ns = "urn:schemas-microsoft-com:office:office"
/><o:p></o:p></FONT></FONT></SPAN></P></FONT></DIV></BODY></HTML>