Network Manager questions - startup etc

Hi all,
I have a couple of questions about the Network Manager in 10g Spatial that i'm wondering if someone can help me with.
1) Are there any plans to supply the "ShortestPath" type functionality currently (to my knowledge) only available in Java to PL/SQL?
2) It seems that the NetworkManager.readNetwork() function reads the entire specified network into memory (not surprisingly given it's name). When i've tried this with a pretty decent sized network it has swallowed huge quantities of memory and taken upwards of 40 minutes or so to perform this operation. And this isn't even on the largest network I can imagine. What would happen if I tried to read an entire US "minor road" set? I've seen the app in the "Pro Oracle Spatial" book which seems to load the network and keep it accessible via a JSP session handle (p493). Is this the recommended approach - a "one-time" initialisation and a machine with LOTS of memory?!
3) Does anyone know if the source code for the "eLocation" demo (http://elocation.oracle.com/elocation/elocation_entry.jsp) is available?
Thanks all,
Steve

Hi Steve,
1) PL/SQL API for Network Analysis is coming in Oracle 10g Release 2.
2) In Oracle 10g Release 1 it is a requirement to load the entire network. Loading the entire street network of new york city on my 1 Ghz laptop requires about 1 minute. In Oracle 10g Release 2 you can specify a predicate on the load network so you do not have to load the entire network.
3) Source code for elocation will be available as an Oracle 10g Release 2 feature (I'm not sure what the "name" of the feature is, but it is a bundling of geocoding and routing, and when combined with MapViewer is a complete "elocation in a box" type of feature.
Hope this helps.

Similar Messages

Network Management: Question about calculating network,host and broadcast a

I would like to say i am new to this forum and I do not know if this is the right place to post this but i am currently in a cisco academy for CCNA and if anyone else is in this class i am stuck @ 6.2.2 in the online cisco material.....
given the following address/prefix of 141.124.88.174/30
enter the last octet in binary of the network,
I am totally lost @ how to find the network octet i know /30 means the first 30bits are network and the last 2 are host i also know the last octet is 10101100 or 172
my question how do you get .174 to .172??? if you are wondering how i know the answer --it is in the book i just dont know how to do it on my own :)
thanks much

Eric
My sense is that you may have skipped a step (or maybe I skipped in understanding your post). The best way to explain this is to refer to binary - which you have started to do.
For address ...174 the last octet is 101011 10 (in which 101011 represent the network bits and 10 represent the host bits). To find the network bits make the host bits all binary 0 - which means that the subnet address is 101011 00 or 172.
So the answer to your question is that you get from 174 (host address ) to 172 (network address) by changing all host bits to binary zero.
HTH
Rick

No interfaces shown in network manager [SOLVED]

Hi All,
I have just done a fresh install of Arch on my new Sony Vaio VGN-FW53GF, all goes well, except for Network Manager.
I can use my wired connection ok as eth0 shows up as active when I hover over the kde applet in the task bar. However when I go to "Manage Connections"
I do not see any Wireless networks or even my "working" wired connection in any list.
Wireless seems to be working as iwconfig shows an interface.
wlan0 IEEE 802.11abgn ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=0 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
But a scan gives this:
iwlist wlan0 scan
wlan0 Interface doesn't support scanning : Network is down
This machine is using the Intel driver "iwlagn" supplied by the kernel (2.6.31).
My /etc/rc.conf is:
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.utf8"
HARDWARECLOCK="UTC"
USEDIRECTISA="no"
TIMEZONE="Pacific/Auckland"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=()
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="Laptop2"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
wlan0="dhcp"
INTERFACES=(!eth0 !wlan0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng !network hal networkmanager netfs crond)
Can anyone offer some suggestion on how to get network manager going, I would like to use it. In the past
I have used Wicd, but it has some limitations.
Cheers,
Bernie
Last edited by bmentink (2009-12-24 04:19:49)

bmentink wrote:
Ok, I found the issue. I was missing the firmware for the card. I downloaded firmware from the intel site as per the wiki on wireless and
my interface comes up (shown with ifconfig) and I can see all the networks.
However, I cannot seem to connect to my network with WPA. When I go to connect I get network manager thinking the access point is WEP and asking for pass phrase.
If I select WPA(personal) and fill in a password, nothing happens .... just says unavailable.
Can anyone give some idea's here. I have not used network manager before for WPA.
Cheers,
Bernie
I use WPA2 with network manager without a problem. It should "just work", im not sure why you have issues, can you switch your router to a different security protocol to test?

