Osmo-gbproxy » History » Version 12
laforge, 01/29/2020 08:53 PM
link to manuals
1 | 7 | laforge | {{>toc}} |
---|---|---|---|
2 | 1 | laforge | |
3 | 7 | laforge | h1. The Gb proxy |
4 | |||
5 | |||
6 | 10 | laforge | The purpose of the Gb proxy is to aggregate the Gb links of multiple BSS's and present them in one Gb link to the SGSN. |
7 | 1 | laforge | |
8 | 10 | laforge | More specifically, the Gb proxy terminates the NS-VCs of each BSS locally. Furthermore, it establishes one NS-VC with the SGSN. |
9 | |||
10 | It also contains support for converting form a NS/UDP/IP (Gb over IP) stacking to a frame-relay based NS/FR/GRE/IP stacking. |
||
11 | 1 | laforge | |
12 | 7 | laforge | Source code available as part of [[OpenBSC]] repository: |
13 | <pre> |
||
14 | 6 | laforge | git clone git://git.osmocom.org/openbsc.git |
15 | 7 | laforge | </pre> |
16 | 6 | laforge | |
17 | 1 | laforge | The proxy then forwards NS-DUs (BSSGP PDUs) between the SGSN and the |
18 | respective BSS (and vice versa). |
||
19 | 9 | laforge | |
20 | {{graphviz_link() |
||
21 | 5 | laforge | digraph G { |
22 | 1 | laforge | rankdir=LR; |
23 | nanobts1->OpenBSC [ label="Abis/IP" ]; |
||
24 | 5 | laforge | nanobts2->OpenBSC [ label="Abis/IP" ]; |
25 | 1 | laforge | nanobts1->gb_proxy [ label="Gb/IP" ]; |
26 | nanobts2->gb_proxy [ label="Gb/IP" ]; |
||
27 | gb_proxy->SGSN [ label="Gb/IP or\nGb/FR/GRE/IP" ]; |
||
28 | 11 | laforge | nanobts2 [ label = "OsmoBTS" ]; |
29 | nanobts1 [ label = "nanoBTS" ]; |
||
30 | 9 | laforge | OpenBSC [ label = "OpenBSC" ] |
31 | 5 | laforge | } |
32 | 9 | laforge | }} |
33 | 5 | laforge | |
34 | 12 | laforge | h2. Documentation |
35 | |||
36 | * "User manual":https://ftp.osmocom.org/docs/latest/osmogbproxy-usermanual.pdf |
||
37 | * "VTY reference manual":https://ftp.osmocom.org/docs/latest/osmogbproxy-vty-reference.pdf |
||
38 | |||
39 | Documentation is somewhat minimalistic at this point, as this is not a general-purpose network element but something highly specialized for some niche use cases. Feel free to contact sales@sysmocom.de in case you would want to hear more about its capabilities. |
||
40 | |||
41 | 8 | laforge | {{child_pages}} |
42 | 1 | laforge | |
43 | 7 | laforge | h2. Configuring and using osmo-gbproxy |
44 | |||
45 | |||
46 | 1 | laforge | Like other programs in this project, osmo-gbproxy accepts a number of command line arguments |
47 | but is generally configured by a configuration file (which can be interactively created/edited |
||
48 | from the VTY). |
||
49 | 3 | laforge | |
50 | 1 | laforge | The command line arguments are: |
51 | 7 | laforge | <pre> |
52 | 1 | laforge | -h --help this text |
53 | -d option --debug=DNS:DGPRS,0:0 enable debugging |
||
54 | -c --config-file filename The config file to use. |
||
55 | 3 | laforge | -s --disable-color |
56 | -T --timestamp Prefix every log line with a timestamp |
||
57 | 7 | laforge | -V --version. Print the version of [[OpenBSC]]. |
58 | 3 | laforge | -e --log-level number. Set a global loglevel. |
59 | 7 | laforge | </code></pre> |
60 | 3 | laforge | |
61 | 7 | laforge | There is a wiki page [[osmo-gbproxy_VTY]] with a reference for all VTY commands |
62 | 1 | laforge | |
63 | |||
64 | h2. Advanced use cases |
||
65 | 7 | laforge | |
66 | |||
67 | h3. Cascading proxies |
||
68 | |||
69 | |||
70 | 2 | laforge | You can also cascade multiple Gb proxies behind each other, where a number |
71 | 1 | laforge | of BSS connect to one Gb proxy, which in turn connects to another Gb proxy, |
72 | which then finally connects to the SGSN. |
||
73 | |||
74 | The reason for this type of use can be broken or limited Gb implementations |
||
75 | in proprietary BSS equipment, which fails to re-connect the Gb link after some |
||
76 | intermittent network outage. |
||
77 | |||
78 | |||
79 | 7 | laforge | h2. Design documentation |
80 | |||
81 | |||
82 | There's a more detailed [[osmo-gbproxy_design|design description]] outlining |
||
83 | 1 | laforge | details of the proxy. |