01-07-2013
You might write a proxy for them to report to, that annotates the event with the proxy outbound IP. If they log events locally, you could poll the logs to determine which called.
This User Gave Thanks to DGPickett For This Post:
10 More Discussions You Might Find Interesting
1. BSD
how do i configure proxy in freeBSD or NAT so that when i set it up as a server can connect other to my new gateway (0 Replies)
Discussion started by: AkinOkin
0 Replies
2. IP Networking
Hi All,
Is there any possibility to change the IP address of a package according to its MAC address. It would be a sort of L2 NAT. (i.e. If the MAC address is 00:1A:A0:1E:XX:XX so the dir IP will be 192.168.X.X)
Thanks!. (4 Replies)
Discussion started by: lagigliaivan
4 Replies
3. Shell Programming and Scripting
hellou, can anybody help me with nat detection in real time ? i prefer some detection script because i try some nat detection program's for example p0f or i'm using tcpdump, but i would get contain of specific packet. Some ideas? (1 Reply)
Discussion started by: TheTechnic
1 Replies
4. Solaris
Hi everybody,
I'm running on Solaris 10 X86 (update 1009).
I would like to make NAT's rule. I explain you.
On Solaris, I configure the principal interface e1000g0 with IP : 192.168.0.33
I created the first logical interface like that :
ifconfig e1000g0 addif 192.168.0.40 netmask... (0 Replies)
Discussion started by: aureliensm
0 Replies
5. IP Networking
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
6. Red Hat
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
7. IP Networking
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
8. Infrastructure Monitoring
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
9. UNIX for Dummies Questions & Answers
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
10. Solaris
Hi.
I am attempting to set up an OpenVPN server on my Solaris 11 box by following all the Linux guides. Thus far I have a working VPN that I can connect to and ssh onto my VPN server over which is great but not what I require long term.
I would like to route all VPN client requests for addresses... (0 Replies)
Discussion started by: nickb1976
0 Replies
LEARN ABOUT DEBIAN
radsecproxy
radsecproxy(1) General Commands Manual radsecproxy(1)
NAME
radsecproxy - a generic RADIUS proxy that provides both RADIUS UDP and TCP/TLS (RadSec) transport.
SYNOPSIS
radsecproxy [-c configfile] [-d debuglevel] [-f] [-i pidfile] [-p] [-v]
DESCRIPTION
radsecproxy is a generic RADIUS proxy that in addition to to usual RADIUS UDP transport, also supports TLS (RadSec). The aim is for the
proxy to have sufficient features to be flexible, while at the same time to be small, efficient and easy to configure. Currently the exe-
cutable on Linux is only about 48 KB, and it uses about 64 KB (depending on the number of peers) while running.
The proxy was initially made to be able to deploy RadSec (RADIUS over TLS) so that all RADIUS communication across network links could be
done using TLS, without modifying existing RADIUS software. This can be done by running this proxy on the same host as an existing RADIUS
server or client, and configure the existing client/server to talk to localhost (the proxy) rather than other clients and servers directly.
There are however other situations where a RADIUS proxy might be useful. Some people deploy RADIUS topologies where they want to route
RADIUS messages to the right server. The nodes that do purely routing could be using a proxy. Some people may also wish to deploy a proxy
on a site boundary. Since the proxy supports both IPv4 and IPv6, it could also be used to allow communication in cases where some RADIUS
nodes use only IPv4 and some only IPv6.
OPTIONS
-f
Run in foreground
By specifying this option, the proxy will run in foreground mode. That is, it won't detach. Also all logging will be done to stderr.
-d <debug level>
Debug level
This specifies the debug level. It must be set to 1, 2, 3, 4 or 5, where 1 logs only serious errors, and 5 logs everything. The
default is 2 which logs errors, warnings and a few informational messages.
-p
Pretend
The proxy reads configuration files and performs initialisation as usual, but exits prior to creating any sockets. It will return
different exit codes depending on whether the configuration files are okay. This may be used to verify configuration files, and can
be done while another instance is running.
-v
Print version
When this option is specified, the proxy will simply print version information and exit.
-c <config file path>
Config file path
This option allows you to specify which config file to use. This is useful if you want to use a config file that is not in any of
the default locations.
-i <pid file path>
PID file path
This option tells the proxy to create a PID file with the specified path.
SIGNALS
The proxy generally exits on all signals. The exceptions are listed below.
SIGHUP
When logging to a file, this signal forces a reopen of the log file.
SIGPIPE
This signal is ignored.
FILES
/etc/radsecproxy.conf
The default configuration file.
SEE ALSO
radsecproxy.conf(5), RadSec internet draft http://tools.ietf.org/html/draft-ietf-radext-radsec
1 Jun 2010 radsecproxy(1)