10-06-2009
Quote:
As I recall, if there are routers in between, they must also be configured property for X to work across a network.
"Routers" in a closer sense (that is: Layer-3-devices) will not have to be configured for this at all, because X uses simple TCP connections (to port 6000, as mentioned) and routers will almost always forward TCP packets.
If the router in question has some gateway/firewall (which is a Layer-4-device) functionality, then what garethr has said applies. If you want to avoid tunneling then, yes, you would have to configure the router accordingly.
bakunin
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
i have a box here that can only be accessed with telnet. now, i was wondering if anyone know of a way of which i can run a command on that box remotely. (2 Replies)
Discussion started by: Terrible
2 Replies
2. Shell Programming and Scripting
now, i have a program that i would very much prefer to run remotely as i hate having to log into the box it is on.
the problem is, every command i have tried to run this remotely doesn't work.
the commands tries to kick off the program on the remote box but then hangs.
like take for... (3 Replies)
Discussion started by: Terrible
3 Replies
3. HP-UX
hi to all,
I am installed mozilla on hp-ux machine.
That was after installing the software, i just do, the gunzip to that depot file, then untar it.
after what i have to do.
b'coz i am new to hp-ux.
i don't know which script i have to run.
thanks & regards,
Balaraju. (3 Replies)
Discussion started by: balarajum
3 Replies
4. Shell Programming and Scripting
If I run this
# ssh remote-server 'du -sk /usr/platform/`uname -i`/'
174 /usr/platform/SUNW,Sun-Fire-V245
I get my output just fine,
However, if i try to do the same but populate a local variable within my script called for example 'result'
#!/bin/ksh
result=`ssh remote-server... (3 Replies)
Discussion started by: hcclnoodles
3 Replies
5. Solaris
Hi
Can i ask?
I had multiple solaris workstation running and some local users using it. Is it possible to bind to the local user terminal or console he's using as if like the user well type and I can see it and what my typing in the local user see it also.
Is it possible..
Thanks. (3 Replies)
Discussion started by: jao_madn
3 Replies
6. Shell Programming and Scripting
When i use ssh command to execute local script on remote server , I am unable to do it.
Please let me know how this can be done in ksh
req=abc
dte=ghd
ssh username@hostname "$req $dte" < run_script.sh (2 Replies)
Discussion started by: lalitpct
2 Replies
7. Shell Programming and Scripting
facing issue with then error while running a local script aginst a remote server. i facing the same issue in multiple scripts. So what i am missing here or what is needed.
#!/bin/ksh
echo "enter the filename"
read file
if
then
echo "file exists"
else
echo "file does not exists"
fi
... (0 Replies)
Discussion started by: NarayanaPrakash
0 Replies
8. Shell Programming and Scripting
Hello,
Please, what is the difference between running a script remotely:
ssh -t root@$machine -x "sshpass -p 'ubuntu' ssh -t ubuntu@$address -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/nul -x './c-launch.sh'"
and running a script directly on the host:
... (1 Reply)
Discussion started by: chercheur111
1 Replies
9. Shell Programming and Scripting
Hi all.
I need a bash script to run a function remotely. I think it should be similar to the following but can't figure out the exact syntax.
Here is the script:
#!/bin/bash
function nu ()
{
for var in {0..5}; do printf "$var, "; done; echo
}
ssh host "$(typeset -f); nu"
... (9 Replies)
Discussion started by: ziguy
9 Replies
10. UNIX for Beginners Questions & Answers
Dear Experts,
I have found this script on internet that can be used to execute local script remotely
#!/bin/bash
# runremote.sh
# usage: runremote.sh localscript remoteuser remotehost arg1 arg2 ...
realscript=$1
user=$2
host=$3
shift 3
# escape the arguments
declare -a args
... (4 Replies)
Discussion started by: mukulverma2408
4 Replies
FAITH(4) BSD Kernel Interfaces Manual FAITH(4)
NAME
faith -- IPv6-to-IPv4 TCP relay capturing interface
SYNOPSIS
device faith
DESCRIPTION
The faith interface captures IPv6 TCP traffic, for implementing userland IPv6-to-IPv4 TCP relay like faithd(8).
Each faith interface is created at runtime using interface cloning. This is most easily done with the ifconfig(8) create command or using
the cloned_interfaces variable in rc.conf(5).
Special action will be taken when IPv6 TCP traffic is seen on a router, and the routing table suggests to route it to the faith interface.
In this case, the packet will be accepted by the router, regardless of the list of IPv6 interface addresses assigned to the router. The
packet will be captured by an IPv6 TCP socket, if it has the IN6P_FAITH flag turned on and matching address/port pairs. As a result, faith
will let you capture IPv6 TCP traffic to some specific destination addresses. Userland programs, such as faithd(8) can use this behavior to
relay IPv6 TCP traffic to IPv4 TCP traffic. The program can accept some specific IPv6 TCP traffic, perform getsockname(2) to get the IPv6
destination address specified by the client, and perform application-specific address mapping to relay IPv6 TCP to IPv4 TCP.
The IN6P_FAITH flag on a IPv6 TCP socket can be set by using setsockopt(2), with level IPPROTO_IPV6 and optname IPv6_FAITH.
To handle error reports by ICMPv6, some ICMPv6 packets routed to an faith interface will be delivered to IPv6 TCP, as well.
To understand how faith can be used, take a look at the source code of faithd(8).
As the faith interface implements potentially dangerous operations, great care must be taken when configuring it. To avoid possible misuse,
the sysctl(8) variable net.inet6.ip6.keepfaith must be set to 1 prior to using the interface. When net.inet6.ip6.keepfaith is 0, no packets
will be captured by the faith interface.
The faith interface is intended to be used on routers, not on hosts.
SEE ALSO
inet(4), inet6(4), faithd(8)
Jun-ichiro itojun Hagino and Kazu Yamamoto, An IPv6-to-IPv4 transport relay translator, RFC3142.
HISTORY
The FAITH IPv6-to-IPv4 TCP relay translator first appeared in the WIDE hydrangea IPv6 stack.
BSD
April 10, 1999 BSD