Sponsored Content
Operating Systems Linux Red Hat Help with exporting DISPLAY from Linux to Windows XP Post 302489573 by Corona688 on Thursday 20th of January 2011 06:13:53 PM
Old 01-20-2011
192.168.99.73 is also an internal IP address as stated above. You didn't need to obscure it, it started obscure, nothing except things on your local network know what it is. So, for servers that aren't, you need to

1) have things connect to your external ip address, i.e. your router's WAN address
2) have your router forward the appropriate port to the internal address 192.168.99.73

You may also want to make sure the router's set to always give you 192.168.99.73, otherwise, the port forwarding might break every time you get a new address.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

exporting display

how do I export my display from my unix box to my pc basically what is the syntax for export DISPLAY (2 Replies)
Discussion started by: csaunders
2 Replies

2. UNIX for Advanced & Expert Users

How to open display from windows to solaris?

How can I telnet from my windows XP machine to my Ultra 60 and run firefox? I am unable to open the display using /usr/openwin/bin/xhost like I do from one Sun machine to another? Thanks (2 Replies)
Discussion started by: ridgeback00
2 Replies

3. Solaris

Exporting X display question

I have a sun box i can connect to using exceed in broadcast or query mode. I have been using passive mode to call up just a few apps, xcalc for example. How do i get the solaris 9 user login screen using passive mode? is it dtlogin or something that im should run frmo the shell? (0 Replies)
Discussion started by: BG_JrAdmin
0 Replies

4. UNIX for Dummies Questions & Answers

Exporting Files from Unix to a Windows Platform

I was able to convert my csv file in Unix to xls. I would like to export the converted xls file to a windows environment. I have to manually connect using the following below: ftp: 192.x.x.x -> username/pass -> cd -> mget *.xls and then confirm. Could I automate this process into a shell... (4 Replies)
Discussion started by: ravzter
4 Replies

5. Linux

What's better for running Windows software in Linux, Wine or Windows VMware?

What are the differences, advantages, and disadvantages? (1 Reply)
Discussion started by: Advice Pro
1 Replies

6. UNIX for Advanced & Expert Users

X Windows display

Hello Folks, Have X-Win 32 installed on my desktop. Earlier when it used to be XP, ran the following commands on unix system: export DISPLAY=<desktop ip>:0.0 xterm Above used to work like charm Now it got upgraded to Windows 7 Setting the display & triggering xterm doesn't work. It... (8 Replies)
Discussion started by: vibhor_agarwali
8 Replies

7. Solaris

Exporting display to windows machine

hello all, I have been googling alot about my problem and finally thought to post a question. server: SunOS 5.1 64bit pn Sun Netra 240 i need to run an application which shows a gui tool but i believe SunOS cant show the GUI so i need to export the display to my system which is running... (3 Replies)
Discussion started by: wonderwall
3 Replies

8. Solaris

Problem exporting NFS filesysytem with root permissions to Linux

Hi, I have a Solaris 10 server and I want to export a filesystem to a linux client and give the client's root user root priviliges on the filesystem. The client is an ubuntu 14.04 LTS server. the dfstab on the server looks lik this: /usr/sbin/share -F nfs -o ... (1 Reply)
Discussion started by: nvanvliet
1 Replies

9. UNIX for Beginners Questions & Answers

Seen Windows pc, having all the features of Linux, could exe, read and edit save like windows

Hi, totally new to linux base using windows when started learning and using computers. but i remember that one pc was there , look alike windows desktop, but could not do the task as windows just click and open and view edit etc. But, you could do a little differently even saving in and opening... (8 Replies)
Discussion started by: jraju
8 Replies
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
All times are GMT -4. The time now is 02:10 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy