Success! Sort of. Once I changed the address from 192.168.1.121 to ...122
I was able to connect to the MESA and also the WiFi.
auto eth0
iface eth0 inet static
address 192.168.1.122
netmask 255.255.255.0
I can even use Chrome to surf the web although it keeps asking for those
stupid keys (3x).
Next problem though is I want to install samba to link the way I have my
linux based Raspberry Pi, Beagles and even a macbook running linux with a Pi
user interface.
I get this dreadful feeling that I'm going to have to rebuild my Linux
system for a newer version.
john@LinuxCNC-G3616:~$ uname -a
Linux LinuxCNC-G3616 4.9.0-16-rt-amd64 #1 SMP PREEMPT RT Debian 4.9.272-2
(2021-07-19) x86_64 GNU/Linux
If I do a
sudo apt update
I get path not found errors. Kind of like Windows no longer supporting
WIN-7 I guess.
And therefore
sudo apt install samba
doesn't work either.
What will I break if I do a
sudo apt upgrade
Thanks
John
> -----Original Message-----
> From: Les Newell [mailto:les.new...@fastmail.co.uk]
> Sent: February 23, 2024 2:42 AM
> To: emc-users@lists.sourceforge.net
> Subject: Re: [Emc-users] WiFi & MESA
>
> I have 3 machines running Ethernet Mesa cards and have had no problems
> using them with USB wifi dongles.
>
> Do you have your Ethernet port assigned with a static IP address? This
> link may help <https://gnipsel.com/linuxcnc/debian-9-eth.html>
>
> Les
>
>
> On 23/02/2024 07:46, John Dammeyer wrote:
> > Hi all,
> > My LCNC system is in the garage and the PC has only one hardware
> Ethernet
> > port which is connected to the MESA 7i92H. Works like a charm. No
issues.
> > I thought instead of sneakernet I'd try a WiFi adaptor I found in my
sons
> > things when I was cleaning up his stuff after his untimely passing.
> >
> > No problem. Plug in the adaptor. Boot the PC.
> > https://support.dlink.com/resource/products/DWA-140/REVA/DWA-
> 140_DATASHEET_1
> > .00_EN.PDF
> > Once I entered the correct password to get into my network it was alive.
> > Visible on the network.
> >
> > I then clicked on the ICON to start LinuxCNC and nada. Couldn't connect
to
> > the MESA and therefore LinuxCNC didn't start.
> >
> > OK. Backtrack. Unplug WiFi USB. Restart PC and run LinuxCNC. Home all
> axis
> > and move to XY home. Super. It works. Then plug in the WiFi dongle.
It
> > connects to the network and the Axis Interface immediately reports a
> > communications problem with the MESA board. Unplugging the WiFi
> doesn't
> > matter. I have to stop AXIS but the command line window also needs to
be
> > killed. Trying to restart tells me LCNC is still running and do I want
to
> > restart.
> >
> > Yes. And all is good in the LCNC world.
> >
> > So the question is: How do I tell Linux to cooperate with both the MESA
> and
> > the WiFi Dongle?
> > Thanks
> > John
> >
> >
> >
> > _______________________________________________
> > Emc-users mailing list
> > Emc-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/emc-users
>
>
>
>
> _______________________________________________
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
