Mesa 7i96s and wifi -- solved --

I setup my new CNC configuration using the Mesa 7i96s set to the default 192.168.1.121 ip address just to get things up and running. Works great.
Now I would like to be able to have my computer access my local LAN so I can transfer files to it.  How do I do this?  When I select the W6 jumper to the UP position to use the EEPROM default address of 10.10.10.10, I cannot ping the card. is there something I need to set in my network configurations for the ethernet connection? I am not understanding how this is intended to be setup.

I also tried using Mesaflash to set the IP address of the card to 192.168.0.225.  That flashed successfully. I then enabled wifi on my computer and the computer can now access the LAN and internet, but I cannot ping the card. How does the computer know to look for the card on the ethernet adapter versus the wifi when doing a ping? I have a degree in Computer Engineering, but am not a network expert so am feeling really stupid right now. 

Okay, thought about what was going on and here is the path I have taken:
I had the Ethernet adapter setup with the PC manual IP address of 192.168.1.100.  The Mesa 7i96s board was set on the default W5-W6 both down, using the IP address 192.168.1.121.  Ping of the card worked fine and LinuxCNC finds the card.

I powered off the Mesa card, switched W6 to the up position, to use the address stored in EEPROM,( which I had previously set to 192.168.0.225).
I then powered up the Mesa Card, plugged in the wifi dongle on the PC and rebooted the PC. I can still ping the Mesa Card, but cannot get out to my LAN.  Tried setting a static IP address, use DHCP, DNS server address is correct.  The PC shows an active wifi connection, with an appropriate IP address assigned from my router.  But yet I cannot ping the router.  Weird.

 

In general it's better to use the 10.10.10.10 address on the motion control card
so there is no possible overlap with normal DHCP ranges.

The host needs to be configured with a static address for the Ethernet interface
used for the motion control card. Thsi shoud be say 10.10.10.100. This static IP address
setup should not affect normal network access as it's on (and must be on) a different interface.

The way I usually go is to do the following.

Home network/access to interwebs vis 192.168.1.1

Mesa network> static IP of 10.10.10.x, No DNS, No Gateway, netmask 255.255.225.0
"Rest of the world" network> static IP of 19.168.1.x, DNS to 192.168.1.1, Gatway to 192.168.1.1, netmask 255.255.255.0
or you can go with DHCP for "rest of the world" network. But I prefer static IPs, tho you can set up a static IP via your DHCP server on a machine by machine basis.

Importnat thing is to have your Mesa network & "Rest of the world " network be on physical separate networks and have seperate IP networks.

I'm a builder's labourer.