Sponsored Content
Full Discussion: Accept SNMP Packets...
Special Forums UNIX and Linux Applications Infrastructure Monitoring Accept SNMP Packets... Post 302471240 by karlochacon on Friday 12th of November 2010 10:15:04 AM
Old 11-12-2010
any idea

any idea guys?

I was thinking maybe using hosts.allow/deny

but I am not sure how to use it

hosts.allow
snmpd: 192.168.1.2 192.168.1.3

basically I want any kind of connection to my server but SNMP only 6 servers

how should I ply with hosts.deny/allow or SNMP to do this?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

sending packets

How can i send a packet, and what is an empty packet? (8 Replies)
Discussion started by: Avatar0fEvil
8 Replies

2. Programming

Packets Getting Lost

I am working on a project, which has the following type of hardware setup. A special hardware device is receiving data from an external network interface. So we can have multiple such a hardware devices. Now these hardware devices will route the captured incoming data through the external... (4 Replies)
Discussion started by: S.P.Prasad
4 Replies

3. IP Networking

counting the packets

there are a number of clients connected to a server.... how can i count that each clients recieve ...? how do i moniter the activity of the client..? (2 Replies)
Discussion started by: damn_bkb
2 Replies

4. Infrastructure Monitoring

capture snmp packets in AIX

Hi, I want to capture snmp packets in AIX. When i give print from AIX6.1, Printer will give its response thru' snmp. I used iptrace command like below, but it is not capturing snmp packets other packets are captured like udp, tcp.. 1. iptrace command: /usr/sbin/iptrace -a -i en0... (1 Reply)
Discussion started by: meeraramanathan
1 Replies

5. HP-UX

packets statistics

Hi there, are there any functions that can get the packets statistics on UNIX ? thanks. (2 Replies)
Discussion started by: Frank2004
2 Replies

6. IP Networking

Sending data from DELL OMSA SNMP and Custom SNMP MIB to same UDP port 161

Hi , Currently DELL OMSA SNMP sends data through default udp port 161.I want my custom SNMP MIB also to send data in the same udp port 161.Whether its possible.If yes where to configure .I tried starting my custom MIB in udp port 161,but it throws port already in use.Kindly guide. (0 Replies)
Discussion started by: prabakar4all
0 Replies

7. Red Hat

Sending data from DELL OMSA SNMP and Custom SNMP MIB to same UDP port 161

Hi , Currently DELL OMSA SNMP sends data through default udp port 161.I want my custom SNMP MIB also to send data in the same udp port 161.Whether its possible.If yes where to configure .I tried starting my custom MIB in udp port 161,but it throws port already in use.Kindly guide. (1 Reply)
Discussion started by: prabakar4all
1 Replies

8. IP Networking

SNMP Problem - SNMP not getting to the agent.

I am having a problem with an SNMP event, and I am not sure where I should be looking to solve this problem. Description: There is an SNMP event in our system that for one reason or another is not getting sent out as an email because it is never getting to our SNMP agent. I see where the... (0 Replies)
Discussion started by: broberts
0 Replies

9. Infrastructure Monitoring

SNMP traps to SNMP server

Dear Champs, I am new to unix, and need to configure linux server to send below traps to a SNMP server. Monitoring TRAP Disk Space Low Monitoring TRAP Memory Low Monitoring TRAP CPU high Monitoring TRAP Admin login/Logoff Please help me how to send this information to my SNMP server... (2 Replies)
Discussion started by: stavar
2 Replies

10. UNIX for Dummies Questions & Answers

Need to transfer all kernel logs (var/log/messages) to the snmp listener as snmp trap

i am working with embedded system -Dell DCS management sub system. my question is as below: currently we are using linux kernel 2.6.30 build and we have a kernel logs stored to the /var/log/messages path. now we have to transfer all this logs to the specified SNMP target as a part of SNMP... (4 Replies)
Discussion started by: vipul_prajapati
4 Replies
DOVEADM-DIRECTOR(1)						      Dovecot						       DOVEADM-DIRECTOR(1)

