All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: Cisco VPN Client + Cisco 800 + Firewall
Date: Thu, 21 Oct 2004 15:29:49 -0400	[thread overview]
Message-ID: <20041021192949.GA11650@bender.817west.com> (raw)
In-Reply-To: <1098385275.7ic0vxrrb5hc@mail.sapo.pt>

On Thu, Oct 21, 2004 at 08:01:15PM +0100, shore@sapo.pt wrote:
> Hi,
> 
> I don't know how to start, so I'll just start by showing how my network is
> build:
> 
> 
> 		Internet
> 		    |
> 		    |
> 		Cisco(800)(dsl modem/router)
> 		192.168.10.254
> 		    |
> 		    |
> 		192.168.10.1(eth0)
> 		Firewall
> 		192.168.0.50(eht1)
> 		    |
> 		    |
> 		LAN 192.168.0.0/24
> 
> 
> The Cisco is controled by the ISP, so I can't change any configuration on it,
> only if I ask them to. The Firewall is running squid also.
> 
> The ISP configured the Cisco modem/router to accept VPN connections from the
> internet with Cisco VPN client, and to attribute them a 10.0.0.0/8 range ip.
> The problem is I can't access the LAN from the VPN clients. I'm not an iptables
> master, but i've already searched everywhere for a solution and could't find
> one. Mostly, I think, because I didn't want to get rid of my Firewall script,
> it is doing a nice job so far.
> 
> Thanks

before i start parsing through 800 lines of firewall script, i gotta ask
this first--when you connect with the cisco vpn client out on the
internet--what shows up in the list of "secured routes?"  is it
192.168.0.0/24?  is it 0.0.0.0/0.0.0.0?  or is it 192.168.10.0/24?

-j

-- 
Jason Opperisano <opie@817west.com>


  reply	other threads:[~2004-10-21 19:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-21 19:01 Cisco VPN Client + Cisco 800 + Firewall shore
2004-10-21 19:29 ` Jason Opperisano [this message]
2004-10-27 11:23   ` shore
2004-10-27 20:15     ` Jason Opperisano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041021192949.GA11650@bender.817west.com \
    --to=opie@817west.com \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.