Closed zarigata closed 1 year ago
Are you able to login locally and check SSH server, if it has been started correctly.
yes i am, no problems on that
SSH server is running a listen to correct port? Are you able to ping anything on the web? You get correct IP address assigned?
journalctl -u dropbear.service
ss -tulpn | grep LISTEN
ping google.com
ip a, ip r
yes it can leave the signal journalctl -u dropbear.service = no records it is a IP fixed
I would be appreciated if you can share the output of the commands I request. Did you changed to OpenSSH server?
and
ss -tlpn
?
One thing I see is that you have IPv6 enabled but no GUA assigned. IPv6 seems to be not supported in your LAN, or at least not through the Hyper-V bridge. Try to disable IPv6 and see whether this helps.
Ah, and does the host use WiFi or Ethernet? Network bridges via WiFi generally do not support IPv6.
Is 192.168.15.0
your local network range?
yes
ethernet
To be honest, it's not that easy to communicate with you. Some more words would be appreciated. As well, please answer our questions. Can you post the output as requested by @MichaIng . Did you disabled IPv6 in meantime? What interface type you setup on Hyper-V? What is the IP range of your local network?
sorry not a good response, i have to do this while doing some other stuff at the company and they sell what they cant demand, so i have to keep,
SS - tlpn
ipv6 is not enabled, it can be activated ath the modem, but it is not recommended, it is on a 100mbts ethernet, it has a IP locked on it.
disable IPv6 on your DietPi device. And still an outstanding question, what is the IP range of your local network? Is it 192.168.15.0
?
ive dissembled when you mentioned it is 192,168,15,0 to 192,168,15,255, being 255 used to end
are you able to reach PiHole web interface located on this VM? Did you installed UFW?
are you able to reach PiHole web interface located on this VM? Did you installed UFW?
yes i can acees the progtrams i have made available, i have a firewall but is not UFW, it is a modem one
Double check your firewall rules then. The VM is generally connected to LAN and reachable, SSH is listening and not reporting any errors, so there is something else in front of it blocking requests. If there is any firewall, the very first attempt to solve connection issues is disabling the firewall 😉.
i checked, it was not, i installed a BIOS version and it went well, perhaps some HYPER-V modification?
You mean you updated the BIOS on your host system? I'm not sure about Hyper-V changes, don't use it unless I need to test with one of our Hyper-V images. But great that it works now.
Creating a bug report/issue
Required Information
Steps to reproduce
Expected behaviour
Actual behaviour
Extra details