Sponsored Content
Top Forums UNIX for Advanced & Expert Users Encrypt traffic between Solaris 8 hosts Post 65475 by reborg on Saturday 5th of March 2005 01:02:54 PM
Old 03-05-2005
Also you could consider using a secure tunnel between the machines for this and routing this fraffic through the tunnel.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

remote hosts access problem on solaris

hey guys, i am on a box named pluto and i need to be able to log into another box named genesis. i need to be able to ssh into genesis as root and not get asked for the password. what file do i need to edit on genesis to make this happen? i searched for the .rhosts file it doesn't seem to exist.... (1 Reply)
Discussion started by: Terrible
1 Replies

2. Solaris

Multiple Hosts on Solaris CDE window

I forgot how to configure multiple host servers on the my CDE windows in Solaris. I'll appreciate any help Thanks, Remi (2 Replies)
Discussion started by: Remi
2 Replies

3. UNIX for Dummies Questions & Answers

Traffic count in Solaris

Hello, Iam looking for a solution to keep track on my traffic usuage, monthly usuage. Anybody could recommend anything? /empty (2 Replies)
Discussion started by: empty
2 Replies

4. Red Hat

SSH broke and network traffic / talking issue between hosts and server

Ok Time warner cable / voip modem feeding Cisco PIX 501 Wan port from PIX 501 LAN port to WAN port on Linksys wrt54GL wireless router. so -->Modem-->PIX 501-->WRT54GL-->Linux Server, wireless desktop, wireless laptop (2), Wireless MAC Pro, Wireless Apple TV, Wireless printer. my... (0 Replies)
Discussion started by: tedeansiii
0 Replies

5. Solaris

Solaris 10 encrypt command: can't use heredocs

I'm trying to use the Solaris 10 "encrypt" command in a script. I want to encrypt a file called "database", but not using a keyfile, instead using a keyphrase. Running this from the cli requests the user to input "Enter key:" which is fair enough but I want to run this from a script. I've tried... (1 Reply)
Discussion started by: fixit9660
1 Replies

6. Solaris

[Solaris 10] /etc/hosts.allow

Hi, I am trying to find a Solaris 10 alternative to the HPUX inetd.sec functionality. I want to grant access to one service for one IP address only. # grep fme2eall /etc/services fme2eall 35000/tcp # svcs -a | grep fme2eall online Mar_09 ... (2 Replies)
Discussion started by: ejdv
2 Replies

7. Solaris

/etc/hosts.allow on Solaris 10

I added some entries in the /etc/hosts.allow on a Solaris 10 system. Do I need to bounce inetd? I have read some accounts where any changes made to the /etc/hosts.allow will be taken in automatically. And other accounts where you need to run: svcadm refresh inetd My... (1 Reply)
Discussion started by: snoman1
1 Replies

8. Solaris

Solaris Question - How to find outgoing traffic on UDP ports

Hello All, I am trying find a command that would show me the stats of outgoing traffic on UPD ports on a Solaris 10 box. I would appreciate if anybody could help me out on this. Thank you much!!! Best Regards Sudharma. (7 Replies)
Discussion started by: sudharma
7 Replies

9. Solaris

HBA data traffic monitor in Solaris 10.

Hi All We have T4-4 Server with 2 HBA configured for SAN connectivity. We want to monitor Data traffice going through these HBA. On other AIX system we have that capability with nmon. Following screen shows nmon HBA monitoring can we achieve same in Solaris 10. ... (1 Reply)
Discussion started by: uxravi
1 Replies

10. Proxy Server

IPtable rules for DNS/http/https traffic for specific hosts only, not working.

Hi there, I have a VPS and am working on a little side project for myself and friend which is a DNS proxy. Everything was great till recently. My VPS IP has been detected by some botnet or something, and I believe SMURF attacks are occuring. The VPS provider keeps shutting down my VPS... (3 Replies)
Discussion started by: phi0x
3 Replies
IODINE-CLIENT-START(8)					  System Administration Utilities				    IODINE-CLIENT-START(8)

NAME
iodine-client-start - start an iodine IPv4-over-DNS tunnel SYNOPSIS
iodine-client-start [option] DESCRIPTION
'iodine-client-start' starts an iodine IP-over-DNS tunnel. -h, --help Print help and exit -v, --version Print version info and exit Invoking the program without options attempts to set up and configure an iodine IP-over-DNS tunnel using the configuration in the file /etc/default/iodine-client or by querying the user. It tries to figure out the right way to set things up by observing the network, and if all else fails by guessing. QUICK CONFIGURATION Put two lines in the file /etc/default/iodine-client subdomain=your.tunnel.sub.domain passwd=password_for_that_tunnel or invoke the script with those environment variables set: env subdomain=xxx passwd=xxx iodine-client-start If these are not set, the script will query the user for them. DETAILS The configuration file consists of lines which are either comments starting with '#', or settings of the form VAR="val". Valid VARs are: subdomain Sample value: your.tunnel.sub.domain (no default, must be set) passwd Sample value: password_for_that_tunnel (no default, must be set) testhost Hostname to ping when testing if network is working (default: slashdot.org) bounce_localnet Take the local network down and then up again before starting tunnel (default: false) test_ping_localnet Test if the local network is working by pinging the gateway (default: true) test_ping_tunnel Test if the iodine tunnel is working after it has been set up by pinging the host at the other end (default: true) test_ping_final Test if the tunnel is working after everything is ostensibly set up by trying to ping an external host (default: true) default_router IP address of router on the local network---should be found automatically, set this if that fails and the program guesses wrong. interface Interface to use (e.g., eth1, eth0, etc) for connection to DNS server used for the iodine tunnel---should be found automatically, set this if that fails and the program guesses wrong. mtu Set if tunnel MTU needs to be manually changed (lowered). Should not be necessary anymore, as recent versions of iodine negotiate an appropriate MTU during tunnel setup. But if that negotiation does not happen, or if you are using an older version of iodine, the default tunnel MTU is 1024, and if the local DNS server restricts to 512 byte packets you might need to use an MTU of 220. skip_raw_udp_mode Set "-r" option in iodine command line. With this option, iodine does not try to establish a direct UDP socket to the iodine server on port 53. (default: true). continue_on_error Set if the script should continue even if a command fails. Use to test script when running as non-root. Defaults to false if run- ning as root, true otherwise. iodine-client-start 1.0.4 June 2014 IODINE-CLIENT-START(8)
All times are GMT -4. The time now is 11:10 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy