Trying to work my way through a science project…
Current configuration;
- Balance 20 ([email protected]) at my home connected using Starlink residential (SL router removed)
- UBR+ ([email protected]) in RV connected using Starlink Priority with public IP (SL router removed)
I have been able to get SpeedFusion VPN to connect (Green box, “Established”) between devices but only get IPV6 traffic to pass (I can see IPV6 devices and connect to them), unable to see IPV4 devices.
Have tried to ping IPV4 devices, not working
Have watched more than a few video’s trying to see what I may have incorrectly configured, just not seeing anything obvious.
Where do I start looking to allow IPV4 traffic?
What screen shots should I post to help troubleshoot this?
Thanks in advanced for any help offered
Hi Kirk
So the info from you which would be useful would be the type of tunnel you are trying to create (L2 or L3) if layer 3 then then subnet addressing for each side of the tunnel (192.168.50.0/24). Tests that have been done and shows it failing.
Screenshot of the tunnel status (Status | speedfusion/pepvpn) for each side.
IPv4 traffic is what the peplink does (IPv6 is just passthru) and it will work by default.
thanks
@Kirk_Almquist
May I know you are working on the Layer 3 or Layer 2 SpeedFusion tunnel ? Also , can you share some of the tunnel status screenshot so that we can have more info to help ?
Thank you
L2, (all the instructions/vidoes show setting up this type)
Please see attached pic’s, hope I’ve provide what was requested.
@Kirk_Almquist ,
For the ping tool test & VPN tunnel status , I’m seeing you are ping 192.168.50.1 & 192.168.10.1 . This is not a expected IPs for L2 SF tunnel which allowed to communicate.
(LAN IP) 192.168.50.1-B20 <---- L2 SF----> UBR -192.168.50.2 (LAN IP)
|XXXXXXXXXXX________192.168.50.0/24____XXXXXXXXX____|
For L2SF design (Refer to the design above), expected both end LAN networks are running 192.168.50.x/24. You can use the ping tools to ping the LAN interface IP for the remote device.
L2 SF is like network extension (192.168.50.x/24) to remote network.
Suggest you can change the 192.168.10.1/24 (LAN interface IP) to 192.168.50.2 and redo the test.
Thank you
Thank for the reply and that fixed my issue!
1 Like