Re: Help on wireless network connectivity
Thanks a lot , I could able to connect internet now. Regards, ravi Larry Finger <[EMAIL PROTECTED]> wrote: Ravi wrote: > Hi, > > I have installed fedora 9 on my laptop recently and I wanted to enable > WiFi using Network manager. > Lan interface : Broadcom 802.11a/b/g WLAN > > Please help me how can I get this done. Please tell us more. From a terminal, issue the command '/sbin/lspci -nnv', find the first two lines of the output that describe your wireless, and post them. Note: I'm not certain that lspci is in /sbin. If you get a "command not found", become root and issue the command 'lspci -nnv'. Second, issue the command 'dmesg | grep b43' and post the results. Larry ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Help on wireless network connectivity
Hi Larry, Output of lspci looks as below: 00:00.0 RAM memory [0500]: nVidia Corporation MCP67 Memory Controller [10de:0547] (rev a2) Subsystem: Hewlett-Packard Company Unknown device [103c:30cf] Flags: bus master, 66MHz, fast devsel, latency 0 Capabilities: And the output of dmesg as below: firmware (version 4). b43-phy0: Broadcom 4311 WLAN found b43-phy0 debug: Found PHY: Analog 4, Type 2, Revision 9 b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2 input: b43-phy0 as /devices/virtual/input/input10 b43-phy0 ERROR: Firmware file "b43/ucode13.fw" not found or load failed. b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and download the latest May be i am not having right devicefirmware to support.I am trying to download firmware. thanks a lot regards, Ravi Larry Finger <[EMAIL PROTECTED]> wrote: Ravi wrote: > Hi, > > I have installed fedora 9 on my laptop recently and I wanted to enable > WiFi using Network manager. > Lan interface : Broadcom 802.11a/b/g WLAN > > Please help me how can I get this done. Please tell us more. From a terminal, issue the command '/sbin/lspci -nnv', find the first two lines of the output that describe your wireless, and post them. Note: I'm not certain that lspci is in /sbin. If you get a "command not found", become root and issue the command 'lspci -nnv'. Second, issue the command 'dmesg | grep b43' and post the results. Larry ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Help on wireless network connectivity
Ravi wrote: Hi, I have installed fedora 9 on my laptop recently and I wanted to enable WiFi using Network manager. Lan interface : Broadcom 802.11a/b/g WLAN Please help me how can I get this done. Please tell us more. From a terminal, issue the command '/sbin/lspci -nnv', find the first two lines of the output that describe your wireless, and post them. Note: I'm not certain that lspci is in /sbin. If you get a "command not found", become root and issue the command 'lspci -nnv'. Second, issue the command 'dmesg | grep b43' and post the results. Larry ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Help on wireless network connectivity
Hi, I have installed fedora 9 on my laptop recently and I wanted to enable WiFi using Network manager. Lan interface : Broadcom 802.11a/b/g WLAN Please help me how can I get this done. thanks, Ravi ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager and NFS
On Thu, 2008-08-14 at 11:29 -0700, Robert Smits wrote: > > I think what you're asking for is called Network Location Awareness --- > > how an interface distinguishes to which network it is attached, and then > > the machine configures itself as appropriate. I think there a few > > implementations of this [standards, anybody?] but personally I like this > > one: authenticated DHCP, since it should also work securely for plain > > old wired Ethernet. > > Will that also work with fixed IP addresses? Not unless said addresses are dished out by the DHCP server from its own fixed database. Otherwise, one would have to resort to something more exotic to determine the network, or do it manually. > From my point of view, SCMP already works, but I can't use it together with > Network Manager. Can we either configure Network Manager to work with SCMP or > SCMP to work with Network Manager? I don't know which route is more feasible, > largely because I don't understand from a technical viewpoint why the > programs don't play nicely together. Is there a solution here that's easier > than re-inventing the wheel? The "best" solution is probably a dbus-aware module for SCMP that listens for changes announced by NM, and reacts accordingly. This is something you might wish to discuss with the SCMP developers. James -- The Holy ettlz [EMAIL PROTECTED] PGP key ID: 03F94B5D --- 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: Network Manager and NFS
On Thu, 2008-08-14 at 11:29 -0700, Robert Smits wrote: > On August 13, 2008 03:30:21 pm The Holy ettlz wrote: > > On Wed, 2008-08-13 at 14:37 -0700, Robert Smits wrote: > > > My workaround, which isn't entirely satisfactory, is to use ifup and > > > dispense with network manager altogether. Unfortunately, that doesn't > > > allow me to see other possible network connections and make quick and > > > easy connections when I'm on the road. > > > > > > What I still don't understand, though, is why Network Manager isn't > > > configured to deal with managing changing nfs networks. > > > > I think what you're asking for is called Network Location Awareness --- > > how an interface distinguishes to which network it is attached, and then > > the machine configures itself as appropriate. I think there a few > > implementations of this [standards, anybody?] but personally I like this > > one: authenticated DHCP, since it should also work securely for plain > > old wired Ethernet. > > Will that also work with fixed IP addresses? > > From my point of view, SCMP already works, but I can't use it together with > Network Manager. Can we either configure Network Manager to work with SCMP or > SCMP to work with Network Manager? I don't know which route is more feasible, > largely because I don't understand from a technical viewpoint why the > programs don't play nicely together. Is there a solution here that's easier > than re-inventing the wheel? You'd use the currently connected network as _input_ to scpm to get it to change the current profile, if I understand scpm correctly. When NM connects to a known network, then you can poke scpm to update your scpm "profile" to the one you want for that specific network. You could do this based on the SSID of the wifi network (and the AP's security options too, hopefully) or the MAC address of the DHCP server obtained via ARP or something like that. How do you change scpm profiles now? Manually? Dan > > http://www.cl.cam.ac.uk/~sjm217/papers/securecomm07authdhcp.pdf > > > > I've got a bit of time on my hands, I might code up my earlier HTTPS > > idea. > > > > There's a whole bunch of things you can hook into changes in network > > such as iptables, service daemons, etc., and of course NFS mounts. But > > before that the relevant NLA infrastructure needs to be in place. This > > means having (1) a mechanism to identify the network, and (2) telling > > other processes (such as other config daemons) that we're on that > > network. It should be up to the latter what action we take. NM already > > has "network link awareness", viz. Pidgin and Evolution. Am I right in > > thinking that the replacement for init is also dbus-aware? > > > > Of course, all this takes time ...and planning ;) > > Yes, it does. And thanks for thinking about the issue. I appreciate it. > > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [Suggestion] Specify additional DHCP options?
On Thu, 2008-08-14 at 09:23 +0100, The Holy ettlz wrote: > Hello, > > Just trying out NetworkManager-0.7.0-0.11.svn3930.fc8 from Koji. > send-hostname seems to be working great --- nice. > > You know, it might be useful (in the future) if there were a way to > specify extra DHCP options via the GUI (or system settings?) to retrieve > from the server, and expose them in the usual manner. Maybe; but we do want to draw a line somewhere between overloading the GUI with options and dropping to a text editor. You can actually put the options you'd like into /etc/dhclient-.conf and NM should merge them into the dhclient config it uses when bringing up the device. Granted, it might be nice to have different options on a per-connection basis though. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network Manager and NFS
On August 13, 2008 03:30:21 pm The Holy ettlz wrote: > On Wed, 2008-08-13 at 14:37 -0700, Robert Smits wrote: > > My workaround, which isn't entirely satisfactory, is to use ifup and > > dispense with network manager altogether. Unfortunately, that doesn't > > allow me to see other possible network connections and make quick and > > easy connections when I'm on the road. > > > > What I still don't understand, though, is why Network Manager isn't > > configured to deal with managing changing nfs networks. > > I think what you're asking for is called Network Location Awareness --- > how an interface distinguishes to which network it is attached, and then > the machine configures itself as appropriate. I think there a few > implementations of this [standards, anybody?] but personally I like this > one: authenticated DHCP, since it should also work securely for plain > old wired Ethernet. Will that also work with fixed IP addresses? >From my point of view, SCMP already works, but I can't use it together with Network Manager. Can we either configure Network Manager to work with SCMP or SCMP to work with Network Manager? I don't know which route is more feasible, largely because I don't understand from a technical viewpoint why the programs don't play nicely together. Is there a solution here that's easier than re-inventing the wheel? > http://www.cl.cam.ac.uk/~sjm217/papers/securecomm07authdhcp.pdf > > I've got a bit of time on my hands, I might code up my earlier HTTPS > idea. > > There's a whole bunch of things you can hook into changes in network > such as iptables, service daemons, etc., and of course NFS mounts. But > before that the relevant NLA infrastructure needs to be in place. This > means having (1) a mechanism to identify the network, and (2) telling > other processes (such as other config daemons) that we're on that > network. It should be up to the latter what action we take. NM already > has "network link awareness", viz. Pidgin and Evolution. Am I right in > thinking that the replacement for init is also dbus-aware? > > Of course, all this takes time ...and planning ;) Yes, it does. And thanks for thinking about the issue. I appreciate it. -- Robert Smits CEP525G Nanaimo, Duncan & District Labour Council Box 822 Nanaimo, V9R 5N2 Ph 250-753-0201 Fax 250-753-2954 Email [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
[Suggestion] Specify additional DHCP options?
Hello, Just trying out NetworkManager-0.7.0-0.11.svn3930.fc8 from Koji. send-hostname seems to be working great --- nice. You know, it might be useful (in the future) if there were a way to specify extra DHCP options via the GUI (or system settings?) to retrieve from the server, and expose them in the usual manner. Regards, James. -- The Holy ettlz [EMAIL PROTECTED] PGP key ID: 03F94B5D --- 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