NAME
doveadm-director - Manage Dovecot directors SYNOPSIS
doveadm [-Dv] director add [-a director_socket_path] host [vhost_count] doveadm [-Dv] director flush [-a director_socket_path] host|all doveadm [-Dv] director map [-a director_socket_path] [-f users_file] [host] doveadm [-Dv] director remove [-a director_socket_path] host doveadm [-Dv] director dump [-a director_socket_path] doveadm [-Dv] director status [-a director_socket_path] [user] DESCRIPTION
doveadm director can be used to manage and query the status of the list of backend mail servers where Dovecot proxy can redirect connec- tions to. OPTIONS
Global doveadm(1) options: -D Enables verbosity and debug messages. -v Enables verbosity, including progress counter. Command specific options: -a director_socket_path This option is used to specify an alternative socket. The option's argument is either an absolute path to a local UNIX domain socket, or a hostname and port (hostname:port), in order to connect a remote host via a TCP socket. By default doveadm(1) will use the socket /var/run/dovecot/director-admin. The socket may be located in another directory, when the default base_dir setting was overridden in /etc/dovecot/dovecot.conf. ARGUMENTS
host A mail server's hostname or IP address. user Is a user's login name. Depending on the configuration, a login name may be for example jane or john@example.com. vhost_count The number of "virtual hosts" to assign to this server. The higher the number is relative to other servers, the more connections it gets. The default is 100. COMMANDS
director add doveadm director add [-a director_socket_path] host [vhost_count] The command's tasks are: * assign a new mail server to the director. * increase/decrease the vhost_count of an already assigned server. director flush doveadm director flush [-a director_socket_path] host|all doveadm director flush drops all user associations either from the given host or all hosts. This command is intended mainly for testing purposes. director map doveadm director map [-a director_socket_path] [-f users_file] [host] The command doveadm director map is used to list current user -> host mappings. Note that the director works using 32bit hashes which makes collisions quite likely, so this command can't reliably list exactly which users have recently logged in. -f users_file Path to a file containing all user names (one per line). When given no userdb lookup will be performed. This may be a helpful alternative when for example the network connection to the LDAP or SQL server is slow. host Specify a server's IP address or hostname, to list only mappings of the given host. director remove doveadm director remove [-a director_socket_path] host Use this command in order to remove the given host from the director. director dump doveadm director dump [-a director_socket_path] Dump the current host configuration as doveadm commands. These commands can be easily run after a full director cluster restart to get back to the dumped state. director status doveadm director status [-a director_socket_path] [user] This command is used to show the current usage of all assigned mail servers. When a user name is given, this command shows which server the user is currently assigned to, where the user will be assigned after the current saved assignment gets removed and where the user would be assigned to if the whole proxy cluster was restarted fresh. FILES
/etc/dovecot/dovecot.conf Dovecot's main configuration file. /etc/dovecot/conf.d/10-director.conf Director specific settings. EXAMPLE
Add a director with vhost count 150 (or change existing one's vhost count to 150): doveadm -v director add x1357.imap.ha.example.net 150 2001:db8:543:6861:143::1357: OK Remove a director: doveadm director remove x1357.imap.ha.example.net Query the status of mail hosts in a director: doveadm director status mail server ip vhosts users 192.168.10.1 100 125 192.168.10.2 100 144 192.168.10.3 100 115 Query the status of a user's assignment: doveadm director status user@example.com Current: 192.168.10.1 (expires 2010-06-18 20:17:04) Hashed: 192.168.10.2 Initial config: 192.168.10.3 This means that the user is currently assigned to mail server on IP 192.168.10.1. After all of user's connections have logged out, the assignment will be removed (currently it looks like at 20:17:04, but that may be increased). After the assignment has expired, the user will next time be redirected to 192.168.10.2 (assuming no changes to director settings). If the entire Dovecot proxy cluster was restarted, so that all of the director configuration would revert back to its initial values, the user would be redirected to 192.168.10.3. REPORTING BUGS
Report bugs, including doveconf -n output, to the Dovecot Mailing List <dovecot@dovecot.org>. Information about reporting bugs is avail- able at: http://dovecot.org/bugreport.html SEE ALSO
doveadm(1) Dovecot v2.2 2013-07-12 DOVEADM-DIRECTOR(1)
All times are GMT -4. The time now is 06:21 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy