LinuxQuestions.org
Review your favorite Linux distribution.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Mandriva
User Name
Password
Mandriva This Forum is for the discussion of Mandriva (Mandrake) Linux.

Notices


Reply
  Search this Thread
Old 04-21-2004, 04:43 AM   #16
snodnipper
LQ Newbie
 
Registered: Aug 2003
Location: UK
Distribution: Mandrake
Posts: 11

Rep: Reputation: 0

Quote:
Originally posted by suppaman
I just found out that the driver partially works. i can access my own router configuration which is 192.168.0.1 (Netgear MR314) However, I still cannot access the internet. It seems like I cannot get the ip address.
I'm confused as to what stage you've got to (do you need to register you MAC address with your WiFi router?)

If Linux problem:
You need to locate where your ifcfg-eth0 script is (this will tell you where you need to create the wlan0 script.
From there, you can input the HARDWARE ADDRESS OF YOUR DEVICE {I'm guessing you've found it, look on the side of the device} - you need to change the HWADDR variable.
Also, you need to make sure the protocol is set to DHCP (BOOTPROTO variable), to obtain an IP address
> then input your ESSID (i.e. the name of your access point).

Use Mandrake 10 if you have problems - it would solve your hassles!
 
Old 04-23-2004, 09:28 PM   #17
suppaman
LQ Newbie
 
Registered: Apr 2004
Location: Malaysia
Distribution: SuSE
Posts: 15

Rep: Reputation: 0
I got some files here

First file : ifcfg.template

# This is a template for a network interface configuration file used with ifup.
# See 'man 8 ifup' for details.
# Additionally to the following variables you can set every variable from the
# interface independent configurations files (config, dhcp, wireless) to
# overwrite the global settings.

# STARTMODE tells ifup when a interface should be set up. Possible values are:
# - onboot: start it at boot time
# - manual: start it only when ifup is called manually
# - hotplug: start it when ifup is called by hotplug or pcmcia
# - [off|ignore]: ignore this configuration
# Do not use 'onboot' for hotpluggable devices. That does not work.
STARTMODE=

# With BOOTPROTO you can choose between a 'static' configuration with fixed
# IP addresses or 'dhcp'. (bootp does not work on SuSE Linux 8.0)
BOOTPROTO=

# If using a static configuration you have to set an IP address and a netmask
# or prefix length. The following examples are equivalent:
# 1) IPADDR=192.168.1.1
# NETMASK=255.255.255.0
# 2) IPADDR=192.168.1.1
# PREFIXLEN=24
# 3) IPADDR=192.168.1.1/24
IPADDR=
NETMASK=
PREFIXLEN=

# Set the broadcast address of this interface. If you leave it empty a default
# will be used. See DEFAULT_BROADCAST in /etc/sysconfig/network/config.
BROADCAST=

# If you'd like to set up a point to point connection you may specify the
# remote IP here.
REMOTE_IPADDR=

# Set a label for the interface. See 'multiple addresses' below.
LABEL=

# This options defines whether the script /etc/ppp/poll.tcpip is run after
# connecting to the internet via a dialup connection or not. The script
# itself calls various jobs like fetchmail, fetchnews and sendmail.
# Default to yes
RUN_POLL_TCPIP=

# Have a look at the iproute2 documentation.
SCOPE=

# Every other option from "ip address add" can be added here.
IP_OPTIONS=

# Set a specific Maximum Transmission Unit (MTU) for this interface.
MTU=

# Set a specific link level address (LLADDR), a.k.a. MAC address or hardware address,
# for this interface (if the driver supports it).
LLADDR=

# Every other option from "ip link set" can be added here.
# Example:
# LINK_OPTIONS="multicast off"
LINK_OPTIONS=

# Multiple addresses (aka aliases)
# There are several ways to assign more than one IP address to a network
# interface. If you ever want to use YaST2 for this you should choose the
# first possibility:
# 1) one IP address per config file:
# create multiple copies of your master config files and add ':<string>' to
# the filenames of the copy. Prefer increasing number starting at 1.
# 2) multiple IP addresses per config file:
# You can extend the variable name 'IPADDR' by any string you like (IPADDR_1,
# IPADDR_FOO, IPADDRxxx, ...) and use these variables for your IP addresses.
# If you need some additional parameters for these addresses, then just add
# the same extension to these variable names.
# IPADDR_AAA=1.2.3.4
# NETMASK_AAA=255.0.0.0
# BROADCAST_AAA=1.2.3.55
# IPADDR_BBB=10.10.2.3/16
# LABEL_BBB=BBB
# an so on ...
#
# You do not need to set a label for any address. But then you should not use
# ifconfig any longer; go and use ip. If you want to use ifconfig then omit the
# label for your main address and set a label for every additional address.
# This is equivalent with using aliases with method 1.
#
# !!! YaST2 is not able to read multiple addresses from one file. Use this only
# if you configure your stuff manually anyway !!!

# Routing:
# If you need special routes for a configuration, then use a file named
# ifroute-<config> where <config> is the same string as in ifcfg-<config>.
# It has the same syntax like routes except one difference:
# If you omit the interface name (4th field) in the ifroute file it will be
# set to the current interface name when setting up the interface. You need to
# do this with hotpluggable devices, where you do not know which interface name
# they will get at the time when you plug them.
# See man 5 routes.


# Multiple DHCP clients:
#
# With two or more DHCP clients running, they would concurrently try to replace
# the default route or rewrite resolv.conf, rewrite ntp.conf etc. There are two
# ways of dealing with this conflict (and it is a conflict, because you can
# have only one default route even though routes are stackable, and there can
# only be one resolv.conf file):
#
# 1) allow both clients to do that stuff. This would work in many cases if
# only one of the interfaces is used at a time. However, it would lead to
# undefined behaviour.
#
# 2) allow only one of the DHCP clients to do that stuff. This implies
# that there would be a "primary" interface and a "secondary". This is the
# assumption the default configuration is based on. But since the system
# can't guess which interface is "more important" and should have the
# default route and resolver configuration associated with it, it simply
# chooses the first interface that is started with DHCP to be
# "authoritative". Which one that is can be influenced by adding
# DHCLIENT_PRIMARY_DEVICE=yes to one of the /etc/sysconfig/network/ifcfg-*
# files. This can even be added to more than one file, to achieve the
# behaviour described in 1). Thus, there is the flexibility to do it
# either way.
#
# Per default, only the DHCP client that is started first will be allowed to
# change the default route / resolver configuration etc. All other running
# clients will only configure the interface with an address, but not change
# "global" configuration.
#
# Thus, to specifically allow an interface's DHCP client to change "global"
# configuration, set the following variable to "yes":
DHCLIENT_PRIMARY_DEVICE=

# Even more finegrained control can be excerted by setting any of the variables
# from /etc/sysconfig/network/dhcp here:
DHCLIENT_DEBUG=
DHCLIENT_SET_HOSTNAME=
DHCLIENT_SET_DOMAINNAME=
DHCLIENT_KEEP_SEARCHLIST=
DHCLIENT_MODIFY_RESOLV_CONF=
DHCLIENT_SET_DEFAULT_ROUTE=
DHCLIENT_MODIFY_NTP_CONF=
DHCLIENT_MODIFY_NIS_CONF=
DHCLIENT_TIMEOUT=
DHCLIENT_REBOOT_TIMEOUT=
DHCLIENT_CLIENT_ID=
DHCLIENT_HOSTNAME_OPTION=
DHCLIENT_VENDOR_CLASS_ID=
DHCLIENT_LEASE_TIME=
DHCLIENT_ADDITIONAL_OPTIONS=

next file : wireless

## Path: Hardware/Wireless
## Description:
## Type: yesno
## Default: ""
## ServiceRestart: network
# If you have a wireless NIC and want to set some special wireless parameters
# then you can do that here in this file globally for all cards you have. But
# you can write each of these variables to the interface specific ifcfg-* files
# to handle things per card.
# The WIRELESS_* variable names match the option names of iwconfig. Have a look
# at 'man iwconfig' for details. Except WIRELESS_NICK the variables do nothing
# if empty.
#
# This variables decides if the special handling for wireless HW is used. If you
# have only one network interface card and it is wireless you can set it here to
# 'yes'. But it is much better, if you use that variable in the interface
# configuration files 'ifcfg-*', which overrides the general settings made here.
WIRELESS=""

## Type: string
## Default: ""
# Set the operating mode of the device, which depends on the network
# topology. The mode can be Ad-hoc (network composed of only one cell and
# without Access Point), Managed (network composed of many cells, with
# roaming or with an Access Point), Mas_ ter (the node is the synchronisation
# master or act as an Access Point), Repeater (the node forward packets on the
# air), Secondary (the node act as a backup master/repeater) or Auto
WIRELESS_MODE=""

## Type: string
## Default: ""
# Set the ESSID (or Network Name - in some products it may also called Domain
# ID). The ESSID is used to identify cells which are part of the same virtual
# network.
WIRELESS_ESSID="Wireless"

## Type: string
## Default: ""
# Set the nickname, or the station name. Most 802.11 products do define it,
# but this is not used as far as the protocols (MAC, IP, TCP) are concerned
# and completely accessory as far as configuration goes. If this variable is
# empty we use the hostname
WIRELESS_NICK=""

## Type: string
## Default: ""
# Set the Network ID (in some products it is also called Domain ID). As all
# adjacent wireless net_ works share the same medium, this parameter is used
# to differenciate them (create logical colocated networks) and identify
# nodes belonguing to the same cell.
WIRELESS_NWID=""

## Type: string
## Default: ""
# Set the operating frequency or channel in the device. Value below
# 1000 are the channel number, value over this is the frequency in Hz. You
# must append the suffix k, M or G to the value (for exam_ ple, "2.46G" for
# 2.46 GHz frequency), or add enough '0'.
WIRELESS_FREQ=""

## Type: string
## Default: ""
# Channels are usually numbered starting at 1, and you may use iwpriv(8) to
# get the total number of channels and list the available frequencies.
# Depending on regulations, some frequencies/channels may not be available.
WIRELESS_CHANNEL=""

## Type: string
## Default: ""
# Set the sensitivity threshold. This is the lowest signal level for which we
# attempt a packet recep_ tion, signal lower than this are not received. This
# is used to avoid receiving background noise
WIRELESS_SENS=""

## Type: string
## Default: ""
# For cards supporting multiple bit rates, set the bit-rate in b/s. The
# bit-rate is the speed at which bits are transmitted over the medium, the
# user speed of the link is lower due to medium sharing and overhead.
WIRELESS_RATE=""

## Type: string
## Default: ""
# Used to manipulate encryption or scrambling keys and encryption mode. To
# set the current encryption key, just enter the key in hex digits as
# XXXX-XXXX-XXXX-XXXX or XXXXXXXX. You can also enter the key as an ASCII
# string by using the s: prefix. 'off' disables encryption. Additionally you
# may add 'open' or 'restricted' after the key, open set the system in open
# mode (accept non-encrypted packets) and restricted discard non-encrypted
# packets.
# Examples: "0123-4567-89"
# "sassword"
# "sassword open"
# "off" (Don't do that! No! No! No!)
WIRELESS_KEY=""

## Type: string
## Default: ""
# RTS/CTS adds a handshake before each packet trans_ mission to make sure
# that the channel is clear. This adds overhead, but increase performance
# in case of hidden nodes or large number of active nodes.
WIRELESS_RTS=""

## Type: string
## Default: ""
# Fragmentation allow to split a IP packet in a burst of smaller fragments
# transmitted on the medium. In most cases this adds overhead, but in very
# noisy environment this reduce the error penalty.
WIRELESS_FRAG=""

## Type: string
## Default: ""
# If you need other options for iwconfig, then write the complete option string
# as you would append it to iwconfig but without the interface name to the
# variables below. For multiple options you may (but need not) add linebreaks in
# the string.
WIRELESS_IWCONFIG_OPTIONS=""

## Type: string
## Default: ""
# If you need to set options for iwspy, then write the complete option string as
# you would append it to iwspy but without the interface name to the variables
# below. For multiple options you may (but need not) add linebreaks in the
# string.
WIRELESS_IWSPY_OPTIONS=""

## Type: string
## Default: ""
# If you need to set options for iwpriv then write the complete option string as
# you would append it to iwpriv but without the interface name to the variables
# below. For multiple options you may (but need not) add linebreaks in the
# string.
WIRELESS_IWPRIV_OPTIONS=""

I really dont know what to do.
Is there any way to contact you? icq? msn?

Thanks a lot
 
Old 04-24-2004, 06:54 AM   #18
snodnipper
LQ Newbie
 
Registered: Aug 2003
Location: UK
Distribution: Mandrake
Posts: 11

Rep: Reputation: 0
Post off topic - Susu

suppaman, this is an issue regarding Susu, unfortunately I don't know enough about Susu to be able to help you further.
From looking on Google I've found these links:

http://www.linuxquestions.org/questi...5&pagenumber=1

http://www.justlinux.com/forum/showt...hreadid=125969

I wish you the best of luck, and if you don't succeed, install Mandrake 10 and come back here

p.s. according to my profile, I'm only a newbie!
 
Old 05-09-2004, 06:14 AM   #19
suppaman
LQ Newbie
 
Registered: Apr 2004
Location: Malaysia
Distribution: SuSE
Posts: 15

Rep: Reputation: 0
can i have ur msn/icq pls snodnipper
 
Old 05-09-2004, 06:16 AM   #20
suppaman
LQ Newbie
 
Registered: Apr 2004
Location: Malaysia
Distribution: SuSE
Posts: 15

Rep: Reputation: 0
i kinda wanna use mandrake this time
 
Old 08-28-2004, 09:57 PM   #21
zerogood
LQ Newbie
 
Registered: Aug 2004
Posts: 9

Rep: Reputation: 0
wheres the console

i have redhat 9 and i'm trying to follow the instructions but first of where is the console, and second of all where to put in commands like “su” -->
 
Old 10-11-2004, 11:28 AM   #22
jmorse
Member
 
Registered: Mar 2004
Location: United Kingdom
Distribution: LFS
Posts: 74

Rep: Reputation: 15
If you are using 'KDE' or 'Gnome' then the console is not immediatly obvious.

There should be an icon somewhere labeled 'shell', or 'console', which will open a window, where you can type all these commands.

If not... hold Alt and F2, under KDE and Gnome [I think], up comes a 'run program' dialog, the program to run [to get a console window] is 'xterm' [or 'aterm', or 'konsole', or 'eterm'].

my reason for being here:

I have a MA111 usb adaptor...
I have compiled the driver, it all works, modprobe... ifconfig denies the device exists. I have done prism2_doreset=1 when I modprobe, no effect, I have an entry in /etc/modules.conf to call it wlan0, no effect.

Hotplug denies there is a driver available, even though I have copied the modules.usbmap into the apporpriate place. Hotpluig does however put an entry to syslog with the correct vendor/product... so it isn't an usb problem.

Any suggestions!

James


I think the box is running Slackware.. at least it was once!

Last edited by jmorse; 10-11-2004 at 12:06 PM.
 
Old 10-18-2004, 03:26 AM   #23
karses
LQ Newbie
 
Registered: Oct 2004
Distribution: Mandrake 10
Posts: 3

Rep: Reputation: 0
I followed the whole process with no problem.

During the boot it tells me : "No dhcp client found" and then it doesn't work.

What info do you need for in order to help me?

Thanks
 
Old 02-16-2005, 05:10 PM   #24
bluepopcorn
LQ Newbie
 
Registered: Feb 2005
Posts: 1

Rep: Reputation: 0
Trouble with kernel-source

Sorry, I'm a complete newbie, but my first day wrestling with linux didn't get me very far because I could not get internet access. I tried to follow your guide, but it failed. I think my issue might be that when I ran "urpmq -r kernel-source" it returned "kernel-source-2.4.27-0.pre2.1mdk," when later the Configure file told me that this wasn't the actual version I was running - I guess my problem isn't wlan-ng, but I have no idea what it is, any suggestions?


Also, the wlan-ng Configure file did not automatically find the source code, but I told it where it was (for me with a brand new Mandrake 10.1 install after your instructions, /usr/src/linux-2.4.27-0.pre2.1mdk), but then it told me:

WARNING: the current running kernel is actually version 2.6.8.1-12mdk.
The current kernel build date is Fri Oct 1 12:53:41 2004.

Having no idea what to do about that, I ignored this and continued, and Configure ended with "Configuration Succesful."

When I ran make all, it spent a while spitting out incomprehensible-to-me lines, ending with several errors- but I assume the error was before this.
 
Old 02-16-2005, 06:07 PM   #25
opjose
Senior Member
 
Registered: Sep 2004
Location: Outlying D.C.
Distribution: Mandriva
Posts: 2,090

Rep: Reputation: 46
Point /etc/resolv.conf to your DNS server.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Netgear MA111 USB wireless adapter TWF MEPIS 1 10-18-2005 04:50 AM
Netgear MA111 USB Wireless Adapter subaruwrx Linux - Wireless Networking 2 01-20-2005 11:20 PM
Netgear MA111 Wireless USB Adapter woes kadaver Slackware 6 10-28-2004 02:39 AM
Netgear MA111 USB wireless adapter!HELP ME! jarrywhu Linux - Wireless Networking 13 09-28-2004 12:55 AM
FREAKISHLY URGENT: Netgear Wireless USB Adapter MA111 nealkochhar Linux - Wireless Networking 2 06-10-2004 05:50 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Mandriva

All times are GMT -5. The time now is 03:57 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration