xterm: Xt error: Can't open display: xterm: DISPLAY is not set

Did you logout and login after installing XQuartz? Or reboot?

Otherwise the DISPLAY environment variable will not be in your environment.

If XQuarts in stalled ocrrectly, then you should be able to see that DISPLAY has a value

echo $DISPLAY

/tmp/launch-5MOIEc/org.x:0

which will look similar (but not exactly) like the above.

Shja,

Did you try using, a '-Y' instead of '-X' so that the ssh command looks somthing like:

ssh -Y mininet@192.168.**.*"

Then after you've ssh'd into the remote system, what does 'echo $DISPLAY' return?

Nils

That means your DISPLAY variable is properly setup on take local Mac.

If you ssh -X or ssh -Y into a remote Unix/Linux system, then at that end your DISPLAY environment variable should look something like: localhost:10, which will indicate that the remote system is ready to send X11 display output over the ssh tunnel established by the -X or -Y option.

I didn't quite understand what you were saying but when i typed "ssh -Y ..." this is what happened:

mobile-172-16-103-167:~ mininet$ ssh -Y mininet@192.168.56.1

Password:

Last login: Sat May 18 20:25:50 2013 from 192.168.56.1

mobile-172-16-103-167:~ mininet$

ssh -X and ssh -Y do essentially the same thing. -Y is just less restrictive on X11 return traffic authority (basically it tells the local X11 display server that you trust the remote system sending X11 traffic to it).

Now what you are display seems strange. You prompt implies that your current system's IP address is 172.16.103.167 and you are ssh'ing to 192.168.56.1. You get a password prompt as expected, but then the "Last Login" messages says you are coming from 192.168.56.1, which is should be where you are coming, but that it the address you are trying to ssh to. And then to top it off, you command line prompt has not changed.

So I'm wondering if 192.168.56.1 is the same system you are currently using, but just a different account on that system?

Is this true?

Also your prompt implies you were logged into the 'mininet' account when you issued the ssh -Y command to login to the 'mininet' account on 192.168.56.1.

Or is it possible that you are loosing track of which system and account you are current remotely logged into?

OK, the IP address info makes sense if you are logging into the same system.

In another post (since blocked), you mentioned not having permissions to use the 'sudo' command. That tells me when you created the account, you did not make it and 'Admin', so the 'sudo' command was complaining.

If you have not already gone back to System Perferences -> Users & Groups and add 'Admin' to 'mininet', then you need to do that, then start over with new ssh into 'mininet'. At which point the 'sudo' command should work.

Note: when prompted for a password when working via a terminal/xterm command line session, you will not see any password characters displayed. You just have to take it on faith that the computer saw the password, and as soon as you type the return or enter key, the password you didn't see will be accepted.

I believe that you are expected to have installed VirtualBox and gotten the virtual machine running at this point. That VM, running on a virtual IP address, is what you should be connecting to. Are you in fact running VirtualBox and that download virtual machine image? As the tutorial suggests, you should ping that IP address to make sure it is working.

The idea is that you will ssh into the virtual machine and have it display windows in your Mac environment. From those windows (running from the virtual machine), you run the mininet program.