Hosted epdg playground » History » Version 14
lynxis, 03/14/2024 09:43 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 | 8 | lynxis | |enp7s0|10.74.0.11-10.74.0.13|internal network| |
16 | 2 | laforge | |
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 | 8 | lynxis | |eth1|10.74.0.21-10.74.0.24|internal network| |
26 | 2 | laforge | |
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 | 8 | lynxis | |eth1|10.74.0.31-10.74.0.33|internal network| |
37 | 1 | laforge | |
38 | 12 | laforge | This is a Debian 12 -lxc container- VM where we'll run the IMS core (Kamailio) |
39 | 1 | laforge | |
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 | 13 | lynxis | osmo-epdg and strongswan are now managed by systemd units. |
60 | 4 | lynxis | |
61 | 13 | lynxis | - to improve development speed, you should restart the smfd or you need to wait until it re-connects. |
62 | 4 | lynxis | - The pcrfd also needs to be restarted because the smfd will otherwise reject Session. (It will also automatic re-connect, but takes time too). |
63 | |||
64 | <pre> |
||
65 | ssh root@epc.epdg.osmocom.org systemctl restart open5gs-smfd |
||
66 | sleep 1 |
||
67 | ssh root@epc.epdg.osmocom.org systemctl restart open5gs-pcrfd |
||
68 | </pre> |
||
69 | 14 | lynxis | |
70 | h3. Add an IMSI |
||
71 | |||
72 | <pre> |
||
73 | ssh root@epc.epdg.osmocom.org |
||
74 | # imsi, ki, opc |
||
75 | open5gs-dbctl add 901700000000000 11111111111111111111111111111111 AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA |
||
76 | # take a free msisdn |
||
77 | open5gs-dbctl msisdn 901700000000000 0301234 |
||
78 | # allow to use ims apn |
||
79 | open5gs-dbctl update_apn 901700000000000 ims 1 |
||
80 | </pre> |