Cellular Network Infrastructure » EPC - Evolved Packet Core » osmo-ePDG - VoWifi Evolved Packet Data Gateway

h1. Hosted epdg playground

This page is going to document the _playground_ that we're setting up for playing with the (in-development state) of osmo-epdg.

The setup is also described using "ansible":https://gitea.osmocom.org/ims-volte-vowifi/ansible-prototype

h2. Hosts

h3. epdg

Hostname: @epdg.osmocom.org@ (IPv4 + IPv6)

|_.netdev|_.IP|_.Description|

|enp1s0|213.95.46.81 2001:780:45:1d::46:81|Public Internet|

|enp7s0|10.74.0.11-10.74.0.13|internal network|

This is a Debian 12 VM where the osmo-epdg (consiting of modified strongswan code, erlang ePDG and linux kernel GTP) will run.

h3. epc

Hostname: @epc.epdg.osmocom.org@ (IPv6 only)

|_.netdev|_.IP|_.Description|

|eth0|2001:780:45:1d::f046:1000|Public Internet|

|eth1|10.74.0.21-10.74.0.24|internal network|

This is a Debian 12 lxc container where we'll run HSS + PGW (open5gs)

h3. ims

Hostname: @ims.epdg.osmocom.org@ (IPv6 only)

|_.netdev|_.IP|_.Description|

|eth0|2001:780:45:1d::f046:1001|Public Internet|

|eth1|10.74.0.31-10.74.0.33|internal network|

This is a Debian 12 lxc container where we'll run the IMS core (Kamailio)

h2. Internal network

The hosts mentioned above share a private bridged network.  That network has no DHCP server and no router. It's purely for communication between the network elements

h2. How to use the playground:

h3. Configure your local UE

Point your UE or use SWu-IKEv2 to use @epdg.osmocom.org@.

Alternative you can override the correct dns entries.

E.g. @epdg.epc.mnc001.mcc001.pub.3gppnetwork.org -> 213.95.46.81@

Get your Simcard into the database on epc.epdg.osmocom.org. Use @open5gs-dbctl add@

h3. Development

To do a test run with the current development state:

# ssh epdg.osmocom.org

# @tmux attach -t epdg@

# window 0 should contain the osmo-epdg

# window 1 should contain the strongswan

# restart osmo-epdg in window 0. @cd /srv/osmo-epdg ; rebar3 shell --config ./config/local.config@

# restart strongswan in window 1 @systemctl restart strongswan ; journalctl -f -u strongswan@

- to improve development speed, you should restart also the smfd or you need to wait until it re-connects.

- The pcrfd also needs to be restarted because the smfd will otherwise reject Session. (It will also automatic re-connect, but takes time too).

<pre>

ssh root@epc.epdg.osmocom.org systemctl restart open5gs-smfd

sleep 1

ssh root@epc.epdg.osmocom.org systemctl restart open5gs-pcrfd

</pre>