"-keevill-" <keevillus@yahoo.com> hath wroth:
>> If the two networks have different SSID's, then there won't be any
>> cross pollenation.
>
>They have different SSIDS , I can see the name of his network on our
>machines when we scan network for wireless routers.
Well, that mostly eliminates your neighbor as a possible culprit. His
wireless computah might have been setup to connect to literally ANY
wireless access point, which I guess would include yours. However,
that's not the default and rather uncommon.
>Yes that's what I am guessing too. Is there anyway to prevent that ? Perhaps
>block an ip range on our network ??
Nope. He'll just find another IP address to borrow.
I have a similar "open" setup. I use a MAC address filter for the
wireless connections. It's very easy to bypass, but it does serve the
purpose of preventing accidental connections. I have a neighbor that
just can't stay off the porno sites. He has his own wireless router
and DSL, but he turns it off a night. Meanwhile, the laptop wanders
over to my system and spews viruses and worms. So, I made a list of
the acceptable MAC addresses, applied the NAC filter, and he was
history. He could easily change his MAC address, but I have a trick
that will easily detect his laptop. The SSID is my address, so if
anyone wants to use the system, they can bang on the door or call me.
I've added about 10 such transient laptops for various neighbors.
>The wired machines have fixed ip in the range 192.168.0.1-10
>The 1st router has DCHP range of 192.168.0.50-80
>The 2nd router has DCHP range of 192.168.0.100-120
Perfect. The IP conflict is not coming from one of your machines.
Unfortunately, that probably means a hacker or someone looking for
some free bandwidth. Such is the joy of running an open and
unencrypted wireless system. Good luck.
--
Jeff Liebermann
jeffl@cruzio.com
150 Felker St #D
http://www.LearnByDestroying.com
Santa Cruz CA 95060
http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558