I've been playing around with Xming, and trying to redirect X11 from the Untangle server to my desktop. My ultimate goal is to get the kiosk X console to render to my windows station.
So step one is to get Xming and install it.
You have to download it from the sourceforge.net site, as they've password protected access off the project's primary web server.
After that you just need putty, and an open SSH port to your Untangle server.
Now to configure the X server, run XLaunch.
1.) Select the One Window without titlebar option, leave display number at 0, click next
-Note: I actually prefer the One Window option, however I've had intermittent issues with the window eating 100% of the desktop space even when I've forced it into a smaller window.
2.) Select Start no Client, click next
3.) In the additional Parameters for Xming input this "-screen 0 1024x768"
-Note: Remember the screen number from step one? That's the zero, the rest can be whatever size you want your window to be. Click next, then finished.
At this point you should have a 1024x768 window with the X grey hash background on it. If you need to move it to a new location, right click on the Xming :0.0 item in the task tray, select move, and tap one of the cursor keys on your keyboard. At this point you can move the window around and choose a final destination with a single click.
Now, fire up putty.
In the connection category, expand SSH and select the X11 tree item. Tick the box that says Enable X11 Forwarding, and fill 127.0.0.1 into the box. Go back up to the Session Category, fill in the IP address of your Untangle server and log in normally.
Verify your X is redirected with this command
It should report something like localhost:10.0
You can test your graphical window by running this command.
You should see the cursor in your putty session go inactive, and a clock appear in the graphical window.
A useful command at this point is...
Having a root enabled copy of wireshark running on your Untangle server, but rendering on your desktop. Handy to say the least.
The part I'm having trouble with is kiosk's X environment. I can run the startxfce4 at the root prompt and get a generic xfce4 session to render. However, if I su - kiosk and run the command there I get an error.
a quick echo $DISPLAY after running su shows that the display variable is incorrect. That's easy enough to fix with a quick change to the environment variable. export DISPLAY=localhost:10.0
Now we get an xauth error when we try and run xclock.
That link contains details on how to import the magic cookie from the root account to the kiosk account. After that is done, I can run xclock, wireshark, and many other X applications as kiosk. However, startxfce4 simply doesn't work. No real errors, not beyond what it spews when run as root, but it doesn't render either.
Seems I need to bone up on my X some more. Being able to redirect the X console would have many positive applications. Not the least of which would be clean screen shots of the console, and potentially a way to bundle xming and putty together with some basic configuration scripts to act as a remote administration package. Freeing the Untangle server from needing to render a graphical configuration screen at all.
Anyone else have some experience with X have any insite as to how to get that kiosk X environment to render? It would be trivial to get it working if I could log into the kiosk account directly. But, I'm loath to forcibly reset the password on that account so I can login with it... I have no idea what that would do to an Untangle installation. The last thing we need is the local console to stop working because we reset a password.
- NG Firewall
- Solutions by Industry
- Solutions by Issue