Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Network is not up using wired-ethernet #84

Closed
matsujirushi opened this issue Sep 3, 2019 · 7 comments

Comments

@matsujirushi
Copy link

@matsujirushi matsujirushi commented Sep 3, 2019

modified main.c and app_manifest.json of HTTPS_Curl_Easy, but it got error message.
"Not doing download because network is not up."
Could you tell me how to fix?

Setup:

  1. azsphere recover
  2. azsphere image package-board-config --preset lan-enc28j60-isu0-int5 --output enc28j60-isu0-int5.imagepackage
  3. azsphere device prep-debug
  4. azsphere device sideload deploy --imagepackage enc28j60-isu0-int5.imagepackage

Application:

  1. clone https://github.com/Azure/azure-sphere-samples/tree/master/Samples/HTTPS/HTTPS_Curl_Easy
  2. Modify main.c and app_manifest.json
    image
    image

Output:

Remote debugging from host 192.168.35.1
cURL easy interface based application starting.
This sample periodically attempts to download a webpage, using curl's 'easy' API.
Not doing download because network is not up.

Not doing download because network is not up.

Not doing download because network is not up.

Not doing download because network is not up.

FYI
https://social.msdn.microsoft.com/Forums/en-US/8b07758e-08c3-4e04-ac70-e3afcd6d42a7/network-is-not-up-using-wiredethernet?forum=azuresphere

@richardtaylorrt

This comment has been minimized.

Copy link
Contributor

@richardtaylorrt richardtaylorrt commented Sep 4, 2019

Hi - please could you tell us more about the Ethernet network the device is connected to? Is it assigning the device an IP address? Does it have a DNS server? Does it meet the network requirements explained here?

It may help to call Networking_GetInterfaceConnectionStatus() to get more information about the network status.

@Alberto-Vega-MSFT

This comment has been minimized.

Copy link

@Alberto-Vega-MSFT Alberto-Vega-MSFT commented Sep 6, 2019

Hi @matsujirushi Did you have a chance to follow the advice on Richard's comment?

@matsujirushi

This comment has been minimized.

Copy link
Author

@matsujirushi matsujirushi commented Sep 10, 2019

Sorry for replying late.

My network changed, Wired-Ethernet is working.

case 1:
Internet <-(PPPoE)-> Wi-Fi Router A(w DHCP/DNS) <-(Wi-Fi)-> Azure Sphere
case 2:
Internet <-(PPPoE)-> Wi-Fi Router A(w DHCP/DNS) <-(Wired)-> Azure Sphere
case 3:
Internet <-(PPPoE)-> Wi-Fi Router A(w DHCP/DNS) <-(Wired)-> Router B(w DHCP/DNS) <-(Wired)-> Azure Sphere

case 1 and 2 is NG.
case 3 is fine. (Add subnet)

I will close this issue.
(And I plan to investigate the cause of failure in case 1 and 2.)

Thanks.

@matsujirushi

This comment has been minimized.

Copy link
Author

@matsujirushi matsujirushi commented Sep 12, 2019

I got network capture.
AzureSphere don't sync time server of case 1 and 2.

image

Azure Sphere ask time to name server (!)

image

And the name server not respond time.

matsujirushi@wioserver:~$ sudo ntpdate -q 95.100.173.129
server 95.100.173.129, stratum 0, offset 0.000000, delay 0.00000
12 Sep 05:35:17 ntpdate[1006]: no server suitable for synchronization found
@richardtaylorrt

This comment has been minimized.

Copy link
Contributor

@richardtaylorrt richardtaylorrt commented Sep 17, 2019

Thanks for raising this - it was very useful. Our team has investigated and have identified the problem. We will fix in an upcoming OS release.

@richardtaylorrt

This comment has been minimized.

Copy link
Contributor

@richardtaylorrt richardtaylorrt commented Oct 2, 2019

We expect this problem is fixed in our 19.09 release. This release is currently available in our Release Evaluation feed. If you are able, please set up a device to access this feed and let us know if it fixes the problem. Otherwise, this release should hit the main Retail feed soon.

@matsujirushi

This comment has been minimized.

Copy link
Author

@matsujirushi matsujirushi commented Oct 3, 2019

Thanks for your support.
I tested.

C:\>azsphere device show-ota-status
Your device is running Azure Sphere OS version 19.09.
The Azure Sphere Security Service is targeting this device with Azure Sphere OS version 19.09.
Your device has the expected version of the Azure Sphere OS: 19.09.
Command completed successfully in 00:00:06.7638308.

C:\>

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.