Community
cancel
Showing results for 
Search instead for 
Did you mean: 
MClif
New Contributor I
1,392 Views

Intel Edison WAN access - Network Unreachable

Hi,

This is a repeat of a reply I made on the 9th to this discussion:

It did not seem to appear at or near the top of :

Maybe it got lost, so I am reposting my reply.

Hi,

My version of Edison/Yocto is: 201603141535 (hmmm Pi Day

When I ping elsewhere I get network unreachable.

netstat -rn

Kernel IP routing table

Destination Gateway Genmask Flags MSS Window irtt Iface

192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 usb0

192.168.42.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0

No 0.0.0.0 for the Gateway.

Question: should do the following: route add default gw 192.168.42.0 wlan0

Regards,

Bill

0 Kudos
3 Replies
idata
Community Manager
60 Views

Hi Bill,

 

 

Thank you for reaching out! Let me try to help you with this issue.

 

First, I would like to know if you need to use the image you're currently using or if you are able to update to the latest image. In case you have no problem with that, here's the link: https://software.intel.com/en-us/iot/hardware/edison/downloads https://software.intel.com/en-us/iot/hardware/edison/downloads.

 

Now regarding the issue:
  1. Did you connect to your WiFi network successfully?
  2. Did you make sure to connect your Edison to the same network of your host computer?
  3. I'm still a bit unsure about your last statement, the one about the command route add default gw 192.168.42.0 wlan0. Did you try to add this at some point? What results did you get?
We'll be waiting for your reply.

 

 

Kind regards,

 

-Pablo
MClif
New Contributor I
60 Views

Hi Pablo,

Good News!

Executing configure_edison --wifi solved the problem. I thought I had done this last spring.

Now I have good netstat -rn output. Edison can ping the router and the PC host and the PC host can ping edison.

Regarding: do I need the current image?

I don't need it. I am in experiment mode trying various things. WiFi was next on my list. I could update to the current image but I am afraid something will go wrong and then I'll spend time dealing with that.

Regarding: your other questions.

No need to answer those questions. Especially about the 192.168.42.0 wlan0 in the route command. That was absolutely stupid on my part.

This was not a good use of your time.

Embarrassed,

Bill

idata
Community Manager
60 Views

Hi Bill,

 

 

You don't need to worry! We appreciate you taking the time to let us know that you solved the issue on your own.

 

 

-Pablo
Reply