Welcome, Guest. Please login or register.
Did you miss your activation email?
Thursday 28 November 2024, 12:32:43 am

Login with username, password and session length

Visit the Official Endian Reference Manual  HERE
14261 Posts in 4377 Topics by 6517 Members
Latest Member: Sandro
Search:     Advanced search
+  EFW Support
|-+  Support
| |-+  Installation Support
| | |-+  network configuration issue, behind nat
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: network configuration issue, behind nat  (Read 20973 times)
josh.smith@eagleview.com
Jr. Member
*
Offline Offline

Posts: 1


« 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?
Logged
biased99
Jr. Member
*
Offline Offline

Posts: 3


« Reply #1 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.
Logged
necomputer
Full Member
***
Offline Offline

Posts: 15


« Reply #2 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.
Logged
davvidde
Full Member
***
Offline Offline

Gender: Male
Posts: 68


« Reply #3 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).
Logged
Pages: [1] Go Up Print 
« previous next »
Jump to:  

Page created in 0.094 seconds with 18 queries.
Powered by SMF 1.1 RC2 | SMF © 2001-2005, Lewis Media Design by 7dana.com