hello guys

i have rb750 and mikrotik hosted on VPS,

i use it to access netflix and other movies service that designed to be used in USA, and as you know guys for streaming you need a very stable connection and fast,

i used EOIP ( very slow) and pptp ( good speed but not very fast response) then i go for GRE, the speed was great also the response and streaming is prefect ( got my full speed while streaming)


but as you know the GRE doesn't accept anything rather than just adding ip address (layer 2) (no dhcp client no server no bridge )

so i specify local ip for the tunnel in remote router 192.168.88.1
and the router in my location is 192.168.88.2

then i specify the 192.168.88.1 as gateway on my local router,

everything work great and wonderful more than expected as a speed (100% satisfied comparing to pptp or eoip)

my question is:-

1 )is there any protocol worth trying?

2 )in my local site i have pppoe connection which has dynamic ip address, which i use it as my local adress ( is there anyway to solve it)?
i guess scripting could but i don't prefer it

3 ) where can i found wiki or documentation for GRE ?


4 ) whats the use of keepalive option?

is the mpls faster and less overhead than GRE?

1 )is there any protocol worth trying?

Worth trying for what? It sounds like you're happy with GRE.

2 )in my local site i have pppoe connection which has dynamic ip address, which i use it as my local adress ( is there anyway to solve it)?
i guess scripting could but i don't prefer it

I don't understand the question.

3 ) where can i found wiki or documentation for GRE ?

It's more or less EoIP without the proprietary extensions. You can find lots of information about the protocol in general on Cisco's and Juniper's sites. GRE is a standard.

4 ) whats the use of keepalive option?

To detect whether the other side of the tunnel is down, or just not sending any data because there isn't any data to send.

is the mpls faster and less overhead than GRE?

GRE and MPLS are fundamentally different, and MPLS doesn't apply to the problem you're trying to solve (stream Netflix).

thanks fewi for your reply


yeah i refer to cisco already,

hehe, i m very happy with GRE, i know that EOIP and GRE almost the same, but GRE is much faster


and i want to run scrip to update my remote ip (in vps) and source ip (on RB750G)

i found alot of similar script for EOIP, but i faced problem on updating the source ip in the rb750 , any help?

Look up the dyndns (and changeip, etc.) scripts on the wiki. You can modify them to resolve the other end periodically and update the configuration.

Look up the dyndns (and changeip, etc.) scripts on the wiki. You can modify them to resolve the other end periodically and update the configuration.

yeah thanks i was working on it and it has been solved,


script is very simple

i add the famous dyndns script

on server (vps)

:global "eoipint1" "gre-tunnel1"
:global "eoipconnectclient1" "my.dyndns"
:global "eoip1hostip" [:resolve $"eoipconnectclient1"]
:global "eoipconnectto" [/interface gre get $eoipint1 remote-address]
:if ($eoip1hostip != $eoipconnectto) do={
:log info "****** Updating EOIP Tunnel for $eoipint1"
/interface gre set $"eoipint1" remote-address=$"eoip1hostip"}
:if ($eoip1hostip = $eoipconnectto) do={
:log info "**** No Update necessary for EOIP Tunnel $eoipint1"}

on client (rb750)


:global "eoipint1" "gre-tunnel1"
:global "eoipconnectclient1" "my.dyndns"
:global "eoip1hostip" [:resolve $"eoipconnectclient1"]
:global "eoipconnectto" [/interface gre get $eoipint1 local-address]
:if ($eoip1hostip != $eoipconnectto) do={
:log info "****** Updating EOIP Tunnel for $eoipint1"
/interface gre set $"eoipint1" local-address=$"eoip1hostip"}
:if ($eoip1hostip = $eoipconnectto) do={
:log info "**** No Update necessary for EOIP Tunnel $eoipint1"}


now working great

is there anyway to update dyndns without abusing there services?

The scripts on the wiki account for that. Basically resolve your own name and see if it matches what is on the interface. If it does, don't update.

I suspect if you adjusted the MTU/MSS on both sides of your PPTP you might have better luck with it.

And you wouldn't have to fiddle with IPs on both sides...but just have your local side connect back to the VPS with the static IP.
The default of 1460 doesn't take into account PPPoE overhead...so you'd probably want to start with something lower than that. (I've had to go as low as 1400 for some freaky installations). Remember to do it on both client and server side.