Guess who managed to totally screw up his 678 today?

[Goldom]

But guess what? It only took me 3 hours to figure out how to re-setup the CBOS to get it back working. I didn't, however, manage to do what I was trying to in the first place, which is to get the 678's NAT to forward every port on to my BEFSR41, so that it's NAT could properly distribute them. That didn't work out so well. But I at least got it back to working as well as it did before, now. On that note though, can anyone explain how to do that?

[bemildred]

1. Turn NAT off completely on the Cisco box.

Tell the LinkSys to get a DHCP address on the WAN side from the Cisco.
Tell your internal machines to get DHCP addresses from the LinkSys.

[Goldom]

2. Disabling the 678's NAT

was what caused it to stop working entirely in the first place. I had assumed it would just all go through then, but it didn't... maybe I'm missing that 2nd step, how do you "Tell the LinkSys to get a DHCP address on the WAN side from the Cisco"?

[bemildred]

3. The Cisco is a DSL Modem/Router, it should therefore route.

It seems to require a separate hub to handle multiple machines,
hence you seem to have got a second router with a built in hub.
I'm using guess and google here, but that's what I'm guessing.

You don't need it to do NAT, only the LinkSys needs to do NAT.
I don't have the manuals, I have different hardware, and I would
not touch a Cisco with a pole unless forced to, but nevertheless
I can tell you that all the Cisco needs to do is forward traffic
both ways.

The hardware I have provides web pages accessible via

http://172.16.0.254 (DSL Modem)

and

http://192.168.0.1 (Dlink Router/Hub)

And these allow all configuration to be done as I stated. The
678 seems to use a text mode configuration interface. It would seem
you just type enable/disable nat to turn it on/off, set up DHCP,
etc. I would guess from the dialog so far that you have routing
issues and the NAT works around them, but that's just a guess.

[Goldom]

5. I like that title.

but anyway, I dunno why, but it doesn't properly.

I don't know why I can't get it to work without the NAT, but I got it to work finally even with both NATs on - and in case anyone else is searching around the internet trying to figure it out, here it is.

In 678's connection-
set nat entry delete all
set nat entry add 10.0.0.4 0 icmp
set nat entry add 10.0.0.4 23 tcp
set nat entry add 10.0.0.4 113 tcp
(these 3 are cause, for some reason, by default they were all being shown as open, even though my other router should not have been forwarding them. So I had the 678 forward them so this non-existant instead. There's prolly a cleaner way, but it worked)
set nat entry add 10.0.0.2
(that sends everything but those 3 on to the router)
then in router, just forward the few ports you need into 192.168.1.xxx

What my problem was is I was trying to get the 678 to forward to 192.168.1.1, not realizing that that is what the router calls itself on the inside, and to the 678, it is 10.0.0.2 instead. Intriguingly, the router's set up page can be reached from typing in either 192.168.1.1 or 10.0.0.2. How that works I'm not entirely sure, but tis ok by me.

[bemildred]

6. Glad you got it working.

For what it's worth, port 23 is telnet and port 113 is the
auth(orization) service, so it may have had them open for the
admin login stuff it does, in some form.

[Goldom]

7. I noticed those from running that thing at

grc.com that checks common ports... notice that those two were open, as well as responding to pings on 0 icmp... that may indeed be why, but I also know that before I totally screwed up my modem yesterday, they used to all be closed.

Let me tell you though, I've never been so happy to fail a test as when I saw that the ports I was trying to get were finally open and available to be hacked into! (well, that part not so much, but one implies the other, so eh.)

[bemildred]

4. Routing issues:

The routing should look like this:

(Big Fuzzy Cloud -- The INTERNET)
|
DSL Concentrator at Phone Co,
|
Address negotiated by PPOE
|
Address Negotiated by PPOE
|
DSL Modem (Cisco)
|
Inside DSL modem address (fixed? set by config?)
|
DHCP address obtained from DSL Modem
(LinkSys Outside address)
|
LinkSys Router
|
LinkSys Inside address (192.168.1.1 Password: (blank/admin))
|
Various inside machines configured with DHCP