From: unruh@invalid.ca   
      
   On 2012-07-23, TJ  wrote:   
   > On 07/22/2012 10:39 PM, Moe Trin wrote:   
   >> On Sun, 22 Jul 2012, in the Usenet newsgroup alt.os.linux.mandriva, in   
   article   
   >> , TJ wrote:   
   >>   
   >>> Moe Trin wrote:   
   >>   
   >>>> TJ wrote:   
   >>   
   >>>>> Not sure what's involved where Mageia's concerned, or if my old   
   >>>>> Linksys WRT54G V8 router would be a stumbling block,   
   >>   
   >>>> How old is the router?   
   >>   
   >>> Gotta get a flashlight, it's dark in that corner. Dang it, cat! If   
   >>> you weren't underfoot your tail wouldn't get stepped on!   
   >>   
   >> Sounds familiar - hope the cat doesn't take revenge later   
   >>   
   >>> Ah, there it is: 11/2007. And I remember updating to the latest   
   >>> firmware last winter, but I don't remember the date of it... Sigh.   
   >>> Need my browser, and just another sec... There. Firmware version   
   >>> 8.00.8, dated Oct 5, 2009.   
   >>   
   >>> Does that help?   
   >>   
   >> Hard to say for sure, but that _should_ be new enough - the RFC4074   
   >> dates from 2005, and it did make enough waves that a number of   
   >> manufacturers were embarassed into fixing things.  A stock WRT54G   
   >> should be at 192.168.1.254, and have something resembing a caching   
   >> nameserver - so   
   >>   
   >>    dig @192.168.1.254 a.root-servers.net     or   
   >>    host a.root-servers.net 192.168.1.254   
   >>   
   >> should return a list of root-name-server IPs, and 9 of the 13 root   
   >> servers have both IPv4 and IPv6 addresses, like   
   >>   
   >>    a.root-servers.net      3600000 IN      A       198.41.0.4   
   >>    a.root-servers.net      3600000 IN      AAAA    2001:503:ba3e::2:30   
   >>   
   >>          Old guy   
   >>   
   > Hmm. That's disturbing. The second command timed out before finding   
   > anything. The first returned this:   
   >   
   > ; <<>> DiG 9.9.1-P1 <<>> @192.168.1.254 a.root-servers.net   
   > ; (1 server found)   
   > ;; global options: +cmd   
   > ;; connection timed out; no servers could be reached   
   >   
   > Something is awry. Yet it's working, anyway. The "Gateway" is reported   
   > by Mageia 2 at 192.168.1.1. Should I be using that instead of the IP you   
      
   For an internal home router that is a very common address for the   
   router/switch, and it will also be the gateway. If it works, use it.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)