192.168.0.100 not accessible

Having issues with your DietPi installation, or, found a bug? Post it here.
Post Reply
jeyjey
Posts: 8
Joined: Wed Jan 17, 2018 4:21 pm

192.168.0.100 not accessible

Post by jeyjey »

I made the image and I turned on the OrangePi Zero plus SBC. The standard in the world is 192.168.1.1 as the first ip. It should have been received by the DHCP, or a number like: 192.168.1.100, and not 192.168.0.100!! What kind of number? It is better to have a DHCP request and then find the 22 port by a NMAP scan. Now I have a DietPi SOC running but I cannot find the way to connect it via SSH, I must stop the operations and try to mount another Distro.
User avatar
johnvick
Legend
Posts: 693
Joined: Wed Jun 08, 2016 11:53 am
Location: New Zealand

Re: 192.168.0.100 not accessible

Post by johnvick »

Can you not find the device's IP address from your router?

John
jeyjey
Posts: 8
Joined: Wed Jan 17, 2018 4:21 pm

Re: 192.168.0.100 not accessible

Post by jeyjey »

Not. Probably there is an issue in the DHCP. I am not the owner of the router. I tryed to change the config files assigning a static ip, but nothing. I think that the image itself should be released with this address: 192.168.1.100 and not *.*.0.100!
User avatar
johnvick
Legend
Posts: 693
Joined: Wed Jun 08, 2016 11:53 am
Location: New Zealand

Re: 192.168.0.100 not accessible

Post by johnvick »

The image is issued without an address i.e. DHCP by default. If you want to change this then you can do so with dietpi-config and assign a fixed IP address. The address you quote 192.168.0.100 is just an example.

If the owner of the router can tell you the IP of your device then problem solved.

John
jeyjey
Posts: 8
Joined: Wed Jan 17, 2018 4:21 pm

Re: 192.168.0.100 not accessible

Post by jeyjey »

Ok if it is DHCP by default it is ok, but .... it did not find a number, probably a mistake in the imaging. I will try later, thanks.
Post Reply