06-27-2016, 01:31 PM
I've got a strange problem trying to setup new boards while at work. The xenial image dated 7th of may (which seems to be the latest AFAICT) isn't able to reach the DHCP, at work.
On another image I've fully upgraded and updated prior (with MATE desktop) I am able to access network normally. so it doesn't seem like a hw issue, just that the image may be missing some configs or packages to operate in the network at work which is pretty tight with VPNs and such.
Any pointers on what I should do to allow the virgin image to access the dhcp server?
(FWIW : I had the same issues with the android image which shipped with these boards. )
when I run ifconfig, I get a few thousand kb worth of packets on both TX and RX (and counting) and no errors, dropped or any other bad packets.
I also ONLY have a single board activated at a time, so it's not the fabled "same mac address" issue.
On another image I've fully upgraded and updated prior (with MATE desktop) I am able to access network normally. so it doesn't seem like a hw issue, just that the image may be missing some configs or packages to operate in the network at work which is pretty tight with VPNs and such.
Any pointers on what I should do to allow the virgin image to access the dhcp server?
(FWIW : I had the same issues with the android image which shipped with these boards. )
when I run ifconfig, I get a few thousand kb worth of packets on both TX and RX (and counting) and no errors, dropped or any other bad packets.
I also ONLY have a single board activated at a time, so it's not the fabled "same mac address" issue.