Jump to content

Banner.jpg.b83b14cd4142fe10848741bb2a14c66b.jpg

Networking - No Route to Host


Gina

Recommended Posts

  • Replies 208
  • Created
  • Last Reply

There seems to have been corruption of some files.  Strangely though, when connected by cable the system runs the ASC functions fine - running the camera and displaying the images on the Mint desktop. 

Link to comment
Share on other sites

I strongly suspect the WiFi problem is something to do with the MAC address having changed hardware.  I suspect previous WiFi problem was due to not using a fixed IP address.

Link to comment
Share on other sites

In case this might help in future. This is the procedure I follow for every RPi I use to setup static IP addresses.

set xxx and yyy to a number outside the DHCP range of your router. My router uses 192.168.1.64 - 192.168.1.163 for DHCP so I use addresses below and above that for statics.

My router is on 192.168.1.254 (as are many others) but yours may be different (192.168.1.1 is sometimes used). Whatever it is use that address for the static routers and static domain_name_servers values.
 


/etc/wpa_supplicant/wpa_supplicant.conf
---------------------------------------

add lines:

network={
    ssid="your_AP_SSID"
    psk="Your_wifi_password"
    key_mgmt=WPA-PSK
}


/etc/dhcpcd.conf
----------------

add lines:

interface eth0
static ip_address=192.168.1.xxx
static routers=192.168.1.254
static domain_name_servers=192.168.1.254
static domain_search=

interface wlan0
static ip_address=192.168.1.yyy
static routers=192.168.1.254
static domain_name_servers=192.168.1.254
static domain_search=


then reboot:

sudo reboot

Log in with the new ip address(es)

 

Link to comment
Share on other sites

So fixed IP addresses want to go outside the DHCP pool rather than within.  I added the MAC address and IP address within the pool - wrong then.

278673306_Screenshotfrom2019-03-0214-23-24.png.190f78fc7590d0bb34d1aff77b0f0f91.png

Link to comment
Share on other sites

Best avoided - something might already have grabbed 192.168.1.80 causing a conflict.

There should be a way on your router to view what ip addresses are allocated to which device. You should also be able to change the DHCP range to make more space for statics if you need to.

Link to comment
Share on other sites

Added that configuration to the appropriate places on the SD card and set up static IP addresses in router.  Now to see if it works...

Link to comment
Share on other sites

Put SD card back in RPi and powered up.  No joy on either of the new IP addresses.  Nor do either 192.168.1.226 or asc2!

gina@Mint-Desktop ~ $ ssh gina@192.168.1.40
ssh: connect to host 192.168.1.40 port 22: No route to host
gina@Mint-Desktop ~ $ ssh gina@192.168.1.41
ssh: connect to host 192.168.1.41 port 22: No route to host
gina@Mint-Desktop ~ $ ssh gina@192.168.1.226
ssh: connect to host 192.168.1.226 port 22: No route to host
gina@Mint-Desktop ~ $ ssh gina@asc2
ssh: connect to host asc2 port 22: No route to host
gina@Mint-Desktop ~ $ 

505567509_Screenshotfrom2019-03-0216-05-11.png.2d7854b2937481bbc0268289ff0dd9d5.png

Link to comment
Share on other sites

gina@Mint-Desktop ~ $ ifconfig
enp2s0    Link encap:Ethernet  HWaddr 40:8d:5c:e9:18:c8  
          inet addr:192.168.1.79  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fd53:7f53:4e13:0:cdfc:5f58:1621:c0f4/64 Scope:Global
          inet6 addr: fe80::dd:9173:1f3d:49ff/64 Scope:Link
          inet6 addr: fd53:7f53:4e13:0:7481:897b:ce6e:7987/64 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:436898 errors:0 dropped:0 overruns:0 frame:0
          TX packets:240808 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:458947946 (458.9 MB)  TX bytes:42997996 (42.9 MB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:80354 errors:0 dropped:0 overruns:0 frame:0
          TX packets:80354 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:23769253 (23.7 MB)  TX bytes:23769253 (23.7 MB)

gina@Mint-Desktop ~ $ 

 

Link to comment
Share on other sites

6 minutes ago, Gina said:

Put SD card back in RPi and powered up.  No joy on either of the new IP addresses.  Nor do either 192.168.1.226 or asc2!


gina@Mint-Desktop ~ $ ssh gina@192.168.1.40
ssh: connect to host 192.168.1.40 port 22: No route to host
gina@Mint-Desktop ~ $ ssh gina@192.168.1.41
ssh: connect to host 192.168.1.41 port 22: No route to host
gina@Mint-Desktop ~ $ ssh gina@192.168.1.226
ssh: connect to host 192.168.1.226 port 22: No route to host
gina@Mint-Desktop ~ $ ssh gina@asc2
ssh: connect to host asc2 port 22: No route to host
gina@Mint-Desktop ~ $ 

505567509_Screenshotfrom2019-03-0216-05-11.png.2d7854b2937481bbc0268289ff0dd9d5.png

Did you add those on the router or are they just showing up because the pi is using them. If you added them yourself you may be reserving them, preventing the pi from using them.

Link to comment
Share on other sites

7 minutes ago, Gina said:

gina@Mint-Desktop ~ $ ifconfig
enp2s0    Link encap:Ethernet  HWaddr 40:8d:5c:e9:18:c8  
          inet addr:192.168.1.79  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fd53:7f53:4e13:0:cdfc:5f58:1621:c0f4/64 Scope:Global
          inet6 addr: fe80::dd:9173:1f3d:49ff/64 Scope:Link
          inet6 addr: fd53:7f53:4e13:0:7481:897b:ce6e:7987/64 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:436898 errors:0 dropped:0 overruns:0 frame:0
          TX packets:240808 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:458947946 (458.9 MB)  TX bytes:42997996 (42.9 MB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:80354 errors:0 dropped:0 overruns:0 frame:0
          TX packets:80354 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:23769253 (23.7 MB)  TX bytes:23769253 (23.7 MB)

gina@Mint-Desktop ~ $ 

 

Make sure you have used enp2s0 not eth0 in the dhcpcd.conf file.

Also make sure you remove any other lines relating to enp2s0

Link to comment
Share on other sites

INDI drivers accessed from Mint with KStars/Ekos.  And yes it run headless.  Been using it for a couple of years until a bad storm wrecked my ASC and I needed to rebuild.  I also use KStars/Ekos/INDI for standard astro imaging with the RPi.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. By using this site, you agree to our Terms of Use.