Agi,

Did you get this working at all?

I have the same situation. Two subnets and want my VPN users to access both 
subnets.

Regards,

Chuck

From: Agi Subagio [mailto:[email protected]]
Sent: Tuesday, February 10, 2009 3:00 AM
To: [email protected]
Subject: Re: [pfSense Support] ip aliases for LAN interface

i'm using pfSense 1.2-RELEASE.

i try to add this line:
    <shellcmd>ifconfig sk0 inet 172.16.1.252 netmask 255.255.255.0 
alias</shellcmd>
    </system>
    <interfaces>
        <lan>
            <if>sk0</if>
            <ipaddr>172.16.4.252</ipaddr>
            <subnet>24</subnet>
            <media/>
            <mediaopt/>
            <bandwidth>100</bandwidth>
            <bandwidthtype>Mb</bandwidthtype>
            <bridge/>
        </lan>

and the result look like this:
sk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=b<RXCSUM,TXCSUM,VLAN_MTU>
        inet 172.16.4.252 netmask 0xffffff00 broadcast 172.16.4.255
        inet6 fe80::211:2fff:fedb:f729%sk0 prefixlen 64 scopeid 0x2
        inet 172.16.1.252 netmask 0xffffff00 broadcast 172.16.1.255
        ether 00:11:2f:db:f7:29
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active

but i still can't ping vpn client from LAN-2 (172.16.1.0/24) and can't ping the 
ip 172.16.1.252 also.

if i upgrade to pfSense-Full-Update-2.0-ALPHA-ALPHA-20090208-0149.tgz, what 
will happen to my existing configuration?

Chris Buechler wrote:

On Mon, Feb 9, 2009 at 5:09 AM, Agi Subagio 
<[email protected]><mailto:[email protected]> wrote:



I want to make VPN box with pfSense.



I have two office LAN:

LAN-1: 172.16.4.0/24

LAN-2: 172.16.1.0/24



and roadwarrior vpn client use 172.16.100.0/24.



In pfSense's LAN interface I use 172.16.4.252/24 and I can ping vpn client

from LAN-1 vice versa.

How to add another ip alias in pfSense's LAN interface so I can ping vpn

client from LAN-2?







Generally not a good practice, but if you must:

http://doc.pfsense.org/multiple-subnets-one-interface-pfsense.pdf


Reply via email to