/ ip hotspot walled-garden ip add dst-address=hotspotip action=accept
/ ip hotspot walled-garden add dst-host=:^www\\.paypal\\.com\$ dst-port=443 action=allow
/ ip hotspot walled-garden add dst-host=:^content\\.paypalobjects\\.com\$ dst-port=443 action=allow

if you copy and past or even type this which is what is listed to put into the walled garden in version 3.0r2 you get a syntax error
I have ssl installed and it works for the hotspot login, once im logged in i can go to paypal and pay , but not before hand, anyone have the correct syntax for v3.0r2, i want to put this in the walled garden

its wierd cause if i login and then go to http://www.paypal.com or https://www.paypal.com i have no problems , but i have a link so customers can sign up. Yes i have the cert installed and it works fine for login and with the user and userman options , and if im logged in i can purchase credits thru paypal no problem, but if im not logged in and im at the default secure hotspot login page and i try to get to paypal it just hangs
ip walled-garden add dst-host hostslisedbelow action=allow
*.paypal.com.au
*.paypalobjects.com
*.akamaiedge.net
paypalobjects.com
http://www.paypal.com
*.paypal.com
history.paypal.com
*.history.paypal.com
paypalssl.doubleclick.net
*.paypalssl.doubleclick.net
https://*.paypalobjects.com

Is anyone using paypal on 3.0 mikrtotik on the hotspot for signups? What did you put int he walled garden to make it work , cause the stuff on wiki dont work for 3.0

got it to work

walled garden info for version 3.0r2
For paypal to work perfectly
Go to walled-ip-garden

ADD your router local address
/ ip hotspot walled-garden ip add dst-address=127.0.0.1 action=accept
Add this ip for http://www.paypalobjects.com
/ ip hotspot walled-garden ip add dst-address=72.247.72.146 action=accept
ADD this ip range for paypal.com add the whole range
/ ip hotspot walled-garden ip add dst-address=216.113.160.0/19 action=accept
ADD paypal.coma and paypalobjects.com
/ ip hotspot walled-garden ip add dst-host=paypal.com action=accept
/ ip hotspot walled-garden ip add dst-host=paypalobjects.com action=accept

About first post,
you have to include expression into ""
/ ip hotspot walled-garden add dst-host=":^www\\.paypal\\.com\$" dst-port=443 action=allow
then it should work (3.0 has some changes in syntax and scripting).

Having same problems with Paypal. And it isn't just Paypal- Its several sites that I need to allow access to.
One similarity between them all is that after you first access them via http, they switch you to https.
Not that this means anything, but "regular" sites put into the walled garden work great.

NateDog, what is that 72.x.x.x address you suggested? If it is an address at Paypal, I don't think your suggestion will be effective for long.
This is because Paypal and others change these IP addresses all the time. We have to be able to use DNS for this stuff, and it is broken in R3. I am on RC13 and it is STILL broken.

Yes, if I test all the DNS and put the addresses that resolve in the Walled IP Garden, then mostly it works, but I don't think this is any more than a workaround and a temporary one at thet.

I really need my payment gateway to work all the time, and MT needs to fix whatever is broken in R3.

Anyone else got any light for this subject??

We have discovered some issues, that may cause to work incorrectly 'ip hotspot walled-garden' entries. It is fixed in the upcoming version.
You may try to switch to 'ip hotspot walled-garden ip' rules for now.
Then Paypal page should work fine.

The problem I speak of is not when using IP walled garden. It is using the original walled garden.
It is true that I can switch to the IP walled garden, but the IP addresses of Paypal and the other sites required for operation are not always the same. This will cause inconsistent operation.

I want to make sure that Mikrotik understands that the problem I speak of is when I use DNS names in the walled garden, and that it happens when the user is redirected to https format once on the site listed. If I place DNS that are *only* http, then the walled garden works OK. However Paypal and others change to https once you are on the site.

If you want to demonstrate this, simply place paypal.com or wirelessorbit.com in the walled garden and attempt to access while you are unauthorized. You will get no response. Now log in and try again, and the sites will work. This proves it is something to do with https.

I hope this is of some help. I will try rc14 when it is released, but I am worried that the problem it corrects is not the one I have.

rwf, yes we are aware of this problem. we have determined, that Paypal and other pages could be accessed, when regular 'ip hotspot walled-garden' is used.
The particular issue will be fixed at 3.0rc14, let us know if there will be any problems, when 3.0rc14 will be released.

Hi all
I have the same problem with paypal.
I have v3.7 on X86 machine (hotspot router)
I followed the instructions at : http://wiki.mikrotik.com/wiki/User_Mana ... quirements
but nothing ...
when users are logged in everything is ok.
For non logged in users paypal is not working properly because (as I thing !!!) the css cannot be accessed
(https://www.paypalobjects.com/WEBSCR-51 ... e/core.css)
what should i do for that ???
Thanks in advance.

Have you added all the pages to walled-garden from here ?

/ ip hotspot walled-garden add dst-host=":^www\\.paypal\\.com\$" dst-port=443 action=allow
/ ip hotspot walled-garden add dst-host=":^content\\.paypalobjects\\.com\$" dst-port=443 action=allow
/ ip hotspot walled-garden add dst-host=*.akamaiedge.net action=allow

It works fine for me.

I solved it.
I have 2 dns server except from mt. That was the problem.
When I configured dhcp server to provide clients default dns the mt, everything worked fine.
Thanks .............................................

did you get it to work with 3.0 , and if so how , you said you had something about dns set in the mt or what