2.9.18 has a serious problem with PPTP (gre) traffic passing through it.
ONLY 1 client can ever connect to the same PPTP server at any given time !
PC 1---------LAN----- MT2.9.18 ------- internet ---------PPTP Server
PC 2
You can easily replicate like this: (so dont ask me to send a supout.rif)
1) PC 1 can connect to the PPTP server no problem
2) PC 2 cannot connect to PPTP server (timeout)
3) disconnect PC1
4) try again to connect PC2 and it will timeout again
5) go to MT2.9.18 connection tracking window and delete the cached GRE entry from PC1
6)Try again to connect with PC2 and it will connect fine
7)Try with PC1 and it will timeout and so on....
WARNING: 2.9.18 does not pass PPTP traffic properly
Last edited by airnet on Wed Mar 29, 2006 5:37 am, edited 1 time in total.
To make matters worse you can no longer download previous software to roll back.
A week ago downloading old versions was possible so we no longer bother 'saving' old versions.
**DONT UPGRADE** unless you have a copy of the old 'working' version. The more they fix, the more they break. It's not until you put it into production with 000's of client PC's that you find the bugs.
A week ago downloading old versions was possible so we no longer bother 'saving' old versions.
**DONT UPGRADE** unless you have a copy of the old 'working' version. The more they fix, the more they break. It's not until you put it into production with 000's of client PC's that you find the bugs.
If there is not NAT for MT 2.9.18, where users PC 1 and PC 2 connected,
firewall on this router should pass TCP port 1723 and IP protocol GRE (IP protocol ID 47).
If there is not firewalls and NAT on both routers,
make and send support output files and send them to support@mikrotik.com
firewall on this router should pass TCP port 1723 and IP protocol GRE (IP protocol ID 47).
If there is not firewalls and NAT on both routers,
make and send support output files and send them to support@mikrotik.com
No problems here, too.
Just created a test-setup (all 2.9.18, of course):
One RB532 as PPTP-server. Routed connection to another RB532. From behind the second RB532 I right now have two concurrent PPTP sessions through router2 to the PPTP server on router1. Both are up, running and passing traffic...
Best regards,
Christian Meis
Just created a test-setup (all 2.9.18, of course):
One RB532 as PPTP-server. Routed connection to another RB532. From behind the second RB532 I right now have two concurrent PPTP sessions through router2 to the PPTP server on router1. Both are up, running and passing traffic...
Best regards,
Christian Meis
-
-
wildbill442
Forum Guru
- Posts: 1055
- Joined:
- Location: Sacramento, CA
I'm having problems with a Cisco Hardware VPN client not being able to connect using IPSEC..
The only firewall rules I have on my network are incoming port 25, 135-139 (TCP/UDP), and 445 (TCP). Connection tracking is enabled. I just sent an email to mikrotik support with a supout.rif of my edge router. It's a pure mikrotik network running 2.9.17. It appears to be an MTU issue, any additional input is appreciated.
See this thread for more info: http://forum.mikrotik.com/viewtopic.php?t=7555
The only firewall rules I have on my network are incoming port 25, 135-139 (TCP/UDP), and 445 (TCP). Connection tracking is enabled. I just sent an email to mikrotik support with a supout.rif of my edge router. It's a pure mikrotik network running 2.9.17. It appears to be an MTU issue, any additional input is appreciated.
See this thread for more info: http://forum.mikrotik.com/viewtopic.php?t=7555
Make and send support output file from the router with the latest MikroTik RouterOS version to support@mikrotik.com, when you have problems with PPTP passtrough.
, Its not so fun to reroll all the uppgrades in my network. We had alot of angry customers running with VPN to thier work.Unfortunately we had the same problem, but was not lucky enough to have an older version of 2.9 on hand. A few weeks back we could happily download older versions, so we didnt bother holding them.
Oh yes that hurt.
The last known working version for us was 2.9.12 that I asked MT to email a download link. No such luck.
So back to square-one happily working on 2.8.28 still....
Please tap me on the shoulder when 2.9.74 is released.
Oh yes that hurt.
The last known working version for us was 2.9.12 that I asked MT to email a download link. No such luck.
So back to square-one happily working on 2.8.28 still....
Please tap me on the shoulder when 2.9.74 is released.