I'm using the networking module to control my network over ubuntu 16, with this wifi driver: https://github.com/morrownr/88x2bu-20210702
I configured static IP using the /etc/network/interfaces file.
The computer is installed on a moving robot so the link quality of the wifi is changing and can drop until a level that the robot loses its connection.
I've printed to file both the iwconfig and ifconfig commands, and I can see that when the robot loses connection and returns, it's still connected to an access point with high link quality, but it can't gain the IP again when checking the ifconfig.
It doesn't happen every time.
What can I check in order to investage it?
Related
I use the Blink shell on my iPad to connect to Jupyter on my Mac. The connection works perfectly while on the same network, but it either returns "Network is down" or "Connect timeout."
The app has all the permissions required and so does the Mac.
I set the Mac as a host in two ways: using the ip address shown in System Preferences and once from https://www.whatismyip.com/my-ip-information/.
Anyoke know how to make the connection work remotely?
Information is not clear, I'm assuming your Mac sits behind an Internet router (NAT).
You can either set up a port forward (e.g. 60022 -> $mac_ip_address:22) from your internet router to the Mac or put the Mac in DMZ (which is not recommended)
I have this strange problem that i haven't been able to figure out. Can anyone please suggest what to try:
I have a piece of software to control my camera from my computer. It's called "Control my Nikon". It has a built-in web server. The purpose is to be able to connect from a smartphone to use it as a remote control. You choose what port it should listen to and enable it. You get a simple interface with buttons. Exposing a photo, for example, triggers the URL 127.0.0.1:8090/?c=3. Very basic stuff.
On the computer it works perfectly, but from my phone, i just get a timeout. I figured i needed to open the port (8090) in my firewall and spent some time setting that up, but it still won't work. I am using my computer's IP address on the network: 192.168.1.214:8090, which should reach the same place as 127.0.0.1:8090 from the computer.
I then set up a Spring boot application to listen to the 8090 port and i was able to reach that from the phone just fine. This suggests that the firewall is not the issue. I can trigger the control my Nikon URL from within the Spring boot application too, by making a call to http://127.0.0.1:8090/?c=3. I can also reach pages served by Apache (192.168.1.214/testpage.html) on the computer from the phone without any problems.
What am i missing here?
The Nikon software is probably binding itself to the 127.0.0.1 network interface and not every network interface it finds.
The software doesn't appear to be designed for network control but just runs a web server so it can present a UI in HTML.
You would need to change the Nikon software so it listens on other ports (or configure port forwarding or a reverse proxy).
I am building a sample vagrant box to install Jenkins and push it to atlas cloud.Please find below the steps that I followed.
Vagrant init ubuntu/trusty64
and the normal command to initialize the vagrant machine.
vagrant up
After this if i type command to ssh into the machine
vagrant ssh
It gives me error saying please increase timeout and so.
The main question is how can I ssh into the newly created vagrant machine.
To understand this, I have to go through all the basics. Please find below my findings.
Not attached
In this mode, VirtualBox reports to the guest that a network card is present, but that there is no connection -- as if no
Ethernet cable was plugged into the card. This way it is possible to "pull" the virtual Ethernet cable and disrupt the connection, which can be useful to inform a guest operating system that no network connection is available and enforce a reconfiguration.
Network Address Translation (NAT)
If all you want is to browse the Web, download files and view e-mail inside the guest, then this
default mode should be sufficient for you, and you can safely skip the rest of this section. Please note that there are certain limitations when using Windows file sharing (see Section 6.3.3, “NAT limitations” for details).
NAT Network
The NAT network is a new NAT flavour introduced in VirtualBox latest versions.
Bridged networking
This is for more advanced networking needs such as network simulations and running servers
in a guest. When enabled, VirtualBox connects to one of your installed network cards and exchanges network packets directly, circumventing your host operating system's network stack.
Internal networking
This can be used to create a different kind of software-based network which is visible to selected virtual machines, but not to applications running on the host or to the outside world.
Host-only networking
This can be used to create a network containing the host and a set of virtual machines, without the need for the host's physical network interface. Instead, a virtual network interface (similar to a loopback interface) is created on the host, providing connectivity among virtual machines and the host.
Generic networking
Rarely used modes share the same generic network interface, by allowing the user to select a driver which can be included with VirtualBox or be distributed in an extension pack.
At the moment there are potentially two available sub-modes:
UDP Tunnel
This can be used to interconnect virtual machines running on different hosts directly, easily and transparently, over existing network infrastructure.
VDE (Virtual Distributed Ethernet) networking
This option can be used to connect to a Virtual Distributed Ethernet switch on a Linux or a FreeBSD host. At the moment this needs compiling VirtualBox from sources, as the Oracle packages do not include it.
Out of these, only NAT and Host-only network is important.So, to solve this issue, I modified the predefined Vagrant file with the following code.
jenkins.vm.provider "virtualbox" do |vb|
jenkins.vm.network "private_network",ip:'192.168.56.5',:adapter => 2
jenkins.vm.hostname = 'jenkins.ci'
vb.name = "Jenkins"
end
Here, I have created a private network with static Ip and also, I specified the adapters count to use 2. The Private adapter is Host-only adapter and 1st adapter which is default one is NAT.
How to enable Hyper-V to connect VPN for external internet access in Windows 8?
I'm trying to run Windows phone 8 app using emulator, and while see app in emulator it doesn't connect the VPN to access internet.
Please advice.
Thanks.
MSDN has a troubleshooting page for the Windows Phone 8 emulator. Perhaps you can find related info there. Something like this might help:
Cannot connect to Internet destinations
The Windows Phone 8 Emulator uses the HTTP proxy settings from the host computer. If you can’t access Internet resources from the emulator, check with your IT administrator to make sure that your proxy settings will work with the emulator.
If your network’s proxy servers are unavailable or malfunctioning, it might be possible to restore connectivity for the emulator by disabling automatic proxy detection on the host computer. However this only works in certain network configurations.
To disable automatic proxy detection on the host computer
On the host computer, open Internet Options from the Control Panel. The Internet Properties dialog box opens.
In the Internet Properties dialog box, click the Connections tab.
On the Connections page, click the LAN settings button. The Local Area Network (LAN) Settings dialog box opens.
In the Local Area Network (LAN) Settings dialog box, deselect all the check boxes. Click OK twice to close both dialog boxes.
Restart the emulator and retry the connection.
Also this MSDN blog-post can be helpful: Why can’t the Windows Phone Emulator go online?. Useful part of the article:
As you see, clicking the “>>” on the bar parallel to the Emulator will open a small window with 4 tabs. The last tab is for “Network”. To explain in simpler terms, there are two adapters here – one is for internal use by Emulator and other is for external network connectivity. Each adapter will have an IP address (IPv4) associated with itself. The one of our interest is under Adapter #2.
I have erased out the IPv4 address that is assigned to Adapter #2 (Yellow box), but you find that the IP assigned here starts with 169.254.x.x…., then Bingo! - we have figured out the problem. How?
The IP addresses starting with 169.254.x.x …. Are usually the self-assigned default addresses to a device and not really helpful to get the device to go online. This IP should either be a static IP or the one assigned by the DHCP server (if you have one in the environment) for the device to be able to connect to external networks.
Hope this helps.
I don't know why? Whenever I install AOL desktop (9.5, 9.6, 10.0) on my computer and I'm connected to the internet using cable, every thing is ok. I can browse websites and sign in to AOL.
But whenever I connect to the internet using my wireless network at home, I can not sign in to AOL, but I can still browse the web.
My wireless network uses WPA2-Personal with AES encryption type.
I always get the AC-3000 error message whenever I want to sign into AOL. None of AOL solutions could be useful to solve this.
What do I have to do ?
You didn't mention what version of windows you are using but my suspicion would be that if you are on Windows Vista/7 then the cable connection is identified as "home" or private and that the wireless connection is identified as public and the AOL connection (which used to be on port 5190 IIRC) is getting blocked as a result.
If I am right, to change what apps have access on which network types, you can follow the instructions here:
http://www.addictivetips.com/windows-tips/how-to-stop-a-program-from-gaining-unsolicited-internet-access-in-windows-7/
Although it is about how to stop a program from accessing the internet, it works just as well the other way around ;)
You could use netstat to determine what the successful connection to AOL is on the cable set up in terms of destination and IP and then attempt a simple telnet connection to the same address/port on the wireless set up to verify if this is blocked at the network/port level or if it is blocking the application (usually referred to as ACS). If the telnet connection succeeds and does not timeout, then it is an application level restriction which you will need to fix .