01-29-2002
A SOCKS server and a default gateway are two different things, and may or may not be the same machine (most likely not the same). If you want to use a SOCKS or other web-proxy to access the net, setup your client (AIX) machine as you normally would -- i.e. set your default gateway as provided by your network admin. Then setup your web-browser preferences to use the proxy server IP address.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm trying to get a Unix server on the internet (mostly for DNS requests) but this server is on a network behind a Proxy server. How can I configure my unix server that he will pass the proxy server for internet requests? (2 Replies)
Discussion started by: RSlegers
2 Replies
2. Linux
i have installed a proxy server on my linux box .
how to get the IP for that proxy .
cheers (3 Replies)
Discussion started by: ppass
3 Replies
3. Red Hat
Hi,
I want to be able to get my server to update via yum through our work proxy.
I have tried the usual method of exporting the http_proxy=http://username:password@domain.com but this does not work for me.
I opce heard about a guy who set up a proxy on his XP laptop (Don't flame me I have... (0 Replies)
Discussion started by: pobman
0 Replies
4. IP Networking
Hi,
I am involved in a project on Debian. One of my requirement is to route an IP packet in my application to a proxy server and receive the reply from the proxy server as an IP packet. My application handles data at the IP frame level. My application creates an IP packet(with all the necessary... (0 Replies)
Discussion started by: Rajesh_BK
0 Replies
5. Cybersecurity
I may be doing this incorrectly, so if you have any suggestions, I'm open to it. So I installed a reverse proxy server on my LAN. It's not on the DMZ because it's coming from a blade running inside a virtual machine. Anyways, so I installed iptables and locked everything down from the outside... (1 Reply)
Discussion started by: sdotsen
1 Replies
6. UNIX for Advanced & Expert Users
Hello,
i have Sun one Messaging Server 6.3 Up and running, i want to route emails that are destined to a certain email address, let's say test@mydomain.com through the tcp_local channel for example, to another email, and not allowing test@mydomain.com to receive them.
So in short, i want... (0 Replies)
Discussion started by: lemonshare
0 Replies
7. IP Networking
We have two subnets, say 'domA' (192.168.0.0/24) and 'domB' (10.10.0.0/16). These subnets are connected through the router 'router01'. One server 'base01' has two network cards, configured to domA and domB subnets respectively.
Now let's consider a host host01.domA (192.168.0.5) trying to... (0 Replies)
Discussion started by: amriksk
0 Replies
8. UNIX for Dummies Questions & Answers
Hi,
i would like to enable all operations/connections to use a proxy server in a redhat server ,
witch file should i config to get this for all conections ....
Thanks (0 Replies)
Discussion started by: prpkrk
0 Replies
9. UNIX and Linux Applications
Hi Friends,
I am trying to connect to remote server via proxy server and transfer files from my server .
the proxy server is windows.
I wanted to know is that is it possible?
I am using command to connect is
/usr/local/bin/sftp -o "ProxyCommand nc proxyserver.com 8080"(E-Mail... (6 Replies)
Discussion started by: mallayanala
6 Replies
10. IP Networking
Hey there,
I am a network administrator of a student dorm. Me and my team (we do this in our spare time) have the task to upgrade and rebuild our dorm intern network. But unfortunately we don't have that much experience with server setup and ip-routing and stuff. So here is the topic I want to... (8 Replies)
Discussion started by: mrgruen
8 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)