Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.networking > #2765
| From | "Charlie Gibbs" <cgibbs@kltpzyxm.invalid> |
|---|---|
| Newsgroups | comp.os.linux.networking |
| Subject | Re: Laptop wireless - flaky at home, OK at office |
| Date | 2014-03-03 11:36 -0800 |
| Organization | NewsGuy - Unlimited Usenet $23.95 |
| Message-ID | <2365.210T2464T6965521@kltpzyxm.invalid> (permalink) |
| References | <2523.209T780T11284469@kltpzyxm.invalid> <slrnlh7v58.aq6.ibuprofin@fermi.phx.az.us> |
In article <slrnlh7v58.aq6.ibuprofin@fermi.phx.az.us>, ibuprofin@painkiller.example.tld.invalid (Moe Trin) writes: > On 02 Mar 14, in the Usenet newsgroup comp.os.linux.networking, in > article <2523.209T780T11284469@kltpzyxm.invalid>, Charlie Gibbs wrote: > >> I have a laptop running CrunchBang Waldorf: > > Not familiar with it It's a lean distribution built on Debian. > So, is 192.168.0.x on eth0 or wlan0. ONE, NOT BOTH. But it is both - eth0 gets 192.168.0.24, wlan0 gets 192.168.0.23. > When the kernel sees two routes to the same destination, it chooses > the one that was declared last, because it assumes you screwed up > making the first declaration, and the second one is the correction. > You can prove this by running a packet sniffer on each interface, > and seeing which one is getting which packets. Yup, eth0 was getting all the packets. > Solution: change wlan0 _OR_ eth0 to some other address range. > Or simply don't use two interfaces. cjg@cjglap-crunchbang:$ sudo ifconfig eth0 down Presto! As for why it worked at the office, I never bothered plugging in an Ethernet cable there, and wlan0 picked up an address of 192.168.1.xxx instead of 192.168.0.xxx, so there was no conflict. Thanks for the help. I was primarily using the wired connection to my laptop at home because I haven't been able to get VirtualBox to bridge to a wireless connection, and I need my laptop to have access to machines on my LAN as well as to the Internet, both natively and through the virtual WinXP machine. Unfortunately, this means that I get wireless access to my LAN from the Linux host at the cost of any network access from the virtual machine. It could be worse, I suppose. The WinXP VM is for work, so if I want to use it I'll go into my home office, plug in the Ethernet cable, bring up eth0, and do work. If I want to play somewhere else in the house, I'll unplug the cable, set eth0 down, and have full wireless access from the Linux side. It beats borrowing my wife's laptop, which is a singularly unpleasant experience seeing as it runs Windows 7 and has a really crappy keyboard. -- /~\ cgibbs@kltpzyxm.invalid (Charlie Gibbs) \ / I'm really at ac.dekanfrus if you read it the right way. X Top-posted messages will probably be ignored. See RFC1855. / \ HTML will DEFINITELY be ignored. Join the ASCII ribbon campaign!
Back to comp.os.linux.networking | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Laptop wireless - flaky at home, OK at office "Charlie Gibbs" <cgibbs@kltpzyxm.invalid> - 2014-03-02 18:48 -0800
Re: Laptop wireless - flaky at home, OK at office Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2014-03-03 03:53 +0000
Re: Laptop wireless - flaky at home, OK at office "Charlie Gibbs" <cgibbs@kltpzyxm.invalid> - 2014-03-03 11:36 -0800
Re: Laptop wireless - flaky at home, OK at office Moe Trin <ibuprofin@painkiller.example.tld.invalid> - 2014-03-04 19:45 +0000
Re: Laptop wireless - flaky at home, OK at office "Charlie Gibbs" <cgibbs@kltpzyxm.invalid> - 2014-03-04 18:23 -0800
csiph-web