09-21-2015
Quote:
Originally Posted by
MichaelFelt
Starting with AIX 7.1 the http proxy is no longer an environment variable. Instead, you configure the proxy via the electronic service agent.
As you noted, the fastpath to that is "
smitty srv_conn". I did not realize that was the fast path
at me.
Yeah, I had just noticed that in the man page for suma. Unfortunately configuring the http proxy successfully still hasn't yielded the results I need as IBM is complaining that the serial does not have any software entitlement, which is funny, because I just checked on Fix Central and it does. Fun stuff!
7 More Discussions You Might Find Interesting
1. IP Networking
Does any one know how to block HTTP Tunnel in squid proxy server.
Pls reply (1 Reply)
Discussion started by: vishwanathhcl
1 Replies
2. Shell Programming and Scripting
Hi there
I am currently trying to access an http site using the wget utility from a solaris box. I am going through proxies to do this and we have two types of proxies.
For the first one, which is a netcache proxy, I am able to use the wget command to export the proxy information
export... (2 Replies)
Discussion started by: memonks
2 Replies
3. Solaris
Hi ,
I have installed solaris 10 on x 86 architecture. Now i want to configure this system as Proxy Server. I am new to the solaris. Please help me how can i configure this. Which packages or patches are needed ? or Which files have to be modify ?
Please help me to resolve.
Thanks and... (0 Replies)
Discussion started by: raviraj001
0 Replies
4. Red Hat
Hi there.. :D
I"m new in Linux. Trying to install squirrelmail-imap_proxy-1.2.7 on Red Hat WS 4. Errors from ./configure as shown below:
# ./configure
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking... (5 Replies)
Discussion started by: che.din
5 Replies
5. Programming
I am having problems receiving data from a remote server. It seems that I can send an HTTP request to any host such as http://www.google.com, but I can't get a reply.
I'm sending the host a HTTP 1.0 request that is formatted as such:
GET / HTTP/1.0
Host: http://www.google.com
Connection:... (0 Replies)
Discussion started by: shubham92
0 Replies
6. Shell Programming and Scripting
Simple Http Proxy Server Checker Script with curl
mirror proxies-scripts/proxc at master * Anoncheg1/proxies-scripts * GitHub
output in terminal
HTTP, HTTP Connect (HTTPS not supported)
command line:
proxc filename
where filename is file like
119.110.69.185:8080
119.235.16.41:8080... (4 Replies)
Discussion started by: 654321
4 Replies
7. Web Development
I am having a hard time with this one. We have a websocket server listening on port 80 at myserver.com/wsDemo?ID=12. We need to test a client program by connecting it to this server through a proxy. I am trying nginx 1.2.7 as the proxy on port 8080, running on proxy-server. We want the client to... (1 Reply)
Discussion started by: glev2005
1 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)