NetworkManager on Fedora 7

2007-06-09 Thread John Lagrue
It seems that there's a problem with NM on F7 when using WPA.

My wireless network uses WPA2-Personal, with AES encryption. However
when I try to connect to it on F7 using NM I don't get those options
to choose from; it only offers WPA Personal and type of Automatic or
AES-CCMP (whatever that might be)

Is the problem with my driver? Or with NM? Or with Fedora? Any
pointers of where to start looking would be greatly appreciated.

Currently I'm without wireless until I can find a solution.

JDL
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Wired network unavailable

2007-06-09 Thread Dan Williams
On Sat, 2007-06-09 at 18:21 -0400, Darren Albers wrote:
> 
> 
> On 6/9/07, Jeroen van de Nieuwenhof <[EMAIL PROTECTED]> wrote:
> Hi,
> 
> I use NetworkManager (on Ubuntu Feisty) to connect to wireless
> networks
> and everything runs pretty fine.
> 
> However, when i plug in a ethernet cable in my laptop, the
> wired network
> is always unavailable in NetworkManager. If i restart my
> system the 
> wired connection is available though. What can i do to solve
> this?
> 
> This is my /etc/network/interfaces:
> 
> auto lo
> iface lo inet loopback
> 
> auto eth0 #wired interface
> auto eth1 #wireless interface 
> 
> Regards,
> 
> Jeroen
> 
> 
> What type of NIC is it?  I think a few NIC cards don't properly
> support link detection, though I think this is really rare now.

A few NE2000 compatible ones don't AFAIK, and a lot of PCMCIA pcnet32
ones don't either.  But those are usually older cards.

Dan

> 
> 
> 
> ___
> NetworkManager-list mailing list
> NetworkManager-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: nm-openswan is alive again!

2007-06-09 Thread Dan Williams
On Sat, 2007-06-09 at 18:03 -0400, steve wrote:
> Hi,
> 
> Just a quick post to inform anyone who cares, that I've finished my 
> employment transition, re-created my development environment and I've 
> re-started work on the openswan vpn plugin.
> 
> I've made two design changes to allow for multiple concurrent vpn 
> connections (in future releases) as it will be required for my new job.
> I'll post again when I've got a tar ball for others to test.

Awesome!  You might want to look at an email recently sent about a new
API for VPNs to see if it would also work for openswan.

"Proposal for a new VPN DBUS interface" - May 8th

Dan

> If anyone feels inclined to help with the effort (which is mainly bug 
> fixing at this point), feel free to contact me.
> 
> Steve.
> ___
> NetworkManager-list mailing list
> NetworkManager-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Wired network unavailable

2007-06-09 Thread Darren Albers

On 6/9/07, Jeroen van de Nieuwenhof <[EMAIL PROTECTED]> wrote:


Hi,

I use NetworkManager (on Ubuntu Feisty) to connect to wireless networks
and everything runs pretty fine.

However, when i plug in a ethernet cable in my laptop, the wired network
is always unavailable in NetworkManager. If i restart my system the
wired connection is available though. What can i do to solve this?

This is my /etc/network/interfaces:

auto lo
iface lo inet loopback

auto eth0 #wired interface
auto eth1 #wireless interface

Regards,

Jeroen




What type of NIC is it?  I think a few NIC cards don't properly support link
detection, though I think this is really rare now.
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


nm-openswan is alive again!

2007-06-09 Thread steve
Hi,

Just a quick post to inform anyone who cares, that I've finished my 
employment transition, re-created my development environment and I've 
re-started work on the openswan vpn plugin.

I've made two design changes to allow for multiple concurrent vpn 
connections (in future releases) as it will be required for my new job.
I'll post again when I've got a tar ball for others to test.

If anyone feels inclined to help with the effort (which is mainly bug 
fixing at this point), feel free to contact me.

Steve.
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Wired network unavailable

2007-06-09 Thread Yaakov Nemoy
Hi Jeroen

On 6/9/07, Jeroen van de Nieuwenhof <[EMAIL PROTECTED]> wrote:
> However, when i plug in a ethernet cable in my laptop, the wired network
> is always unavailable in NetworkManager. If i restart my system the
> wired connection is available though. What can i do to solve this?
>
> This is my /etc/network/interfaces:
>
> auto lo
> iface lo inet loopback
>
> auto eth0 #wired interface
> auto eth1 #wireless interface

Try commenting out those last two lines for eth0 and eth1, and then
reboot your computer.  That may not solve your problem, but it's the
first place I would look.

Network Manager acts funny when the distro tries to do it's own
specific configuration to any of the network interfaces, and it works
the best when it's left alone.

