Adding alias IP subnet to an interface or VLAN

In the PFsense docs it tells you to use the ‘alias’ option in the web interface… but this won’t work for routed (non-NAT) interfaces that require more than 1 subnet attached to them. To overcome this, I utilized this article:

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

In summary:

Log into the webGUI, and click Diagnostics -> Backup/Restore. Click the “Download configuration” button. Open the xml file downloaded in a text editor, like Notepad. Above the line, insert the following:

<shellcmd>ifconfig fxp0 inet 192.168.2.1 netmask 255.255.255.0 alias</shellcmd>

Replacing fxp0 with the name of the interface you’re using, and the IP and subnet mask as appropriate. You can find the name of the desired interface in the config file. For example, for LAN, see this portion of the config.

<interfaces> 
    <lan> 
        <if>fxp1</if>

This is showing the LAN interface as fxp1.

In order to add the alias without rebooting the whole firewall, SSH into the box and issue the shellcmd command manually:

ifconfig fxp0 inet 192.168.2.1 netmask 255.255.255.0 alias

Then edit /conf/config.xml manually using vi so next time the router reboots you don’t lose the subnet.

I did lose a subnet once when changing or add some interfaces through the GUI… so keep in mind when making interface changes that you may have to manually keep re-adding the subnets in the shell… I have not had an opportunity to find a work around for this.

Clean upgrade from SAM3 to SAM4 with playlist in-tact

SAM4 has a slightly different database format and filesystem layout than SAM3. You should not try an in-place upgrade, or bad things can happen. The best way to upgrade if you have a large or refined playlist, is to install SAM4 along side SAM3 and copy the playlist tables over. This way you can leave SAM3 running while you install and set up SAM4’s settings and encoders, then make a clean cutover without losing your audience.

1. First, install SAM4 in it’s own location, separate from SAM3. For example, c:\program files\spacial audio\SAMBC4

2. When launching SAM4 for the first time, you MUST define custom MySQL database settings. Change the default database name from SAMDB to SAMDB4

3. Dump your SAM3 playlist with the following command (mysql/bin must be in your path):

mysqldump -u root --database SAMDB --table songlist --table category --table categorylist --skip-extended-insert --complete-insert --no-create-db --no-create-info > SAM3_songs.sql

4. Import the playlist into SAM4:

mysql -u root SAMDB4 < SAM3_songs.sql

5. Now, press F5 on the SAM4 playlist window to see your songs. Be sure to run ‘Tools -> Mass Tagger -> Load ALL Tags’

6. Configure all settings and encoders, set encoders to auto connect. Start one of the decks.

7. Shut down SAM3.

Now SAM4 should connect and take over your streams.