Xfce4 and gnome-network-manager [solved]

I just made a clean install of archlinux. installed xorg and Xfce4, xfce-goodies, gnome-panel, gnome-desktop and gnome-network-manager. also I enabled GNOME services in startup and sessions. how do I start that network manager now? is nowhere in the settings, nor there is icon to add to the taskbar (i got xfapplets installed too)
Last edited by anarxi (2009-01-14 00:22:42)

quoted from a previous thread
I solved it by uncommenting my <locale><charset> in /etc/locale.gen.
First you have to enable the locales you want being supported by your system. To enable or disable them, the file /etc/locale.gen is used. It contains every locale you can enable, and you have just to uncomment lines you want to do so.
As we want to setup an english UTF-8 conform system, we want to enable en_US.UTF-8. But for compatibility to programs that don't support UTF-8 yet, it's recommended to support any other locale, prefixed with en_US as well. Having this in mind, we enable this set of locales:
en_US.UTF8 UTF-8
en_US ISO-8859-1
After you've enabled the necessary locales, you have to run locale-gen as root to update them:
# sudo locale-gen
Generating locales...
en_US.UTF-8... done
en_US.ISO-8859-1... done
Generation complete.

[Solved] Can't get gnome network manager running

Alright this one is a head scratcher. I've folowed the wiki for network manager to a T except I can't get the network manager icon to show up (I have notification addon already running). I don't have any network loss though.
Here's my rc.conf
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="Canada/Pacific"
KEYMAP="dvorak/dvorak"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(powernow-k8 cpufreq_ondemand cpufreq_powersave forcedeth snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="myhost"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
INTERFACES=(lo !eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng !network netfs crond laptop-mode dhcdbd networkmanager @alsa @hal @fam @gdm)
Last edited by dr/owned (2009-01-09 05:16:43)

I assume you're running nm-applet --sm-disable once you get a window manager session up?
Try starting networkmanager after hal. From the wiki:
You must also "disable" the default network daemon, and add the hal, dhcdbd and networkmanager daemons in this order:
DAEMONS=( ... !network hal dhcdbd networkmanager ... )

Network Manager applet won't show up on my desktop

I use wifi-menu to connect to wifi, even if I'd like to use NetworkManager since I used it in debian. Anyways, I have NetworkManager installed, and xfce tells me it's in the systray except it's not. This is a pretty huge problem for me, especially because my wifi drivers tend to disconnect and wifi-menu doesn't help that much when I have an internet that doesn't work. In Debian, if my drivers disconnected all I'd have to do is reconnect from NetworkManager and they'd magically work again.

waddicto wrote:However, I have a different problem now, I have two network applets in my systray.
The network-manager-applet package installs the startup file: /etc/xdg/autostart/nm-applet.desktop
Are you starting up another nm-applet somewhere else?

Need getting network list with Network Manager

I have not been able to get the list of networks to show up in Network Manager. I tried the NM wiki but still no luck. Help would be greatly appreciated.
Wireless Card:
06:00.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)
rc.conf
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(e100 mii slhc !bcm43xx b43 snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="myhost"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
eth0="dhcp"
INTERFACES=(!eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.1.1"
ROUTES=(gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng !network hal dhcdbd networkmanager fam !netfs crond alsa gdm)
Last edited by 449 (2008-08-28 22:42:39)

I cannot get the LED light on. The card works fine because I am using XP right now.
I installed both the bcm43xx and the bm43 firmware in an attempt to get it working. Could one or the other be causing a conflict?
When I tried to modprobe either of the two I get something like "invalid operation."
When I do
b43-fwcutter -w "/lib/firmware/" wl_apsta_mimo.o
it gives me an error saying the input doesn't exist.
edit: Could I get this moved to the wireless section?
Last edited by 449 (2008-09-05 17:07:51)

Network management methods

I have a problem with choosing the most suitable network management method in Arch for my laptop. The question itself may seem silly, but after reading some articles in ArchWiki I got a bit confused.
What I need is to be able to connect and disconnect reasonably quickly to different wireless networks (manually) and to be able to connect automatically to my home network during startup. KDE applets are welcome, but not necessary. As far as ethernet network card is concerned, I'd like it to connect automatically when the cable is plugged in.
Which method would be the most efficient solution (NetworkManager, netcfg, other)?

There are three main choices: NetworkManager, wicd and netcfg. All of them should work for you, but NM and wicd seem a better fit for KDE. Of those two, NM seems to have more features (e.g. connecting with usb modems/phones), but it not always wanted to play nice with my hardware, while wicd always did. With NM, you can use gnomish nm-applet (network-manager-applet package), which is most featureful and stable, or you can try using knetworkmanager or NM applet from the kdeplasma-applets-networkmanagement package - those seem to be somewhat buggy. With wicd, you can use wicd-client-kde from AUR.

Network management system recommendations

I have been looking at some network management systems such as SolarWinds, but I would like to kick the question back to the community to see what you guys recommend.
I am looking for a powerful, uniform, monitoring system that includes the following:
1. Network device management (syslog, configuration management, inventory, device tracker [like CW CampusManager], etc.)
2. Application monitoring (checking if hyperlinks are working, availability, etc.)
3. Database monitoring (SQL query response times, etc.)
4. QoS monitoring (jitter, delay, SLA, etc.)
5. Alerts
Anything beyond this would be a plus.
I am looking for the "best" solution out there in terms of performance and features ...

NetFlow and IPSLA are different technologies.
Cisco NetFlow captures header information from actual IP traffic passing through router interfaces and reports on traffic usage, applications used, souce and destination of traffic, port and protocol used, ToS, DSCP, next hop and so on. Using NetFlow you can see who is using your bandwidth, what application is being used, etc.
Cisco IPSLA is a feature from Cisco that lets you measure the performance of a link using simulated packets and reports on jitter, latency, packet loss, Round-Trip time, packet loss, link availability, etc.
In short, NetFlow is used for bandwidth monitoring and traffic analysis of actual IP traffic that is passing through a link and IPSLA is used to measure how a link will perform when traffic passes through it.
Cisco supports both features - NetFlow and IPSLA.
IPSLA needs Cisco devices with IPSLA support at the source and destination ends with atleast IOS 12.3(14)T
NetFlow is exported as UDP packets to a flow analyzer tool - many tools use 9996 or 2055 for NetFlow export
IPSLA requires routers with Cisco IPSLA capability and IPSLA stats is collected via SNMP.
There are tools in the market which can monitor both. We at ManageEngine have NetFlow Analyzer, which supports NetFlow and IPSLA in addition to many more monitoring technologies like Cisco NBAR, WAAS monitoring, Cisco Medianet, etc.
Cisco NBAR is a deep packet inspection technology which analyzes data packets to report on application usage. NBAR can detect applications hiding behind well know ports or using random ports and you can also further use NBAR to define your QoS polcies.
If you need to know more on the software that can monitor these technologies, you can contact ManageEngine NetFlow Analyzer support at netflowanalyzer-support 'at' manageengine. com
Regards,
Don Thomas Jacob
www.netflowanalyzer.com
NOTE: Please rate posts and close questions if your query has been answered

(wifi) broadcom-wl or network-manager trouble not sure

I configurated my broadcom bcm4313 (4727) with broadcom-wl (driver recommanded for my needs by broadcom devellopers), up and running in network-manager (seen there to connect with ...) ... (Checked it with CalimeroTeknik today)
When I connect to my wifi relay (an adhoc by wifi), it try to connect and fail ... (I couldn't use wicd for my needs, as I use multiples connections and AP to make an adhoc that is not possible with wicd and need a gui tools as my gf uses it sometimes or may lend it to make peoples try Archlinux for example ...
Any ideas of what could be the trouble ?
My lsmod : http://pastebin.com/eveinQdU
My dmesg : http://pastebin.com/rhigpitH
ip a s : http://pastebin.com/qxmw6DYy
ifconfig -a then iwlist scan : http://pastebin.com/vvMuY0Q0

spiky25 wrote:
Does it mean that the manual configuration worked ?
Edit : seem to have made another wifi adhoc of the same name and key, how I change this line : # iwconfig wlan0 mode ad-hoc ???
Yes, your manual configuration worked just fine.
The IP address Gusar refers to, you still have to acquire from the router - which is at the end of step 4 of the wiki. If it does not work like described in the wiki (#dhcpcd eth0), you have to start the dhcpcd daemon first by
sudo /etc/rc.d/dhcpcd restart
Question 2: You only have to change the interface in the iwconfig line, since your wireless seems to be on eth0:
iwconfig eth0 mode ad-hoc
However, you really dont need to do that since you already connected to the wireless "sharenet" according to your output.
So, just redo the steps and go the steps4 to the end to get an IP. If you see that working, you can ping any internet site to see if it works (or start any browser), as /dev/zero says. (if that works , your wicd should actually also work after network restart).
If it does not work, come back to us with the error you see plus the output of
ip addr
ip route
edit: add words
Last edited by Strike0 (2011-11-22 21:54:39)

How Can I configure network manager correctly?

Well, in debian, when I started the gnome session, immediately I was asked for a password to connect my default wireless connection. It is the correct way I want.
In arch, the process is: First, the network manager connects to localhost (I don't know why...), and I have to select manually my wireless net to connect to it, and put my password.
Is there anyway to make this process as it was in debian? So, when I start gnome session, be asked for password and connect immediately.
My rc.conf:
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="es_ES.UTF-8"
HARDWARECLOCK="localtime"
TIMEZONE="Europe/Madrid"
KEYMAP="es"
CONSOLEFONT="lat1-16"
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# Scan hardware and load required modules at bootup
MOD_AUTOLOAD="yes"
# Module Blacklist - modules in this list will never be loaded by udev
MOD_BLACKLIST=()
# Modules to load at boot-up (in this order)
# - prefix a module with a ! to blacklist it
MODULES=(ipw3945 8139too mii cpufreq_powersave cpufreq_userspace
freq_table acpi_cpufreq asus_acpi sn9c102)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
HOSTNAME="samantha"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available
# interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
lo="lo 127.0.0.1"
eth0="dhcp"
eth2="dhcp"
INTERFACES=(lo !eth0 !eth2)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.1.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network-profiles
#NET_PROFILES=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng crond hal hwd cpudyn @alsa xinetd vmware ipw3945d
laptop-mode dhcdbd networkmanager !network netfs gdm)
# End of file
Greetings

If i'm not misstaken, this is a bug in the latest version of NetworkManager (0.64).

Network Manager & Keyring password

This question has probably been asked "ad nauseam" but I'm trying to get Network Manager (in GNOME) to stop asking me for my keyring password. I searched in the forums and I found out there used to be a pam_keyring package that took care of this but it's not available anymore. Strangely this can be done with other distros so surely, it is also doable in Arch, right? TIA.

Allan wrote:Is this possible without logging in using gdm? I use networkmanager in XFCE with slim login manager and can't manage to get this to work.
I was able to disable the annoying 'feature' whereby the Gnome Keyring keeps asking for a password at login by editing /etc/pam.d/login in addition to the other edits suggested to /etc/pam.d/gdm (http://wiki.archlinux.org/index.php/Net … Kit_issues). I also deleted ~/.gnome2/keyrings. This is especially useful since I don't use gdm to login, rather loggin straight from the shell. YMMV if you use kde or another DE.

Network-manager-applet cannot run!!!!!!!!!!

Installed networkmanager and network-manager-applet, but I found it could not startup at boot time.....
When I run nm-applet in terminal as normal user, it print:
[yin@q ~]$ nm-applet
** (nm-applet:2168): WARNING **: <WARN> request_name(): Could not acquire the NetworkManagerUserSettings service.
Error: (9) Connection ":1.39" is not allowed to own the service "org.freedesktop.NetworkManagerUserSettings" due to security policies in the configuration file
When I run "sudo nm-applet", noting was wrong ,and the icon appeared in the panel right top.
Another question:
What's the difference between daemons in rc.conf and startup applications in gnome ?
I add "networknamager" in daemons line in rc.conf ,but I found there is a network manager entry in startup applications in gnome with the command : nm-applet --sm-disable. Does they conflict ??
Last edited by iamybj (2010-03-27 12:52:56)

iamybj wrote:
ngoonee wrote:You did not search the forums. Please do so before asking a question.
I think if the question was resolved, it should be updated to the wiki....
I find the wiki updating is very slow right now.
You misunderstand how this community works.
Users update the wiki, voluntarily. If you find a solution and feel its a common enough problem to post on the wiki, please do so.
Also, if you can't even bother to do a forum search or google search before asking questions, this may not be the right distro for you. Please read http://wiki.archlinux.org/index.php/FAQ … se_Arch.3F, especially the 'do-it-yourself' part.

Network Management System procedure

Hi All,
I have some confusion about the subject. Please correct me if i am wrong
There are two techniques to have compelte network management system.
Netflow Analyzer
IP SLA
Question:
Both supported by cisco?
Both use snmp (not sure)?
Both use specific port (like netflow use 9996 but dont know ip sla use or not)?
Both monitor network ?
Both can be monitered by one software?
what is nbar?

NetFlow and IPSLA are different technologies.
Cisco NetFlow captures header information from actual IP traffic passing through router interfaces and reports on traffic usage, applications used, souce and destination of traffic, port and protocol used, ToS, DSCP, next hop and so on. Using NetFlow you can see who is using your bandwidth, what application is being used, etc.
Cisco IPSLA is a feature from Cisco that lets you measure the performance of a link using simulated packets and reports on jitter, latency, packet loss, Round-Trip time, packet loss, link availability, etc.
In short, NetFlow is used for bandwidth monitoring and traffic analysis of actual IP traffic that is passing through a link and IPSLA is used to measure how a link will perform when traffic passes through it.
Cisco supports both features - NetFlow and IPSLA.
IPSLA needs Cisco devices with IPSLA support at the source and destination ends with atleast IOS 12.3(14)T
NetFlow is exported as UDP packets to a flow analyzer tool - many tools use 9996 or 2055 for NetFlow export
IPSLA requires routers with Cisco IPSLA capability and IPSLA stats is collected via SNMP.
There are tools in the market which can monitor both. We at ManageEngine have NetFlow Analyzer, which supports NetFlow and IPSLA in addition to many more monitoring technologies like Cisco NBAR, WAAS monitoring, Cisco Medianet, etc.
Cisco NBAR is a deep packet inspection technology which analyzes data packets to report on application usage. NBAR can detect applications hiding behind well know ports or using random ports and you can also further use NBAR to define your QoS polcies.
If you need to know more on the software that can monitor these technologies, you can contact ManageEngine NetFlow Analyzer support at netflowanalyzer-support 'at' manageengine. com
Regards,
Don Thomas Jacob
www.netflowanalyzer.com
NOTE: Please rate posts and close questions if your query has been answered

Trying to use wireless N with iwlwifi & network manager

Have all the h/w necessary to use wireless N:
Intel Centrino-N 1030
Linksys E3200 running Tomato 1.28
Linksys E4200 running dd-wrt 21286
Also updated everything today (pacman -Syu):
>uname -a
Linux hostname 3.12.9-2-ARCH #1 SMP PREEMPT Fri Jan 31 10:22:54 CET 2014 x86_64 GNU/Linux
So, with either router set up with as an AP at 2.4GHz and N-Only (the centrino 1030 doesn't support 5GHz), and the module defaults loaded, I see odd behavior. First, once connected to either AP, Network Manager still reports the connection to be at B/G.
I checked the module config, and this part is relevant:
>modinfo iwlwifi | grep 11n
parm: 11n_disable:disable 11n functionality, bitmap: 1: full, 2: agg TX, 4: agg RX (uint)
There's a lot of chatter on the forums about earlier kernels not supporting N w/ iwlwifi, and recommending to disable it with '11n_disable=1' in /etc/modprobe.d/iwlwifi.conf. So I tried explicitly enabling it, and assuming it's a binary value:
>cat /etc/modprobe.d/iwlwifi.conf
options iwlwifi 11n_disable=0
After reloading the module(s) (and restarting wpa_supplicant & networkmanager), the thing I'm finding confusing is that I can see evidence of this change take effect:
>cat /sys/module/iwlwifi/parameters/11n_disable
0
...but it doesn't affect the output of modinfo (same as above), nor am I able to connect to either router at N (NM still reports B/G). Also confused how it connects at all when the routers are set to N-Only?

modinfo iwlwifi
That is not supposed to change. It just shows you the parameters and their valid configurations.
options iwlwifi 11n_disable=0
>cat /sys/module/iwlwifi/parameters/11n_disable
0
Did you check that it was not already 0?
...but it doesn't affect the output of modinfo (same as above), nor am I able to connect to either router at N (NM still reports B/G). Also confused how it connects at all when the routers are set to N-Only?
If the card connects with the routers set to n only, then the card is capable of working with n. I usually check with nm-tools and look at the speed indicated.
Here is the thing: Routers and cards sometimes negotiate a lower speed to prevent intereference with other devices. I usually 'get' N-speed only once I start to saturate the link.

Network Manager questions - startup etc

Similar Messages

Maybe you are looking for