[SATLUG] Wireless Driver Installation
wg5o at sbcglobal.net
Fri Jun 27 11:28:17 CDT 2008
My additional efforts only succeeded in turning OUT the WiFi card light.
I'm taking way too much of everyone's time. I'm going to temporarily
move the modem back here, plug in an Ethernet cable, and update my
Ubuntu. Then, I'll try again. I'll report when I've done that.
Many thanks to all of you patient people.
Bruce Dubbs wrote:
> FIRESTORM_v1 wrote:
>> He's using a 2wire router. These things are the most ornery things to
>> work with. They have batty IP ranges, oddball DHCP options and are
>> generally a pain in the rear. I don't mean to sound bullish, but the
>> 2wire does really hand out bizarre IP ranges like this and by some act
>> of the divine, they actually route!
> Good to know.
>> On Thu, Jun 26, 2008 at 3:35 PM, Andy Pickens <wg5o at sbcglobal.net>
>>> a. Oops. Did you set the IP addresses manually? The IP address
>>> is always localhost the numbers after 127 are meaningless. Try using
>>> 10.x.x.x, 172.16.x.x, or 192.168.x.x instead.
>>> No. I put in DHCP and left IP address, Subnet mask, & Gateway
>>> address all
>>> b. Are you running your own DNS server at 172.16.0.1?
>>> No. That is the product of my confusion. I have to find how to ID
>>> the DNS,
>>> but that won't keep me form receiving, will it? How do you find DNS?
>>> c. Most routers for home systems use a 192.168.1.x/255.255.255.0
>>> scheme. Your systems need to use the same address scheme as the router.
>>> Usually this is done automatically with dhcp.
>>> See above. But, in XP, if I select Start, Run,cmd, and at the
>>> prompt type,
>>> "ipconfig," it shows that both ethernet local adapters are
>>> disconnected, &
>>> Ethernet adapter Wireless Network Connection 4:
>>> Connection-specific DNS Suffix: gateway.2wire.net
>>> IP Address: 172.16.1.34
>>> Subnet Mask: 255.255.0.0
>>> Default Gateway: 172.16.0.1
>>> So, somehow, I picked that last one up & used it for DNS.
> DHCP should set the DNS for you. It is probably not the gateway, but
> it could be, depending on the setup and software of the router. In
> any case, we don't need it until after we get the connection and have
> dhcp give you your IP address.
> The numbers above are the standard Class B private addresses. They
> are OK.
> You can set up your system for static IP addresses using the above.
> The main problem right now is not establishing a wireless connection.
>>> d. You will need to get away from WEP. It is not secure. You need
>>> to use
>>> WPA, but I recommend disabling encryption completely until you can
>>> get a
>>> basic connection. Then we can go back and secure it properly.
>>> I seem to have a personal problem with this one. I dug back and
>>> found out
>>> how to do it, but the system rejects the password I have recorded.
>>> My, my
> Check the documentation, including on line, to see if there is a way
> to reset the password to factory default.
> -- Bruce
More information about the SATLUG