EFW Support

Support => Installation Support => Topic started by: josh.smith@eagleview.com on Thursday 19 February 2009, 08:11:59 am



Title: network configuration issue, behind nat
Post by: josh.smith@eagleview.com on Thursday 19 February 2009, 08:11:59 am
Greetings, Im currently using a ASA5505 as my home security appliance but I am noticing severe throttling when I download anything.

I have taken an older box and installed the endian firewall software v2.2

When configuring the green and red interfaces what my plan was to do is assign 2 IPs within the network, one green and one red and use the green interface as the new gateway for my home computers (kids, wife and so forth) This will give me traffic shapping with the additional benefits of dans guardian and such.

My problem is that when I am trying to specify the 2nd ip address to the red interface its saying its on the network and fais to assign.


interface = ip / subnet / gateway

eth0 = 10.10.10.7 /255.255.0.0
eth1 = 10.10.10.9 /255.255.0.0 / 10.10.10.1

is this possible or is there something I am doing wrong? should the interface IP's be in a more defined subnet scheme?


Title: Re: network configuration issue, behind nat
Post by: biased99 on Tuesday 26 May 2009, 08:25:05 pm
Is it just me, or do both these NICs appear to be on the same subnet?

If so, then yes you will have issues.

As an example, I run an Endian box on my Network in the following configuration:

1) Green: 192.168.1.0/24

2) Orange: 10.0.0.0/24

3)Red: 192.168.2.0/24

All routing works as it should, as all 3 NICs are in different Networks.

HTH.


Title: Re: network configuration issue, behind nat
Post by: necomputer on Sunday 12 July 2009, 04:28:40 pm
biased99 that is how I would configure it because I can definately see a problem with the user's current config.


Title: Re: network configuration issue, behind nat
Post by: davvidde on Monday 13 July 2009, 08:11:20 am
255.255.0.0 (or /16) is a class B netmask so, the net portion 10.10.x.y is assigned on eth0 and eth1 and also an alias for eth1: the result is the same network for all interfaces which cannot works: here is the error. Use a more restrictive netmask such as 255.255.255.0 (or /24).