Derek Atkins [EMAIL PROTECTED] writes:
Peter Jones [EMAIL PROTECTED] writes:
On Thu, 2005-07-14 at 13:00 -0400, Derek Atkins wrote:
Hi,
I've got two issues with 0.3.5 right now (well, STABLE_0_3 branch):
1) it's not noticing eth0. I've got kernel log messages that the
cable is
Derek Atkins [EMAIL PROTECTED] writes:
Running STABLE_0_3, where can I put scripts that get run when NM binds
to a _new_ IP address? I don't see anything obvious in /etc or
in the docs.
Searching through the code I found the answer: /etc/NetworkManager.d
HOWEVER, it appears that the FC3 RPM
Thanks. Unfortunately there is no /etc/init.d/NetworkManagerDispatcher
initscript in the 0.3.5 package, which was the basis of my question. I
suppose
I could create a new initscript based on the existing one...
Thanks for the additional information.. It sounds like the script location
Until a few days ago, I had never heard of a non-beaconing access point
(AP). A friend of mine has a NetGear MR814v2 and when you hide the
ESSID, you don't just blank the ESSID in the beacon packet, you stop
transmitting beacon packets. This is an area not covered by the 802.11
standard. In
On Fri, 2005-08-05 at 13:02 -0400, Colin Slater wrote:
When restarting nscd in nm_system_update_dns, the gentoo backend
checks `/etc/init.d/nscd status` to determine if nscd is running. If
the script returns non-zero, networkmanager restarts nscd properly.
However, gentoo init
scripts return
Hi i have managed to install Network Manager on a debian system, I had
to modify some of the directories that dhcdbd looks in, everything
seems to be working ok during the 25 first seconds, the wired
interface is brought up using the dhcp information, the dns daemon
updated, i can ping google.com.
On Mon, 2005-08-08 at 10:05 -0400, Bill Moss wrote:
When you started early versions of NM in a area with no wireless
beacons, the detecting icon would spin forever. If you clicked on
'Connect to Other Wireless Network ...', entered ESSID and WEP key, you
could make a connection to a
On Mon, 2005-08-08 at 17:14 +0200, Diego González wrote:
Hi i have managed to install Network Manager on a debian system, I had
to modify some of the directories that dhcdbd looks in, everything
seems to be working ok during the 25 first seconds, the wired
interface is brought up using the
On Fri, 2005-08-05 at 11:40 -0400, Robert Love wrote:
We have a few problems:
- Weird extraneous space on the left
- Bevel below the icon on some themes
- Area is framed on some themes
Fair enough.
In any case, the original idea here was that since NM _is_ a menu, it
I have a Linksys router with the painfully annoying
key index setup. I have written a patch for
NetworkManager to be able to interface with the WEP
key indexes on the router. I used the Linksys GPL
code to figure out their system. Anyway, I used glade
to edit the nm-applet and add four radio
Eric wrote:
I have a Linksys router with the painfully annoying
key index setup. I have written a patch for
NetworkManager to be able to interface with the WEP
key indexes on the router. I used the Linksys GPL
code to figure out their system. Anyway, I used glade
to edit the nm-applet and add
On Mon, 2005-08-08 at 09:45 -0700, Eric Wenger wrote:
Don't get me wrong...the key indexes are silly and
insecure (they simply obfuscate the passphrase which
doesn't make WEP any more secure). The problem is
that NM cannot connect to a Linksys router unless you
are using the first key index.
Is there a yum repo with development snapshots of NetworkManager? I see
updates getting posted to the FC5 development branch but I don't want to
send my laptop to development land just to test and play with the newer
versions of NetworkManager.
Thanks
Joe
Here's the actual code...it looks like there was
originally a cut and paste error in the mix as well
since there are two parts: first some extra characters
at the end of the passphrase and additionally the
first bytes of the WEP key are skipped in the
additional keys.
if (weptype == 128)
{
14 matches
Mail list logo
