Hamachi
-
Sorry for the delay in replaying … spring break time and all. I have upgraded pfsense to the beta 2 rc5, but I am still having difficulties. Here are screenshots of my pfsense setup. I am also getting errors loading my NAT settings. The error is:
[filter_load] There were error(s) loading the rules: /tmp/rules.debug:21: the static-port option can't be used when specifying a port rangepfctl: Syntax error in config file: pf rules not loaded. The line in question reads [21]: nat on xl1 from 10.1.10.0 / 24 to any -> (xl1) port 12975 static-port
Also, I go to the Hamachi beta download page and try to download release 52 and the download times out trying to get the file off the servers. I can't update through the software either. Not expecting you guys to do anything, just informing.
-
Hmm, dunno what to say. I remember having that error too, I don't remember what fixed it, but it's gone. All I can suggest is trying a complete fresh install of your firewall from the iso with the latest version. Just save a backup of your config on the Backup/Restore page, and then copy that config<whatever>.xml to a floppy. On the floppy make a folder called conf (edit) and copy that config file you saved, but rename it to config.xml.
Hope that helps.</whatever>
-
I did a fresh reinstall from the Beta 2 LIVE iso and it still hasn't worked … I am fresh out of ideas. I still get the same error as well.
Thanx for the Hamachi Beta mirror, worked like a charm.
-
Well, heh, I finally took a closer look, and I see the error…I've made some "grade 2" drawings on the jpeg for ya...
The source port needs the <12975> or whatever port entry, and the destination and translation ports need to be blank, just the static port option checked in the Translation section…
-
hello,
superman, I tried your method…
it doesn't work for me :-(
EDIT: after selecting in nat:outbound: "enable advanced outbound NAT" It works :-) Thank you...
-
Did you check the options are set properly as per these:
http://forum.pfsense.org/index.php?topic=334.msg2785#msg2785
http://forum.pfsense.org/index.php?topic=334.msg4433#msg4433Not implying anything, but I found for myself, when it didn't work, it was one minor detail that I kept overlooking, when I finally noticed it and set it properly all worked!!
Let us know how it goes.
-
It works ;D see previous message…
-
Cool!! Enjoy the "HAM"!! ;)
It's the little details that'll get you every time!! ::)
-
yes… you are right ;D thanks again :-*
-
Hey everyone, well, I did get this working and all, but that was on a Cable connection.
Someone else I have on pfSense is using an ADSL PPPoE connection. Previously, they were using pfSense behind the Modem/Router, but now pfSense is connected directly to a modem and is looking after PPPoE and Firewall/Router duties. With that change Hamachi no longer works properly, even with all the settings just as I and others set out earlier in this thread. I guess it has to do with the way PPPoE works, but I don't know exactly what to change to make this work…
Can any more network savvy folks help me out?
TIA
-
Okay, well, it seems that the problem is just with the Linux client…so we just have to wait for an update from the Hamachi team...
The windows clients seem to work fine. (I just hadn't tried to connect from windows before my previous message...)
Thanks anyways! :D
-
Me and a friend are using Hamachi 1.0.0.54 without trouble. It works as long as ONE party has forwardet an UDP port and enabled it in Hamachi preferences (Magic Option)
Our config:
Friend's comp. - pfSense - internet - ruter NAT - pfSense - My comps
Yellow until I forwared a UDP port to one of my machines. Then I wanted a second machine online, that one got yellow. So my friend forwarded the UDP port on his pfSense box, and green on that too.
-
I've read everyone's suggestions, and i have tried them all, nothing seems to work for me. When i was using ip-cop i had no problems. I've got a linux box on one end and linux and windows at home. obviously the 2 on the same network can see each other, but not the one thats at my work. I've talked to my network guy, he says that all outbound is unregulated, so that shouldn't be the problem. Any other ideas why this would be failing?