From: TJ@noneofyour.business   
      
   On 09/27/2012 09:33 PM, Adam wrote:   
   > TJ wrote:   
   >> On 09/27/2012 12:53 AM, Adam wrote:   
   >>> TJ said the updates to Mageia 2 include a better "wireless config"   
   >>> helper.  Of course I can't get the updates until it has some kind of   
   >>> working connection.  Right now I'm working on getting a wired connection   
   >>> solely to get those updates.   
   >>>   
   >> Um, I merely said the tools had been updated. That should mean that   
   >> they're "better,"   
   >   
   > I'm sorry, you're right. "Updated" ought to mean "improved", but we   
   > can't count on it.  The immediate problem turned out to be the cat5e   
   > cable between the computer and router, which had been working properly   
   > for years.  I replaced that, and then (as you said) it was simple   
   > getting a wired connection for Mageia set up.  Now I have all the   
   > updates so far, 600 MB including the config helpers.  I haven't got the   
   > wireless connection working yet, but I haven't tried everything.   
   >   
   Should have thought of that possibility myself. Haven't had it with an   
   ethernet cable, but I have had it with monitor and IDE cables before   
   now. Seems strange that it would work on some distros and not others,   
   though.   
      
   Mentioned before, one computer worked with wireless using the drakx   
   tools, but another didn't. Different wireless devices, both using   
   different chips than yours. The one that didn't work with the drakx   
   tools did work fine with the gnome networkmanager plasma app. (There was   
   a conflict between networkmanager and the drakx tools, but I believe   
   that was resolved with one of the updates.)   
      
   The first still works after the updates, and because it still works I've   
   left things alone. The other one hasn't been fired up in months, as I'm   
   using the monitor on my main computer until I can get the time to   
   attempt to fix the monitor for that. Bad capacitors, I suspect. It   
   hasn't had the updates yet, so I can't say if things have changed.   
      
   >>>> How is the eth0 interface being configured?   
   >>>   
   >>> All static IP from files for each distro on eris.   
   >>>   
   >> FWIW, my router, a Linksys WRT54G, is set to DHCP, so that an authorized   
   >> "guest" could connect more easily.   
   >   
   > I don't get many guests here. :-)  Actually I think I switched to static   
   > IPs because my dinosaur laserjet's interface has to be manually assigned   
   > an IP IIRC.   
   >   
   I don't get many either, but there have been a few times when my   
   sister-in-law wanted/needed access with her laptop. I don't have any   
   printers with wireless capability.   
      
   But my point was that there doesn't seem to be any reason why you can't   
   have both fixed IPs and DHCP, if you want. Not sure why he does this,   
   but my ISP's antenna/router (connects by wireless to his network, but   
   wired to the user) is configured like that. That's where I got the idea.   
   It recognizes assigned fixed IPs and gives them their full allotted   
   speed. It will give an unknown device an IP, but at a much reduced   
   connection speed. I found that out when I replaced my old wired router   
   with the current one, and forgot the fixed IP that had been assigned to   
   me. I had a connection, but it was S L O W. I thought at first that the   
   router was bad, but the ISP let me know what was going on. Sure is nice   
   to be able deal with an individual, rather than a faceless corporate minion.   
      
   TJ   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)