Cheers,
Yaakov
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: NM 0.6.5 unable to reconnect to WPA2 network (first connection fine) - take 2

2007-06-09 Thread Tomáš Hnyk
On Thu, 07 Jun 2007 17:08:41 +0200, Jon Escombe <[EMAIL PROTECTED]> wrote:

>
> - "Dan Williams" <[EMAIL PROTECTED]> wrote:
>
>> > Attaching a new version of my patch, this checks whether a private
>> key file is configured for the connection before attempting to read a
>> password from the keyring. I believe this should suit both of the
>> above 802.1X configuration types..
>>
>> Wouldn't this not change the behavior for Tomas?  Since his config
>> doesn't show a private key file, it seems like your patch won't change
>> behvior for him.
>>
>> I guess we should get him to test the patch first and see :)
>>
>> In any case, I've committed your fix since it's obviously correct.  I
>> added a bit to make sure we free the private_key_file variable since
>> that's actually allocated memory.
>>
>> Dan
>>
>
> Thanks,
>
> I believe Tomas is using 6.4, which doesn't work (for him) because it  
> always tries to get a password from the keyring. 6.5 includes a patch to  
> never get a password from the keyring (which I'm assuming would work for  
> Tomas - but breaks the private key password scenario). This *should* now  
> be the best of both worlds  ;)
>
> Regards,
> Jon.
> ___
> NetworkManager-list mailing list
> NetworkManager-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list
I am afraid I will not be able to confirm this (although I think ou are  
right)  since it does not compile with my version of NM (0.6.4):
applet-dbus-info.c: In function ‘nmi_dbus_get_key_for_network’:
applet-dbus-info.c:193: error: ‘NM_AUTH_TYPE_LEAP’ undeclared (first use  
in this function)
applet-dbus-info.c:193: error: (Each undeclared identifier is reported  
only once
applet-dbus-info.c:193: error: for each function it appears in.)
I tried to install the current svn, but it did not work for some reason  
(no idea what reason).
I found the patch  
(http://mail.gnome.org/archives/networkmanager-list/2006-July/msg00034.html)  
that introduces LEAP into NM, but it does not work with my source anyway  
since it is far too huge.
I hope it work anyway.
Sorry and regards,
Tomas


___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Question regarding Madwifi signal strength

2007-06-09 Thread Simon Geard
On Fri, 2007-06-08 at 14:53 -0400, Darren Albers wrote:
> If you use those packages make sure you remove network-manager and
> network-manager-gnome first.
> 
> Let me know if the patches bring things closer to normal for you.
> 

Hmm. I've just rebuilt NM 0.6.5 with the Ubuntu patch. It *has*
increased the signal strength reported by NM, but I don't think it's
done so correctly - it's now reporting 100% strength for every access
point listed (compared to the 65% reported by gnome's network monitor
applet).

Despite that, I'll leave the patch in place. I've had quite a few
problems maintaining a connection to my access point lately, and this
can hardly make things any worse.

Simon.


signature.asc
Description: This is a digitally signed message part
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Question regarding Madwifi signal strength

2007-06-09 Thread Simon Geard
On Fri, 2007-06-08 at 10:21 -0400, Dan Williams wrote:
> On Sat, 2007-06-09 at 00:11 +1200, Simon Geard wrote:
> > 00:17:9A:12:31:72 : Quality=49/70  Signal level=-46 dBm  Noise
> level=-95 dBm
> 
>    This looks wrong
> 
> Quality is supposed to be a linear value between 0 and max_qual.qual
> inclusive.  49/70 = 70%; and with a signal of -46dBm and a noise of -95
> dBm, that seems bogus.  It should be higher than that.  -46 dBm is
> _really good_.
> 
> > 00:14:7C:AD:39:92 : Quality=120/70  Signal level=-256 dBm  Noise 
> > level=-95 dBm
> 
>    This is wrong
> 
> A value of 120 is clearly outside the bounds of 0, 70.

I've actually seen *positive* dBm values reported by the drivers before,
so yeah, not very good.

Simon.


signature.asc
Description: This is a digitally signed message part
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Wired network unavailable

2007-06-09 Thread Jeroen van de Nieuwenhof
Hi,

I use NetworkManager (on Ubuntu Feisty) to connect to wireless networks
and everything runs pretty fine.

However, when i plug in a ethernet cable in my laptop, the wired network
is always unavailable in NetworkManager. If i restart my system the
wired connection is available though. What can i do to solve this?

This is my /etc/network/interfaces:

auto lo
iface lo inet loopback

auto eth0 #wired interface
auto eth1 #wireless interface

Regards,

Jeroen

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list