Replies: 2 comments 2 replies
-
|
I have connected MT to SE dev over SSTP with no issue [ client (sstp) ] => [ MT (hop-1) ] => [ SE dev (hop-2) ] => Internet your condition is a bit unclear to me |
Beta Was this translation helpful? Give feedback.
-
|
For dumb connetion to internet of course you have no issue. |
Beta Was this translation helpful? Give feedback.
-
|
I got it almost , SE virtual NAT only routes what ever the traffic is to its host (running on) if you want to send/forward your request/traffic from SE to further application , you better to use
and if you cannot use Linux , so the only choice remains will be vSwitch I have tested SE vSwitch, it has worked fine, but not your scenario |
Beta Was this translation helpful? Give feedback.
-
|
SSTP is based on PPP, and PPP is a layer 3 point to point protocol, it needs a remote endpoint to just work. And this is that endpoint which will actually do the complex routing if needed. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have SE server latest version and 2 routers with sstp mikrotik and keenetic.
On both routers i cannot setup routing over sstp.
It seems it caused by "Local" and "Remote" adresses.
If we using dhcp on virtual-nat we receive local adress from pool and thats good but remote address is always virtual-nat ip. But virtual-nat cannot route traffic!
On both routers we can provide local and remote address manually but if we define other address the tunnel just dont up. if we manually put route to network over interface it will not work also.
Both routers can access the network created by virtual-nat directly. But routing form networks behind doesnt work.
It seems in needs to combine L3 Switch and dhcp functionality or add routing fature to virtual-nat ?
Or i do something wrong ?
@chipitsine
Beta Was this translation helpful? Give feedback.
All reactions