DragonFly BSD
DragonFly users List (threaded) for 2010-07
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: Networking problem - Just how to do this?

From: mikel king <mikel.king@xxxxxxxxxxx>
Date: Tue, 20 Jul 2010 06:52:06 -0400

On Jul 19, 2010, at 11:45 PM, elekktretterr@exemail.com.au wrote:

The situation is like this:

DF Box is on a public IP -  - The box is connected to a switch,
and the switch is connected to the upstream router -

Now, I've also connected another router(Cisco ASA 5505) to the switch. Its
also got a public IP - - and the router will be used to establish
VPN connections to another network on the internet. The problem is I dont
have a "private network", the DF box is on a public IP.

So I aliased the network interface on the DF Box and gave it a private IP:

I'm kind of at loss as what to do next. Has anyone been in a similar
situation? Worst come worst i'll have to run another cable to the second
NIC on the DF Box and split the topology physically.


Do you have a second NIC in the DF box? The ASA5505 is a firewall security device and not a router therefore do not make the mistake in believing it will behave like a router. Cisco ASA's are persnickety devices and will only VPN from an insecure to a secure  interface. If your DF box had a second NIC that you could put on the ASA's secure interface (LAN) then you could VPN via the ASA. This is not optimal and only based on the assumption that you do not want to relocate the DF box completely behind the ASA which is the other option.

I hope that helps.

Mikel King
Senior Editor, BSD News Network
Columnist, BSD Magazine
6 Alpine Court,
Medford, NY 11763
o: 631.627.3055

[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]