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 OSX
internetsharing
InternetSharing(8) BSD System Manager's Manual InternetSharing(8)
NAME
InternetSharing -- simple NAT/router configuration daemon
SYNOPSIS
InternetSharing -d
DESCRIPTION
InternetSharing is the back-end for the Internet Sharing feature. It is responsible for configuring the network interfaces, the DHCP server
bootpd(8), the network address translation daemon natd(8), and the Internet domain name server named(8). named(8) is run in caching-only
mode and allows the DHCP server to always offer the same DNS server address to the DHCP clients, regardless of the value of the actual DNS
server addresses.
The single command line option -d places additional debugging information to stdout/stderr.
InternetSharing is launched by launchd(8) both at start-up and when the user turns Internet Sharing on in the Sharing preferences pane.
By default, InternetSharing configures the IP addresses for non-AirPort interfaces starting at 192.168.2.1, walking up by one class C network
(subnet mask 255.255.255.0) for each subsequent interface i.e. 192.168.3.1, 192.168.4.1, 192.168.5.1, and so on. The AirPort interface by
default is assigned 10.0.2.1.
CONFIGURATION
InternetSharing reads the property list com.apple.nat.plist stored in the /Library/Preferences/SystemConfiguration.
Details of the com.apple.nat.plist are subject to change and are not completely documented here. The plist is a contract between the Sharing
preferences pane and InternetSharing. Any details provided here are for informational purposes only.
The plist is a dictionary with a single sub-dictionary called NAT containing properties to control which interfaces to use and other set-
tings. It may also have a sub-dictionary called AirPort that is used to configure the AirPort interface when it is put into access point
mode.
One property worth mentioning is SharingNetworkNumberStart. This property controls the behavior of InternetSharing when it configures IP
addresses for the local interfaces. The property is encoded as a string containing the dotted decimal network IP address, assumed to be a
class C network. For example:
<key>SharingNetworkNumberStart</key>
<string>192.168.100.0</string>
If the SharingNetworkNumberStart appears directly in the NAT dictionary, it controls the starting IP address chosen for the non-AirPort
interfaces. If the property appears within the AirPort sub-dictionary, it controls the IP address assigned to the AirPort interface.
The purpose of the property is to allow the user to avoid address collisions with existing NAT'd networks.
SEE ALSO
bootpd(8), launchd(8), natd(8), named(8)
Mac OS X Feburary 26, 2007 Mac OS X