Hello community, I really need some help with a configuration which I couldn’t be able to make it works. The situation is as follow:
We have a big wireless IP network in the city of Havana, Cuba, which is named SNET. This network has a wireless backbone. We have dynamic protocols and statics protocols between the nodes. Each node has a private network and we do not have access to Internet through SNET. We could play games with private servers and games without server (P2P games or LAN party games). The LAN party games could be played with others friends form others nodes (other IP range) with the “BattleLAN” app.
What do we want?
We want to be able of connect PlayStation 4 consoles to each other PS4 consoles through SNET IP network. The problem is that PS4 is not a PC and we can’t run the “BattleLAN” app there nether a VPN client on a PS4 system. So, the PS4 games with multiplayer LAN local only works if we are playing on the same subnet (does not work through routers, because the broadcast limitation…I think). But, with a little of research, I have found a possible way to fix this with the implementation of L2TPv3. As we don’t have MPLS and VPLS is not an option, and the person who is writing this post (…I) does not have an admin rights on those backbone´s routers, the only way I have is an end-to-end solution (use two IP address to set up an L2TPv3 tunnel and connect two PS4 consoles to the same network).
What is the problem?
As I said before, I dont know what I´m doing wrong. I need to connect two PS4 consoles (two host) to the same subnet throught L2TPv3. I tried using VLAN with this, but does not work. I need to bind the VLAN 100 (the network of the PS4) to the tunnel interface to put both host on the same subnet, using L2TPv3.
Please help me to fix the configuration that I´m going to show you now. A will be waiting for any answer that could help:
#################################################################
ROUTER1
#################################################################
vyos@vyos:~$ configure
vyos@vyos# set interfaces ethernet eth0 address 10.24.10.10/24
vyos@vyos# set interfaces ethernet eth0 vif 100
vyos@vyos# set interfaces ethernet eth1 vif 100
vyos@vyos# set interfaces bridge br100 address 192.168.100.10/24
vyos@vyos# set interfaces ethernet eth1 bridge-group bridge br100
vyos@vyos# set protocols static route 10.24.11.0/24 next-hop 10.24.11.1
vyos@vyos# set interfaces l2tpv3 l2tpeth0 bridge-group bridge br100
vyos@vyos# set interfaces l2tpv3 l2tpeth0 encapsulation ip
vyos@vyos# set interfaces l2tpv3 l2tpeth0 local-ip 10.24.10.10
vyos@vyos# set interfaces l2tpv3 l2tpeth0 peer-session-id 2
vyos@vyos# set interfaces l2tpv3 l2tpeth0 peer-tunnel-id 20
vyos@vyos# set interfaces l2tpv3 l2tpeth0 remote-ip 10.24.11.11
vyos@vyos# set interfaces l2tpv3 l2tpeth0 session-id 1
vyos@vyos# set interfaces l2tpv3 l2tpeth0 tunnel-id 10
vyos@vyos# commit
vyos@vyos# save
#################################################################
ROUTER2
#################################################################
vyos@vyos:~$ configure
vyos@vyos# set interfaces ethernet eth0 address 10.24.11.11/24
vyos@vyos# set interfaces ethernet eth0 vif 100
vyos@vyos# set interfaces ethernet eth1 vif 100
vyos@vyos# set interfaces bridge br100 address 192.168.100.11/24
vyos@vyos# set interfaces ethernet eth1 bridge-group bridge br100
vyos@vyos# set protocols static route 10.24.10.0/24 next-hop 10.24.10.1
vyos@vyos# set interfaces l2tpv3 l2tpeth0 bridge-group bridge br100
vyos@vyos# set interfaces l2tpv3 l2tpeth0 encapsulation ip
vyos@vyos# set interfaces l2tpv3 l2tpeth0 local-ip 10.24.10.10
vyos@vyos# set interfaces l2tpv3 l2tpeth0 peer-session-id 1
vyos@vyos# set interfaces l2tpv3 l2tpeth0 peer-tunnel-id 10
vyos@vyos# set interfaces l2tpv3 l2tpeth0 remote-ip 10.24.10.10
vyos@vyos# set interfaces l2tpv3 l2tpeth0 session-id 2
vyos@vyos# set interfaces l2tpv3 l2tpeth0 tunnel-id 20
vyos@vyos# commit
vyos@vyos# save
