I am running ubuntu 18.04 LTS on virtual box. Is it possible to scan for real (non virtual) BACnet devices on a LAN through the virtual box VM?
How would I set the BACpypes.ini?
My Windows 10 machine if I do a ipconfig/all this doesn't work with the BACpypes.ini when run bacnet_scan.py on my VM
Or this IP address of my Windows 10 machine.
Both IP addresses implemented onto the BACpypes.ini will throw an:
OSError: [Errno 99] Cannot assign requested address
If I do an ifconfig of my ubuntu VM this doesnt appear to error anything on the bacnet_scan.py but none of my BACnet devices come up either. Any tips greatly appreciated...
Currently your VM is set up with a host-only connection. Host-only connection does what it says on the tin: you're only able to communicate with the host. To contact with the LAN around the host, set the VM's networking mode to "NAT" (This makes your VM routable through the host machine). Then, look up your VM's IP again and try that.
Related
I'm using a container to develop for an embedded system. To interact with the debugger I need openocd running on the host machine (as it needs USB access, and it's on a Windows machine therefore I can't access the USB port from the container), and connect to it with a gdb running in the container. I'd like to know if it is possible to forward/connect to a port from the host machine - from all that I've read until now this does not seem to be possible?
My current workaround is to run an SSH server in the container, forward it's port and open an SSH connection from the host to the container with reverse forwarding the openocd port. But that is quite a bit more convoluted than I'd like.
Just exposing the port to the local network and connecting via the public IP came to mind as well, but our corporate firewall blocks that.
I'm currently having a Macbook Pro M1 as my development machine, running Docker on Mac for my containerised applications and Windows 11 VM using Parallels as my development environment. In this Windows VM lies the SQL Server database that Docker needs to connect to. To those who may be unaware, no, the M1 chip doesn't support nested virtualisation.
Therein lies my question: how do I establish a connection from Docker through the MacOS host to SQL Server in Windows VM?
Points that I'm aware of:
There is no direct connection between Docker and Windows
Docker has its own subnet assigned by default e.g. 192.168.65.0/24
Parallels uses shared network by default, which places the Windows VM in an invisible subnet e.g. 10.211.55.x
Parallels support bridged network but ideally would like the corporate VPN to just be in the MacOS host
Inside Mac's host file, an entry exists to resolve the private IP of the Windows VM to a hostname e.g. 10.211.55.x windows-11.shared
Docker uses a specific hostname to establish a connection to the MacOS host i.e. host.docker.internal
SQL Server is configured to accept TCP connections through port 1433
Using the connection string Server=windows-11.shared;Database=xxx;User ID=xxx;Password=xxx throws the "Server not found" error because no direct connection
Advice greatly appreciated!
I have a RPi running an instance of volttron-central. I can VNC into the RPi and view the Web UI from a browser pointed to localhost, so I know that it is running. However, when I attempt to connect from a PC connected to the same LAN using the RPi's IP address, I get "refused to connect" error.
Is this a security feature? If so, is there any-way of viewing the WEB UI from a different machine, or does it need to be running an instance of volttron-central locally?
Edit your config file to use an external address (e.g. not 127.0.0.1). In VOLTTRON_HOME (~/.volttron) edit the config file. Change the bind-web-address setting to equal (what you have above as 192.168.1.4) to http://192.168.1.4:8080. Then restart the platform.
Note: you should also make sure your /etc/hosts file has a mapping from the 192.168.1.4 onto your hostname, then you could goto https://foo:8080 rather than using the address. This will work with the bind-web-address, but not the vip-address.
What I can do:
can connect to desktop Win10pro from phone (wifi/data)
can connect to desktop Win10pro from laptop Win10pro (wifi only)
can connect to desktop Win10pro from work Win7 (desktop)
can connect to desktop Win10pro from TeamViewer
Problem:
When I try to connect to my desktop from my laptop using the usb ethernet dongle, everything listed above seizes to function; only a black screen after logging in. Keep in mind, this setup did work 5 months ago, only thing that changed was that I reset/refresh my laptop because it became bogged down and switched from college to home.
What I've tried:
System Restore on the host desktop
sfc /scannow both host and laptop
resetting network adapter and settings on laptop
checking regedit to make sure 3389 was listening on laptop
disabled/enabled NLA
disabled/enabled RDP on host desktop
enabled RDP on latop
uninstalled network adapter and reinstalled on laptop
turning off wifi on laptop and then trying to connect
If anyone has any other suggestions, that would be awesome.
UPDATE: As someone suggest to get a new USB Dongle, went out and bought one. Still does not work. Extremely laggy and black boxes everywhere.
What solved my issue was using the internal ipv4 address when I am on the local network; else, using the external ipv4 when I am away from home.
Thing to note is that even when I was internally using ipv6, I had a huge issue with this and could not connect to it internally using external ipv4 with :3389 at the end of it.
Hope this helps someone.
I upgraded my desktop machine from windows 8 to 10 and now I'm unable to connect to any of my Vms (hosted on another server) using RDC.
I have one server(Ubuntu no GUI) that host multiple VM's(windows and Linux w and w/o GUI) using VirtualBox. From my laptop I normally connect with RDC using the host(server) ip followed by port number (192.168.0.2:3396 assigned during create VM process) works fine, at that point I adjust network setting(static ip) for the LAN and exit. etc etc..
On the windows 10 desktop I receive and error; This computer can not connect to the remote computer. I can however connect with the ip address (192.168.0.5) no port. this part is fine for existing Vms that have static ip. I need to connect and assign the ip.
Thanks for any feedback or suggestions