We had an identical issue with all of our clients. Even with bridging turned
off AND inhibit NAT from 802.11, the internal (private ip of the RG) would
STILL 'leak' over to the wireless side. Our ISP bases were all in bridging
mode.
This was with 4.02 - Maybe this has been fixed with 4.31?
In our situation, the only cure we found was to spend several days
reconfiguring every client site (connected to the same ISP base to have
different internal subnets. ie client A 192.168.1.x client b 192.168.2.x
client C 192.168.3.x and so on.....
This fixed all issues, but still didnt change the fact that the private IP
was leaking. We tried this by setting up a w2k machine with multiple IP's
(192.168.1.200, 192.168.2.200 and so on). This was connected at our NOC and
bridged to the ISP base. We could still ping each and every RG's internal
address (192.168.1.254, 192.168.2.254 and so on etc...)
We could even configure each and every RG by their so-called 'private IP
addresss'!!
-Sam
-----Original Message-----
From: karlnet-admin@WISPNotes.com [mailto:karlnet-admin@WISPNotes.com]On
Behalf Of Charles Chia Sheng Wu
Sent: Monday, 6 January 2003 5:34 a.m.
To: karlnet@WISPNotes.com
Subject: RE: [Karlnet] my bridging issue
yup
-----Original Message-----
From: karlnet-admin@WISPNotes.com [mailto:karlnet-admin@WISPNotes.com]On
Behalf Of Brett Hays
Sent: Sunday, January 05, 2003 7:06 AM
To: Karlnet List
Subject: [Karlnet] my bridging issue
Thanks to Charles for the answer to my configurator issue. I turned off
bridging on all my clients and selected inhibit NAT from 802.11b interface
as well.
I am wondering if having bridging enabled on all these clients could have
been the source of a long standing issue I have been fighting with my
wireless clients. On clients that had an excellent signal, etc. I was
having tiny little interruptions in service. It was only noticeable if you
were using Yahoo instant messenger or when downloading a file over about
4mb, you would get connection to the server reset messages.
The interruptions were just a fraction of a second. Could this have been ip
conflicts from the private ip's in use behind the clients (rg1100's) since
bridging was enabled?
_______________________________________________
Karlnet mailing list
Karlnet@WISPNotes.com
http://lists.wispnotes.com/mailman/listinfo/karlnet
_______________________________________________
Karlnet mailing list
Karlnet@WISPNotes.com
http://lists.wispnotes.com/mailman/listinfo/karlnet
|