Hamachi
-
I'll poke at this over the weekend and see if I can figure out what's wrong with the NAT. We aren't using static-port as they suggest, but we should have been forcing the source port to be what was specified.
–Bill
-
I got it working with a 1:1.
-
Remove all prior outbound nat rules and nat port forwards pertaining to Hamachi previously setup
-
Add a Firewall -> NAT -> 1:1 to your computer
-
enable magic option in Hamachi
-
add a firewall rule to the magic port with your internal ip. the default is 12975
-
-
Erg, I hate to reply w/in an hour of the last reply, but I think I see the problem. We are going to need static-port, the implementation of that will need to be somewhat carefully thought out as it's very easy to hose stuff up (windows doesn't use terribly random source ports, conflicts are guaranteed). 1:1 nat (for those with more than one IP) might be an option - or for those with only one machine behind pfsense.
–Bill
-
I must thank you all for testing this, i know that you all have limited time for supporting something that isent pfsense specific.
This is much appreciated! -
Well I got it working using 1:1. I have multiple static IPs from my ISP. I set up a second one as a vitrual IP and then used that IP 1:1 to the computer I want to use Hamachi on.
So this is a workable situation for me, because I have multiple static IPs. But I have a friend who gets one dynamic IP, and this wouldn't work for him because his PC could do 1:1 but then his other PCs couldn't get out. -
Well I got it working using 1:1. I have multiple static IPs from my ISP. I set up a second one as a vitrual IP and then used that IP 1:1 to the computer I want to use Hamachi on.
So this is a workable situation for me, because I have multiple static IPs. But I have a friend who gets one dynamic IP, and this wouldn't work for him because his PC could do 1:1 but then his other PCs couldn't get out.Understood. I'll work on this for 1.1, the NAT code is so important that we can't really risk breaking it in the middle of the beta cycle (unless it was actually broken).
We have a number of checks in place to stop 1:1 NATs being used on the same external address as an oubound nat, but play around a little bit, I suspect you might be able to create the 1:1, then create an outbound nat using the same address (just using Interface Address). It might work depending on how we order the NATs in the rule file (I can't recall if we put binat first or nat - the order obviously makes a huge difference in packet matching :))
–Bill
-
Only one of you needs to do the 1:1 trick.
I left my work machine off of a 1:1 and I am still green to it.
-
I see that you are working on som static port? http://cvstrac.pfsense.com/chngview?cn=9024
Is this a solution to the Hamachi problem??
-
Yep
-
It's working using Outbound NAT in PREBETA2-BUGVALIDATION4 (yeah the one that's been pulled from the server…)
I set it up like this:
And as noted in other posts, set the Hamachi > Preference > System > Magic Option to that default port.
Works great here with no other added rules, etc!!
I'm not sure which pfSense Version is the first to have the Outbound NAT with the Static-port option, but it works in this build...
Otherwise perhaps update yours from the cvstrac link in an earlier post in this thread...
And just an update:
If you have more than 1 Hamachi client behind your firewall, set each one to a different port, and then add that port to the Outbound NAT just like the first one. Make sure the rule ends up above the "Default" Allow All rule as is pictured on the bottom in the second linked screenshot.
-
Great to hear! This option was added right after beta 1 was released so its included in all the pre-beta2 images.
-
I am running the 1.0-BETA1-TESTING-SNAPSHOT-2-20-06 and I can't get this to work for me. I have my configs the same way as the screenshots and my Hamachi still doesn't connect. What version of Hamachi are you running? I can't get a newer version than 1.39 anywhere, everyone mirrors back to Hamachi's servers. Any other ideas?
-
Works for every version of the Ham I've used, starting from 0.99.xx up to most recent.
Did you remember to set the "Magic option"?
If you're running Windows XP SP2, did you make sure the firewall is opened on it? (Or if you're running some other system firewall…)
Did you make sure the Outbound NAT option that you added is above the default "allow all" rule?Maybe send us a screenshot of your Outbound NAT screen. (Alt+PrintScreen on Windows will capture only the active window to the clipboard, then just paste it into M$ Paint, or another Image Program if you have it...)
Hope this helps! :D
PS: You can find the latest Betas on the forum here: http://forums.hamachi.cc/viewforum.php?f=14&sid=e03938855a339e23331b702b18b6657a
-
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…