Project

General

Profile

Hosted epdg playground » History » Version 7

lynxis, 02/08/2024 07:53 PM

1 1 laforge
h1. Hosted epdg playground
2
3
This page is going to document the _playground_ that we're setting up for playing with the (in-development state) of osmo-epdg.
4 7 lynxis
The setup is also described using "ansible":https://gitea.osmocom.org/ims-volte-vowifi/ansible-prototype
5 1 laforge
6
7
h2. Hosts
8
9
h3. epdg
10
11
Hostname: @epdg.osmocom.org@ (IPv4 + IPv6)
12
13 2 laforge
|_.netdev|_.IP|_.Description|
14
|enp1s0|213.95.46.81 2001:780:45:1d::46:81|Public Internet|
15
|enp7s0|?|internal network|
16
17 1 laforge
This is a Debian 12 VM where the osmo-epdg (consiting of modified strongswan code, erlang ePDG and linux kernel GTP) will run.
18
19
h3. epc
20
21 3 lynxis
Hostname: @epc.epdg.osmocom.org@ (IPv6 only)
22 1 laforge
23 2 laforge
|_.netdev|_.IP|_.Description|
24
|eth0|2001:780:45:1d::f046:1000|Public Internet|
25
|eth1|?|internal network|
26
27
28 1 laforge
This is a Debian 12 lxc container where we'll run HSS + PGW (open5gs)
29
30
h3. ims
31
32
Hostname: @ims.epdg.osmocom.org@ (IPv6 only)
33 2 laforge
34
|_.netdev|_.IP|_.Description|
35
|eth0|2001:780:45:1d::f046:1001|Public Internet|
36
|eth1|?|internal network|
37 1 laforge
38
This is a Debian 12 lxc container where we'll run the IMS core (Kamailio)
39
40
h2. Internal network
41
42
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
43 4 lynxis
44
45
h2. How to use the playground:
46
47
h3. Configure your local UE
48
49 5 lynxis
Point your UE or use SWu-IKEv2 to use @epdg.osmocom.org@.
50
Alternative you can override the correct dns entries.
51 6 lynxis
E.g. @epdg.epc.mnc001.mcc001.pub.3gppnetwork.org -> 213.95.46.81@
52
53
Get your Simcard into the database on epc.epdg.osmocom.org. Use @open5gs-dbctl add@
54 4 lynxis
55
h3. Development
56
57
To do a test run with the current development state:
58
59
- @tmux attach -t epdg@
60
- window 0 should contain the osmo-epdg
61
- window 1 should contain the strongswan
62
63
- restart osmo-epdg in window 0. @cd /srv/osmo-edpg ; rebar3 shell --config ./config/local.config@
64
- restart strongswan in window 1 @systemctl restart strongswan ; journalctl -f -u strongswan@
65
66
- to improve development speed, you should restart also the smfd or you need to wait until it re-connects.
67
- The pcrfd also needs to be restarted because the smfd will otherwise reject Session. (It will also automatic re-connect, but takes time too).
68
69
<pre>
70
ssh root@epc.epdg.osmocom.org systemctl restart open5gs-smfd
71
sleep 1
72
ssh root@epc.epdg.osmocom.org systemctl restart open5gs-pcrfd
73
</pre>
Add picture from clipboard (Maximum size: 48.8 MB)