02-07-2011
X11 forwarding does not work after networking change
Hi all
I'm having an issue with X11 Forwarding
I have a VM set up on my computer which I usually "ssh -X" to over a home network (192.168.1.*).
Client 192.168.1.100
Server 192.168.1.103
This worked perfectly fine for X11 forwarding.
However I am not at home now (and have no access to my network) and need to add a host only network interface card to the VM so as that I can connect to it from the host machine.
Client 192.168.56.1
Server 192.168.56.103
I am able to SSH to the server fine and can run commands in the terminal etc.
But X11 forwarding is disabled when I use the host only network for some reason?
Any Ideas?
G.
10 More Discussions You Might Find Interesting
1. OS X (Apple)
Hi,
I have issues with running graphical interfaces on my computer being remotely logged into a network via the -X option of ssh. My .cshrc shows DISPLAY=hostname:0 and I think there should be a different number instead of the 0. I changed the ssh_config file already to 'X11 forwarding yes', which... (0 Replies)
Discussion started by: ginese
0 Replies
2. Debian
I have 2 Debian boxes.
In my ssh.com client and my putty client, I have X11 fowarding turned
on for both boxes.
When I connect one, I can xterm with no problem back to my pc.
On the other, I keep getting:
xterm Xt error: Can't open display:
xterm: DISPLAY is not set
On both... (3 Replies)
Discussion started by: natter
3 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I am using Putty, enabled SSH X11 forwarding and entered the X11 display location as "localhost:0". However I encountered the following error:
------------------------------------
# xclock &
2941
# X connection to localhost:10.0 broken (explicit kill or server shutdown).
+ Exit 1... (4 Replies)
Discussion started by: panggou
4 Replies
4. Red Hat
X11 forwarding problem between 2 RHEL4 machines with SSH
Already configured the following on both machines under /etc/ssh
Under sshd_config:
UsePAM no
AllowTcpForwarding yes
Under ssh_config:
ForwardAgent yes
ForwardX11 yes
ForwardX11Trusted yes
-----------------------------
Using... (1 Reply)
Discussion started by: panggou
1 Replies
5. HP-UX
Hi,
We've been facing a strange issue. Clients use X11 forwarding via SSH on HP server and sometimes the same DISPLAY is assigned to two (maybe more) sessions. As a result, some users can't open their applications, and some have their windows redirected to somebody else.
It looks as if sshd... (1 Reply)
Discussion started by: piooooter
1 Replies
6. UNIX for Dummies Questions & Answers
Hello. I installed a Debian box, and its installed remotely. I need to boot up iceweasel from there to do a quick test.
I log on using:
ssh root@<IP> -X
I have modified the /etc/ssh/sshd_config file, and added the X11Forwarding yes flag
And yet I still get:
Error: cannot open... (10 Replies)
Discussion started by: dynelight
10 Replies
7. Red Hat
Is it possible to launch an X11 application and have it use an X11 server on the other side of a bastion host? Specifically, here's my setup:
my laptop ------------- bastion -------------- remote host
I have putty installed on my laptop. The bastion is rhel 6.5 and the remote host is... (1 Reply)
Discussion started by: tsreyb
1 Replies
8. IP Networking
I would like to disable X11 session forcefully. I have tried the following things:
1. Setting appropriate DISPLAY variable in the /etc/environment file to be "0.0"
2. I have tried setting the sshd_config parameter X11Forwarding to be "no"
This session communication is happening by exchanging... (2 Replies)
Discussion started by: vaibhavvsk
2 Replies
9. UNIX for Beginners Questions & Answers
Unable to get X11 activated on my login even after Unix admin has enabled it (2 Replies)
Discussion started by: tomsayer1977
2 Replies
10. Red Hat
hi,
I'm trying to run a bash script that starts GUI. Though it says application started when I run this bash script doesn't show up any GUI. Here is what I've tried so far and please let me know if I'm missing something with the X11 set up here.
cat /etc/redhat-release
Red Hat Enterprise... (8 Replies)
Discussion started by: fop4658
8 Replies
LEARN ABOUT FREEBSD
if_gre
GRE(4) BSD Kernel Interfaces Manual GRE(4)
NAME
gre -- encapsulating network device
SYNOPSIS
To compile the driver into the kernel, place the following line in the kernel configuration file:
device gre
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
if_gre_load="YES"
DESCRIPTION
The gre network interface pseudo device encapsulates datagrams into IP. These encapsulated datagrams are routed to a destination host, where
they are decapsulated and further routed to their final destination. The ``tunnel'' appears to the inner datagrams as one hop.
gre interfaces are dynamically created and destroyed with the ifconfig(8) create and destroy subcommands.
This driver corresponds to RFC 2784. Encapsulated datagrams are prepended an outer datagram and a GRE header. The GRE header specifies the
type of the encapsulated datagram and thus allows for tunneling other protocols than IP. GRE mode is also the default tunnel mode on Cisco
routers. gre also supports Cisco WCCP protocol, both version 1 and version 2.
The gre interfaces support a number of additional parameters to the ifconfig(8):
grekey Set the GRE key used for outgoing packets. A value of 0 disables the key option.
enable_csum Enables checksum calculation for outgoing packets.
enable_seq Enables use of sequence number field in the GRE header for outgoing packets.
EXAMPLES
192.168.1.* --- Router A -------tunnel-------- Router B --- 192.168.2.*
/
/
+------ the Internet ------+
Assuming router A has the (external) IP address A and the internal address 192.168.1.1, while router B has external address B and internal
address 192.168.2.1, the following commands will configure the tunnel:
On router A:
ifconfig greN create
ifconfig greN inet 192.168.1.1 192.168.2.1
ifconfig greN inet tunnel A B
route add -net 192.168.2 -netmask 255.255.255.0 192.168.2.1
On router B:
ifconfig greN create
ifconfig greN inet 192.168.2.1 192.168.1.1
ifconfig greN inet tunnel B A
route add -net 192.168.1 -netmask 255.255.255.0 192.168.1.1
NOTES
The MTU of gre interfaces is set to 1476 by default, to match the value used by Cisco routers. This may not be an optimal value, depending
on the link between the two tunnel endpoints. It can be adjusted via ifconfig(8).
For correct operation, the gre device needs a route to the decapsulating host that does not run over the tunnel, as this would be a loop.
The kernel must be set to forward datagrams by setting the net.inet.ip.forwarding sysctl(8) variable to non-zero.
SEE ALSO
gif(4), inet(4), ip(4), me(4), netintro(4), protocols(5), ifconfig(8), sysctl(8)
A description of GRE encapsulation can be found in RFC 2784 and RFC 2890.
AUTHORS
Andrey V. Elsukov <ae@FreeBSD.org>
Heiko W.Rupp <hwr@pilhuhn.de>
BUGS
The current implementation uses the key only for outgoing packets. Incoming packets with a different key or without a key will be treated as
if they would belong to this interface.
The sequence number field also used only for outgoing packets.
BSD
November 7, 2014 BSD