Welcome, Guest. Please login or register.
Did you miss your activation email?
Saturday 14 December 2024, 02:42:38 am

Login with username, password and session length

The Latest Endian Firewall is now available for download HERE
14261 Posts in 4377 Topics by 6517 Members
Latest Member: Sandro
Search:     Advanced search
+  EFW Support
|-+  Support
| |-+  General Support
| | |-+  Alias addresses do not get created correctly for the red interface
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: Alias addresses do not get created correctly for the red interface  (Read 15573 times)
Shane_08
Jr. Member
*
Offline Offline

Posts: 5


« on: Friday 17 October 2008, 12:51:49 am »

Hi

I have installed Endian 2.2 RC3 and am having trouble adding aliases to the red interface. The red interface connects via PPPoE which works fine however I have an additional 6 ip's which I would like to add to the red interface.

I have tried adding these under:
Network
Interfaces
Edit (main link)
Add additional addresses
123.123.123.123/32

When I try to update the link I receive an error:
The RED IP address or network mask "123.123.123.123/32" is not correct.
I have also tried adding this using the format 123.123.123.123/255.255.255.255 which produces the same error.

Shouldn't individual IP's have a netmask of 32 or 255.255.255.255?

Other netmasks get added correctly however the routing doesn't seem to work (I am guessing this is because of the incorrect netmask).

Can anyone help me with this as I have looked all through the forums without any luck?  Huh
Logged
smoke_007
Jr. Member
*
Offline Offline

Posts: 5


« Reply #1 on: Thursday 16 April 2009, 06:51:58 am »

Hi Shane,

I had the exact same problem with version 2.2 RC3.

I dug around a little and found that the settings for the uplink are stored in file "settings" at /var/efw/uplinks/main/ on my box.  I found that I could manually edit the file in something nice like WinSCP and get the /32 CIDR or 255.255.255.255 subnet to work.

Here is my file for an example.

Code:
DEFAULT_GATEWAY=192.168.0.10
DNS2=172.22.6.250
DNS1=172.22.6.251
ENABLED=on
MTU=
AUTOSTART=on
BACKUPPROFILE=
RED_DEV=eth2
RED_ADDRESS=192.168.0.82
MANAGED=on
ONBOOT=on
MAC=
CHECKHOSTS=
RED_NETADDRESS=192.168.0.82
RED_NETMASK=255.255.255.255
RED_TYPE=STATIC
RED_BROADCAST=192.168.0.82
RED_IPS=192.168.0.82/32,192.168.0.83/32,192.168.0.84/32,192.168.0.85/32,192.168.0.86/32,192.168.0.90/32,192.168.0.91/32,192.168.0.92/32,192.168.0.93/32,192.168.0.94/32,192.168.0.114/32,192.168.0.115/32,192.168.0.116/32,192.168.0.117/32,192.168.0.118/32
RED_CIDR=32

After you save the file and then go back in to the network setup wizard or uplink setup wizard, you'll see it's setup correctly.  Now, the problem is that Endian firewall still thinks it's setup wrong, so you can't make any changes or resave in the GUI wizard.  To make any changes, you'll have to do it manually to the settings file.

Now, the interesting part.  I took a closer look at how my old Linux firewall setup the network card alias settings and I found that it setup all the alias IPs with a /24 even though they were supposed to be /32.  My old setup has been working fine for a few years.  So, I tried setting up all the alias red IPs with a /24 in the GUI wizard and it works!!

Here is an example from my settings file that is currently working fine.

Code:
AUTOSTART=on
BACKUPPROFILE=
CHECKHOSTS=80.190.199.138,64.233.183.99,pool.ntp.org,www.google.com,www.yahoo.com,www.sf.net
DEFAULT_GATEWAY=192.168.0.10
DNS2=172.22.6.250
DNS1=172.22.6.251
ENABLED=on
MAC=
MTU=
ONBOOT=on
RED_ADDRESS=192.168.0.1
RED_BROADCAST=192.168.0.255
RED_CIDR=24
RED_DEV=eth2
RED_IPS=192.168.0.1/24,192.168.0.82/24,192.168.0.83/24,192.168.0.84/24,192.168.0.85/24,192.168.0.86/24,192.168.0.90/24,192.168.0.91/24,192.168.0.92/24,192.168.0.93/24,192.168.0.94/24,192.168.0.114/24,192.168.0.115/24,192.168.0.116/24,192.168.0.117/24,192.168.0.118/24
RED_NETADDRESS=192.168.0.0
RED_NETMASK=255.255.255.0
RED_TYPE=STATIC

You'll see I set 192.168.0.1 as my first RED IP because it made things more organized to me. 

I hope these examples might help someone...  Good luck!
Marc
Logged
mrkroket
Hero Member
*****
Offline Offline

Posts: 495


« Reply #2 on: Thursday 14 May 2009, 11:45:25 pm »

 I think you can't have a subnet with mask 32. This means that there is only one IP on the subnet, therefore it wont connect to any other computer (there is only one IP on the subnet, its IP).

If you want an interface with 6 IP's on the same LAN, the setup should be like:

192.168.0.1/24  <- Main RED IP

Additionals IP's:
192.168.0.2/24
192.168.0.3/24
192.168.0.4/24
192.168.0.5/24
192.168.0.6/24


If they are on different lans:
192.168.0.1/24  <- Main RED IP

Additionals IP's:
192.168.1.1/24
192.168.2.1/24
192.168.3.1/24
192.168.4.1/24
192.168.5.1/24
Logged
Pages: [1] Go Up Print 
« previous next »
Jump to:  

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