On Fri, 6 Sep 2019 05:39:16 -0700 (PDT), user pc
<petercohen8877@gmail.com> declaimed the
following:
I should add that I need to get this working both at home (wifi) and at
workplace (wifi also).
The latter will require checking with your IT staff. For example, at my
last employer, the WiFi system was limited to devices issued by the IT
department, and hence configured for the internal network by using the
user's corporate login information.
There was a guest WiFi, but users had to obtain the password (changed
monthly) from the IT desk -- and they preferred to only provide that to,
well, guests visiting the facility who had to provide justification for the
need -- and guests only had access to the WAN, they could not reach any LAN
nodes (whereas our issued computers could connect to each other and to the
email server). In this situation, you will likely not be able to connect to
the Beagle from your work computer (corporate firewalls will likely block
attempts to connect to any devices inside the guest WiFi).
In order to work with ad-hoc hardware (various development boards, et
al) we /had/ to use wired ethernet connections, and often had at least one
if not more USB<>Ethernet adapters connected to the computers (since the
computer's own Ethernet NIC was connected to the corporate LAN, anything
not on the LAN needed an additional NIC.
Heck, I've got two of
laying in a box of odds&ends, along with a pair of USB<>RS-232 adapters
(since most of the stuff we worked with had debug serial ports needed to
configure them before the network was usable) (Current version is
)