[PLUG] Belkin N900 Not Seen at 192.168.2.1

Mike C. mconnors1 at gmail.com
Sun Aug 11 21:36:17 UTC 2013


"After many months I'm finally setting up the Belkin Advance N900 wireless
router. It's connected via a cat5 cable directly to my laptop. The default
IP address for the Belkin is 192.168.2.1"

Rich - Can you ping and get a response from the ip address of the Belkin.
If not, and you're directly connected to it, you must have an ip address on
the same subnet. Also, which port of the Belkin device are you connected
to? Hopefully, one of the LAN switch ports. If it responds to a ping, then
try "telnet 192.168.2.1 80". That will tell you whether or not you connect
to the device via http in the event some configuration setting has disabled
that ability.


On Sun, Aug 11, 2013 at 10:54 AM, <plug-request at lists.pdxlinux.org> wrote:

> Send PLUG mailing list submissions to
>         plug at lists.pdxlinux.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://lists.pdxlinux.org/mailman/listinfo/plug
> or, via email, send a message with subject or body 'help' to
>         plug-request at lists.pdxlinux.org
>
> You can reach the person managing the list at
>         plug-owner at lists.pdxlinux.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of PLUG digest..."
>
>
> Today's Topics:
>
>    1. Default Route Lost When System Is Rebooted (Rich Shepard)
>    2. Re: Default Route Lost When System Is Rebooted [RESOLVED]
>       (Rich Shepard)
>    3. Re: Ownerships and permissions mess (Richard England)
>    4. Re: Need 32-bit Debian based user (wes)
>    5. Belkin N900 Not Seen at 192.168.2.1 (Rich Shepard)
>    6. Re: Belkin N900 Not Seen at 192.168.2.1 (Dale Snell)
>    7. Re: Belkin N900 Not Seen at 192.168.2.1 (Russell Johnson)
>    8. Re: Belkin N900 Not Seen at 192.168.2.1 (Fred James)
>    9. Re: Belkin N900 Not Seen at 192.168.2.1 (Rich Shepard)
>   10. Re: Belkin N900 Not Seen at 192.168.2.1 (Fred James)
>   11. Re: Belkin N900 Not Seen at 192.168.2.1 (Rich Shepard)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 10 Aug 2013 12:54:40 -0700 (PDT)
> From: Rich Shepard <rshepard at appl-ecosys.com>
> Subject: [PLUG] Default Route Lost When System Is Rebooted
> To: plug at pdxlinux.org
> Message-ID:
>         <alpine.LNX.2.00.1308101251070.17784 at salmo.appl-ecosys.com>
> Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
>
>    Last week I discovered that the default route for eth0 on the Sony Vaio
> went AWOL so I added it back. However, when the laptop was shut down and
> rebooted the default route was again missing.
>
>    Has anyone ideas on what might remove the default route when the system
> is
> shut down? I've not seen this happen before and the only changes were
> upgraded packages such as bind, php, and openssl.
>
> Rich
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 10 Aug 2013 13:12:27 -0700 (PDT)
> From: Rich Shepard <rshepard at appl-ecosys.com>
> Subject: Re: [PLUG] Default Route Lost When System Is Rebooted
>         [RESOLVED]
> To: plug at pdxlinux.org
> Message-ID:
>         <alpine.LNX.2.00.1308101309030.17784 at salmo.appl-ecosys.com>
> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
>
> On Sat, 10 Aug 2013, Rich Shepard wrote:
>
> >   Has anyone ideas on what might remove the default route when the system
> > is shut down? I've not seen this happen before and the only changes were
> > upgraded packages such as bind, php, and openssl.
>
>    Please accept my apologies for cluttering your mailbox on such a nice
> summer Saturday afternoon. After posting my message I went back to looking
> for the source of the problem and found it; naturally, after sending the
> message, not before.
>
>    Apparently, when checking configuration files after upgrading packages I
> must have inadvertently changed one digit in the IP address of the default
> gateway in /etc/rc.d/rc.inet1.conf. Sigh. As there was no valid default
> gateway in the configuration file none was established when the system was
> rebooted.
>
> Mea culpa,
>
> Rich
>
>
>
> ------------------------------
>
> Message: 3
> Date: Sat, 10 Aug 2013 14:52:16 -0700
> From: Richard England <rlengland at frontier.com>
> Subject: Re: [PLUG] Ownerships and permissions mess
> To: plug at lists.pdxlinux.org
> Message-ID: <5206B610.2030307 at frontier.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 08/10/2013 08:40 AM, Michael Rasmussen wrote:
> > On Sat, Aug 10, 2013 at 09:30:56AM -0500, David Fleck wrote:
> >>> On 08/08/2013 06:47 PM, John Jason Jordan wrote:
> >>>> Is there a way to do a ls command and have it sort by date of
> creation?
> >> Try
> >>
> >>     ls -lrt
> > Creation?
> >
> > That isn't available in contemporary *nix, including Linuxes.
> >
> >      ctime  https://en.wikipedia.org/wiki/Stat_(Unix)
> >
> >      ctime originally meant creation time,[8] however it has since been
> >      used almost always to refer to change time. It is updated any time
> >      file content changes (together with mtime), and also by changes in
> >      metadata such as file permissions, file ownership, and creation and
> >      deletion of hard links. In some implementations, ctime is affected
> by
> >      renaming a file (both original Unix and modern Linux tend to do
> this).
> >
> >      Unlike atime and mtime, ctime cannot be set to an arbitrary value
> >      with utime() (as used e.g. by touch). Instead, when utime() is used,
> >      the ctime value is set to the current time.
> >
> > And this is confirmed by `man 2 stat`
> >
> > All of these system calls return a stat structure, which contains the
> following fields:
> >
> >             struct stat {
> >                 dev_t     st_dev;     /* ID of device containing file */
> >                 ino_t     st_ino;     /* inode number */
> >                 [ other stuff snipped ]
> >                 time_t    st_atime;   /* time of last access */
> >                 time_t    st_mtime;   /* time of last modification */
> >                 time_t    st_ctime;   /* time of last status change */
> >             };
> >
> >
>
> Fedora 19 provides the following 'ls' command
>
> ls -ltcr
>
>
> -r reverse  (newest last in the list)
>
>   -c     with  -lt:  sort by, and show, ctime (time of last modification
> of file
>           status information) with -l: show ctime and  sort  by name
> otherwise:
>           sort by ctime, newest first
>
>
>
> ------------------------------
>
> Message: 4
> Date: Sun, 11 Aug 2013 10:08:16 -0700
> From: wes <plug at the-wes.com>
> Subject: Re: [PLUG] Need 32-bit Debian based user
> To: "Portland Linux/Unix Group" <plug at lists.pdxlinux.org>
> Message-ID:
>         <CAA1wLO=
> T0-s9RYd7z2mnQNB0obSo3kXBinEFi7kgntr-UJLZrA at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> >
> >
> >
> > Now, of course there is the source file. But wouldn't it need the same
> > dependencies?
> >
> >
> it would, but may offer more information about what's missing. it does
> specify version of the given packages. your system could perhaps have
> different, incompatible versions installed.
>
> -wes
>
>
> ------------------------------
>
> Message: 5
> Date: Sun, 11 Aug 2013 10:19:48 -0700 (PDT)
> From: Rich Shepard <rshepard at appl-ecosys.com>
> Subject: [PLUG] Belkin N900 Not Seen at 192.168.2.1
> To: plug at pdxlinux.org
> Message-ID: <alpine.LNX.2.00.1308111015330.355 at salmo.appl-ecosys.com>
> Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
>
>    After many months I'm finally setting up the Belkin Advance N900
> wireless
> router. It's connected via a cat5 cable directly to my laptop. The default
> IP address for the Belkin is 192.168.2.1. When I enter that address
> (without
> the http protocol preceeding it, per the Belkin users manual) firefox
> responds by telling me that it cannot establish a connection to that
> server.
>
>    Opera also reports it cannot connect to a server at that IP address.
>
>    Is there anything obvious I've missed? If not, I will wait for next
> week's
> clinic and bring Belkin N900, laptop, cable, and myself there for help.
>
> Rich
>
>
>
> ------------------------------
>
> Message: 6
> Date: Sun, 11 Aug 2013 10:36:28 -0700
> From: Dale Snell <ddsnell at frontier.com>
> Subject: Re: [PLUG] Belkin N900 Not Seen at 192.168.2.1
> To: Rich Shepard <rshepard at appl-ecosys.com>, Portland Linux/Unix Group
>         <plug at lists.pdxlinux.org>
> Message-ID: <20130811103628.5d6b7691 at zothique.localnet>
> Content-Type: text/plain; charset=US-ASCII
>
> On Sun, 11 Aug 2013 10:19:48 -0700 (PDT)
> Rich Shepard <rshepard at appl-ecosys.com> wrote:
>
> >    After many months I'm finally setting up the Belkin Advance N900
> > wireless router. It's connected via a cat5 cable directly to my
> > laptop. The default IP address for the Belkin is 192.168.2.1. When I
> > enter that address (without the http protocol preceeding it, per the
> > Belkin users manual) firefox responds by telling me that it cannot
> > establish a connection to that server.
> >
> >    Opera also reports it cannot connect to a server at that IP
> > address.
> >
> >    Is there anything obvious I've missed? If not, I will wait for
> > next week's clinic and bring Belkin N900, laptop, cable, and myself
> > there for help.
>
> Try specifying the http:// protocol anyway.  You're going to be
> connecting to an html page, so it can't hurt.  I think Belkin is
> expecting the browser to prepend the protocol specifier automatically.
> In these suspicious days, they may not do that anymore.
>
> --Dale
>
> --
> "A little paranoia is a good thing."  --me
>
>
> ------------------------------
>
> Message: 7
> Date: Sun, 11 Aug 2013 10:36:55 -0700
> From: Russell Johnson <russ at dimstar.net>
> Subject: Re: [PLUG] Belkin N900 Not Seen at 192.168.2.1
> To: Rich Shepard <rshepard at appl-ecosys.com>,    Portland Linux/Unix Group
>         <plug at lists.pdxlinux.org>
> Message-ID: <85FB58FD-A19A-4584-8891-FB7EDB7740D2 at dimstar.net>
> Content-Type: text/plain;       charset=us-ascii
>
> On Aug 11, 2013, at 10:19, Rich Shepard <rshepard at appl-ecosys.com> wrote:
>
> > me that it cannot establish a connection to that server.
>
> Do you have a network address in that network?  What's the output of
> 'ifconfig -a'?
>
> ------------------------------
>
> Message: 8
> Date: Sun, 11 Aug 2013 13:36:45 -0400
> From: Fred James <fredjame at fredjame.cnc.net>
> Subject: Re: [PLUG] Belkin N900 Not Seen at 192.168.2.1
> To: Rich Shepard <rshepard at appl-ecosys.com>,    Portland Linux/Unix Group
>         <plug at lists.pdxlinux.org>
> Message-ID: <5207CBAD.5030109 at fredjame.cnc.net>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Rich Shepard wrote:
> >     After many months I'm finally setting up the Belkin Advance N900
> wireless
> > router. It's connected via a cat5 cable directly to my laptop. The
> default
> > IP address for the Belkin is 192.168.2.1. When I enter that address
> (without
> > the http protocol preceeding it, per the Belkin users manual) firefox
> > responds by telling me that it cannot establish a connection to that
> server.
> >
> >     Opera also reports it cannot connect to a server at that IP address.
> >
> >     Is there anything obvious I've missed? If not, I will wait for next
> week's
> > clinic and bring Belkin N900, laptop, cable, and myself there for help.
> >
> > Rich
> >
> Have you tried
>      http://192.168.2.1
> ??? (every router I have ever had ... not too many, by the way ... has
> required the http://)
> Regards
> Fred James
>
>
>
> ------------------------------
>
> Message: 9
> Date: Sun, 11 Aug 2013 10:52:05 -0700 (PDT)
> From: Rich Shepard <rshepard at appl-ecosys.com>
> Subject: Re: [PLUG] Belkin N900 Not Seen at 192.168.2.1
> To: Portland Linux/Unix Group <plug at lists.pdxlinux.org>
> Message-ID: <alpine.LNX.2.00.1308111049200.355 at salmo.appl-ecosys.com>
> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
>
> On Sun, 11 Aug 2013, Dale Snell wrote:
>
> > Try specifying the http:// protocol anyway.  You're going to be
> connecting
> > to an html page, so it can't hurt. I think Belkin is expecting the
> > browser to prepend the protocol specifier automatically. In these
> > suspicious days, they may not do that anymore.
>
> Dale,
>
>    I did use http://192.168.2.1 first. Makes no difference. And, both
> firefox
> and opera pre-pend the protocol.
>
>    After searching for more insights on the Web and futzing here I've
> decided
> that the Belkin just does not want to work here. I reset it, tried
> different
> ethernet ports, tried from the workstation, etc. No previous wireless
> access
> point/router was this recalcitrant.
>
>    So, I've ordered an Asus N900 unit.
>
> Rich
>
>
>
> ------------------------------
>
> Message: 10
> Date: Sun, 11 Aug 2013 13:51:22 -0400
> From: Fred James <fredjame at fredjame.cnc.net>
> Subject: Re: [PLUG] Belkin N900 Not Seen at 192.168.2.1
> To: Portland Linux/Unix Group <plug at lists.pdxlinux.org>
> Message-ID: <5207CF1A.1090603 at fredjame.cnc.net>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Rich Shepard wrote:
> >     After many months I'm finally setting up the Belkin Advance N900
> wireless
> > router. It's connected via a cat5 cable directly to my laptop. The
> default
> > IP address for the Belkin is 192.168.2.1. When I enter that address
> (without
> > the http protocol preceeding it, per the Belkin users manual) firefox
> > responds by telling me that it cannot establish a connection to that
> server.
> >
> >     Opera also reports it cannot connect to a server at that IP address.
> >
> >     Is there anything obvious I've missed? If not, I will wait for next
> week's
> > clinic and bring Belkin N900, laptop, cable, and myself there for help.
> >
> > Rich
> >
> Have you tried
>       http://192.168.2.1
> ??? (every router I have ever had ... not too many, by the way ... has
> required the http://)
> Regards
> Fred James
>
> Oops ... I amend ... I just connected to my old Linksys without the http://
> Regards
> Fred James
>
>
> ------------------------------
>
> Message: 11
> Date: Sun, 11 Aug 2013 10:54:32 -0700 (PDT)
> From: Rich Shepard <rshepard at appl-ecosys.com>
> Subject: Re: [PLUG] Belkin N900 Not Seen at 192.168.2.1
> To: Portland Linux/Unix Group <plug at lists.pdxlinux.org>
> Message-ID: <alpine.LNX.2.00.1308111053161.355 at salmo.appl-ecosys.com>
> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
>
> On Sun, 11 Aug 2013, Russell Johnson wrote:
>
> > Do you have a network address in that network?  What's the output of
> 'ifconfig -a'?
>
> Russell,
>
>    No, I don't. But, I can reach external web servers via their IP address
> even though I'm not on their network.
>
>    ifconfig -a shows eth0 UP and RUNNING.
>
> Rich
>
>
>
> ------------------------------
>
> _______________________________________________
> PLUG mailing list
> PLUG at lists.pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug
>
>
> End of PLUG Digest, Vol 107, Issue 19
> *************************************
>



More information about the PLUG mailing list