I have several server machines in my home network. I install tmux on one of them and connecting to it from my laptop. I open multiple panes on 1 tmux window, and anytime that I run some thing too 'heavy' like running apt-get install multiple-packages -y on all servers, the ssh from my laptop to the server is disconnected, and I cannot ssh into it. After some time, the packages were installed, and I can connect to the server with ssh again.
So my questions are:
Is this normal that ssh keeps disconnecting like this? I'm suspecting that this is a network congestion problem. Or it is the tmux receiving all outputs from all server, which kicks me out of ssh?.Or ssh is like second class citizen, so when server needs more bandwidth, it'll terminate ssh for more essential activities? How can I troubleshoot this, and know where this problem comes from? network's not sufficient, or it's server problem. Thanks
I am trying to connect my Android devices present on a different network than my Appium Server but having no success.
P.S. The adb connects with the device over the same network and over USB but not to devices on a different network.
First of all, you need to get the IP address of the remote machine, your device is connected to. Assuming adb default port is 5555 and it is exposed to another machine with Appium server:
On machine with Appium server you run adb connect <ip_address>:5555, then adb devices should list remote device.
To have a robust solution you can have a look at OSS libraries like OpenSTF
I have some device in MIPS architecture, on this device unfortunately wasn't instal any server ssh, but telnet daemon is present. I try connect to this device in goal remote debbuging but I do not can connect. Also If I try test connect.
So it is possible to remote debugging in Qt trought Telnet ? Whether this function is only reserved for SSH server ?
I have NetBSD-4.0.1-x68k installed as a guest virtual machine on Windows (using the XM6i 68030 emulator for windows 7). I am trying to setup a host only connection on the NetBSD guest. However, I can't ping the guest from the host unless I run:
tcpdump -i ne0 #executed on guest
ping 192.168.2.17 #executed on host
ping 192.168.2.1 #executed on guest
Right after I run these commands in that order I can continue to ping successfully ...but not forever, after a certain point I am unable to ping again from neither the host nor guest. Also, when I restart the system, I still can only do pings unless I do the above process beforehand, and again, not forever.
Is there anyway I can setup this host only connection without using tcpdump as a short term temporary handicap?
I turns out on the latest version of XM6i. In order to get a complete 68030 networking emulation you need to use tcpdump command on boot. So there is no way around this.
I have a question about Checking small network by opendaylight
I am not really sure why I can't accress Opendaylight menu which I created from mininet
I am using windows 7 and VMWare player to run mininet and opendaylight(on Ubuntu).
First, i run Ubuntu to run Opendaylight ( I checked that 120.0.0.1:8080 was working)
Second, I run mininet to get IP address.( i will say "192.168.139.128")
Third, based on IP address , it run two putty to run wireshark and building small network
I used sudo mn --mac --controller=remote, ip=192.168.139.128, port=6633.
It successfully build small network. Because i can check all the node infor by command "nodes" and "dump"
However, when I go back to Ubuntu VM and access Opendaylight by 192.168.139.128:8080 (it is given IP from mininet)
I am sure really sure why this happen. Is there any possible reasons ?
Just in case, if anyone is facing the same issue, change network adapter settings in VMWare to use bridge mode.
From the official page
Important troubleshooting - if you are running VirtualBox on the same
host/desktop where the controller is running, and trying to start the
virtual network on Mininet VM produces this error: "Unable to contact
the remote controller at ...", then the following resolves the
problem:
In VirtualBox, go to File-Preferences-Network and make sure you have at least one interface defined as Host-Only. Lets say its name is
vboxnet0
In VirtualBox - Mininet Vm - Settings - Network, check that the adapter is of type Host only , and is connected to the interface from
item 1 (vboxnet0)
On your host where controller and VirtualBox run, do "ifconfig" command to display all network interfaces on the machine.
Search for the interface as in item 1 (vboxnet0 in our example) Take
the ip address specified there (most probably 192.168.56.1 - default),
and that is the correct remote controller ip address to use when
starting a virtual network in mininet vm as stated in the example
above (--controller=remote,ip=192.168.56.1) .
If you are still not able to connect, you might want to consider temporarily disabling firewall on the host running the controller (on
Linux, for example, iptables -F will do the job)
Sometimes, the way you start the mininet is a problem, it does not give error, but does not connect to the remote server. Here is a wrong
example:
sudo mn --topo=tree,3 --mac --switch=ovsk --controller=remote,
ip=192.168.16.10
Here is the correct example:
sudo mn --topo=tree,3 --mac --switch=ovsk
--controller=remote,ip=192.168.16.10
The difference is the "SPACE" between "remote," and "ip".
Also check if you are VMWare player, at IP use this command
sudo mn --mac --controller=remote,--ip=192.168.139.128 --topo tree,5
and refresh your OpenDay Light Controller.
The easiest way is to install Gnome on your Mininet/ODL virtual machine.
I am using the latest (Helium) ODL release so the GUI of ODL is at http://localhost:8181/dlux/indexh.html
on Helium, ODL run inside your distribution folder with ./bin/karaf command (also install required modules inside karaf with feature:install
Attached is my screenshot: https://pbs.twimg.com/media/B8ZgSA6CMAAzuSf.jpg:large
Start the Opendaylight and install the odl-dlux-core plugin. After that the OpenDaylight UI can be accessed through browser on port 8181. So try http://localhost:8181/index.html and you login using username password admin/admin. You should see your topology show up on the UI.