thanks for the response.
I just used that URL as an example not as something I might be using in the future.
I am using it for test purposes ...... as it reports what IP address the connection is made from. In that way I am very sure which NIC is being used to make the connection.
route add -host 184.108.40.206 gw 192.168.1.254
The present difficulty is that the 'route' command requires root privileges, so is not available to the user.
I may have to set up something in the sudoers file for it.
I do not wish to have to specify a host ....... but it seems I must?
What I am aiming to do at this time to see if it works for me is to use a script into which I will put some URL or other that I wish to connect to, using the wlan0 NIC.
So I guess that will have something like this
1. route command to make wlan0 default
2. command to launch browser or wget or whatever to connect to some URL yet to be determined.
3. route command to undo 1.
Presumably the connection made in 2. above will continue using wlan0 even after 3. has been executed.
If not then it won't work for me.
I am trying to find a method to use a particular NIC for some connections ....... and if I have to use a script to achieve that then I will test it for a while to see if it fits in.
What I connect to, or use for the connection, cannot be predetermined.
So setting up static routes is not of any use apparently.
But if I can make the wlan0 NIC the default or whatever, make the connection, then revert the change, and have the connection continue on that NIC, while I use the eth0 NIC for other connections then all should be OK.
Thanks again for your post.