On Feb 24, 2014 3:07 PM, "John Jason Jordan" <[email protected]> wrote: > > On Mon, 24 Feb 2014 01:03:38 -0800 > Bill Barry <[email protected]> dijo: > > >On Sun, Feb 23, 2014 at 10:56 PM, John Jason Jordan > ><[email protected]> wrote: > >> > >> At this point the Linksys is connected to nothing and powered off. > >> It's going to have to stay that way for the time being, as I don't > >> have time to deal with a messed up network right now. I can live > >> without the Linksys, but not without an internet connection. > > >There should not be too many things to configure. For your > >consideration here are a few. > > > >1) The IP address of the Linksys is set in the Admin and should be an > >address on the D-Link network that is not already used. > >2) Configure the Default Gateway of the Linksys to be the address of > >the D-Link. > >3) Turn off/ Disable the WAN on the Linksys if there is a setting to > >do that. 4) Set the Static DNS of the Linksys to be the address of the > >D-Link 5) Partition the DHCP space so that the addresses the D-Link > >gives out do not overlap the addresses the Linksys gives out. > >6) Change the SSID > > Couldn't work on it any more yesterday because I had an early exam > today. Now I am home and the exam is over, so I decided to revisit this > mess. > > I started by putting my spare Linksys back in the closet and plugging > the old one back in. This one had the name JJJ and password set. After > I plugged it in I grabbed the phone, and it connected straight off. So > did the laptop. However, I am worried because neither the phone or the > laptop prompted me for the password, although both display a padlock on > the icon. I'm pretty sure I entered the password at one time or another > on both devices, so maybe they saved it and connected automatically > without prompting me. Still, I want to double check that the password > is set in the Linksys. > > And that's where strange things happen. While it appears to be working > fine, I cannot get into its admin page with Firefox. The ifconfig > command now returns: > > eth0 Link encap:Ethernet HWaddr 00:90:f5:ef:f2:59 > inet6 addr: fe80::290:f5ff:feef:f259/64 Scope:Link > UP BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:224 errors:0 dropped:12 overruns:0 frame:0 > TX packets:89 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:48950 (48.9 KB) TX bytes:12754 (12.7 KB) > > eth1 Link encap:Ethernet HWaddr 00:23:54:8c:65:20 > inet addr:192.168.0.126 Bcast:192.168.0.255 > Mask:255.255.255.0 inet6 addr: fe80::223:54ff:fe8c:6520/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:55497133 errors:0 dropped:0 overruns:0 frame:0 > TX packets:74416205 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:8725814863 (8.7 GB) TX bytes:65815244794 (65.8 GB) > > 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:65536 Metric:1 > RX packets:788901 errors:0 dropped:0 overruns:0 frame:0 > TX packets:788901 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:70046669 (70.0 MB) TX bytes:70046669 (70.0 MB) > > wlan0 Link encap:Ethernet HWaddr 00:c2:c6:00:1e:1e > inet addr:192.168.0.147 Bcast:192.168.0.255 > Mask:255.255.255.0 inet6 addr: fe80::2c2:c6ff:fe00:1e1e/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:37562 errors:0 dropped:2 overruns:0 frame:0 > TX packets:11214 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:2950545 (2.9 MB) TX bytes:1381951 (1.3 MB) > > Now, there are more strange things about this. The first in the list, > eth0, shows no ip address, but does show an inet6 address, where the > second one, eth1, shows the reverse - an ip address but no inet6 > address. This is just a guess from a dummy here, but does my laptop > connect to both via different eth numbers? That would explain why I > have both an eth0 and an eth1. > > And I determined that wlan0 does not appear unless the laptop is > actually connected to the Linksys. That's why it did not appear with > the ifconfig command before. (Duh!) > > So now all I need to do is get into the admin page for the Linksys to > make sure that the password is set. I tried 1.1 (the default it shipped > with, 0.179 (the address it is connected to in the D-Link) and 0.147 > (the address that the D-Link gives for it when connected to the > laptop. None of them work. Do I have to disconnect it from the D-Link > and then use a direct cable to the laptop in order to get into it from > the laptop? Last time I did this the whole network came down. >
While not strictly necessary, the easiest way to do this is too connect directly from the laptop to the Linksys until you get it configured correctly. I don't know how it could bring down your network but I guess you should be prepared. _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
