- Mobatek Blog
- How to keep X11 display after su or sudo
- RHEL Can't open display - Red Hat Customer Portal
- Recent Posts
You may wish to invoke debug logging on your ssh client to see why X11 forwarding isn't working. On OS X and Linux, you can use. By default ssh -X times out after a while - you may prefer ssh -Y for that reason, although it is less secure. There is a wealth of information on the internet explaining how to set up X11 forwarding correctly on any platform.
This is easily found using Google or the search engine of your choice. As an alternative to X11, you could also use VNC, but that is probably about as complicated as X11 and is left as an exercise to the reader. If this seems too complicated, you can simply run X11 in the VM console window as described below!
- multi tab text editor mac?
- adobe creative suite for mac system requirements?
- convert cue files to mp3 mac.
First, log in to the VM in its console window i. Reboot the VM, log in and run startx , and you should be able to resize the VM console window and desktop. This allows you to run programs like wireshark or firefox. You might want to su to another user e. The CLI xterm command actually sets up an X11 tunnel which you can continue to use, e. You can also use the x command to set up the X11 tunnel and optionally run an X program :. Using a graphical browser requires that you get X11 traffic out of your Mininet host namespace and into the environment where you actually have an X display.
Say the X display is the host environment with IP address of In short, run sshd inside Mininet's h1. Then SSH from the host environment If you are asking this question, it means you haven't yet consulted the Documentation. If you are incredibly lazy, please at least look at the Sample Workflow. Note that this procedure will simply uninstall Mininet itself - it will not remove Open vSwitch, the Stanford reference switch or controller, or any other related software which may be installed on your system.
I tested this and got the following error:. Your bit guest will fail to detect a bit CPU and will not be able to boot. Usually the problem is not that you don't have a bit CPU you probably do if you have anything as good as, say an intel Core 2 Duo from It is much more likely that:. You are trying to run two virtual machine monitors - Hyper-V and VirtualBox - at the same time, and this does not work with bit guest OSes.
This has been tested and verified on Windows 8. Make sure that the VM is actually booting without any errors of any kind. Alternately, you can use Hyper-V to run the VM as noted above! Or you can try the bit image, which seems to work fine on most configurations. If the VM is booting but boots to a blank screen, then you probably just need to either wake up the Linux console or switch to another virtual console, as follows:.
First, select the VM console window. Second, press a key like A or return a few times - see if any text appears.
Unfortunately, when VirtualBox was updated to 4. Some other VMMs may also not be able to import it directly, but there is an easy workaround:. If you extract the. Configure, boot, and enjoy! In VirtualBox, you need two different network interfaces set up if you want to both access the internet from your VM and access your VM from the host.http://www.inboundsportmarketing.com/components
One of them should be a NAT interface to get to the internet , and the other should be a host-only interface to get to, well, the host. AppArmor's configuration for lxc seems to forbid recursive private mounts, which Mininet wants. In Ubuntu Mininet should work out of the box in a privileged docker container, but AppArmor breaks tcpdump in docker containers. The workaround is either:. You are asking the right question!! We also provide Python DocStrings for every Mininet class and method, and you can view them using from within Python.
You can't ping google. This is usually a good thing! Usually Mininet networks use a non-routable IP address range like In order for DNS to work in the Mininet hosts, you should not be using dnsmasq for local caching. You can change this range using the --ipbase option, for example --ipbase The illustrious Glen Gibb provided a script to do it back in on mininet-discuss.
There was also a follow-up message from Leo Alterman. You may need to change it if this is not the case!
If this script does not work for you, please make an effort to debug and fix the problem, and then update this FAQ entry. The Ubuntu For example:. Mininet currently includes support for the user space reference implementations, Open vSwitch in kernel and user space modes, and the Indigo Virtual Switch. Mininet used to support the OpenFlow 0. The command line options are --switch user and --switch ovsk for the user reference and Open vSwitch kernel switches, respectively.
You can also install the CPqD ofsoftswitch13 switch using install. See below for an example of using it. Usually the switch and controller will negotiate the highest version of OpenFlow that they both support. If you wish to use OpenFlow 1. Additionally, the CpQD switch may be installed using install. As a result, many Ethernet bridges implement variants of a Spanning Tree Protocol STP , which simply deactivates links in the network to remove loops. Of course, this also throws away network bandwidth that you could otherwise be using, and creates a bottleneck at the root of the tree!
As a result, they will not work with a network that has loops in it. In general, if you want to use a network with loops in it, you need to be absolutely sure that your controller supports such a network. As mentioned above, ovs-controller , controller and pyswitch do not by default. A simple test is to use RemoteController pointed at your controller and use the torus topology, e. If you just want to get your network "working", you can run STP.
How to keep X11 display after su or sudo
In Mininet 2. You will need to wait for STP to converge. You can also call net. Note that if you are running a remote controller rather than a local OVS or Linux bridge as suggested here , waitConnected will only wait for the switches to connect to your controller. If you are using a remote controller, you should check the controller console or logs for any updates.
As noted above, running spanning tree removes any performance improvement from multipath networks, although it can still provide redundancy for reliability if you deactivate a link, STP can compute a new spanning tree that uses a different link and restores connectivity. If this sounds terrible, it's because it is - one of the advantages of using a multipath-capable OpenFlow controller is that you can potentially escape the tyranny of Spanning Tree! But, you will still probably have to do some work and actually understand what you are doing.
You can further troubleshoot Mininet startup by running mn -v debug and carefully looking at the output for error messages. The MAC addresses reported by Linux for the switch data ports are meaningless. The switch is controlled by OpenFlow, so you should use OpenFlow to ensure that any packets destined "for the switch" are properly routed. If you attempt to use the Linux IP stack instead, it really won't work unless you are using the Linux kernel for routing which you aren't - you're using an OpenFlow switch!
You should never attempt to use ifconfig or ip addr or other utilities to assign an IP address to a switch data port that is connected to a host or another switch veth interfaces are not bridges! Usually you will want your controller to handle packets such as ARP and ICMP which are sent to and from "the switch," and you will want IP packets which are sent to to be handled by appropriate flow table entries. You can pick any "MAC" address you like for the switch.
For Mininet 2. Unfortunately ovs-controller only supports up to 16 switches. If you want to use more than 16 switches, you should use a controller that supports more than 16 switches, for example:. Make sure you've installed the Mininet version of the OpenFlow reference controller, which is easily done using:. You can also create a custom controller class or use --controller external:IP and use any custom or off-the-shelf controller that you like.
RHEL Can't open display - Red Hat Customer Portal
If you are using the default controller or any controller which implements an Ethernet bridge aka learning switch , be sure that your network does not have loops in it or that you have activated spanning tree. It's trivial to control Mininet hosts from the CLI or from within a Python script running locally, but what if you want some other process or even another computer on your LAN to be able to control your Mininet network remotely? Well, there are lots of ways to do this.
One idea is that anything you can do in Python, you can do in Mininet, and it's often very easy to do so. For example, there are all sorts of frameworks available for any kind of messaging you can imagine. See below for a REST example - it's just a few lines of code. For example if my Mininet server is ubuntu1 , I can run ifconfig on host h1 using. Another way is to actually connect your Mininet network to your LAN and to run sshd on your Mininet hosts. This is left as an exercise for the reader, but you may want to look at the hwintf.
Basically anything you can do in Python you can do in Mininet, and it's often very easy to do so. You can hook Python code up to node. Note however that if you are running locally it's much easier to control Mininet directly from within a Python script or using the CLI. For example, using the Bottle framework, you could do something like:. Note that host. But it's quite convenient, isn't it? In a real example you would probably want a method to shut down both the REST server and the Mininet network in a graceful manner rather than using control-C and mn -c.