Hi Ryan,
I understand... hope you agree the proper way to do this is to define one VLAN
(ex. eth1.10) instead of an aliased subnet. The Firewall sub-tab supports
allowing traffic between LAN interfaces (ex. 1st and 2nd Internal Interface),
that is all you need to do. (a reboot is required aft
Hi Lonnie,
This particular customer has 3 different LAN subnets 2 of which run in the
same layer 2 switch. The alix device only has 3 interfaces. The pfsense
router had a second virtual address on one of the LAN ports allowing both
networks to communicate with it. I was hoping to replicate the set
Ryan,
Sorry, currently alias IP's are only for external interfaces.
It looks like that would be fairly easy to add since we have a
alias_interface() function in the network init.d/ .
But, can you explain why you need, or find this useful. It is clear for the
external interface, but not so muc
Thanks for the info Lonnie
The virtual address needs to be on an internal lan interface that is
separate from the external interface. Are internal interfaces supported?
-Ryan
On Thu, Jun 4, 2015 at 5:50 PM, Lonnie Abelbeck
wrote:
> Hi Ryan,
>
> AstLinux supports this for the External Interface
Hi Ryan,
AstLinux supports this for the External Interface(s) using static IPv4's:
--
## External Interface Alias (Virtual) IPv4 Addresses
## If EXTIP (or EXT2IP) is set, using a 'static' configuration, alias interfaces
## on EXTIF (or EXT2IF) may be defined creating $EXTIF:1, $EXTIF:2, etc. .
##
