From: adam@address.invalid   
      
   unruh wrote:   
   > On 2012-09-24, Adam  wrote:   
      
   (Background: my older computer "eris" had been moved to the other room   
   as a testbed for various distros, with only a Wi-Fi connection.  It's   
   temporarily filling in as my main system on my computer desk.  Its   
   wireless card is still enabled but while it's here next to the router   
   there's also temporarily a wired connection.  I'd gotten Wi-Fi working   
   for two distros (Fedora 17 and CentOS 6.3) so I'm using one of those to   
   send this, but haven't yet gotten either a wired or wireless connection   
   on it with Mageia 2 (or any of the other distros on it).  Eventually   
   "eris" will be going back to the other room and have only wireless   
   connectivity again.)   
      
   >> I'm confused about whether both can have the same IP address, or whether   
   >> I need two addresses and hostnames for the same installation.   
   >   
   > You could try but it cannot work. the address is a delivery route. the   
   > net has to decide which delivery route it will take. It is certainly not   
   > going to send along all routes. It asks the dns server for a route. I   
   > will use the first one (I believe)   
      
   That makes sense; it's just something I never thought about before.   
   "eris" has always been 192.168.1.23 (my little LAN is 192.168.1.0/26),   
   so I'll keep that for the wireless connection on it and use "eris-wired"   
   192.168.1.24 for the wired connection.  I can see that's two separate   
   lines in /etc/hosts, and still only one of the two connections can be   
   active at a time.   
      
   >> I've kept working at it, using my ISP's DNS to start.  Last I checked,   
   >> 'ping' works, "ifup eth0" works, but a web browser can't even find my   
   >> router's IP.  This is typical for me when trying for 'net connectivity.   
   >   
   > What are the outputs of ifconfig , route -n, cat /etc/resolv.conf for   
   > starters   
      
   Under Mageia 2 (no updates), with no working connection yet:   
      
   [root@eris ~]# uname -a   
   Linux eris.aplomb.invalid 3.3.6-desktop-2.mga2 #1 SMP Thu May 17   
   16:25:59 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux   
   [root@eris ~]# ifconfig   
   eth0      Link encap:Ethernet  HWaddr 00:1B:B9:B4:06:54   
              inet addr:192.168.1.23  Bcast:192.168.1.63  Mask:255.255.255.192   
              inet6 addr: fe80::21b:b9ff:feb4:654/64 Scope:Link   
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1   
              RX packets:6 errors:0 dropped:0 overruns:0 frame:0   
              TX packets:23 errors:0 dropped:0 overruns:0 carrier:0   
              collisions:0 txqueuelen:1000   
              RX bytes:360 (360.0 b)  TX bytes:4426 (4.3 KiB)   
              Interrupt:40 Base address:0x6000   
      
   lo        Link encap:Local Loopback   
              inet addr:127.0.0.1  Mask:255.0.0.0   
              inet6 addr: ::1/128 Scope:Host   
              UP LOOPBACK RUNNING  MTU:16436  Metric:1   
              RX packets:8 errors:0 dropped:0 overruns:0 frame:0   
              TX packets:8 errors:0 dropped:0 overruns:0 carrier:0   
              collisions:0 txqueuelen:0   
              RX bytes:440 (440.0 b)  TX bytes:440 (440.0 b)   
      
   [root@eris ~]# route -n   
   Kernel IP routing table   
   Destination     Gateway         Genmask         Flags Metric Ref    Use   
   Iface   
   0.0.0.0         192.168.1.13    0.0.0.0         UG    5      0        0 eth0   
   169.254.0.0     0.0.0.0         255.255.0.0     U     5      0        0 eth0   
   192.168.1.0     0.0.0.0         255.255.255.192 U     5      0        0 eth0   
   [root@eris ~]# cat /etc/resolv.conf   
   # Dynamic resolv.conf(5) file for glibc resolver(3) generated by   
   resolvconf(8)   
   #     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN   
   nameserver 71.243.0.12   
   nameserver 68.237.161.12   
   [root@eris ~]#   
      
   169.254.0.0 is "link-local", and the two entries in resolv.conf are my   
   ISP's DNS.  I ran the same commands under Fedora and CentOS, but I think   
   those are irrelevant as those have only wireless connectivity.   
      
   What may be relevant is that for a while earlier today, using Mageia's   
   wired connection, attempts to ping local hosts were completely   
   successful, while attempts to ping remote hosts (e.g. www.google.com)   
   reported around 65-70% packet loss.   
      
   > No idea what "cannot find my router's ip" means.   
      
   Even when 'ping' returns results as in the previous paragraph, a web   
   browser times out when I point it to http://192.168.1.13 which is the   
   router's own IP address, changed by me from 192.168.1.1 long ago.  When   
   I try to access that address from a system with a working 'net   
   connection, that immediately displays my router's main menu.  There /is/   
   an entry for it in /etc/hosts.   
      
   The solution is probably something that would be obvious to anyone with   
   more experience.  Well, at least I have one distro I can use for 'net   
   access and coursework while I try to set up the others.   
      
   Adam   
   --   
   Registered Linux User #536473   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)