Is there a way to save the running config of the device and download it to a pc
(either windows or linux) before I overwrite 2.0.1 with 2.4.2 (I think that is
what is sitting on my system at work) so that I at least have a basis to
troubleshoot the thing and maybe use it to get the other one in place while I do
this. I don't want to lose net access for any extended period because my father
needs it to access work and we don't have dialup accounts (try downloading 10MB
files over modem, yech).
> You first need to download the firmware...something like
> nsrouter.c675.2.4.1.bin
>
> Here is a link to find it on Cisco's web site. You will probably need an
> account.
> http://www.cisco.com/cgi-bin/tablebuild.pl/600-v241?param=case3
>
> Second, log into your 675 with a telnet session.
>
> Third, type...
> cbos# tftp enable
>
> Fourth, tftp the image to the LAN IP on the 675 (10.0.0.1).
> In WinNT the command would be
> C:\> TFTP -i 10.0.0.1 PUT nsrouter.c675.2.4.1.bin
> (I am sorry, I am not familiar with any *NIX TFTP client so I included the
> Windows example.)
>
> Fifth, type...
> cbos# reboot
> (You do not need to type write before reboot.)
>
> I have done this with at least 60 675/678s and have never had a problem, even
> running this procedure from the outside.
>
> Gilbert
>
> At 01:47 AM 8/6/2001 -0700, you wrote:
>
> > OK, well the latest round of Red Code is now giving me more headaches at
> > home
> > than I care to deal with. My poor DSL router (Cisco 675 External DSL
> > router) is
> > going down every few hours and requires a power cycling to bring it back
> > up. It
> > is currently running CBOS 2.0.1 and I want to upgrade it to 2.4.1 (or
> > 2.4.2),
> > but since my experience with the duplicate of the modem (which I upgraded
> > from
> > NSOS 1.4 to CBOS 2.4.2) was, shall we say, less than successful (I can't get
> > the
> > config right to actually use it), I was wondering if anyone knew of what the
> > exact configuration of the modem should be to get it to work.
> >
> > I saw this site http://www.users.uswest.net/~rlutton/ADSL/indexJS.html and
> > used
> > the config he shows on the site, but the modem that I upgraded, while being
> > able
> > to connect to Qwest, is not working as an actual router. The wan light
> > finalizes solid green and the ethernet shows green with a blinking amber
> > activity light (as stuff happens on the net), but nothing actually can get
> > out
> > on the net through it. I've had experience with Qwest's so called
> > tech-support
> > and would rather see if someone else here had already gone through this
> > themselves.
> >
> > The DSL router is set up in PPP mode using DHCP and NAT for the machines in
> > my
> > house (10.0.0.x addresses inside).
> >
> > Any help/suggestions appreciated.
(text/plain)