LinkSys WRE54G, LinkSyS Wireless G PCI (Broadcom), 802.11b Router
Bluewhite64This forum is for the discussion of Bluewhite64 Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
LinkSys WRE54G, LinkSyS Wireless G PCI (Broadcom), 802.11b Router
I simply can't handle networking, sorry.
I need your considerable help, folks. I have a LinkSyS WRE54G Range Expander setup to access my park's wireless network which consists of a 802.11b router with a 64 bit WEP passphrase. The Range Expander has been configured to run on channel 1 with an IP address of 192.168.1.240 with a netmask of 255.255.255.0 . Since both lights, links and activity, on the Range Expander are blue, it appears to communicating with the park's wireless router fine. However, for the life of me, I don't have enough knowledge to configure BW64 12.1 to communicate with this Range Expander so I can access the internet. I was attempting to use my D-Link WBR-1310 router, but I've abandoned it. I have a LinkSys Wireless G PCI card with a Broadcom chipset that I want to use to communicate to the park's 802.11b router THROUGH my Range Expander, because the Range Expander significantly boosts the poor signal coming from the 802.11b router. TIA
As I get time, I'll post some more details here from rc.inet1.conf and terminal output ...
So you need to configure the wireless card in the computer to connect to this Extender device?
Is there some specific configuration required with this, or are you just asking how to configure the wireless interface in general?
Yes. Although the WRE54G has an autoconfiguration button, it doesn't work too well with protected networks so I've resorted to manually configuring the Range Expander in Vista. Basically, I'm just asking how to configure my LinkSyS Wireless G PCI card to communicate with this Range Expander. With my current configuration, I constantly get the message, no carrier on wlan1, which I assume to be no carrier for a DHCP server.
# This file contains the configuration settings for network interfaces.
# If USE_DHCP[interface] is set to "yes", this overrides any other settings.
# If you don't have an interface, leave the settings null ("").
# You can configure network interfaces other than eth0,eth1... by setting
# IFNAME[interface] to the interface's name. If IFNAME[interface] is unset
# or empty, it is assumed you're configuring eth<interface>.
# Several other parameters are available, the end of this file contains a
# comprehensive set of examples.
# Config information for eth0:
# Config information for eth1:
# Config information for eth2:
# Config information for eth3:
# Default gateway IP address:
# Change this to "yes" for debugging output to stdout. Unfortunately,
# /sbin/hotplug seems to disable stdout so you'll only see debugging output
# when rc.inet1 is called directly.
## Example config information for wlan0. Uncomment the lines you need and fill
## in your data. (You may not need all of these for your wireless network)
#WLAN_IWPRIV="set AuthMode=WPAPSK | set EncrypType=TKIP | set WPAPSK=96389dc66eaf7e6efd5b5523ae43c7925ff4df2f8b7099495192d44a774fda16"
## Some examples of additional network parameters that you can use.
## Config information for wlan0:
#IFNAME="wlan0" # Use a different interface name instead of
# the default 'eth4'
#IFNAME="eth0:1" # Set up an IP alias.
#HWADDR="00:01:23:45:67:89" # Overrule the card's hardware MAC address
#MTU="" # The default MTU is 1500, but you might need
# 1360 when you use NAT'ed IPSec traffic.
#DHCP_TIMEOUT=15 # The default timeout for the DHCP client to
# wait for server resonse is 30 seconds, but
# you might want a shorter wait.
#DHCP_KEEPRESOLV="yes" # If you dont want /etc/resolv.conf overwritten
#DHCP_KEEPNTP="yes" # If you don't want ntp.conf overwritten
#DHCP_KEEPGW="yes" # If you don't want the DHCP server to change
# your default gateway
#DHCP_IPADDR="" # Request a specific IP address from the DHCP
#WLAN_ESSID=DARKSTAR # An example of how you can override _any_
# parameter defined in rc.wireless.conf, by
# prepending 'WLAN_' to the parameter's name.
# Useful with multiple wireless interfaces.
#WLAN_IWPRIV="set AuthMode=WPAPSK | set EncrypType=TKIP | set WPAPSK=thekey"
# Some drivers require a private ioctl to be
# set through the iwpriv command. If more than
# one is required, you can place them in the
# IWPRIV parameter (separated with the pipe (|)
# character, see the example).
#WLAN_WPA="wpa_supplicant" # Run wpa_supplicant for WPA support
#WLAN_WPADRIVER="ndiswrapper"# Tell wpa_supplicant to specifically use the
# ndiswrapper driver (if you leave this empty
# the 'wext' driver is used by default)
#WLAN_WPAWAIT=30 # In case it takes long for the WPA association
# to finish, you can increase the wait time
# (defaults to 10 seconds)
In the previous post, the key was intentionally blanked. It's a 64 bit passphrase. I use the 10 hex digits representation of key in wlan_key.
As one can see from the scan of wlan1, the stronger signal of Rural Broadband_S is the Range Expander at MAC 00:1d:xx:0a:xx:b6 . I was attempting to use the 64 bit ndis driver here that used to work fine on another wireless network. The output of iwconfig shows the wlan1 driver's ap as Not-Associated. Using the command as root, iwconfig wlan1 ap 00:1d:7e:0a:09:b6 changes nothing ... still Not-Associated. Remember, that this process is only for the 64 bit ndiswrapper driver, bcmwl5.sys, IIRC. With the b43/ssb driver, I don't get Not-Associated errors, but I still get No carrier (DHCP) detected on wlan1.
Gee whiz, guys and gals... I appreciate the feedback!
Anyhow, I decided to just use Verizon's network for the next two years. The first log onto their network was a bit shaky, but access to the internet seems fine now on Vista. Now, I just have to figure out how to use this Pantech USB modem with BlueWhite64. Maybe, I'll get a more constructive response on that issue.
Since the Pantech modem is detected at /dev/ttyACM0, I simply setup ppp with the script, pppsetup. The only difficulty lies in selecting the chap authentication script. Simply press the spacebar when prompted for a username and password or the pppsetup script won't complete. Once the pppsetup.txt file has been created, simply edit the file, chap-secrets, in /etc/ppp and remove the spaces between the quotation marks. Now, type ppp-go from the console and the you'll be connected to the verizon network. If the speed is a bit slow, you'll have to manually increase the speed of the modem, but that process should be rather trivial. I think the Pantech USB modem is rated at 921600 bps.
Sweet! Now I can use Linux on Verizon's network... it's been awhile since I last used ppp.
BTW, use atdt#777 for the telephone number when completing the pppsetup script.