I looked into this, and found that this is normal to see “Permission denied” at the start of ping, but then it should work correctly after that. Apparently the verbose debug is showing an attempt to use sockets in a way that is not normally allowed. If you adjust so that this is allowed, then even so only root (sudo) will actually succeed without the “Permission denied”. So long as the “non-verbose” ping works, then you can say ping is working as expected.
The clue which is rather important here is “ping: google.com: Name or service not known”. This implies DNS is not set up. To illustrate, if you go to your host PC, then you should be able to successfully run command “host nvidia.com”, and find one of its addresses is “216.228.121.209”. Then on host…or on Jetson…you should be able to ping the dotted-decimal address, “ping 216.228.121.209”. If this ping works, then it implies basic network is set up, and that DNS is not being forwarded.
Assuming DNS failure, what is the content (you can attach files since copy and paste may not work well) of the Jetson’s “/etc/resolv.conf” file? If addresses there (using dotted-decimal) are not present, then you might try copying your host PC’s “/etc/resolv.conf” there to see if things suddenly start working.
Note that if you get your address by DHCP, then resolv.conf is normally set up for you. If you use a static address assignment, then you may need to add resolv.conf as well. If your host PC uses DHCP and the ISP changes DNS server, then at some point the Jetson may once again fail DNS until updating resolv.conf.