1.2.3-RELEASE >> 2.0
-
If you have any international characters in description fields that can also cause the config to fail parsing, which would cause the same symptoms.
-
what do you mean with international characters? There is no üöä etc. I just rechecked.
Could you please have a look at my config? -
I can look if you want. Email it to me at jimp (at) pfsense <dot>org.</dot>
-
it's on the way - thank you very much … Ginne
-
<descr>whois.ripe.net für Cosynus</descr>^ International character in a firewall rule description
Otherwise it's a valid XML file.
-
OK, sorry I was blind!!! So I try a update again or a fresh install with 2.0 and restore of the config?
-
Either way is fine.
I just ran the config through xmllint, it will flag any invalid XML characters. Makes things like that easy to spot without having to hunt all over the GUI. :-)
-
I just ran the config through xmllint, it will flag any invalid XML characters. Makes things like that easy to spot without having to hunt all over the GUI. :-)
That's the difference between a professional and a beginner ….. I'll try a new install
-
Both the update and the restore of the 1.2.3 config in 2.0 worked! But I run in an other problem using 2.0:
My clients do not get DNS info, I finally gave up, and reinstalled 1.2.3 again. Here no problem!! I'll try again tomorrow… it's 4:19 am now! Ginne -
I got it finally working! Thanks again for your great help jimp!!
The DNS needed an other rule on the LAN interface: allow UDP LAN net * (pfsense IP) 53 (DNS)
1.2.3 did not need this.Then an other problem, what took me a long time today:
I could not select the gateway in the Advanced features of the rules! When i clicked on "Gateway" "advanced" nothing happend! I found out this is a browser problem (Firefox 4.0.1) with IE8 it worked fine!
Best regards from Germany :)
Ginne
-
You must have a restrictive ruleset on LAN then. Previously, the "anti-lockout" rule would have allowed that DNS traffic because it allowed anything to hit the pfSense LAN IP, but now that is not the case.
As for the gateway selection, it works fine for me with FF 4.0.1, there may have been something in the browser cache that needed cleared.
