On Sun, 2002-11-24 at 09:50, stefmit wrote:
> Hi, all,
> 
> I am still struggling to identify the root cause of my wireless problems (for 
> those of you having read my recent Netgear MA401 email, you know what I am 
> talking about) - to recap: I am at the point of having to use two different 
> DHCP servers (at home and at work), with two different scopes ... after 
> having "patched" all sorts of scripts (network-functions), and forced 
> non-default drivers (orinoco_cs, vs. wvlan_cs), I am still struggling with 
> the fact that upon moving the laptop from one place (i.e. DHCP server) to the 
> other, the system "remembers" the IP address from the other location, and it 
> does not consider the new scope, neither getting the proper mask or default 
> gateway.

Sorry for what might be a silly question, but are you doing a service
network reload or restart after moving into the new network, or just
suspending at point A and resuming at point B? I think that If you are
reinitializing the dhcpcd and it isn't working, you need to work your
way up the OSI stack to troubleshoot. In gkrellm there's a wireless
plugin, load that and it will show you the layer 1 signal strength. Then
do a service network reload at point B and tail -f /var/log/syslog to
see what happens. My guess is that you're going to see a whole lot of
shorewall packet-dropping because shorewall is still using the point A
address for its wireless zone.

> NOTE: of course booting my system into M$'s W2K gets everything up just fine 
> ... how the H* are they doing that?!?
> 

Depends what they're doing... getting a DHCP address on boot isn't that
big a deal, but autosensing that you've moved into a new network,
getting a new address, and reconfiguring the built-in firewall to work
with the new address is a little trickier. Not impossible or even very
difficult, but you'll notice that W2K doesn't have a built-in firewall.

> I am sorry - but after having shot my whole weekend, I am tired - mainly - of 
> the non-standard way of handling wireless networking in Mandrake (inherited 
> from RedHat, I assume), and also frustrated of having to read each script, 
> one line at a time, to determine what is being done when, and how, in order 
> to trace all the problems ... so here is my kind request to you: is there any 
> kind soul out there able to point me to a document describing in detail the 
> networking boot-up process for Mandrake 9.0, at least for the new scripts for 
> wireless? I know Linux is all about learning one's self, but I was hoping I 
> can move on to new stuff, doing so, with a working system, rather than having 
> to fix problems of things which should have worked to begin with ... I would 
> think ... sorry if I am wrong here ...
> 

Nothing wrong with being frustrated -- sometimes you just have to drop
the problem for a while and come back when you can face it again. I find
that I've usually been staring at the answer in the documentation that I
was reading, it just wasn't sinking in because I was annoyed.

> Thx,
> Stef
> 

-- 
Jack Coates
Monkeynoodle: A Scientific Venture...


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com

Reply via email to