Migration from m0n0wall to pfsense: failure



  • i have been working with GeekGod on this, he says that my m0n0wall configuration should boot pfsense and all should work the way it did in m0n0wall. When I boot pfsense with the m0n0wall config, it seems like everything is working except my LAN and optional interfaces cannot get to the internet. the pfsense box is connected and it can ping the web. my LAN can ping the WAN side of pfsense as well. i do get a bunch of errors about rules not defined. I thought it had something to do with m0n0wall having spaces in optional interface names, i changed those to have underscores but nothing changed.

    Originally i manually added my fw rules, optional interfaces, and the rest of the config to pfsense. i couldnt even ping the lan interface and it didnt like being pluged into a trunk port in my switch. that is resolved when i load the m0n0wall config, for whatever reason.

    so im stuck without the internet when pfsense is loaded. loading m0n0wall back up from the cdrom and all works perfectly.

    a secondary issue is that the remote syslog option lags terribly. my syslog was reporting logs about pppoe connecting that were 10 minutes late, coming in one maybe every 5 seconds or so. that is another issue, although not a HUGE deal, still needing fixed.

    ideas, suggestions, etc. thanks!



  • Two possibilities.
    Blow aways ALL firewall rules on all interfaces. Use the 'Reset to Default settings' Menu option - assigns IP's - and use the minal info to construct a WAN connection.
    Add one rule to the LAN interface : accept all to all with all protocols. You should be able to …...... 'surf'  :)

    Anothyer thing:
    The syslog transmits rather fast it's info to the syslog client (a PC in your Lan).
    I.e., when I SSH in, I receive a notification in a second or less (and, don't laugh, my syslogger PC is more then 8 km from my pFsense box - on the same internal LAN segment).
    Do you have some (hardware) internal LAN network trouble ?



  • This was a bug.  He had spaces and special characters in the interface description names and we where not checking for this during upgrade.

    Once I installed some code to scrub this everything is fine after import.



  • @sullrich:

    This was a bug.  He had spaces and special characters in the interface description names and we where not checking for this during upgrade.

    Once I installed some code to scrub this everything is fine after import.

    yea, because he is THE MAN. sqaushin bugs is fun, especially since i am successfully using pfsense now. :-)


Locked