Well all is working for me just fine in EOIP over PPTP that is bridged on both sides with Ethernet.any known problems with eoip? 6.9 was working fine but after the switch to 6.10 it isn't passing traffic.
this is over a pptp connection, eoip is building and keeping a connection but no packets passed "other then keep alive"
Why name is 6.10 ?
It is pre-release for testing. It should be6.10rc1
Works fine hereAnything about fixing routing marks in 6.10 (broken in 6.9, works in 6.7)?
could you please clarify where exactly you saw "unknown"? I just upgraded a PPTP server running 6.7 to 6.9 and my 'pofile1' still says 'profile1'6.7 to 6.9 broke pptp connections on several of our systems in production. It actually works fine, however after upgrade security profiles were not working/applied ... showinginstead of the configured profile (we always set new profiles rather than "default-profile")
It happens when the 6.7 version was running the experimental PPP package. At least everywhere i got this problem, the 6.7 experimental PPP package was installed and after upgrade all PPP settings/profiles/interfaces were gone.could you please clarify where exactly you saw "unknown"? I just upgraded a PPTP server running 6.7 to 6.9 and my 'pofile1' still says 'profile1'6.7 to 6.9 broke pptp connections on several of our systems in production. It actually works fine, however after upgrade security profiles were not working/applied ... showinginstead of the configured profile (we always set new profiles rather than "default-profile")
What shiny said, although we were not running "ppp experimental' package.could you please clarify where exactly you saw "unknown"? I just upgraded a PPTP server running 6.7 to 6.9 and my 'pofile1' still says 'profile1'
When OVPN start working on UDP?What's new in 6.10 (2014-Feb-10 15:11):
*) ovpn客户端删除密码=任何opti & auth =ons, protocol does not support them;
it is fixed alreadyAnd what about Ticket#2014020366000387, is it fixed or will be?
I asked beacuse there is no info in changelogit is fixed alreadyAnd what about Ticket#2014020366000387, is it fixed or will be?
I love these!Like everyone here should knows what you are talking about... What about it, exactly?What about using MRRU parameter in ppp-server (l2tp/pptp) configuration on RB 1100AHx2? Any fixes?
Very exciting!/ip ipsec peer> set local-address=
The first step in the right direction
Now I was left to wait for the rest of the VPN
Holy crap!Very exciting!/ip ipsec peer> set local-address=
The first step in the right direction
Now I was left to wait for the rest of the VPN
Hopefully/ipsec peer set addressbecomes/ipsec peer set remote-addressto keep things consistent and logical.
Problem is described in two or more post above, but I do it again:I love these!Like everyone here should knows what you are talking about... What about it, exactly?What about using MRRU parameter in ppp-server (l2tp/pptp) configuration on RB 1100AHx2? Any fixes?
Ticket#2014021266000146Upgrade: 6.6 -> 6.9
RouterBOARD: RB 1100AHx2
Tested bugs:
а. [L2TP-Server]:
After upgrade router reboots while first l2tp-session established with watchdog exeption message on serial console.
L2tp-server (and router) crash caused by the use of MRRU (value doesn't matter) parameter in /interface l2tp-server server configuration, so multilink-PPP over single link seems to be broken.
b. [Update]:
Client Mikrotik RB 750G with MRRU option enabled.