On Thursday 25 June 2015 08:46:49 notoneofmyseeds wrote: > On 06/23/2015 10:22 PM, Bob Proulx wrote: > > Another question: When you are connected to both as you have done > > what is the output of these commands so that we can see the (as you > > say broken) state of things? > > > > ip addr show > > > > ip route show | tac > > I had a very long and nice response that I lost, as a result of an > application crash. > > So, now to the specific point: > > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN > group default > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > inet 127.0.0.1/8 scope host lo > valid_lft forever preferred_lft forever > inet6 ::1/128 scope host > valid_lft forever preferred_lft forever > 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP > group default qlen 1000 > link/ether 00:16:d3:27:29:70 brd ff:ff:ff:ff:ff:ff > inet 172.16.1.0/24 brd 172.16.1.255 scope global dynamic eth0 > valid_lft 289sec preferred_lft 289sec > inet6 fe80::216:d3ff:fe27:2970/64 scope link > valid_lft forever preferred_lft forever > 3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP > group default qlen 1000 > link/ether 00:13:02:b8:90:4d brd ff:ff:ff:ff:ff:ff > inet 10.10.10.5/24 brd 10.10.10.255 scope global wlan0 > valid_lft forever preferred_lft forever > inet6 fe80::213:2ff:feb8:904d/64 scope link > valid_lft forever preferred_lft forever > > And: > 172.16.1.0/24 dev eth0 proto kernel scope link src 192.168.1.2 > 169.254.0.0/16 dev wlan0 scope link metric 1000 > 10.10.10.0/24 via 10.0.0.1 dev wlan0 proto static metric 1 > 10.10.10.0/24 dev wlan0 proto kernel scope link src 10.0.0.5 > default via 172.16.1.1 dev eth0 proto static metric 1024 > > And I agree, I think this is a routing problem. And I have tried > setting static ip on wlan and Ethernet, but no luck. I changed the > order as they appear in the network/interfaces file, no luck. Set > dhcp the wlan and static for the ethernet, and did not include a > gateway, no luck. I include its gateway associated with that network, > no luck. > > From all that I've read, this should be very simple and > straightforward. I've followed the rules, but no luck. All I want to > do is connect to my local lan and the internet at the same time, > without having to switch to the ethernet when I want to use the lan > network, and the wifi when I want to go online. Am I the only one > wanting to do this?
No, but most folks setup their local network on a local 192.168.xx.yy address, and NAT translate it in thier router to go web browsing, which allows any machine on your local net full access to the internet. If your router cannot do that, get one that can. I use anything with enough flash and memory to allow dd-wrt to be re-flashed into it. That also allows you to serve your own web page from a machine on the local net, in this case, this machine. The uplink pipe is obviously somewhat slow, but it works. > Thanks a lot. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201506251020.55470.ghesk...@wdtv.com