Re: WEP (and other) problems in current SVN

2007-12-29 Thread Seán de Búrca
Scríobh Dan Williams: > Any chance you could try with latest wpa_supplicant git of either the > trunk or hostap_0_5_branch branches? Jouni just cherry-picked a commit > from trunk that works around a race condition with madwifi Same results with wpa_supplicant trunk. For what it's worth, I'm attac

Re: NM 0.7 on Fedora 8 with 3G USB Modems

2007-12-29 Thread Peter Robinson
> > Been reading through the list for details of the 3G modem support in > > Fedora8/NM. It seems like its almost there, and from my playing it > > seems like I've got it almost working :) > > > > Its one of the seemingly infamous Huawei E220's and a bit of a search > > I got it ready to go, and ad

Re: Autostarting NetworkManager in Fedora 8 prevents sshd to start properly

2007-12-29 Thread Jim
I have the same sort of problem with Network Manager starting well after NFS... go figure. I imagine it has some other dependencies before it can start is the problem. The startup order does need to be looked into at some point however. Jim > >>> Sounds like sshd is binding to an IP addres

Re: Autostarting NetworkManager in Fedora 8 prevents sshd to start properly

2007-12-29 Thread Rui Tiago Matos
On 29/12/2007, Robert Allerstorfer <[EMAIL PROTECTED]> wrote: > On Sat, 29 Dec 2007, 15:59 GMT+01 Robert Allerstorfer wrote: > > > On Sat, 29 Dec 2007, 09:41 GMT-05 Dan Williams wrote: > > >> Sounds like sshd is binding to an IP address and not handling changes > >> when your IP address changes. Y

Re: Autostarting NetworkManager in Fedora 8 prevents sshd to start properly

2007-12-29 Thread Robert Allerstorfer
On Sat, 29 Dec 2007, 15:59 GMT+01 Robert Allerstorfer wrote: > On Sat, 29 Dec 2007, 09:41 GMT-05 Dan Williams wrote: >> Sounds like sshd is binding to an IP address and not handling changes >> when your IP address changes. You should probably set up a >> NetworkManagerDispatcher script to kick s

Re: Autostarting NetworkManager in Fedora 8 prevents sshd to start properly

2007-12-29 Thread Robert Allerstorfer
On Sat, 29 Dec 2007, 09:41 GMT-05 Dan Williams wrote: > On Sat, 2007-12-29 at 15:37 +0100, Robert Allerstorfer wrote: >> When the NetworkManager service is set to autostart on boot in Fedora >> 8 (using 'chkconfig NetworkManager on'), it is no more possible to >> remotely connect via ssh on boot u

Re: WEP (and other) problems in current SVN

2007-12-29 Thread Dan Williams
On Fri, 2007-12-28 at 10:45 -0500, Dan Williams wrote: > On Tue, 2007-12-25 at 20:29 -0700, Seán de Búrca wrote: > > I'm currently attempting to connect to a network configured with > > 128-bit WEP with current SVN. When prompted for the key, I make sure to > > select the 128-bit Hexadecimal option

Re: WEP (and other) problems in current SVN

2007-12-29 Thread Dan Williams
On Fri, 2007-12-28 at 13:17 -0700, Seán de Búrca wrote: > Scríobh Dan Williams: > > That means that the wireless driver failed to send the 'connect' signal > > in time. What version of wpa_supplicant are you using, and would it be > > possible to add the '-ddd' option to the supplicant's command l

Re: Autostarting NetworkManager in Fedora 8 prevents sshd to start properly

2007-12-29 Thread Dan Williams
On Sat, 2007-12-29 at 15:37 +0100, Robert Allerstorfer wrote: > When the NetworkManager service is set to autostart on boot in Fedora > 8 (using 'chkconfig NetworkManager on'), it is no more possible to > remotely connect via ssh on boot unless a login took place directly on > the machine. This pro

Autostarting NetworkManager in Fedora 8 prevents sshd to start properly

2007-12-29 Thread Robert Allerstorfer
When the NetworkManager service is set to autostart on boot in Fedora 8 (using 'chkconfig NetworkManager on'), it is no more possible to remotely connect via ssh on boot unless a login took place directly on the machine. This problem was not present in Fedora 7. Any clues how to solve this problem?