[Forseti]

Hi,

I posted here before regarding a problem with my router... I now have the password to access the CLI by telnetting to my router.

I can get in, but this CLI commands throws me off. All I want to do is configure my router so it allows my PB (which uses Airport) to host servers (such as Carracho, Snapperhead) and connect to battle.net.

Can anyone help me with the commands?

I got the link to the commands manual but I can't make anything out of it...

Here it is:
http://www.cisco.com/univercd/cc/td/...cl.htm#1090663


Thanks.

[Forseti]

Ok I found information on opening ports for access to b.net behind a firewall:

http://www.chebucto.ns.ca/~rakerman/...-battlenet.txt

But it doesn't tell WHAT commands I need to input to enable it.

I searched the internet for an hour on PRACTICAL examples but all I get is unnecesarily complicated garbage... why do they have to complicate it.

Can anyone help me with the commands?

According to the above documents, all I need to do is:

"You must open port 6112 through port 6119, and 4000 to receive inbound and
outbound TCP and UDP packets in your Proxy/Firewall software."

That, and how to host servers (like Snapperhead, Carracho).

Thanks again.

[ghporter]

Is the format of the command examples in the manual the big problem? They're in a fairly standard form for console-type commands called the Backus-Nauer Form or BNF.

For example, this command definition:

Code:
static [(internal_if_name, external_if_name)] {tcp|udp} {global_ip|interface} global_port local_ip local_port [netmask mask]

...means that when you issue the "static" command, you MAY include a non-empty list of internal and external names, 0 or more TCP OR UDP commands (bold in the manual indicates command names), 0 or more global_ip addresses OR interface commands, and an optional netmask command, which must be followed by a netmask.

This is, as you note far more complex than it absolutely needs to be, but that's the way Cisco does things. They have very expensive classes in how to use their configuration language, and the sponsor certifications for people who master it. It's supposed to be hard, because it's very powerful. It is overkill for a small office product, though, and that's what you've run into.

My advice is to read the manual very thoroughly, and find a good BNF reference (I found over 200 hits on the phrase "Backus Nauer Form") to keep handy while you read.

[Forseti]

Thanks for the reply.

I was thinking it was a global language for routers and that someone here knew how to issue these commands.
I don't feel like reading all of it, I'm just an ordinary user... I just want it to WORK, not spend time making something work.
If I had bought AEBS perhaps it would have been much easier.. (I didn't buy this router, I found it in my house).

Thanks in any case.

[ghporter]

Actually there are a LOT of routers and wireless routers available that are both much simpler to configure and use than Cisco products, and MUCH less expensive-I bought a wired router not long ago that cost $28.76-with a $20 rebate! With tax I spent less than $12 after the rebate! (Ok, I'm a little smug about it.) You can get some wireless routers for around $50 if you pay attention to sales and shop around. To my mind, it's worth the cost of buying a new, consumer level router just to be able to figure the darn thing out by yourself.

[kampl]

You have to bear with me on this one as I do not do a lot of PAT or NAT on a regular basis.

You'll need things similar to the following:

nat (inside) 1 0.0.0.0 0.0.0.0
global (outside) 1 interface

The above PATs all outbound traffic from the trusted network to the IP address of the public interface. This assumes you have defined your interfaces already.

static (inside,outside) tcp interface ftp x.x.x.x ftp

Something like that should forward all FTP requests destined to your public IP address to your internal host (x.x.x.x) FTP server port. From there you need an access-list allowing traffic to the server.

access-list inbound permit any host x.x.x.x eq 21

and apply that acess-list to an interface.....

access-group inbound in interface outside

Those are the basics of trying to get traffic to flow through a PIX using private and public addresses. I can help you out to a degree if you need more info than this. Sorry about the poor formating, getting used to the interface still. I used a PIX as an example thinking that's what you have, IOS is a bit easier to do this with actually.

On a side note, if you're going to ditch the box let me know. I may have the resources to purchase it from you at a reasonable price.