2:58 p.m.
Fc12, X86_64
While in Single User mode, how do I start wlan0 to connect to a WEP
192.168.1.1 Router .
Eth0 is not available in this application.
11:28 a.m.
On 08/14/2010 07:02 AM, Tim wrote:
On Fri, 2010-08-13 at 14:42 -0700, JD wrote:
> service wpa_supplicant start
> wait a few minutes for the wpa supplicant to sync up with router
> then
I have to ask: Why would that take minutes, rather than mere seconds?
It's a good question.
Where I am, it takes sometimes up to 30 minutes to connect
because the signal is not that great.
8 p.m.
On 08/13/2010 08:50 PM, JD wrote:
On 08/13/2010 05:00 PM, binarynut(a)comcast.net wrote:
> On 08/13/2010 06:43 PM, Mikkel wrote:
>> On 08/13/2010 05:40 PM, Martin Airs wrote:
>>> sorry, one assumes that the OP is actually capable of going into a
>>> desktop just to tick the box, just to make the wireless network
>>> available in runlevel 3.
>>>
>> But the OP wants it in runlevel 1.
>>
> ifconfig wlan0 is showing the wlan0,but dhclient wlan0 is not giving me
> a IP .
>
> iwconfig wlan0 essid dd-wrt key 8956231064 works , but it didn't like
> 's' so I let it out . The key is a Hex key.
>
> iwlist wlan0 key, shows a key
I have had continuous problems with dhcp over wireless.
In short: it NEVER worked.
So, I assign a static IP and it works just fine.
ifconfig wlan0 inet 192.168.1.X gateway 192.168.1.254 netmask 0xffffff00 up
I think the problem is dhclient took so long to get a connection.
I was just sitting and watching the Router and after about ten minutes I
saw the IP pop up on router for my Wireless Connection.
And it is staying connected after one hour in Single User Mode.
7:56 p.m.
On 08/13/2010 07:50 PM, JD wrote:
I have had continuous problems with dhcp over wireless.
In short: it NEVER worked.
So, I assign a static IP and it works just fine.
ifconfig wlan0 inet 192.168.1.X gateway 192.168.1.254 netmask 0xffffff00 up
One thing I have run into with WEP is that depending on the settings
of the access point, you may have to add the restricted option to
the key. This set the security mode.
Mikkel
--
Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!
7:17 p.m.
On 08/13/2010 08:13 PM, binarynut(a)comcast.net wrote:
On 08/13/2010 08:00 PM, binarynut(a)comcast.net wrote:
> On 08/13/2010 06:43 PM, Mikkel wrote:
>> On 08/13/2010 05:40 PM, Martin Airs wrote:
>>> sorry, one assumes that the OP is actually capable of going into a
>>> desktop just to tick the box, just to make the wireless network
>>> available in runlevel 3.
>>>
>> But the OP wants it in runlevel 1.
>>
> ifconfig wlan0 is showing the wlan0,but dhclient wlan0 is not giving me
> a IP .
>
> iwconfig wlan0 essid dd-wrt key 8956231064 works , but it didn't like
> 's' so I let it out . The key is a Hex key.
>
> iwlist wlan0 key, shows a key
Now it is Connected, but it sure took a long to connect.
I was watching the DHCP connection in Router and after about 10
minutes it connected.
The ;
The;
ifconfig wlan0 up
iwconfig wlan0 dd-wrt key 9856231080 (hex Key)
dhclient wlan0
Did the job
7:13 p.m.
On 08/13/2010 08:00 PM, binarynut(a)comcast.net wrote:
On 08/13/2010 06:43 PM, Mikkel wrote:
> On 08/13/2010 05:40 PM, Martin Airs wrote:
>> sorry, one assumes that the OP is actually capable of going into a
>> desktop just to tick the box, just to make the wireless network
>> available in runlevel 3.
>>
> But the OP wants it in runlevel 1.
>
ifconfig wlan0 is showing the wlan0,but dhclient wlan0 is not giving me
a IP .
iwconfig wlan0 essid dd-wrt key 8956231064 works , but it didn't like
's' so I let it out . The key is a Hex key.
iwlist wlan0 key, shows a key
Now it is Connected, but it sure took a long to
connect.
I was watching the DHCP connection in Router and after about 10 minutes
it connected.
The ;
7 p.m.
On 08/13/2010 06:43 PM, Mikkel wrote:
On 08/13/2010 05:40 PM, Martin Airs wrote:
> sorry, one assumes that the OP is actually capable of going into a
> desktop just to tick the box, just to make the wireless network
> available in runlevel 3.
>
But the OP wants it in runlevel 1.
ifconfig wlan0 is showing the wlan0,but dhclient wlan0 is not giving me
a IP .
iwconfig wlan0 essid dd-wrt key 8956231064 works , but it didn't like
's' so I let it out . The key is a Hex key.
iwlist wlan0 key, shows a key
6:39 p.m.
On 08/13/2010 03:41 PM, Tom H wrote:
On Fri, Aug 13, 2010 at 6:38 PM, JD<jd1008(a)gmail.com> wrote:
> On 08/13/2010 03:24 PM, Tom H wrote:
>> On Fri, Aug 13, 2010 at 6:12 PM, Patrick O'Callaghan
>> <pocallaghan(a)gmail.com> wrote:
>>> On Fri, 2010-08-13 at 14:42 -0700, JD wrote:
>>>> On 08/13/2010 12:58 PM, binarynut(a)comcast.net wrote:
>>>>> Fc12, X86_64
>>>>>
>>>>> While in Single User mode, how do I start wlan0 to connect to a WEP
>>>>> 192.168.1.1 Router .
>>>>>
>>>>> Eth0 is not available in this application.
>>>> service wpa_supplicant start
>>>> wait a few minutes for the wpa supplicant to sync up with router
>>>> then
>>>> service network start
>>> Wonderful. Now one responder told him to use NetworkManager and you've
>>> just told him to use something incompatible with NM. Unless there's
>>> clear evidence that NM is causing him problems, this is only going to
>>> lead to headaches down the road.
>> I missed the "use NM" email. Does NM work in single-user mode?!
>>
>> wpa_supplicant isn't needed to wep anyway.
> Back that up with a how to then!!
> Usually it is wpa_supplicant which will drive the usual wext driver
> to communicate with the underlying wifi chipset driver.
> Unless the OP has specified a different driver in
> /etc/sysconfig/wpa_supplicant.
wpa_supplicant is for wpa - as its name imples
Again - not so in this neck of the
woods.
6:23 p.m.
On Fri, Aug 13, 2010 at 6:51 PM, JD <jd1008(a)gmail.com> wrote:
On 08/13/2010 03:30 PM, Tom H wrote:
> ifconfig wlan0 up
> iwconfig wlan0 essid<essid> key s:<asciikey>
> dhclient wlan0
Are you so sure??
sudo ifconfig ra0 up
sudo iwconfig ra0 essid MYEssID key
s:"SomeLongText..............................."
sudo dhclient ra0
Error for wireless request "Set Encode" (8B2A) :
SET failed on device ra0 ; Invalid argument.
I've use this in the past with wep access points.
5:51 p.m.
On 08/13/2010 03:30 PM, Tom H wrote:
ifconfig wlan0 up
iwconfig wlan0 essid<essid> key s:<asciikey>
dhclient wlan0
Are you so sure??
sudo ifconfig ra0 up
sudo iwconfig ra0 essid MYEssID key
s:"SomeLongText......................................................................"
sudo dhclient ra0
Error for wireless request "Set Encode" (8B2A) :
SET failed on device ra0 ; Invalid argument.
5:47 p.m.
oops ok, sorry
peace out
Martin Airs
http://www.airs.me.uk
On 08/13/2010 11:43 PM, Mikkel wrote:
On 08/13/2010 05:40 PM, Martin Airs wrote:
> sorry, one assumes that the OP is actually capable of going into a
> desktop just to tick the box, just to make the wireless network
> available in runlevel 3.
>
But the OP wants it in runlevel 1.
5:43 p.m.
On 08/13/2010 05:40 PM, Martin Airs wrote:
sorry, one assumes that the OP is actually capable of going into a
desktop just to tick the box, just to make the wireless network
available in runlevel 3.
But the OP wants it in runlevel 1.
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting a bad thing?
5:41 p.m.
On Fri, Aug 13, 2010 at 6:38 PM, JD <jd1008(a)gmail.com> wrote:
On 08/13/2010 03:24 PM, Tom H wrote:
> On Fri, Aug 13, 2010 at 6:12 PM, Patrick O'Callaghan
> <pocallaghan(a)gmail.com> wrote:
>> On Fri, 2010-08-13 at 14:42 -0700, JD wrote:
>>> On 08/13/2010 12:58 PM, binarynut(a)comcast.net wrote:
>>>> Fc12, X86_64
>>>>
>>>> While in Single User mode, how do I start wlan0 to connect to a WEP
>>>> 192.168.1.1 Router .
>>>>
>>>> Eth0 is not available in this application.
>>> service wpa_supplicant start
>>> wait a few minutes for the wpa supplicant to sync up with router
>>> then
>>> service network start
>> Wonderful. Now one responder told him to use NetworkManager and you've
>> just told him to use something incompatible with NM. Unless there's
>> clear evidence that NM is causing him problems, this is only going to
>> lead to headaches down the road.
> I missed the "use NM" email. Does NM work in single-user mode?!
>
> wpa_supplicant isn't needed to wep anyway.
Back that up with a how to then!!
Usually it is wpa_supplicant which will drive the usual wext driver
to communicate with the underlying wifi chipset driver.
Unless the OP has specified a different driver in
/etc/sysconfig/wpa_supplicant.
wpa_supplicant is for wpa - as its name imples
5:40 p.m.
sorry, one assumes that the OP is actually capable of going into a
desktop just to tick the box, just to make the wireless network
available in runlevel 3.
Martin Airs
http://www.airs.me.uk
On 08/13/2010 10:45 PM, JD wrote:
On 08/13/2010 01:56 PM, Martin Airs wrote:
> Hi there,
>
> Go into your desktop of choice, and right click on the network manager
> icon, then edit connections and edit the wireless connection you want
> available in runlevel 3
>
> then tick the box to "make available to all users"
>
> then when you go into runlevel 3 that connection will still be connected
> in runlevel 3
>
>
> Martin Airs
> http://www.airs.me.uk
Hi Martin,
the OP said single user mode,
so there is no desktop.
I have already responded to him
with exactly I do when in single user mode
and need wireless internet in that mode.
> On 08/13/2010 08:58 PM, binarynut(a)comcast.net wrote:
>> Fc12, X86_64
>>
>> While in Single User mode, how do I start wlan0 to connect to a WEP
>> 192.168.1.1 Router .
>>
>> Eth0 is not available in this application.
5:38 p.m.
On 08/13/2010 03:24 PM, Tom H wrote:
On Fri, Aug 13, 2010 at 6:12 PM, Patrick O'Callaghan
<pocallaghan(a)gmail.com> wrote:
> On Fri, 2010-08-13 at 14:42 -0700, JD wrote:
>> On 08/13/2010 12:58 PM, binarynut(a)comcast.net wrote:
>>> Fc12, X86_64
>>>
>>> While in Single User mode, how do I start wlan0 to connect to a WEP
>>> 192.168.1.1 Router .
>>>
>>> Eth0 is not available in this application.
>> service wpa_supplicant start
>> wait a few minutes for the wpa supplicant to sync up with router
>> then
>> service network start
> Wonderful. Now one responder told him to use NetworkManager and you've
> just told him to use something incompatible with NM. Unless there's
> clear evidence that NM is causing him problems, this is only going to
> lead to headaches down the road.
I missed the "use NM" email. Does NM work in single-user mode?!
wpa_supplicant isn't needed to wep anyway.
Back that up with a how to then!!
Usually it is wpa_supplicant which will drive the usual wext driver
to communicate with the underlying wifi chipset driver.
Unless the OP has specified a different driver in
/etc/sysconfig/wpa_supplicant.
5:26 p.m.
On 08/13/2010 03:12 PM, Patrick O'Callaghan wrote:
On Fri, 2010-08-13 at 14:42 -0700, JD wrote:
> On 08/13/2010 12:58 PM, binarynut(a)comcast.net wrote:
>> Fc12, X86_64
>>
>> While in Single User mode, how do I start wlan0 to connect to a WEP
>> 192.168.1.1 Router .
>>
>> Eth0 is not available in this application.
> service wpa_supplicant start
> wait a few minutes for the wpa supplicant to sync up with router
> then
> service network start
>
> That's it.
Wonderful. Now one responder told him to use NetworkManager and you've
just told him to use something incompatible with NM. Unless there's
clear evidence that NM is causing him problems, this is only going to
lead to headaches down the road.
poc
No it is not.
As the OP states - he is in single user mode!!!!!!
5:12 p.m.
On Fri, 2010-08-13 at 14:42 -0700, JD wrote:
On 08/13/2010 12:58 PM, binarynut(a)comcast.net wrote:
> Fc12, X86_64
>
> While in Single User mode, how do I start wlan0 to connect to a WEP
> 192.168.1.1 Router .
>
> Eth0 is not available in this application.
service wpa_supplicant start
wait a few minutes for the wpa supplicant to sync up with router
then
service network start
That's it.
Wonderful. Now one responder told him to use NetworkManager and you've
just told him to use something incompatible with NM. Unless there's
clear evidence that NM is causing him problems, this is only going to
lead to headaches down the road.
poc
4:42 p.m.
On 08/13/2010 12:58 PM, binarynut(a)comcast.net wrote:
Fc12, X86_64
While in Single User mode, how do I start wlan0 to connect to a WEP
192.168.1.1 Router .
Eth0 is not available in this application.
service wpa_supplicant start
wait a few minutes for the wpa supplicant to sync up with router
then
service network start
That's it.
3:23 p.m.
On Fri, 2010-08-13 at 15:58 -0400, binarynut(a)comcast.net wrote:
Fc12, X86_64
While in Single User mode, how do I start wlan0 to connect to a WEP
192.168.1.1 Router .
Eth0 is not available in this application.
----
are you averse to the official documentation?
http://docs.fedoraproject.org/en-US/Fedora/12/html/User_Guide/index.html
Perhaps you should start there, especially the section on connecting to
the Internet/NetworkManager/Wireless
Craig
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
9:02 a.m.
On Fri, 2010-08-13 at 14:42 -0700, JD wrote:
service wpa_supplicant start
wait a few minutes for the wpa supplicant to sync up with router
then
I have to ask: Why would that take minutes, rather than mere seconds?
--
[tim@localhost ~]$ uname -r
2.6.27.25-78.2.56.fc9.i686
Don't send private replies to my address, the mailbox is ignored. I
read messages from the public lists.
5:30 p.m.
On Fri, Aug 13, 2010 at 6:24 PM, Tom H <tomh0665(a)gmail.com> wrote:
On Fri, Aug 13, 2010 at 6:12 PM, Patrick O'Callaghan
<pocallaghan(a)gmail.com> wrote:
> On Fri, 2010-08-13 at 14:42 -0700, JD wrote:
>> On 08/13/2010 12:58 PM, binarynut(a)comcast.net wrote:
>> > Fc12, X86_64
>> >
>> > While in Single User mode, how do I start wlan0 to connect to a WEP
>> > 192.168.1.1 Router .
>> >
>> > Eth0 is not available in this application.
>> service wpa_supplicant start
>> wait a few minutes for the wpa supplicant to sync up with router
>> then
>> service network start
>
> Wonderful. Now one responder told him to use NetworkManager and you've
> just told him to use something incompatible with NM. Unless there's
> clear evidence that NM is causing him problems, this is only going to
> lead to headaches down the road.
I missed the "use NM" email. Does NM work in single-user mode?!
wpa_supplicant isn't needed to wep anyway.
Forgot:
ifconfig wlan0 up
iwconfig wlan0 essid <essid> key s:<asciikey>
dhclient wlan0
7:50 p.m.
On 08/13/2010 05:00 PM, binarynut(a)comcast.net wrote:
On 08/13/2010 06:43 PM, Mikkel wrote:
> On 08/13/2010 05:40 PM, Martin Airs wrote:
>> sorry, one assumes that the OP is actually capable of going into a
>> desktop just to tick the box, just to make the wireless network
>> available in runlevel 3.
>>
> But the OP wants it in runlevel 1.
>
ifconfig wlan0 is showing the wlan0,but dhclient wlan0 is not giving me
a IP .
iwconfig wlan0 essid dd-wrt key 8956231064 works , but it didn't like
's' so I let it out . The key is a Hex key.
iwlist wlan0 key, shows a key
I have had continuous problems with dhcp over
wireless.
In short: it NEVER worked.
So, I assign a static IP and it works just fine.
ifconfig wlan0 inet 192.168.1.X gateway 192.168.1.254 netmask 0xffffff00 up
5:24 p.m.
On Fri, Aug 13, 2010 at 6:12 PM, Patrick O'Callaghan
<pocallaghan(a)gmail.com> wrote:
On Fri, 2010-08-13 at 14:42 -0700, JD wrote:
> On 08/13/2010 12:58 PM, binarynut(a)comcast.net wrote:
> > Fc12, X86_64
> >
> > While in Single User mode, how do I start wlan0 to connect to a WEP
> > 192.168.1.1 Router .
> >
> > Eth0 is not available in this application.
> service wpa_supplicant start
> wait a few minutes for the wpa supplicant to sync up with router
> then
> service network start
Wonderful. Now one responder told him to use NetworkManager and you've
just told him to use something incompatible with NM. Unless there's
clear evidence that NM is causing him problems, this is only going to
lead to headaches down the road.
I missed the "use NM" email. Does NM work in single-user mode?!
wpa_supplicant isn't needed to wep anyway.
4:45 p.m.
On 08/13/2010 01:56 PM, Martin Airs wrote:
Hi there,
Go into your desktop of choice, and right click on the network manager
icon, then edit connections and edit the wireless connection you want
available in runlevel 3
then tick the box to "make available to all users"
then when you go into runlevel 3 that connection will still be connected
in runlevel 3
Martin Airs
http://www.airs.me.uk
Hi Martin,
the OP said single user mode,
so there is no desktop.
I have already responded to him
with exactly I do when in single user mode
and need wireless internet in that mode.
On 08/13/2010 08:58 PM, binarynut(a)comcast.net wrote:
> Fc12, X86_64
>
> While in Single User mode, how do I start wlan0 to connect to a WEP
> 192.168.1.1 Router .
>
> Eth0 is not available in this application.
3:56 p.m.
Hi there,
Go into your desktop of choice, and right click on the network manager
icon, then edit connections and edit the wireless connection you want
available in runlevel 3
then tick the box to "make available to all users"
then when you go into runlevel 3 that connection will still be connected
in runlevel 3
Martin Airs
http://www.airs.me.uk
On 08/13/2010 08:58 PM, binarynut(a)comcast.net wrote:
Fc12, X86_64
While in Single User mode, how do I start wlan0 to connect to a WEP
192.168.1.1 Router .
Eth0 is not available in this application.
5014
days inactive
5015
days old
24 comments
8 participants
participants (8)
-
Craig White -
JD -
Martin Airs -
Mickey -
Mikkel -
Patrick O'Callaghan -
Tim -
Tom H