Bug #28: Problems with m0n0wall configuration conversion - pfSense - pfSense bugtracker

Actions

Copy link

Bug #28

closed

Problems with m0n0wall configuration conversion

Added by Chris Buechler over 15 years ago. Updated about 15 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Category:

Target version:

Start date:

07/08/2009

Due date:

% Done:

100%

Estimated time:

Plus Target Version:

Release Notes:

Affected Version:

2.0

Affected Architecture:

Description

1) ICMP echo rules don't convert properly.
/tmp/rules.debug:122: unknown icmp-type echo
pass in quick on $wan inet proto icmp from any to any icmp-type echo keep state
label "USER_RULE: PING"

2) Rule labels that are too long don't get cut down
/tmp/rules.debug:140: rule label too long (max 63 chars)

3) IPsec rules aren't converted properly because m0n0wall uses <interface>ipsec</interface>
and we use enc0
/tmp/rules.debug:160: macro 'ipsec' not defined
/tmp/rules.debug:160: syntax error
pass in quick on $ipsec from any to any keep state label "USER_RULE: Default IPsec VPN"

Actions

Copy link

Updated by Chris Buechler over 15 years ago

Also one other config conversion issue from cvstrac.

Existing m0n0wall (1.3b3) on WRAP (1E-2); saved config. Removed mini-pci wifi card prior to swaping m0n0wall CF card for pfSense 1.2-RC3 CF card. Configured pfSense through console/webGUI, and restored the m0n0wall config. Existing (up) interfaces are WAN and LAN. Clients connected to the LAN interface cannot pass any traffic through WAN. pfSense shell (via console) can. Removed all references to nonexistant opt2 interface from saved m0n0wall config, reuploaded to restore GUI, and after applying/reboot, LAN clients can now surf.

Actions

Copy link