cellular-infrastructure
/
osmo-bsc
mirror of https://gerrit.osmocom.org/osmo-bsc
9
0
Fork 0
Code Issues Releases Wiki Activity
osmo-bsc/src/osmo-bsc_nat/bsc_nat_vty.c

1337 lines
37 KiB
C
Raw Normal View History

[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
/* OpenBSC NAT interface to quagga VTY */
nat: After we identified the bsc check the key We are using the token to find the right bsc_config and then we can use the last_rand of the bsc_connection to calculate the expected result and try to compare it with a time constant(???) memcmp.
2015-06-08 16:33:28 +00:00
/* (C) 2010-2015 by Holger Hans Peter Freyther
* (C) 2010-2015 by On-Waves
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
* All Rights Reserved
*
* This program is free software; you can redistribute it and/or modify
License change: We are now AGPLv3+ instead of GPLv2+ The reason for this is quite simple: We want to make sure anyone running a customized version of OpenBSC to operate a network will have to release all custom modifiations to the source code.
2011-01-01 14:25:50 +00:00
* it under the terms of the GNU Affero General Public License as published by
* the Free Software Foundation; either version 3 of the License, or
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
* (at your option) any later version.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
License change: We are now AGPLv3+ instead of GPLv2+ The reason for this is quite simple: We want to make sure anyone running a customized version of OpenBSC to operate a network will have to release all custom modifiations to the source code.
2011-01-01 14:25:50 +00:00
* GNU Affero General Public License for more details.
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
*
License change: We are now AGPLv3+ instead of GPLv2+ The reason for this is quite simple: We want to make sure anyone running a customized version of OpenBSC to operate a network will have to release all custom modifiations to the source code.
2011-01-01 14:25:50 +00:00
* You should have received a copy of the GNU Affero General Public License
* along with this program. If not, see <http://www.gnu.org/licenses/>.
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
*
*/
nat: Attempt to update the VTY usage to the latest version * Install the show commands to be available in the enable mode as well * Provide a copyright header..
2010-06-15 12:14:08 +00:00
#include <openbsc/vty.h>
misc: Move the bsc_parse_reg to libcommom and name it gsm_parse_reg Move the regexp parsing code from the NAT to libcommon as it will be used by the NAT and BSC code. This also adds the #include <regex.h> include to gsm_data. This header should be split up.
2011-06-09 19:48:49 +00:00
#include <openbsc/gsm_data.h>
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
#include <openbsc/bsc_nat.h>
nat: Fix compilation with nat not being enabled. common_vty.c was including bsc_nat.h which tried to get the sccp/sccp_types.h which is not required to be installed. Move all structs using/embedding SCCP structures into the bsc_nat_sccp.h and include. This should fix the compilation.
2010-07-30 21:17:17 +00:00
#include <openbsc/bsc_nat_sccp.h>
filter: Move the method definition to the filter module Move the filter methods to the filter module. This is still only usable for the NAT and the _dt/_cr filter routines need to move back to the bsc_nat in the long run.
2015-04-04 18:47:03 +00:00
#include <openbsc/bsc_msg_filter.h>
nat: Print the MSC status with a new vty command.
2010-05-11 11:07:39 +00:00
#include <openbsc/bsc_msc.h>
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
#include <openbsc/gsm_04_08.h>
nat: Add MGCP code and parsing to the nat code.. For the nat we will have NAT and MGCP in the same process and this commit starts with that. We are linking in the MGCP code and one can embed MGCP config snippets...
2010-06-15 10:50:26 +00:00
#include <openbsc/mgcp.h>
nat: Add logging commands for the nat as well.
2010-04-06 10:01:15 +00:00
#include <openbsc/vty.h>
nat: Allow to use the prefix lookup to rewrite numbers * Increase the rewritten rule to five digits (this is the easiest for the unit test). This will add another 40kb to the runtime size. * Create a unit test that tests adding and removing the prefix rules. * Use the regexp match to replace from one package
2013-06-25 09:44:01 +00:00
#include <openbsc/nat_rewrite_trie.h>
nat: Redo a merge with master that happend at this time.
2010-06-15 11:06:18 +00:00
src: use new library libosmogsm and new path to headers in libosmocore libosmogsm is a new library that is distributed in the libosmocore. Now, openbsc depends on it. This patch gets openbsc with this change. This patch also rewrites all include path to the new osmocom/[gsm|core] Signed-off-by: Pablo Neira Ayuso <pablo@gnumonks.org>
2011-03-22 15:47:59 +00:00
#include <osmocom/core/talloc.h>
#include <osmocom/core/rate_ctr.h>
#include <osmocom/core/utils.h>
bsc: change bsc_vty_init to take logging categories as parameter This change is required to finish the integration of the VTY and the per-application logging categories that provides: "vty: integration with logging framework" in libosmocore. It has been tested with osmo-nitb. The other just compiled tested.
2011-03-09 12:36:32 +00:00
#include <osmocom/vty/logging.h>
src: include new file osmocom/vty/misc.h for vty_out_rate_ctr_group() This uses the new include file for vty_out_rate_ctr_group() which available in libosmocore.
2011-03-28 17:35:00 +00:00
#include <osmocom/vty/misc.h>
osmux: move osmux socket initialization out of osmux_enable_endpoint() In the bsc-nat side, the osmux socket initialization can be done from the vty. This ensure that the osmux socket is available by the time the bsc-nt receives the dummy load that confirms that the osmux flow has been set up. This change is required by the follow up patch. This change ensures that the Osmux socket in the bsc-nat is already in place by the time this receives the dummy load.
2014-08-27 12:58:43 +00:00
#include <openbsc/osmux.h>
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
Use new include paths of libosmo-sccp 0.0.2
2010-08-03 13:11:51 +00:00
#include <osmocom/sccp/sccp.h>
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
#include <stdlib.h>
NAT: reload BSCs config dynamically Add vty tests for BSC configuration reloading. Load BSCs configuration on bscs-config-file command: * remove all runtime configured BSC not in the config file * close connections to all BSC with updated token value Fixes: OS#1670 Sponsored-by: On-Waves ehf
2016-04-13 09:36:39 +00:00
#include <stdbool.h>
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
static struct bsc_nat *_nat;
nat: Use 'paging group' because we have paging forbidden. Make paging-group deprecated and introduce the new paging group.
2011-05-17 17:28:07 +00:00
nat: Document all parameters of the VTY commands
2012-07-28 14:14:04 +00:00
#define BSC_STR "Information about BSCs\n"
#define MGCP_STR "MGCP related status\n"
nat: Use 'paging group' because we have paging forbidden. Make paging-group deprecated and introduce the new paging group.
2011-05-17 17:28:07 +00:00
#define PAGING_STR "Paging\n"
nat: Add VTY code to configure the SMSC rewriting
2011-05-30 22:35:46 +00:00
#define SMSC_REWRITE "SMSC Rewriting\n"
nat: Use 'paging group' because we have paging forbidden. Make paging-group deprecated and introduce the new paging group.
2011-05-17 17:28:07 +00:00
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
static struct cmd_node nat_node = {
NAT_NODE,
VTY: improve VTY prompt and make sure exit/end works everywhere Some nodes below 'config' didn't have ournode_exit / ournode_end, and thus were not able to properly perform this function. exit should always only go back one level, while end drops us back to ENABLE_NODE. The prompt now represents the nesting level, and there's one consistent space after the final prompt character (typically #).
2012-08-17 11:16:10 +00:00
"%s(config-nat)# ",
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
1,
};
static struct cmd_node bsc_node = {
nat: Rename BSC_NODE to NAT_BSC_NODE to avoid future issues.
2010-06-17 06:42:20 +00:00
NAT_BSC_NODE,
VTY: improve VTY prompt and make sure exit/end works everywhere Some nodes below 'config' didn't have ournode_exit / ournode_end, and thus were not able to properly perform this function. exit should always only go back one level, while end drops us back to ENABLE_NODE. The prompt now represents the nesting level, and there's one consistent space after the final prompt character (typically #).
2012-08-17 11:16:10 +00:00
"%s(config-nat-bsc)# ",
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
1,
};
nat: Create a Paging Group that BSCs can refer to Introduce a paging group that a BSC can refer to and is used during the LAC lookup. This way paging can be flooded through the network and just filtered at the last element in the core.
2011-05-02 17:16:13 +00:00
static struct cmd_node pgroup_node = {
PGROUP_NODE,
VTY: improve VTY prompt and make sure exit/end works everywhere Some nodes below 'config' didn't have ournode_exit / ournode_end, and thus were not able to properly perform this function. exit should always only go back one level, while end drops us back to ENABLE_NODE. The prompt now represents the nesting level, and there's one consistent space after the final prompt character (typically #).
2012-08-17 11:16:10 +00:00
"%s(config-nat-paging-group)# ",
nat: Create a Paging Group that BSCs can refer to Introduce a paging group that a BSC can refer to and is used during the LAC lookup. This way paging can be flooded through the network and just filtered at the last element in the core.
2011-05-02 17:16:13 +00:00
1,
};
static int config_write_pgroup(struct vty *vty)
{
return CMD_SUCCESS;
}
static void dump_lac(struct vty *vty, struct llist_head *head)
{
struct bsc_lac_entry *lac;
llist_for_each_entry(lac, head, entry)
vty_out(vty, " location_area_code %u%s", lac->lac, VTY_NEWLINE);
}
static void write_pgroup_lst(struct vty *vty, struct bsc_nat_paging_group *pgroup)
{
vty_out(vty, " paging-group %d%s", pgroup->nr, VTY_NEWLINE);
dump_lac(vty, &pgroup->lists);
}
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
static int config_write_nat(struct vty *vty)
{
filter: Remove nat from bsc_nat_acc_lst and replace with msg
2015-04-04 20:40:12 +00:00
struct bsc_msg_acc_lst *lst;
nat: Create a Paging Group that BSCs can refer to Introduce a paging group that a BSC can refer to and is used during the LAC lookup. This way paging can be flooded through the network and just filtered at the last element in the core.
2011-05-02 17:16:13 +00:00
struct bsc_nat_paging_group *pgroup;
[nat] Introduce the concept of access-list One can set one access-list to one BSC and one access-list to one NAT. The matching of IMSIs remains the same for now, also applying the white/blacklist. Access lists can not be deleted for now and no perf opt is done (e.g. one could cache the result of the last lookup in the bsc struct).
2010-05-31 17:03:13 +00:00
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
vty_out(vty, "nat%s", VTY_NEWLINE);
bsc: Allow to have a list of MSCs/MUXs to connect to Be able to configure a list of destinations (duplicates allowed) that will be tried in a round robin fashion. The change is in the bsc_msc_connection to operate on a list. We achieve the round robin nature with the same trick used in the paging code to delete and append the current entry. The nat code was updated to compile but one can only configure one destination.
2011-04-23 21:31:31 +00:00
vty_out(vty, " msc ip %s%s", _nat->main_dest->ip, VTY_NEWLINE);
vty_out(vty, " msc port %d%s", _nat->main_dest->port, VTY_NEWLINE);
nat: Make ping/pong timeout configurable.
2010-05-05 08:57:38 +00:00
vty_out(vty, " timeout auth %d%s", _nat->auth_timeout, VTY_NEWLINE);
vty_out(vty, " timeout ping %d%s", _nat->ping_timeout, VTY_NEWLINE);
vty_out(vty, " timeout pong %d%s", _nat->pong_timeout, VTY_NEWLINE);
NAT: move BSC config into separate file Introduce new configuration option bscs-config-file which includes BSC configuration from the given file. Both absolute and relative (to the main config file) paths are supported. Add 'show bscs-config' command to display current BSC configuration. Note: it is still possible to have BSC configuration in the main file (provided proper index number is used) and in runtime but BSC configuration is no longer saved automatically. The management of included configuration file is left to external tools. Update configuration examples. Fixes: OS#1669 Sponsored-by: On-Waves ehf
2016-04-12 14:59:25 +00:00
if (_nat->include_file)
vty_out(vty, " bscs-config-file %s%s", _nat->include_file, VTY_NEWLINE);
[nat] Add a token to the nat config and handle ID GET This allows to chain a nat with a nat by answering to the id get code and sending the token.
2010-05-14 16:14:58 +00:00
if (_nat->token)
vty_out(vty, " token %s%s", _nat->token, VTY_NEWLINE);
nat: Rename ip-tos to ip-dscp and provide an alias...
2010-07-27 11:21:53 +00:00
vty_out(vty, " ip-dscp %d%s", _nat->bsc_ip_dscp, VTY_NEWLINE);
[nat] Introduce the concept of access-list One can set one access-list to one BSC and one access-list to one NAT. The matching of IMSIs remains the same for now, also applying the white/blacklist. Access lists can not be deleted for now and no perf opt is done (e.g. one could cache the result of the last lookup in the bsc struct).
2010-05-31 17:03:13 +00:00
if (_nat->acc_lst_name)
vty_out(vty, " access-list-name %s%s", _nat->acc_lst_name, VTY_NEWLINE);
nat: Introduce a global IMSI barr list using red-black trees
2013-01-01 10:25:09 +00:00
if (_nat->imsi_black_list_fn)
vty_out(vty, " imsi-black-list-file-name %s%s",
_nat->imsi_black_list_fn, VTY_NEWLINE);
nat: Provide a USSD access list to check for which to play HLR.
2010-10-10 15:29:20 +00:00
if (_nat->ussd_lst_name)
vty_out(vty, " ussd-list-name %s%s", _nat->ussd_lst_name, VTY_NEWLINE);
nat: Add an option to set the query string to match Allow the query string to be set. The ussd matching code will check for this string and then forward it to the bypass.
2010-10-11 08:06:39 +00:00
if (_nat->ussd_query)
vty_out(vty, " ussd-query %s%s", _nat->ussd_query, VTY_NEWLINE);
nat: Keep a ussd token in the config We will have the USSD provider connecting to us and we will use the IPA protocol, including the auth mechanism.
2010-10-12 16:25:52 +00:00
if (_nat->ussd_token)
vty_out(vty, " ussd-token %s%s", _nat->ussd_token, VTY_NEWLINE);
if (_nat->ussd_local)
vty_out(vty, " ussd-local-ip %s%s", _nat->ussd_local, VTY_NEWLINE);
[nat] Introduce the concept of access-list One can set one access-list to one BSC and one access-list to one NAT. The matching of IMSIs remains the same for now, also applying the white/blacklist. Access lists can not be deleted for now and no perf opt is done (e.g. one could cache the result of the last lookup in the bsc struct).
2010-05-31 17:03:13 +00:00
nat: Add vty option for number rewriting Parse a msg file in case we do have a list.
2010-10-21 08:59:54 +00:00
if (_nat->num_rewr_name)
vty_out(vty, " number-rewrite %s%s", _nat->num_rewr_name, VTY_NEWLINE);
nat: Implement a post-routing for the NAT software * The post-routing is applied after the first re-writing. To do this the new number is copied back into the called data structure. * Add a testcase that goes from 0172 to 0049 and then back to 0049 using the post rule with a table lookup.
2013-06-25 13:38:31 +00:00
if (_nat->num_rewr_post_name)
vty_out(vty, " number-rewrite-post %s%s",
_nat->num_rewr_post_name, VTY_NEWLINE);
nat: Add VTY code to configure the SMSC rewriting
2011-05-30 22:35:46 +00:00
if (_nat->smsc_rewr_name)
vty_out(vty, " rewrite-smsc addr %s%s",
_nat->smsc_rewr_name, VTY_NEWLINE);
if (_nat->tpdest_match_name)
vty_out(vty, " rewrite-smsc tp-dest-match %s%s",
_nat->tpdest_match_name, VTY_NEWLINE);
nat: Implement clearing of TP-SRR flags from TPDUs Match IMSI and destination address against a set of entries, if it is matching the header will be modified and no sender report will be requested. Change the test case to request the sender report and then verify that this bit is reset to 0.
2012-01-10 21:39:07 +00:00
if (_nat->sms_clear_tp_srr_name)
vty_out(vty, " sms-clear-tp-srr %s%s",
_nat->sms_clear_tp_srr_name, VTY_NEWLINE);
nat: Add VTY command for the TP-DA rewriting.
2012-01-18 19:40:01 +00:00
if (_nat->sms_num_rewr_name)
vty_out(vty, " sms-number-rewrite %s%s",
_nat->sms_num_rewr_name, VTY_NEWLINE);
nat: Allow to use the prefix lookup to rewrite numbers * Increase the rewritten rule to five digits (this is the easiest for the unit test). This will add another 40kb to the runtime size. * Create a unit test that tests adding and removing the prefix rules. * Use the regexp match to replace from one package
2013-06-25 09:44:01 +00:00
if (_nat->num_rewr_trie_name)
vty_out(vty, " prefix-tree %s%s",
_nat->num_rewr_trie_name, VTY_NEWLINE);
nat: Add vty option for number rewriting Parse a msg file in case we do have a list.
2010-10-21 08:59:54 +00:00
nat: Create a Paging Group that BSCs can refer to Introduce a paging group that a BSC can refer to and is used during the LAC lookup. This way paging can be flooded through the network and just filtered at the last element in the core.
2011-05-02 17:16:13 +00:00
llist_for_each_entry(lst, &_nat->access_lists, list)
filter: Remove nat from bsc_nat_acc_lst and replace with msg
2015-04-04 20:40:12 +00:00
bsc_msg_acc_lst_write(vty, lst);
nat: Create a Paging Group that BSCs can refer to Introduce a paging group that a BSC can refer to and is used during the LAC lookup. This way paging can be flooded through the network and just filtered at the last element in the core.
2011-05-02 17:16:13 +00:00
llist_for_each_entry(pgroup, &_nat->paging_groups, entry)
write_pgroup_lst(vty, pgroup);
nat: Make it possible to send MGCP messages through the IPA multiplex Instead of handling MGCP through the UDP socket, read and write messages through the ipa connection to the MSC.
2012-11-05 13:54:56 +00:00
if (_nat->mgcp_ipa)
vty: Rename 'mgcp-through-msc-ipa' command to 'use-msc-ipa-for-mgcp' Currently the 'mgcp' command fails in the 'config-nat' node, because it get confused with 'mgcp-through-msc-ipa' which is executed instead because of the prefix based command selection. Thus the latter command is renamed by this patch to avoid the common prefix. The workaround in the test suite is removed.
2013-09-02 11:17:17 +00:00
vty_out(vty, " use-msc-ipa-for-mgcp%s", VTY_NEWLINE);
nat: Make mode-set patching optional
2015-04-24 00:25:17 +00:00
vty_out(vty, " %ssdp-ensure-amr-mode-set%s",
_nat->sdp_ensure_amr_mode_set ? "" : "no ", VTY_NEWLINE);
[nat] Introduce the concept of access-list One can set one access-list to one BSC and one access-list to one NAT. The matching of IMSIs remains the same for now, also applying the white/blacklist. Access lists can not be deleted for now and no perf opt is done (e.g. one could cache the result of the last lookup in the bsc struct).
2010-05-31 17:03:13 +00:00
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
return CMD_SUCCESS;
}
static void config_write_bsc_single(struct vty *vty, struct bsc_config *bsc)
{
vty_out(vty, " bsc %u%s", bsc->nr, VTY_NEWLINE);
vty_out(vty, " token %s%s", bsc->token, VTY_NEWLINE);
nat: After we identified the bsc check the key We are using the token to find the right bsc_config and then we can use the last_rand of the bsc_connection to calculate the expected result and try to compare it with a time constant(???) memcmp.
2015-06-08 16:33:28 +00:00
if (bsc->key_present)
vty_out(vty, " auth-key %s%s", osmo_hexdump(bsc->key, 16), VTY_NEWLINE);
nat: Create a Paging Group that BSCs can refer to Introduce a paging group that a BSC can refer to and is used during the LAC lookup. This way paging can be flooded through the network and just filtered at the last element in the core.
2011-05-02 17:16:13 +00:00
dump_lac(vty, &bsc->lac_list);
[nat] Allow to set the description for the bsc. This will allow to add description to each BSC.
2010-05-14 14:06:28 +00:00
if (bsc->description)
vty_out(vty, " description %s%s", bsc->description, VTY_NEWLINE);
[nat] Introduce the concept of access-list One can set one access-list to one BSC and one access-list to one NAT. The matching of IMSIs remains the same for now, also applying the white/blacklist. Access lists can not be deleted for now and no perf opt is done (e.g. one could cache the result of the last lookup in the bsc struct).
2010-05-31 17:03:13 +00:00
if (bsc->acc_lst_name)
nat: Fix the access-list-name command... We have added two commands with the same name to the tree.. the second one should have been the BSC...
2010-06-08 03:18:26 +00:00
vty_out(vty, " access-list-name %s%s", bsc->acc_lst_name, VTY_NEWLINE);
nat: Change number of multiplexes to the max-endpoints
2011-02-27 10:04:27 +00:00
vty_out(vty, " max-endpoints %d%s", bsc->max_endpoints, VTY_NEWLINE);
nat: Create a Paging Group that BSCs can refer to Introduce a paging group that a BSC can refer to and is used during the LAC lookup. This way paging can be flooded through the network and just filtered at the last element in the core.
2011-05-02 17:16:13 +00:00
if (bsc->paging_group != -1)
nat: Use 'paging group' because we have paging forbidden. Make paging-group deprecated and introduce the new paging group.
2011-05-17 17:28:07 +00:00
vty_out(vty, " paging group %d%s", bsc->paging_group, VTY_NEWLINE);
vty_out(vty, " paging forbidden %d%s", bsc->forbid_paging, VTY_NEWLINE);
osmux: Enforce Osmux only global and per BSC configuration Extend the osmux only setting from the MGCP MGW to the NAT. This is applied when an endpoint is allocated and/or when the allocation is confirmed by the remote system. Not tested. The impact should only be when the new option is being used. Fixes: OW#1492
2015-10-02 16:15:18 +00:00
switch (bsc->osmux) {
case OSMUX_USAGE_ON:
mgcp: add voice muxer support This patch adds the voice muxer. You can use this to batch RTP traffic to reduce bandwidth comsuption. Basically, osmux transforms RTP flows to a compact batch format, that is later on decompacted to its original form. Port UDP/1984 is used for the muxer traffic between osmo-bsc_nat and osmo-bsc_mgcp (in the BSC side). This feature depends on libosmo-netif, which contains the osmux core support. Osmux is requested on-demand via the MGCP CRCX/MDCX messages (using the vendor-specific extension X-Osmux: on) coming from the BSC-NAT, so you can selectively enable osmux per BSC from one the bsc-nat.cfg file, so we have a centralized point to enable/disable osmux. First thing you need to do is to accept requests to use Osmux, this can be done from VTY interface of osmo-bsc_nat and osmo-bsc_mgcp by adding the following line: mgcp ... osmux on osmux batch-factor 4 This just initializes the osmux engine. You still have to specify what BSC uses osmux from osmo-bsc_nat configuration file: ... bsc 1 osmux on bsc 2 ... bsc 3 osmux on In this case, bsc 1 and 3 should use osmux if possible, bsc 2 does not have osmux enabled. Thus, you can selectively enable osmux depending on the BSC, and we have a centralized point for configuration from the bsc-nat to enable osmux on demand, as suggested by Holger. At this moment, this patch contains heavy debug logging for each RTP packet that can be removed later to save cycles. The RTP ssrc/seqnum/timestamp is randomly allocated for each MDCX that is received to configure an endpoint.
2014-02-05 17:56:17 +00:00
vty_out(vty, " osmux on%s", VTY_NEWLINE);
osmux: Enforce Osmux only global and per BSC configuration Extend the osmux only setting from the MGCP MGW to the NAT. This is applied when an endpoint is allocated and/or when the allocation is confirmed by the remote system. Not tested. The impact should only be when the new option is being used. Fixes: OW#1492
2015-10-02 16:15:18 +00:00
break;
case OSMUX_USAGE_ONLY:
vty_out(vty, " osmux only%s", VTY_NEWLINE);
break;
}
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
}
static int config_write_bsc(struct vty *vty)
{
struct bsc_config *bsc;
llist_for_each_entry(bsc, &_nat->bsc_configs, entry)
config_write_bsc_single(vty, bsc);
return CMD_SUCCESS;
}
NAT: move BSC config into separate file Introduce new configuration option bscs-config-file which includes BSC configuration from the given file. Both absolute and relative (to the main config file) paths are supported. Add 'show bscs-config' command to display current BSC configuration. Note: it is still possible to have BSC configuration in the main file (provided proper index number is used) and in runtime but BSC configuration is no longer saved automatically. The management of included configuration file is left to external tools. Update configuration examples. Fixes: OS#1669 Sponsored-by: On-Waves ehf
2016-04-12 14:59:25 +00:00
DEFUN(show_bscs, show_bscs_cmd, "show bscs-config",
SHOW_STR "Show configured BSCs\n"
"Both from included file and vty\n")
{
vty_out(vty, "BSCs configuration loaded from %s:%s", _nat->resolved_path,
VTY_NEWLINE);
return config_write_bsc(vty);
}
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
nat: Make sccp/bsc show connections more Cisco like... Second attempt to use a syntax more comparable to 'Cisco', I have never used such a system... let us see how this is going.
2010-04-19 08:06:43 +00:00
DEFUN(show_sccp, show_sccp_cmd, "show sccp connections",
nat: Document all parameters of the VTY commands
2012-07-28 14:14:04 +00:00
SHOW_STR "Display information about SCCP\n"
"All active connections\n")
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
{
nat: Rename "struct sccp_connections" to "struct nat_sccp_connection" The name sccp_connection is used in the osmo-sccp code, sccp_connections was used in the NAT for tracking a sccp_connection. Rename it so it is obvious that the struct belongs to the nat. The rename was done with sed: $ sed -i s,"struct sccp_connections","struct nat_sccp_connection",g \ include/openbsc/*.h src/osmo-bsc_nat/* tests/*/*
2013-04-16 07:53:13 +00:00
struct nat_sccp_connection *con;
nat: Fix the grammar of the sentence for listing open sccp connections
2010-09-15 11:01:31 +00:00
vty_out(vty, "Listing all open SCCP connections%s", VTY_NEWLINE);
nat: Print the remote reference as well.
2010-04-27 05:11:18 +00:00
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
llist_for_each_entry(con, &_nat->sccp_connections, list_entry) {
nat: Allow a BSC to have multiple LACs Make it possible that one BSC is serving multiple cells. Introduce a list of lacs, add functions to manipulate the lists. The current test cases for paging by lac continue to work.
2010-10-08 14:08:29 +00:00
vty_out(vty, "For BSC Nr: %d BSC ref: 0x%x; MUX ref: 0x%x; Network has ref: %d ref: 0x%x MSC/BSC mux: 0x%x/0x%x type: %s%s",
nat: Store the config in the connection instead of the lac This allows that we can print the Nr. next to the lac and it allows us to change the lac at runtime without reconnecting the BSC.
2010-04-06 13:11:34 +00:00
con->bsc->cfg ? con->bsc->cfg->nr : -1,
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
sccp_src_ref_to_int(&con->real_ref),
nat: Print the MSC multiplex as well
2010-04-05 08:10:33 +00:00
sccp_src_ref_to_int(&con->patched_ref),
nat: Print the remote reference as well.
2010-04-27 05:11:18 +00:00
con->has_remote_ref,
sccp_src_ref_to_int(&con->remote_ref),
nat: Make the code work in terms of endpoints instead of timeslot/multiplex We are going to have more than one trunk, so all code hardcoding the multiplex to zero must go. Avoid this kind of problem by saving the MGCP endpoint number and comparing that.
2010-08-28 08:08:39 +00:00
con->msc_endp, con->bsc_endp,
filter: Move the con_type into the filter_state
2015-04-05 19:03:49 +00:00
bsc_con_type_to_string(con->filter_state.con_type),
nat: Print the MSC multiplex as well
2010-04-05 08:10:33 +00:00
VTY_NEWLINE);
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
}
return CMD_SUCCESS;
}
NAT: vty command to display number of BSCs Add command 'show nat num-bscs-configured' to display number of configured BSCs. Sponsored-by: On-Waves ehf
2016-04-06 15:25:44 +00:00
DEFUN(show_nat_bsc, show_nat_bsc_cmd, "show nat num-bscs-configured",
SHOW_STR "Display NAT configuration details\n"
"BSCs-related\n")
{
vty_out(vty, "%d BSCs configured%s", _nat->num_bsc, VTY_NEWLINE);
return CMD_SUCCESS;
}
nat: Make sccp/bsc show connections more Cisco like... Second attempt to use a syntax more comparable to 'Cisco', I have never used such a system... let us see how this is going.
2010-04-19 08:06:43 +00:00
DEFUN(show_bsc, show_bsc_cmd, "show bsc connections",
nat: Document all parameters of the VTY commands
2012-07-28 14:14:04 +00:00
SHOW_STR BSC_STR
"All active connections\n")
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
{
struct bsc_connection *con;
nat: Print the IP address of the connected BSCs
2010-04-08 08:35:20 +00:00
struct sockaddr_in sock;
socklen_t len = sizeof(sock);
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
llist_for_each_entry(con, &_nat->bsc_connections, list_entry) {
nat: Print the IP address of the connected BSCs
2010-04-08 08:35:20 +00:00
getpeername(con->write_queue.bfd.fd, (struct sockaddr *) &sock, &len);
nat: We want the remote to respond to our DLCX request We want to send a TRAP with the MGCP statistics from the NAT and the connected BSC. The BSC endpoint can be either released because of a DLCX from the MGCP CallAgent or the SCCP Connection release on the A-link. This is why we need to queue the statistics when the deleting the endpoint on the BSC. The processing is continued once the response arrives. This code assumes that the response of the DLCX will be sent by the remote side. The current amount of outstanding responses can be seen on the VTY. This assumption is based on the fact that the BSC has already responded to the CRCX and maybe to the MDCX. The MGCP RFC is bended to prefix the transaction identifier with "nat-" to easily detect the response and hand it to the handler. This will then parse the response and generate the TRAP. The current version is v1. We assume that the transaction space is big enough and we will not re-assign the transaction identifier too early.
2012-10-24 19:53:40 +00:00
vty_out(vty, "BSC nr: %d auth: %d fd: %d peername: %s pending-stats: %u%s",
nat: Store the config in the connection instead of the lac This allows that we can print the Nr. next to the lac and it allows us to change the lac at runtime without reconnecting the BSC.
2010-04-06 13:11:34 +00:00
con->cfg ? con->cfg->nr : -1,
nat: Print the IP address of the connected BSCs
2010-04-08 08:35:20 +00:00
con->authenticated, con->write_queue.bfd.fd,
nat: We want the remote to respond to our DLCX request We want to send a TRAP with the MGCP statistics from the NAT and the connected BSC. The BSC endpoint can be either released because of a DLCX from the MGCP CallAgent or the SCCP Connection release on the A-link. This is why we need to queue the statistics when the deleting the endpoint on the BSC. The processing is continued once the response arrives. This code assumes that the response of the DLCX will be sent by the remote side. The current amount of outstanding responses can be seen on the VTY. This assumption is based on the fact that the BSC has already responded to the CRCX and maybe to the MDCX. The MGCP RFC is bended to prefix the transaction identifier with "nat-" to easily detect the response and hand it to the handler. This will then parse the response and generate the TRAP. The current version is v1. We assume that the transaction space is big enough and we will not re-assign the transaction identifier too early.
2012-10-24 19:53:40 +00:00
inet_ntoa(sock.sin_addr), con->pending_dlcx_count,
VTY_NEWLINE);
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
}
return CMD_SUCCESS;
}
nat: Add vty command to show the endpoint allocation status
2010-08-28 10:33:34 +00:00
DEFUN(show_bsc_mgcp, show_bsc_mgcp_cmd, "show bsc mgcp NR",
nat: Document all parameters of the VTY commands
2012-07-28 14:14:04 +00:00
SHOW_STR BSC_STR MGCP_STR "Identifier of the BSC\n")
nat: Add vty command to show the endpoint allocation status
2010-08-28 10:33:34 +00:00
{
struct bsc_connection *con;
int nr = atoi(argv[0]);
nat: Allocate endpoints from multiple multiplexes. This code allocates endpoints from multiple multiplexes but will always leave 0x0 and 0x1f unassigned in the multiplex.
2011-02-26 10:38:00 +00:00
int i, j, endp;
nat: Add vty command to show the endpoint allocation status
2010-08-28 10:33:34 +00:00
llist_for_each_entry(con, &_nat->bsc_connections, list_entry) {
nat: Change number of multiplexes to the max-endpoints
2011-02-27 10:04:27 +00:00
int max;
nat: Add vty command to show the endpoint allocation status
2010-08-28 10:33:34 +00:00
if (!con->cfg)
continue;
if (con->cfg->nr != nr)
continue;
nat: Allocate the endpoint status dynamically Allocate the status for an endpoint dynamically. We will support BSCs with different amount of multiplexes and need to have this flexibility in the future. Add the proper null checks to the current users of this code.
2011-02-25 16:09:07 +00:00
/* this bsc has no audio endpoints yet */
if (!con->_endpoint_status)
continue;
nat: Add vty command to show the endpoint allocation status
2010-08-28 10:33:34 +00:00
vty_out(vty, "MGCP Status for %d%s", con->cfg->nr, VTY_NEWLINE);
nat: Change number of multiplexes to the max-endpoints
2011-02-27 10:04:27 +00:00
max = bsc_mgcp_nr_multiplexes(con->max_endpoints);
for (i = 0; i < max; ++i) {
nat: Fix timeslot range in 'show bsc mgcp' VTY command Currently the inner loop in show_bsc_mgcp iterates of the timeslot interval [0, 31]. Timeslot 0 is not valid, which causes mgcp_timeslot_to_endpoint to generate a corresponding warning and to return an invalid endp value. That value causes an out-of-bound read access, possibly hitting unallocated memory. This patch fixes the loop range by starting with timeslot 1. Note that this does not prevent mgcp_timeslot_to_endpoint from returning an invalid endpoint index when called with arguments not within its domain. Addresses: <000b> ../../include/openbsc/mgcp.h:250 Timeslot should not be 0 [...] vty=0xb4203db0, argc=1, argv=0xbfffebb0) at bsc_nat_vty.c:256 max = 1 con = 0xb4a004f0 i = 0 j = 0 [...] ==15700== ERROR: AddressSanitizer: heap-use-after-free on address 0xb520be4f at pc 0x8062a42 bp 0xbfffeb18 sp 0xbfffeb0c Sponsored-by: On-Waves ehf
2015-04-07 15:49:47 +00:00
for (j = 1; j < 32; ++j) {
nat: Allocate endpoints from multiple multiplexes. This code allocates endpoints from multiple multiplexes but will always leave 0x0 and 0x1f unassigned in the multiplex.
2011-02-26 10:38:00 +00:00
endp = mgcp_timeslot_to_endpoint(i, j);
vty_out(vty, " Endpoint 0x%x %s%s", endp,
con->_endpoint_status[endp] == 0
? "free" : "allocated",
nat: Add vty command to show the endpoint allocation status
2010-08-28 10:33:34 +00:00
VTY_NEWLINE);
nat: Allocate endpoints from multiple multiplexes. This code allocates endpoints from multiple multiplexes but will always leave 0x0 and 0x1f unassigned in the multiplex.
2011-02-26 10:38:00 +00:00
}
}
nat: Add vty command to show the endpoint allocation status
2010-08-28 10:33:34 +00:00
break;
}
return CMD_SUCCESS;
}
nat: Use show bsc config for showing the configuration.
2010-04-22 05:36:46 +00:00
DEFUN(show_bsc_cfg, show_bsc_cfg_cmd, "show bsc config",
nat: Document all parameters of the VTY commands
2012-07-28 14:14:04 +00:00
SHOW_STR BSC_STR "Configuration of BSCs\n")
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
{
struct bsc_config *conf;
llist_for_each_entry(conf, &_nat->bsc_configs, entry) {
nat: Allow a BSC to have multiple LACs Make it possible that one BSC is serving multiple cells. Introduce a list of lacs, add functions to manipulate the lists. The current test cases for paging by lac continue to work.
2010-10-08 14:08:29 +00:00
vty_out(vty, "BSC token: '%s' nr: %u%s",
conf->token, conf->nr, VTY_NEWLINE);
[nat] Introduce the concept of access-list One can set one access-list to one BSC and one access-list to one NAT. The matching of IMSIs remains the same for now, also applying the white/blacklist. Access lists can not be deleted for now and no perf opt is done (e.g. one could cache the result of the last lookup in the bsc struct).
2010-05-31 17:03:13 +00:00
if (conf->acc_lst_name)
vty_out(vty, " access-list: %s%s",
conf->acc_lst_name, VTY_NEWLINE);
[nat] Add option to forbid the paging to the BSC. This can be done for testing purposes and to allow making a BTS crash that can not handle paging requests properly.
2010-04-21 11:05:14 +00:00
vty_out(vty, " paging forbidden: %d%s",
conf->forbid_paging, VTY_NEWLINE);
[nat] Allow to set the description for the bsc. This will allow to add description to each BSC.
2010-05-14 14:06:28 +00:00
if (conf->description)
vty_out(vty, " description: %s%s", conf->description, VTY_NEWLINE);
else
vty_out(vty, " No description.%s", VTY_NEWLINE);
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
}
return CMD_SUCCESS;
}
nat: Introduce a show statistics-by-lac LAC Currently show show statistics only work by given the internal configuration number, add a version that is working by LAC of the BSC.
2010-07-22 12:26:10 +00:00
static void dump_stat_total(struct vty *vty, struct bsc_nat *nat)
{
vty_out(vty, "NAT statistics%s", VTY_NEWLINE);
vty_out(vty, " SCCP Connections %lu total, %lu calls%s",
src: use namespace prefix osmo_counter* Summary of changes: s/struct counter/struct osmo_counter/g s/counter_inc/osmo_counter_inc/g s/counter_get/osmo_counter_get/g s/counter_reset/osmo_counter_reset/g s/counter_alloc/osmo_counter_alloc/g s/counter_free/osmo_counter_free
2011-05-06 10:13:10 +00:00
osmo_counter_get(nat->stats.sccp.conn),
osmo_counter_get(nat->stats.sccp.calls), VTY_NEWLINE);
nat: Introduce a show statistics-by-lac LAC Currently show show statistics only work by given the internal configuration number, add a version that is working by LAC of the BSC.
2010-07-22 12:26:10 +00:00
vty_out(vty, " MSC Connections %lu%s",
src: use namespace prefix osmo_counter* Summary of changes: s/struct counter/struct osmo_counter/g s/counter_inc/osmo_counter_inc/g s/counter_get/osmo_counter_get/g s/counter_reset/osmo_counter_reset/g s/counter_alloc/osmo_counter_alloc/g s/counter_free/osmo_counter_free
2011-05-06 10:13:10 +00:00
osmo_counter_get(nat->stats.msc.reconn), VTY_NEWLINE);
nat: Show if we are connected to the MSC.
2010-08-03 18:34:10 +00:00
vty_out(vty, " MSC Connected: %d%s",
nat: Use bsc_nat_msc_is_connected instead of accessing it directly
2013-08-27 06:47:23 +00:00
bsc_nat_msc_is_connected(nat), VTY_NEWLINE);
nat: Introduce a show statistics-by-lac LAC Currently show show statistics only work by given the internal configuration number, add a version that is working by LAC of the BSC.
2010-07-22 12:26:10 +00:00
vty_out(vty, " BSC Connections %lu total, %lu auth failed.%s",
src: use namespace prefix osmo_counter* Summary of changes: s/struct counter/struct osmo_counter/g s/counter_inc/osmo_counter_inc/g s/counter_get/osmo_counter_get/g s/counter_reset/osmo_counter_reset/g s/counter_alloc/osmo_counter_alloc/g s/counter_free/osmo_counter_free
2011-05-06 10:13:10 +00:00
osmo_counter_get(nat->stats.bsc.reconn),
osmo_counter_get(nat->stats.bsc.auth_fail), VTY_NEWLINE);
nat: Introduce a show statistics-by-lac LAC Currently show show statistics only work by given the internal configuration number, add a version that is working by LAC of the BSC.
2010-07-22 12:26:10 +00:00
}
static void dump_stat_bsc(struct vty *vty, struct bsc_config *conf)
{
nat: Provide an easy view to see if something is connected to the NAT.
2010-07-22 12:37:35 +00:00
int connected = 0;
struct bsc_connection *con;
nat: Allow a BSC to have multiple LACs Make it possible that one BSC is serving multiple cells. Introduce a list of lacs, add functions to manipulate the lists. The current test cases for paging by lac continue to work.
2010-10-08 14:08:29 +00:00
vty_out(vty, " BSC nr: %d%s",
conf->nr, VTY_NEWLINE);
nat: Introduce a show statistics-by-lac LAC Currently show show statistics only work by given the internal configuration number, add a version that is working by LAC of the BSC.
2010-07-22 12:26:10 +00:00
vty_out_rate_ctr_group(vty, " ", conf->stats.ctrg);
nat: Provide an easy view to see if something is connected to the NAT.
2010-07-22 12:37:35 +00:00
llist_for_each_entry(con, &conf->nat->bsc_connections, list_entry) {
if (con->cfg != conf)
continue;
connected = 1;
break;
}
nat: Indent the connected... to make it belong to the BSC group
2010-08-03 18:29:03 +00:00
vty_out(vty, " Connected: %d%s", connected, VTY_NEWLINE);
nat: Introduce a show statistics-by-lac LAC Currently show show statistics only work by given the internal configuration number, add a version that is working by LAC of the BSC.
2010-07-22 12:26:10 +00:00
}
[nat] Add show statistics to the nat
2010-04-12 10:33:27 +00:00
DEFUN(show_stats,
show_stats_cmd,
nat: Allow to only show statistics for a given BSC Cfg.
2010-05-02 10:59:24 +00:00
"show statistics [NR]",
nat: Document all parameters of the VTY commands
2012-07-28 14:14:04 +00:00
SHOW_STR "Display network statistics\n"
"Number of the BSC\n")
[nat] Add show statistics to the nat
2010-04-12 10:33:27 +00:00
{
struct bsc_config *conf;
nat: Allow to only show statistics for a given BSC Cfg.
2010-05-02 10:59:24 +00:00
int nr = -1;
if (argc == 1)
nr = atoi(argv[0]);
nat: Introduce a show statistics-by-lac LAC Currently show show statistics only work by given the internal configuration number, add a version that is working by LAC of the BSC.
2010-07-22 12:26:10 +00:00
dump_stat_total(vty, _nat);
[nat] Add show statistics to the nat
2010-04-12 10:33:27 +00:00
llist_for_each_entry(conf, &_nat->bsc_configs, entry) {
nat: Allow to only show statistics for a given BSC Cfg.
2010-05-02 10:59:24 +00:00
if (argc == 1 && nr != conf->nr)
continue;
nat: Introduce a show statistics-by-lac LAC Currently show show statistics only work by given the internal configuration number, add a version that is working by LAC of the BSC.
2010-07-22 12:26:10 +00:00
dump_stat_bsc(vty, conf);
}
return CMD_SUCCESS;
}
nat: Allow to only show statistics for a given BSC Cfg.
2010-05-02 10:59:24 +00:00
nat: Introduce a show statistics-by-lac LAC Currently show show statistics only work by given the internal configuration number, add a version that is working by LAC of the BSC.
2010-07-22 12:26:10 +00:00
DEFUN(show_stats_lac,
show_stats_lac_cmd,
"show statistics-by-lac <0-65535>",
SHOW_STR "Display network statistics by lac\n"
"The lac of the BSC\n")
{
int lac;
struct bsc_config *conf;
lac = atoi(argv[0]);
dump_stat_total(vty, _nat);
llist_for_each_entry(conf, &_nat->bsc_configs, entry) {
nat: Allow a BSC to have multiple LACs Make it possible that one BSC is serving multiple cells. Introduce a list of lacs, add functions to manipulate the lists. The current test cases for paging by lac continue to work.
2010-10-08 14:08:29 +00:00
if (!bsc_config_handles_lac(conf, lac))
nat: Introduce a show statistics-by-lac LAC Currently show show statistics only work by given the internal configuration number, add a version that is working by LAC of the BSC.
2010-07-22 12:26:10 +00:00
continue;
dump_stat_bsc(vty, conf);
[nat] Add show statistics to the nat
2010-04-12 10:33:27 +00:00
}
return CMD_SUCCESS;
}
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
nat: Print the MSC status with a new vty command.
2010-05-11 11:07:39 +00:00
DEFUN(show_msc,
show_msc_cmd,
"show msc connection",
nat: Document all parameters of the VTY commands
2012-07-28 14:14:04 +00:00
SHOW_STR "MSC related information\n"
"Status of the A-link connection\n")
nat: Print the MSC status with a new vty command.
2010-05-11 11:07:39 +00:00
{
if (!_nat->msc_con) {
nat: Misc changes spotted while going through the file with Jacob * Spell Configure correctly * Use %s and VTY_NEWLINE instead of \n
2013-08-13 09:36:33 +00:00
vty_out(vty, "The MSC is not yet configured.%s", VTY_NEWLINE);
nat: Print the MSC status with a new vty command.
2010-05-11 11:07:39 +00:00
return CMD_WARNING;
}
nat: Misc changes spotted while going through the file with Jacob * Spell Configure correctly * Use %s and VTY_NEWLINE instead of \n
2013-08-13 09:36:33 +00:00
vty_out(vty, "MSC is connected: %d%s",
nat: Use bsc_nat_msc_is_connected instead of accessing it directly
2013-08-27 06:47:23 +00:00
bsc_nat_msc_is_connected(_nat), VTY_NEWLINE);
nat: Print the MSC status with a new vty command.
2010-05-11 11:07:39 +00:00
return CMD_SUCCESS;
}
nat: Add a command to close a given BSC Connection This can be used to clear stale connections for a given BSC or to force a reconnect of the BSC.
2010-04-27 05:21:39 +00:00
DEFUN(close_bsc,
close_bsc_cmd,
"close bsc connection BSC_NR",
nat: Document all parameters of the VTY commands
2012-07-28 14:14:04 +00:00
"Close\n" "A-link\n" "Connection\n" "Identifier of the BSC\n")
nat: Add a command to close a given BSC Connection This can be used to clear stale connections for a given BSC or to force a reconnect of the BSC.
2010-04-27 05:21:39 +00:00
{
struct bsc_connection *bsc;
int bsc_nr = atoi(argv[0]);
llist_for_each_entry(bsc, &_nat->bsc_connections, list_entry) {
if (!bsc->cfg || bsc->cfg->nr != bsc_nr)
continue;
bsc_close_connection(bsc);
break;
}
return CMD_SUCCESS;
}
nat: Misc changes spotted while going through the file with Jacob * Spell Configure correctly * Use %s and VTY_NEWLINE instead of \n
2013-08-13 09:36:33 +00:00
DEFUN(cfg_nat, cfg_nat_cmd, "nat", "Configure the NAT")
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
{
vty->index = _nat;
vty->node = NAT_NODE;
return CMD_SUCCESS;
}
nat: Move MSC ip address into the config.. The address can still be specified on the cli and it will overwrite the config in the config file.
2010-06-15 10:51:04 +00:00
DEFUN(cfg_nat_msc_ip,
cfg_nat_msc_ip_cmd,
[nat] Use A.B.C.D for the IP address The VTY code will then be able to validate the IP Address.
2010-05-13 18:36:42 +00:00
"msc ip A.B.C.D",
nat: Document all parameters of the VTY commands
2012-07-28 14:14:04 +00:00
"MSC related configuration\n"
"Configure the IP address\n" IP_STR)
nat: Move MSC ip address into the config.. The address can still be specified on the cli and it will overwrite the config in the config file.
2010-06-15 10:51:04 +00:00
{
bsc_nat_set_msc_ip(_nat, argv[0]);
return CMD_SUCCESS;
}
nat: Make the MSC configurable.
2010-04-17 05:48:45 +00:00
DEFUN(cfg_nat_msc_port,
cfg_nat_msc_port_cmd,
"msc port <1-65500>",
nat: Document all parameters of the VTY commands
2012-07-28 14:14:04 +00:00
"MSC related configuration\n"
"Configure the port\n"
"Port number\n")
nat: Make the MSC configurable.
2010-04-17 05:48:45 +00:00
{
bsc: Allow to have a list of MSCs/MUXs to connect to Be able to configure a list of destinations (duplicates allowed) that will be tried in a round robin fashion. The change is in the bsc_msc_connection to operate on a list. We achieve the round robin nature with the same trick used in the paging code to delete and append the current entry. The nat code was updated to compile but one can only configure one destination.
2011-04-23 21:31:31 +00:00
_nat->main_dest->port = atoi(argv[0]);
nat: Make the MSC configurable.
2010-04-17 05:48:45 +00:00
return CMD_SUCCESS;
}
nat: Make ping/pong timeout configurable.
2010-05-05 08:57:38 +00:00
DEFUN(cfg_nat_auth_time,
cfg_nat_auth_time_cmd,
"timeout auth <1-256>",
nat: Document all parameters of the VTY commands
2012-07-28 14:14:04 +00:00
"Timeout configuration\n"
"Authentication timeout\n"
"Timeout in seconds\n")
nat: Make ping/pong timeout configurable.
2010-05-05 08:57:38 +00:00
{
_nat->auth_timeout = atoi(argv[0]);
return CMD_SUCCESS;
}
DEFUN(cfg_nat_ping_time,
cfg_nat_ping_time_cmd,
"timeout ping NR",
nat: Document all parameters of the VTY commands
2012-07-28 14:14:04 +00:00
"Timeout configuration\n"
"Time between two pings\n"
"Timeout in seconds\n")
nat: Make ping/pong timeout configurable.
2010-05-05 08:57:38 +00:00
{
_nat->ping_timeout = atoi(argv[0]);
return CMD_SUCCESS;
}
DEFUN(cfg_nat_pong_time,
cfg_nat_pong_time_cmd,
"timeout pong NR",
nat: Document all parameters of the VTY commands
2012-07-28 14:14:04 +00:00
"Timeout configuration\n"
"Waiting for pong timeout\n"
"Timeout in seconds\n")
nat: Make ping/pong timeout configurable.
2010-05-05 08:57:38 +00:00
{
_nat->pong_timeout = atoi(argv[0]);
return CMD_SUCCESS;
}
[nat] Add a token to the nat config and handle ID GET This allows to chain a nat with a nat by answering to the id get code and sending the token.
2010-05-14 16:14:58 +00:00
DEFUN(cfg_nat_token, cfg_nat_token_cmd,
"token TOKEN",
nat: Document all parameters of the VTY commands
2012-07-28 14:14:04 +00:00
"Authentication token configuration\n"
"Token of the BSC, currently transferred in cleartext\n")
[nat] Add a token to the nat config and handle ID GET This allows to chain a nat with a nat by answering to the id get code and sending the token.
2010-05-14 16:14:58 +00:00
{
don't re-implement osmo_talloc_replace_string() osmo_talloc_replace_string() was introducd into libosmocore in 2014, see commit f3c7e85d05f7b2b7bf093162b776f71b2bc6420d There's no reason for us to re-implement this as bsc_replace_string here. Change-Id: I6d2fcaabbc74730f6f491a2b2d5c784ccafc6602
2017-05-29 11:54:27 +00:00
osmo_talloc_replace_string(_nat, &_nat->token, argv[0]);
[nat] Add a token to the nat config and handle ID GET This allows to chain a nat with a nat by answering to the id get code and sending the token.
2010-05-14 16:14:58 +00:00
return CMD_SUCCESS;
}
nat: Rename ip-tos to ip-dscp and provide an alias...
2010-07-27 11:21:53 +00:00
DEFUN(cfg_nat_bsc_ip_dscp, cfg_nat_bsc_ip_dscp_cmd,
"ip-dscp <0-255>",
"Set the IP DSCP for the BSCs to use\n" "Set the IP_TOS attribute")
[nat] Add ip-tos option to the nat. This is applied to all incoming BSC connections.
2010-05-31 02:36:35 +00:00
{
nat: Rename ip-tos to ip-dscp and provide an alias...
2010-07-27 11:21:53 +00:00
_nat->bsc_ip_dscp = atoi(argv[0]);
[nat] Add ip-tos option to the nat. This is applied to all incoming BSC connections.
2010-05-31 02:36:35 +00:00
return CMD_SUCCESS;
}
nat: Rename ip-tos to ip-dscp and provide an alias...
2010-07-27 11:21:53 +00:00
ALIAS_DEPRECATED(cfg_nat_bsc_ip_dscp, cfg_nat_bsc_ip_tos_cmd,
"ip-tos <0-255>",
"Use ip-dscp in the future.\n" "Set the DSCP\n")
[nat] Introduce the concept of access-list One can set one access-list to one BSC and one access-list to one NAT. The matching of IMSIs remains the same for now, also applying the white/blacklist. Access lists can not be deleted for now and no perf opt is done (e.g. one could cache the result of the last lookup in the bsc struct).
2010-05-31 17:03:13 +00:00
DEFUN(cfg_nat_acc_lst_name,
cfg_nat_acc_lst_name_cmd,
"access-list-name NAME",
"Set the name of the access list to use.\n"
"The name of the to be used access list.")
{
don't re-implement osmo_talloc_replace_string() osmo_talloc_replace_string() was introducd into libosmocore in 2014, see commit f3c7e85d05f7b2b7bf093162b776f71b2bc6420d There's no reason for us to re-implement this as bsc_replace_string here. Change-Id: I6d2fcaabbc74730f6f491a2b2d5c784ccafc6602
2017-05-29 11:54:27 +00:00
osmo_talloc_replace_string(_nat, &_nat->acc_lst_name, argv[0]);
[nat] Introduce the concept of access-list One can set one access-list to one BSC and one access-list to one NAT. The matching of IMSIs remains the same for now, also applying the white/blacklist. Access lists can not be deleted for now and no perf opt is done (e.g. one could cache the result of the last lookup in the bsc struct).
2010-05-31 17:03:13 +00:00
return CMD_SUCCESS;
}
NAT: move BSC config into separate file Introduce new configuration option bscs-config-file which includes BSC configuration from the given file. Both absolute and relative (to the main config file) paths are supported. Add 'show bscs-config' command to display current BSC configuration. Note: it is still possible to have BSC configuration in the main file (provided proper index number is used) and in runtime but BSC configuration is no longer saved automatically. The management of included configuration file is left to external tools. Update configuration examples. Fixes: OS#1669 Sponsored-by: On-Waves ehf
2016-04-12 14:59:25 +00:00
DEFUN(cfg_nat_include,
cfg_nat_include_cmd,
"bscs-config-file NAME",
"Set the filename of the BSC configuration to include.\n"
"The filename to be included.")
{
char *path;
int rc;
NAT: reload BSCs config dynamically Add vty tests for BSC configuration reloading. Load BSCs configuration on bscs-config-file command: * remove all runtime configured BSC not in the config file * close connections to all BSC with updated token value Fixes: OS#1670 Sponsored-by: On-Waves ehf
2016-04-13 09:36:39 +00:00
struct bsc_config *cf1, *cf2;
struct bsc_connection *con1, *con2;
NAT: move BSC config into separate file Introduce new configuration option bscs-config-file which includes BSC configuration from the given file. Both absolute and relative (to the main config file) paths are supported. Add 'show bscs-config' command to display current BSC configuration. Note: it is still possible to have BSC configuration in the main file (provided proper index number is used) and in runtime but BSC configuration is no longer saved automatically. The management of included configuration file is left to external tools. Update configuration examples. Fixes: OS#1669 Sponsored-by: On-Waves ehf
2016-04-12 14:59:25 +00:00
if ('/' == argv[0][0])
don't re-implement osmo_talloc_replace_string() osmo_talloc_replace_string() was introducd into libosmocore in 2014, see commit f3c7e85d05f7b2b7bf093162b776f71b2bc6420d There's no reason for us to re-implement this as bsc_replace_string here. Change-Id: I6d2fcaabbc74730f6f491a2b2d5c784ccafc6602
2017-05-29 11:54:27 +00:00
osmo_talloc_replace_string(_nat, &_nat->resolved_path, argv[0]);
NAT: move BSC config into separate file Introduce new configuration option bscs-config-file which includes BSC configuration from the given file. Both absolute and relative (to the main config file) paths are supported. Add 'show bscs-config' command to display current BSC configuration. Note: it is still possible to have BSC configuration in the main file (provided proper index number is used) and in runtime but BSC configuration is no longer saved automatically. The management of included configuration file is left to external tools. Update configuration examples. Fixes: OS#1669 Sponsored-by: On-Waves ehf
2016-04-12 14:59:25 +00:00
else {
path = talloc_asprintf(_nat, "%s/%s", _nat->include_base,
argv[0]);
don't re-implement osmo_talloc_replace_string() osmo_talloc_replace_string() was introducd into libosmocore in 2014, see commit f3c7e85d05f7b2b7bf093162b776f71b2bc6420d There's no reason for us to re-implement this as bsc_replace_string here. Change-Id: I6d2fcaabbc74730f6f491a2b2d5c784ccafc6602
2017-05-29 11:54:27 +00:00
osmo_talloc_replace_string(_nat, &_nat->resolved_path, path);
NAT: move BSC config into separate file Introduce new configuration option bscs-config-file which includes BSC configuration from the given file. Both absolute and relative (to the main config file) paths are supported. Add 'show bscs-config' command to display current BSC configuration. Note: it is still possible to have BSC configuration in the main file (provided proper index number is used) and in runtime but BSC configuration is no longer saved automatically. The management of included configuration file is left to external tools. Update configuration examples. Fixes: OS#1669 Sponsored-by: On-Waves ehf
2016-04-12 14:59:25 +00:00
talloc_free(path);
}
NAT: reload BSCs config dynamically Add vty tests for BSC configuration reloading. Load BSCs configuration on bscs-config-file command: * remove all runtime configured BSC not in the config file * close connections to all BSC with updated token value Fixes: OS#1670 Sponsored-by: On-Waves ehf
2016-04-13 09:36:39 +00:00
llist_for_each_entry_safe(cf1, cf2, &_nat->bsc_configs, entry) {
cf1->remove = true;
cf1->token_updated = false;
}
NAT: move BSC config into separate file Introduce new configuration option bscs-config-file which includes BSC configuration from the given file. Both absolute and relative (to the main config file) paths are supported. Add 'show bscs-config' command to display current BSC configuration. Note: it is still possible to have BSC configuration in the main file (provided proper index number is used) and in runtime but BSC configuration is no longer saved automatically. The management of included configuration file is left to external tools. Update configuration examples. Fixes: OS#1669 Sponsored-by: On-Waves ehf
2016-04-12 14:59:25 +00:00
rc = vty_read_config_file(_nat->resolved_path, NULL);
if (rc < 0) {
vty_out(vty, "Failed to parse the config file %s: %s%s",
_nat->resolved_path, strerror(-rc), VTY_NEWLINE);
return CMD_WARNING;
}
NAT: reload BSCs config dynamically Add vty tests for BSC configuration reloading. Load BSCs configuration on bscs-config-file command: * remove all runtime configured BSC not in the config file * close connections to all BSC with updated token value Fixes: OS#1670 Sponsored-by: On-Waves ehf
2016-04-13 09:36:39 +00:00
don't re-implement osmo_talloc_replace_string() osmo_talloc_replace_string() was introducd into libosmocore in 2014, see commit f3c7e85d05f7b2b7bf093162b776f71b2bc6420d There's no reason for us to re-implement this as bsc_replace_string here. Change-Id: I6d2fcaabbc74730f6f491a2b2d5c784ccafc6602
2017-05-29 11:54:27 +00:00
osmo_talloc_replace_string(_nat, &_nat->include_file, argv[0]);
NAT: reload BSCs config dynamically Add vty tests for BSC configuration reloading. Load BSCs configuration on bscs-config-file command: * remove all runtime configured BSC not in the config file * close connections to all BSC with updated token value Fixes: OS#1670 Sponsored-by: On-Waves ehf
2016-04-13 09:36:39 +00:00
llist_for_each_entry_safe(con1, con2, &_nat->bsc_connections,
list_entry) {
if (con1->cfg)
if (con1->cfg->token_updated || con1->cfg->remove)
bsc_close_connection(con1);
}
llist_for_each_entry_safe(cf1, cf2, &_nat->bsc_configs, entry) {
if (cf1->remove)
bsc_config_free(cf1);
}
NAT: move BSC config into separate file Introduce new configuration option bscs-config-file which includes BSC configuration from the given file. Both absolute and relative (to the main config file) paths are supported. Add 'show bscs-config' command to display current BSC configuration. Note: it is still possible to have BSC configuration in the main file (provided proper index number is used) and in runtime but BSC configuration is no longer saved automatically. The management of included configuration file is left to external tools. Update configuration examples. Fixes: OS#1669 Sponsored-by: On-Waves ehf
2016-04-12 14:59:25 +00:00
return CMD_SUCCESS;
}
nat: Add commands to remove access-list from NAT and BSC config
2011-03-29 15:14:34 +00:00
DEFUN(cfg_nat_no_acc_lst_name,
cfg_nat_no_acc_lst_name_cmd,
"no access-list-name",
NO_STR "Remove the access list from the NAT.\n")
{
if (_nat->acc_lst_name) {
talloc_free(_nat->acc_lst_name);
_nat->acc_lst_name = NULL;
}
nat: Fix the return to return CMD_SUCCESS;
2011-04-01 14:22:51 +00:00
return CMD_SUCCESS;
nat: Add commands to remove access-list from NAT and BSC config
2011-03-29 15:14:34 +00:00
}
nat: Introduce a global IMSI barr list using red-black trees
2013-01-01 10:25:09 +00:00
DEFUN(cfg_nat_imsi_black_list_fn,
cfg_nat_imsi_black_list_fn_cmd,
"imsi-black-list-file-name NAME",
"IMSI black listing\n" "Filename IMSI and reject-cause\n")
{
don't re-implement osmo_talloc_replace_string() osmo_talloc_replace_string() was introducd into libosmocore in 2014, see commit f3c7e85d05f7b2b7bf093162b776f71b2bc6420d There's no reason for us to re-implement this as bsc_replace_string here. Change-Id: I6d2fcaabbc74730f6f491a2b2d5c784ccafc6602
2017-05-29 11:54:27 +00:00
osmo_talloc_replace_string(_nat, &_nat->imsi_black_list_fn, argv[0]);
nat: Introduce a global IMSI barr list using red-black trees
2013-01-01 10:25:09 +00:00
if (_nat->imsi_black_list_fn) {
int rc;
struct osmo_config_list *rewr = NULL;
rewr = osmo_config_list_parse(_nat, _nat->imsi_black_list_fn);
filter: More renaming and remove of "NAT" from it
2015-04-05 14:55:28 +00:00
rc = bsc_filter_barr_adapt(_nat, &_nat->imsi_black_list, rewr);
nat: Introduce a global IMSI barr list using red-black trees
2013-01-01 10:25:09 +00:00
if (rc != 0) {
vty_out(vty, "%%There was an error parsing the list."
" Please see the error log.%s", VTY_NEWLINE);
return CMD_WARNING;
}
return CMD_SUCCESS;
}
filter: More renaming and remove of "NAT" from it
2015-04-05 14:55:28 +00:00
bsc_filter_barr_adapt(_nat, &_nat->imsi_black_list, NULL);
nat: Introduce a global IMSI barr list using red-black trees
2013-01-01 10:25:09 +00:00
return CMD_SUCCESS;
}
DEFUN(cfg_nat_no_imsi_black_list_fn,
cfg_nat_no_imsi_black_list_fn_cmd,
"no imsi-black-list-file-name",
NO_STR "Remove the imsi-black-list\n")
{
talloc_free(_nat->imsi_black_list_fn);
_nat->imsi_black_list_fn = NULL;
filter: More renaming and remove of "NAT" from it
2015-04-05 14:55:28 +00:00
bsc_filter_barr_adapt(_nat, &_nat->imsi_black_list, NULL);
nat: Introduce a global IMSI barr list using red-black trees
2013-01-01 10:25:09 +00:00
return CMD_SUCCESS;
}
nat: Add VTY code to configure the SMSC rewriting
2011-05-30 22:35:46 +00:00
static int replace_rules(struct bsc_nat *nat, char **name,
struct llist_head *head, const char *file)
nat: Add vty option for number rewriting Parse a msg file in case we do have a list.
2010-10-21 08:59:54 +00:00
{
nat: Allow to have a regexp to match the MSISDN The idea that MCC and MNC is enough to classify a subscriber turns out to be wrong. Certain operatos license a number range of IMSIs to others. When we see a '^' in the MCC field we treat it as a regexp. The code now turns the MCC/MNC into a regexp for the IMSI. It is not using extended POSIX regexp to match the behavior of the access list.
2011-05-27 10:38:58 +00:00
struct osmo_config_list *rewr = NULL;
don't re-implement osmo_talloc_replace_string() osmo_talloc_replace_string() was introducd into libosmocore in 2014, see commit f3c7e85d05f7b2b7bf093162b776f71b2bc6420d There's no reason for us to re-implement this as bsc_replace_string here. Change-Id: I6d2fcaabbc74730f6f491a2b2d5c784ccafc6602
2017-05-29 11:54:27 +00:00
osmo_talloc_replace_string(nat, name, file);
nat: Add VTY code to configure the SMSC rewriting
2011-05-30 22:35:46 +00:00
if (*name) {
rewr = osmo_config_list_parse(nat, *name);
bsc_nat_num_rewr_entry_adapt(nat, head, rewr);
nat: Allow to have a regexp to match the MSISDN The idea that MCC and MNC is enough to classify a subscriber turns out to be wrong. Certain operatos license a number range of IMSIs to others. When we see a '^' in the MCC field we treat it as a regexp. The code now turns the MCC/MNC into a regexp for the IMSI. It is not using extended POSIX regexp to match the behavior of the access list.
2011-05-27 10:38:58 +00:00
talloc_free(rewr);
return CMD_SUCCESS;
nat: Add vty option for number rewriting Parse a msg file in case we do have a list.
2010-10-21 08:59:54 +00:00
} else {
nat: Add VTY code to configure the SMSC rewriting
2011-05-30 22:35:46 +00:00
bsc_nat_num_rewr_entry_adapt(nat, head, NULL);
nat: Add vty option for number rewriting Parse a msg file in case we do have a list.
2010-10-21 08:59:54 +00:00
return CMD_SUCCESS;
}
}
nat: Add VTY code to configure the SMSC rewriting
2011-05-30 22:35:46 +00:00
DEFUN(cfg_nat_number_rewrite,
cfg_nat_number_rewrite_cmd,
"number-rewrite FILENAME",
"Set the file with rewriting rules.\n" "Filename")
{
return replace_rules(_nat, &_nat->num_rewr_name,
&_nat->num_rewr, argv[0]);
}
nat: Add a no number-rewrite command and call it through a VTY test The test is just testing the invocation but does not verify that the side effect of this call. It is good enought for now.
2013-06-25 07:08:02 +00:00
DEFUN(cfg_nat_no_number_rewrite,
cfg_nat_no_number_rewrite_cmd,
"no number-rewrite",
NO_STR "Set the file with rewriting rules.\n")
{
talloc_free(_nat->num_rewr_name);
_nat->num_rewr_name = NULL;
bsc_nat_num_rewr_entry_adapt(NULL, &_nat->num_rewr, NULL);
return CMD_SUCCESS;
}
nat: Implement a post-routing for the NAT software * The post-routing is applied after the first re-writing. To do this the new number is copied back into the called data structure. * Add a testcase that goes from 0172 to 0049 and then back to 0049 using the post rule with a table lookup.
2013-06-25 13:38:31 +00:00
DEFUN(cfg_nat_number_rewrite_post,
cfg_nat_number_rewrite_post_cmd,
"number-rewrite-post FILENAME",
"Set the file with post-routing rewriting rules.\n" "Filename")
{
return replace_rules(_nat, &_nat->num_rewr_post_name,
&_nat->num_rewr_post, argv[0]);
}
DEFUN(cfg_nat_no_number_rewrite_post,
cfg_nat_no_number_rewrite_post_cmd,
"no number-rewrite-post",
NO_STR "Set the file with post-routing rewriting rules.\n")
{
talloc_free(_nat->num_rewr_post_name);
_nat->num_rewr_post_name = NULL;
bsc_nat_num_rewr_entry_adapt(NULL, &_nat->num_rewr_post, NULL);
return CMD_SUCCESS;
}
nat: Add VTY code to configure the SMSC rewriting
2011-05-30 22:35:46 +00:00
DEFUN(cfg_nat_smsc_addr,
cfg_nat_smsc_addr_cmd,
"rewrite-smsc addr FILENAME",
SMSC_REWRITE
"The SMSC Address to match and replace in RP-DATA\n"
"File with rules for the SMSC Address replacing\n")
{
return replace_rules(_nat, &_nat->smsc_rewr_name,
&_nat->smsc_rewr, argv[0]);
}
DEFUN(cfg_nat_smsc_tpdest,
cfg_nat_smsc_tpdest_cmd,
"rewrite-smsc tp-dest-match FILENAME",
SMSC_REWRITE
"Match TP-Destination of a SMS.\n"
"File with rules for matching MSISDN and TP-DEST\n")
{
return replace_rules(_nat, &_nat->tpdest_match_name,
&_nat->tpdest_match, argv[0]);
}
nat: Implement clearing of TP-SRR flags from TPDUs Match IMSI and destination address against a set of entries, if it is matching the header will be modified and no sender report will be requested. Change the test case to request the sender report and then verify that this bit is reset to 0.
2012-01-10 21:39:07 +00:00
DEFUN(cfg_nat_sms_clear_tpsrr,
cfg_nat_sms_clear_tpsrr_cmd,
"sms-clear-tp-srr FILENAME",
"SMS TPDU Sender Report Request clearing\n"
"Files with rules for matching MSISDN\n")
{
return replace_rules(_nat, &_nat->sms_clear_tp_srr_name,
&_nat->sms_clear_tp_srr, argv[0]);
}
DEFUN(cfg_nat_no_sms_clear_tpsrr,
cfg_nat_no_sms_clear_tpsrr_cmd,
nat: Fix the no sms-clear-tp-srr command
2012-01-18 19:34:08 +00:00
"no sms-clear-tp-srr",
nat: Implement clearing of TP-SRR flags from TPDUs Match IMSI and destination address against a set of entries, if it is matching the header will be modified and no sender report will be requested. Change the test case to request the sender report and then verify that this bit is reset to 0.
2012-01-10 21:39:07 +00:00
NO_STR
"SMS TPDU Sender Report Request clearing\n")
{
talloc_free(_nat->sms_clear_tp_srr_name);
_nat->sms_clear_tp_srr_name = NULL;
bsc_nat_num_rewr_entry_adapt(NULL, &_nat->sms_clear_tp_srr, NULL);
return CMD_SUCCESS;
}
nat: Add VTY command for the TP-DA rewriting.
2012-01-18 19:40:01 +00:00
DEFUN(cfg_nat_sms_number_rewrite,
cfg_nat_sms_number_rewrite_cmd,
"sms-number-rewrite FILENAME",
"SMS TP-DA Number rewriting\n"
"Files with rules for matching MSISDN\n")
{
return replace_rules(_nat, &_nat->sms_num_rewr_name,
&_nat->sms_num_rewr, argv[0]);
}
DEFUN(cfg_nat_no_sms_number_rewrite,
cfg_nat_no_sms_number_rewrite_cmd,
"no sms-number-rewrite",
NO_STR "Disable SMS TP-DA rewriting\n")
{
talloc_free(_nat->sms_num_rewr_name);
_nat->sms_num_rewr_name = NULL;
bsc_nat_num_rewr_entry_adapt(NULL, &_nat->sms_num_rewr, NULL);
return CMD_SUCCESS;
}
nat: Allow to use the prefix lookup to rewrite numbers * Increase the rewritten rule to five digits (this is the easiest for the unit test). This will add another 40kb to the runtime size. * Create a unit test that tests adding and removing the prefix rules. * Use the regexp match to replace from one package
2013-06-25 09:44:01 +00:00
DEFUN(cfg_nat_prefix_trie,
cfg_nat_prefix_trie_cmd,
"prefix-tree FILENAME",
"Prefix tree for number rewriting\n" "File to load\n")
{
/* give up the old data */
talloc_free(_nat->num_rewr_trie);
_nat->num_rewr_trie = NULL;
/* replace the file name */
don't re-implement osmo_talloc_replace_string() osmo_talloc_replace_string() was introducd into libosmocore in 2014, see commit f3c7e85d05f7b2b7bf093162b776f71b2bc6420d There's no reason for us to re-implement this as bsc_replace_string here. Change-Id: I6d2fcaabbc74730f6f491a2b2d5c784ccafc6602
2017-05-29 11:54:27 +00:00
osmo_talloc_replace_string(_nat, &_nat->num_rewr_trie_name, argv[0]);
nat: Allow to use the prefix lookup to rewrite numbers * Increase the rewritten rule to five digits (this is the easiest for the unit test). This will add another 40kb to the runtime size. * Create a unit test that tests adding and removing the prefix rules. * Use the regexp match to replace from one package
2013-06-25 09:44:01 +00:00
if (!_nat->num_rewr_trie_name) {
vty_out(vty, "%% prefix-tree no filename is present.%s", VTY_NEWLINE);
return CMD_WARNING;
}
_nat->num_rewr_trie = nat_rewrite_parse(_nat, _nat->num_rewr_trie_name);
if (!_nat->num_rewr_trie) {
vty_out(vty, "%% prefix-tree parsing has failed.%s", VTY_NEWLINE);
return CMD_WARNING;
}
vty_out(vty, "%% prefix-tree loaded %zu rules.%s",
_nat->num_rewr_trie->prefixes, VTY_NEWLINE);
return CMD_SUCCESS;
}
DEFUN(cfg_nat_no_prefix_trie, cfg_nat_no_prefix_trie_cmd,
"no prefix-tree",
NO_STR "Prefix tree for number rewriting\n")
{
talloc_free(_nat->num_rewr_trie);
_nat->num_rewr_trie = NULL;
talloc_free(_nat->num_rewr_trie_name);
_nat->num_rewr_trie_name = NULL;
return CMD_SUCCESS;
}
DEFUN(show_prefix_tree, show_prefix_tree_cmd,
"show prefix-tree",
SHOW_STR "Prefix tree for number rewriting\n")
{
if (!_nat->num_rewr_trie) {
vty_out(vty, "%% there is now prefix tree loaded.%s",
VTY_NEWLINE);
return CMD_WARNING;
}
nat_rewrite_dump_vty(vty, _nat->num_rewr_trie);
return CMD_SUCCESS;
}
nat: Provide a USSD access list to check for which to play HLR.
2010-10-10 15:29:20 +00:00
DEFUN(cfg_nat_ussd_lst_name,
cfg_nat_ussd_lst_name_cmd,
"ussd-list-name NAME",
"Set the name of the access list to check for IMSIs for USSD message\n"
"The name of the access list for HLR USSD handling")
{
don't re-implement osmo_talloc_replace_string() osmo_talloc_replace_string() was introducd into libosmocore in 2014, see commit f3c7e85d05f7b2b7bf093162b776f71b2bc6420d There's no reason for us to re-implement this as bsc_replace_string here. Change-Id: I6d2fcaabbc74730f6f491a2b2d5c784ccafc6602
2017-05-29 11:54:27 +00:00
osmo_talloc_replace_string(_nat, &_nat->ussd_lst_name, argv[0]);
nat: Provide a USSD access list to check for which to play HLR.
2010-10-10 15:29:20 +00:00
return CMD_SUCCESS;
}
nat: Add an option to set the query string to match Allow the query string to be set. The ussd matching code will check for this string and then forward it to the bypass.
2010-10-11 08:06:39 +00:00
DEFUN(cfg_nat_ussd_query,
cfg_nat_ussd_query_cmd,
nat: Make the USSD number matching a regexp This allows to match multiple numbers and multiple patterns
2011-04-01 15:32:21 +00:00
"ussd-query REGEXP",
nat: Add an option to set the query string to match Allow the query string to be set. The ussd matching code will check for this string and then forward it to the bypass.
2010-10-11 08:06:39 +00:00
"Set the USSD query to match with the ussd-list-name\n"
"The query to match")
{
misc: Move the bsc_parse_reg to libcommom and name it gsm_parse_reg Move the regexp parsing code from the NAT to libcommon as it will be used by the NAT and BSC code. This also adds the #include <regex.h> include to gsm_data. This header should be split up.
2011-06-09 19:48:49 +00:00
if (gsm_parse_reg(_nat, &_nat->ussd_query_re, &_nat->ussd_query, argc, argv) != 0)
nat: Bail out if the regexp fails to compile and avoid a crash If the regexp fails to compile the internal dfa is NULL and a regexec will crash nicely. Fail and free the string if the regexp fails to compile.
2011-04-04 17:19:26 +00:00
return CMD_WARNING;
nat: Add an option to set the query string to match Allow the query string to be set. The ussd matching code will check for this string and then forward it to the bypass.
2010-10-11 08:06:39 +00:00
return CMD_SUCCESS;
}
nat: Keep a ussd token in the config We will have the USSD provider connecting to us and we will use the IPA protocol, including the auth mechanism.
2010-10-12 16:25:52 +00:00
DEFUN(cfg_nat_ussd_token,
cfg_nat_ussd_token_cmd,
"ussd-token TOKEN",
"Set the token used to identify the USSD module\n" "Secret key\n")
{
don't re-implement osmo_talloc_replace_string() osmo_talloc_replace_string() was introducd into libosmocore in 2014, see commit f3c7e85d05f7b2b7bf093162b776f71b2bc6420d There's no reason for us to re-implement this as bsc_replace_string here. Change-Id: I6d2fcaabbc74730f6f491a2b2d5c784ccafc6602
2017-05-29 11:54:27 +00:00
osmo_talloc_replace_string(_nat, &_nat->ussd_token, argv[0]);
nat: Keep a ussd token in the config We will have the USSD provider connecting to us and we will use the IPA protocol, including the auth mechanism.
2010-10-12 16:25:52 +00:00
return CMD_SUCCESS;
}
DEFUN(cfg_nat_ussd_local,
cfg_nat_ussd_local_cmd,
"ussd-local-ip A.B.C.D",
"Set the IP to listen for the USSD Provider\n" "IP Address\n")
{
don't re-implement osmo_talloc_replace_string() osmo_talloc_replace_string() was introducd into libosmocore in 2014, see commit f3c7e85d05f7b2b7bf093162b776f71b2bc6420d There's no reason for us to re-implement this as bsc_replace_string here. Change-Id: I6d2fcaabbc74730f6f491a2b2d5c784ccafc6602
2017-05-29 11:54:27 +00:00
osmo_talloc_replace_string(_nat, &_nat->ussd_local, argv[0]);
nat: Keep a ussd token in the config We will have the USSD provider connecting to us and we will use the IPA protocol, including the auth mechanism.
2010-10-12 16:25:52 +00:00
return CMD_SUCCESS;
}
vty: Rename 'mgcp-through-msc-ipa' command to 'use-msc-ipa-for-mgcp' Currently the 'mgcp' command fails in the 'config-nat' node, because it get confused with 'mgcp-through-msc-ipa' which is executed instead because of the prefix based command selection. Thus the latter command is renamed by this patch to avoid the common prefix. The workaround in the test suite is removed.
2013-09-02 11:17:17 +00:00
DEFUN(cfg_nat_use_ipa_for_mgcp,
cfg_nat_use_ipa_for_mgcp_cmd,
"use-msc-ipa-for-mgcp",
nat: Make it possible to send MGCP messages through the IPA multiplex Instead of handling MGCP through the UDP socket, read and write messages through the ipa connection to the MSC.
2012-11-05 13:54:56 +00:00
"This needs to be set at start. Handle MGCP messages through "
"the IPA protocol and not through the UDP socket.\n")
{
if (_nat->mgcp_cfg->data)
vty_out(vty,
"%%the setting will not be applied right now.%s",
VTY_NEWLINE);
_nat->mgcp_ipa = 1;
return CMD_SUCCESS;
}
nat: Make mode-set patching optional
2015-04-24 00:25:17 +00:00
DEFUN(cfg_nat_sdp_amr_mode_set,
cfg_nat_sdp_amr_mode_set_cmd,
"sdp-ensure-amr-mode-set",
"Ensure that SDP records include a mode-set\n")
{
_nat->sdp_ensure_amr_mode_set = 1;
return CMD_SUCCESS;
}
DEFUN(cfg_nat_no_sdp_amr_mode_set,
cfg_nat_no_sdp_amr_mode_set_cmd,
"no sdp-ensure-amr-mode-set",
NO_STR "Ensure that SDP records include a mode-set\n")
{
_nat->sdp_ensure_amr_mode_set = 0;
return CMD_SUCCESS;
}
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
/* per BSC configuration */
nat: Document all parameters of the VTY commands
2012-07-28 14:14:04 +00:00
DEFUN(cfg_bsc, cfg_bsc_cmd, "bsc BSC_NR",
"BSC configuration\n" "Identifier of the BSC\n")
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
{
int bsc_nr = atoi(argv[0]);
NAT: allow allocating BSC in arbitrary order Check for existing BSC before allocating new one. Track number of remaining BSCs on deallocation. Explicitly use BSC number in allocation function.
2016-04-07 10:27:11 +00:00
struct bsc_config *bsc = bsc_config_num(_nat, bsc_nr);
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
NAT: allow allocating BSC in arbitrary order Check for existing BSC before allocating new one. Track number of remaining BSCs on deallocation. Explicitly use BSC number in allocation function.
2016-04-07 10:27:11 +00:00
/* allocate a new one */
if (!bsc)
bsc = bsc_config_alloc(_nat, "unknown", bsc_nr);
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
if (!bsc)
return CMD_WARNING;
NAT: reload BSCs config dynamically Add vty tests for BSC configuration reloading. Load BSCs configuration on bscs-config-file command: * remove all runtime configured BSC not in the config file * close connections to all BSC with updated token value Fixes: OS#1670 Sponsored-by: On-Waves ehf
2016-04-13 09:36:39 +00:00
bsc->remove = false;
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
vty->index = bsc;
nat: Rename BSC_NODE to NAT_BSC_NODE to avoid future issues.
2010-06-17 06:42:20 +00:00
vty->node = NAT_BSC_NODE;
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
return CMD_SUCCESS;
}
nat: Document all parameters of the VTY commands
2012-07-28 14:14:04 +00:00
DEFUN(cfg_bsc_token, cfg_bsc_token_cmd, "token TOKEN",
"Authentication token configuration\n"
"Token of the BSC, currently transferred in cleartext\n")
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
{
struct bsc_config *conf = vty->index;
nat/vty: Do not print token update statement On start this would print one line per BSC and this doesn't add a lot of value. Let's just remove this logging message.
2016-04-16 16:52:55 +00:00
if (strncmp(conf->token, argv[0], 128) != 0)
NAT: reload BSCs config dynamically Add vty tests for BSC configuration reloading. Load BSCs configuration on bscs-config-file command: * remove all runtime configured BSC not in the config file * close connections to all BSC with updated token value Fixes: OS#1670 Sponsored-by: On-Waves ehf
2016-04-13 09:36:39 +00:00
conf->token_updated = true;
don't re-implement osmo_talloc_replace_string() osmo_talloc_replace_string() was introducd into libosmocore in 2014, see commit f3c7e85d05f7b2b7bf093162b776f71b2bc6420d There's no reason for us to re-implement this as bsc_replace_string here. Change-Id: I6d2fcaabbc74730f6f491a2b2d5c784ccafc6602
2017-05-29 11:54:27 +00:00
osmo_talloc_replace_string(conf, &conf->token, argv[0]);
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
return CMD_SUCCESS;
}
nat: After we identified the bsc check the key We are using the token to find the right bsc_config and then we can use the last_rand of the bsc_connection to calculate the expected result and try to compare it with a time constant(???) memcmp.
2015-06-08 16:33:28 +00:00
DEFUN(cfg_bsc_auth_key, cfg_bsc_auth_key_cmd,
"auth-key KEY",
"Authentication (secret) key configuration\n"
"Non null security key\n")
{
struct bsc_config *conf = vty->index;
memset(conf->key, 0, sizeof(conf->key));
osmo_hexparse(argv[0], conf->key, sizeof(conf->key));
conf->key_present = 1;
return CMD_SUCCESS;
}
DEFUN(cfg_bsc_no_auth_key, cfg_bsc_no_auth_key_cmd,
"no auth-key",
NO_STR "Authentication (secret) key configuration\n")
{
struct bsc_config *conf = vty->index;
memset(conf->key, 0, sizeof(conf->key));
conf->key_present = 0;
return CMD_SUCCESS;
}
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
DEFUN(cfg_bsc_lac, cfg_bsc_lac_cmd, "location_area_code <0-65535>",
nat: Create a Paging Group that BSCs can refer to Introduce a paging group that a BSC can refer to and is used during the LAC lookup. This way paging can be flooded through the network and just filtered at the last element in the core.
2011-05-02 17:16:13 +00:00
"Add the Location Area Code (LAC) of this BSC\n" "LAC\n")
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
{
nat: Verify that the configured LACs are unique across the nat
2010-03-30 04:08:56 +00:00
struct bsc_config *tmp;
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
struct bsc_config *conf = vty->index;
int lac = atoi(argv[0]);
if (lac == GSM_LAC_RESERVED_DETACHED || lac == GSM_LAC_RESERVED_ALL_BTS) {
vty_out(vty, "%% LAC %d is reserved by GSM 04.08%s",
lac, VTY_NEWLINE);
return CMD_WARNING;
}
nat: Verify that the configured LACs are unique across the nat
2010-03-30 04:08:56 +00:00
/* verify that the LACs are unique */
llist_for_each_entry(tmp, &_nat->bsc_configs, entry) {
nat: Allow a BSC to have multiple LACs Make it possible that one BSC is serving multiple cells. Introduce a list of lacs, add functions to manipulate the lists. The current test cases for paging by lac continue to work.
2010-10-08 14:08:29 +00:00
if (bsc_config_handles_lac(tmp, lac)) {
NAT: move BSC config into separate file Introduce new configuration option bscs-config-file which includes BSC configuration from the given file. Both absolute and relative (to the main config file) paths are supported. Add 'show bscs-config' command to display current BSC configuration. Note: it is still possible to have BSC configuration in the main file (provided proper index number is used) and in runtime but BSC configuration is no longer saved automatically. The management of included configuration file is left to external tools. Update configuration examples. Fixes: OS#1669 Sponsored-by: On-Waves ehf
2016-04-12 14:59:25 +00:00
if (tmp->nr != conf->nr) {
vty_out(vty, "%% LAC %d is already used.%s", lac,
VTY_NEWLINE);
return CMD_ERR_INCOMPLETE;
}
nat: Verify that the configured LACs are unique across the nat
2010-03-30 04:08:56 +00:00
}
}
nat: Allow a BSC to have multiple LACs Make it possible that one BSC is serving multiple cells. Introduce a list of lacs, add functions to manipulate the lists. The current test cases for paging by lac continue to work.
2010-10-08 14:08:29 +00:00
bsc_config_add_lac(conf, lac);
return CMD_SUCCESS;
}
DEFUN(cfg_bsc_no_lac, cfg_bsc_no_lac_cmd,
"no location_area_code <0-65535>",
nat: Create a Paging Group that BSCs can refer to Introduce a paging group that a BSC can refer to and is used during the LAC lookup. This way paging can be flooded through the network and just filtered at the last element in the core.
2011-05-02 17:16:13 +00:00
NO_STR "Remove the Location Area Code (LAC) of this BSC\n" "LAC\n")
nat: Allow a BSC to have multiple LACs Make it possible that one BSC is serving multiple cells. Introduce a list of lacs, add functions to manipulate the lists. The current test cases for paging by lac continue to work.
2010-10-08 14:08:29 +00:00
{
int lac = atoi(argv[0]);
struct bsc_config *conf = vty->index;
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
nat: Allow a BSC to have multiple LACs Make it possible that one BSC is serving multiple cells. Introduce a list of lacs, add functions to manipulate the lists. The current test cases for paging by lac continue to work.
2010-10-08 14:08:29 +00:00
bsc_config_del_lac(conf, lac);
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
return CMD_SUCCESS;
}
nat: Introduce a global IMSI barr list using red-black trees
2013-01-01 10:25:09 +00:00
DEFUN(show_bar_lst,
show_bar_lst_cmd,
"show imsi-black-list",
SHOW_STR "IMSIs barred from the network\n")
{
struct rb_node *node;
vty_out(vty, "IMSIs barred from the network:%s", VTY_NEWLINE);
for (node = rb_first(&_nat->imsi_black_list); node; node = rb_next(node)) {
filter: More renaming and remove of "NAT" from it
2015-04-05 14:55:28 +00:00
struct bsc_filter_barr_entry *entry;
entry = rb_entry(node, struct bsc_filter_barr_entry, node);
nat: Introduce a global IMSI barr list using red-black trees
2013-01-01 10:25:09 +00:00
vty_out(vty, " IMSI(%s) CM-Reject-Cause(%d) LU-Reject-Cause(%d)%s",
entry->imsi, entry->cm_reject_cause, entry->lu_reject_cause,
VTY_NEWLINE);
}
return CMD_SUCCESS;
}
nat: Print the statistics of the access-list matches Print the statistics for the rule matches via the vty.
2010-09-25 08:25:47 +00:00
[nat] Introduce the concept of access-list One can set one access-list to one BSC and one access-list to one NAT. The matching of IMSIs remains the same for now, also applying the white/blacklist. Access lists can not be deleted for now and no perf opt is done (e.g. one could cache the result of the last lookup in the bsc struct).
2010-05-31 17:03:13 +00:00
DEFUN(cfg_bsc_acc_lst_name,
cfg_bsc_acc_lst_name_cmd,
"access-list-name NAME",
"Set the name of the access list to use.\n"
"The name of the to be used access list.")
{
struct bsc_config *conf = vty->index;
don't re-implement osmo_talloc_replace_string() osmo_talloc_replace_string() was introducd into libosmocore in 2014, see commit f3c7e85d05f7b2b7bf093162b776f71b2bc6420d There's no reason for us to re-implement this as bsc_replace_string here. Change-Id: I6d2fcaabbc74730f6f491a2b2d5c784ccafc6602
2017-05-29 11:54:27 +00:00
osmo_talloc_replace_string(conf, &conf->acc_lst_name, argv[0]);
nat: Add config option to filter/handle certain imsi'es.
2010-04-13 07:24:37 +00:00
return CMD_SUCCESS;
}
nat: Add commands to remove access-list from NAT and BSC config
2011-03-29 15:14:34 +00:00
DEFUN(cfg_bsc_no_acc_lst_name,
cfg_bsc_no_acc_lst_name_cmd,
"no access-list-name",
nat: Clarify the documentation of the allow/deny regexp
2011-04-13 18:58:14 +00:00
NO_STR "Do not use an access-list for the BSC.\n")
nat: Add commands to remove access-list from NAT and BSC config
2011-03-29 15:14:34 +00:00
{
struct bsc_config *conf = vty->index;
if (conf->acc_lst_name) {
talloc_free(conf->acc_lst_name);
conf->acc_lst_name = NULL;
}
return CMD_SUCCESS;
}
nat: Change number of multiplexes to the max-endpoints
2011-02-27 10:04:27 +00:00
DEFUN(cfg_bsc_max_endps, cfg_bsc_max_endps_cmd,
"max-endpoints <1-1024>",
"Highest endpoint to use (exclusively)\n" "Number of ports\n")
nat: Start making the number of multiplexes configurable Introduce a VTY setting that right now needs to be set to one. To make updating this setting possible we will now store the number of endpoints in the bsc connection as well.
2011-02-25 19:38:15 +00:00
{
struct bsc_config *conf = vty->index;
nat: Change number of multiplexes to the max-endpoints
2011-02-27 10:04:27 +00:00
conf->max_endpoints = atoi(argv[0]);
nat: Start making the number of multiplexes configurable Introduce a VTY setting that right now needs to be set to one. To make updating this setting possible we will now store the number of endpoints in the bsc connection as well.
2011-02-25 19:38:15 +00:00
return CMD_SUCCESS;
}
[nat] Add option to forbid the paging to the BSC. This can be done for testing purposes and to allow making a BTS crash that can not handle paging requests properly.
2010-04-21 11:05:14 +00:00
DEFUN(cfg_bsc_paging,
cfg_bsc_paging_cmd,
"paging forbidden (0|1)",
nat: Document all parameters of the VTY commands
2012-07-28 14:14:04 +00:00
PAGING_STR "Forbid sending PAGING REQUESTS to the BSC.\n"
"Do not forbid\n" "Forbid\n")
[nat] Add option to forbid the paging to the BSC. This can be done for testing purposes and to allow making a BTS crash that can not handle paging requests properly.
2010-04-21 11:05:14 +00:00
{
struct bsc_config *conf = vty->index;
[nat] Fix the vty option... use the right argument.
2010-04-21 12:07:07 +00:00
if (strcmp("1", argv[0]) == 0)
[nat] Add option to forbid the paging to the BSC. This can be done for testing purposes and to allow making a BTS crash that can not handle paging requests properly.
2010-04-21 11:05:14 +00:00
conf->forbid_paging = 1;
else
conf->forbid_paging = 0;
return CMD_SUCCESS;
}
[nat] Allow to set the description for the bsc. This will allow to add description to each BSC.
2010-05-14 14:06:28 +00:00
DEFUN(cfg_bsc_desc,
cfg_bsc_desc_cmd,
"description DESC",
nat: Document all parameters of the VTY commands
2012-07-28 14:14:04 +00:00
"Provide a description for the given BSC.\n" "Description\n")
[nat] Allow to set the description for the bsc. This will allow to add description to each BSC.
2010-05-14 14:06:28 +00:00
{
struct bsc_config *conf = vty->index;
don't re-implement osmo_talloc_replace_string() osmo_talloc_replace_string() was introducd into libosmocore in 2014, see commit f3c7e85d05f7b2b7bf093162b776f71b2bc6420d There's no reason for us to re-implement this as bsc_replace_string here. Change-Id: I6d2fcaabbc74730f6f491a2b2d5c784ccafc6602
2017-05-29 11:54:27 +00:00
osmo_talloc_replace_string(conf, &conf->description, argv[0]);
[nat] Allow to set the description for the bsc. This will allow to add description to each BSC.
2010-05-14 14:06:28 +00:00
return CMD_SUCCESS;
}
nat: Create a Paging Group that BSCs can refer to Introduce a paging group that a BSC can refer to and is used during the LAC lookup. This way paging can be flooded through the network and just filtered at the last element in the core.
2011-05-02 17:16:13 +00:00
DEFUN(cfg_bsc_paging_grp,
cfg_bsc_paging_grp_cmd,
nat: Use 'paging group' because we have paging forbidden. Make paging-group deprecated and introduce the new paging group.
2011-05-17 17:28:07 +00:00
"paging group <0-1000>",
PAGING_STR "Use a paging group\n" "Paging Group to use\n")
nat: Create a Paging Group that BSCs can refer to Introduce a paging group that a BSC can refer to and is used during the LAC lookup. This way paging can be flooded through the network and just filtered at the last element in the core.
2011-05-02 17:16:13 +00:00
{
struct bsc_config *conf = vty->index;
conf->paging_group = atoi(argv[0]);
return CMD_SUCCESS;
}
nat: Use 'paging group' because we have paging forbidden. Make paging-group deprecated and introduce the new paging group.
2011-05-17 17:28:07 +00:00
ALIAS_DEPRECATED(cfg_bsc_paging_grp, cfg_bsc_old_grp_cmd,
"paging-group <0-1000>",
"Use a paging group\n" "Paging Group to use\n")
nat: Create a Paging Group that BSCs can refer to Introduce a paging group that a BSC can refer to and is used during the LAC lookup. This way paging can be flooded through the network and just filtered at the last element in the core.
2011-05-02 17:16:13 +00:00
DEFUN(cfg_bsc_no_paging_grp,
cfg_bsc_no_paging_grp_cmd,
nat: Use 'paging group' because we have paging forbidden. Make paging-group deprecated and introduce the new paging group.
2011-05-17 17:28:07 +00:00
"no paging group",
NO_STR PAGING_STR "Disable the usage of a paging group.\n")
nat: Create a Paging Group that BSCs can refer to Introduce a paging group that a BSC can refer to and is used during the LAC lookup. This way paging can be flooded through the network and just filtered at the last element in the core.
2011-05-02 17:16:13 +00:00
{
struct bsc_config *conf = vty->index;
conf->paging_group = PAGIN_GROUP_UNASSIGNED;
return CMD_SUCCESS;
}
[nat] Add a regexp test command to the VTY. This allows to test the regexp to be used for allo/deny of the imsi filter.
2010-05-14 15:43:12 +00:00
DEFUN(test_regex, test_regex_cmd,
"test regex PATTERN STRING",
nat: Document all parameters of the VTY commands
2012-07-28 14:14:04 +00:00
"Test utilities\n"
"Regexp testing\n" "The regexp pattern\n"
"The string to match\n")
[nat] Add a regexp test command to the VTY. This allows to test the regexp to be used for allo/deny of the imsi filter.
2010-05-14 15:43:12 +00:00
{
regex_t reg;
char *str = NULL;
memset(&reg, 0, sizeof(reg));
misc: Move the bsc_parse_reg to libcommom and name it gsm_parse_reg Move the regexp parsing code from the NAT to libcommon as it will be used by the NAT and BSC code. This also adds the #include <regex.h> include to gsm_data. This header should be split up.
2011-06-09 19:48:49 +00:00
if (gsm_parse_reg(_nat, &reg, &str, 1, argv) != 0)
nat: Bail out if the regexp fails to compile and avoid a crash If the regexp fails to compile the internal dfa is NULL and a regexec will crash nicely. Fail and free the string if the regexp fails to compile.
2011-04-04 17:19:26 +00:00
return CMD_WARNING;
[nat] Add a regexp test command to the VTY. This allows to test the regexp to be used for allo/deny of the imsi filter.
2010-05-14 15:43:12 +00:00
vty_out(vty, "String matches allow pattern: %d%s",
regexec(&reg, argv[1], 0, NULL, 0) == 0, VTY_NEWLINE);
talloc_free(str);
regfree(&reg);
return CMD_SUCCESS;
}
nat: For debugging make it possible to set the last used endpoint This will influence the allocator from where to search for the next free endpoint. This can be used to force it to allocate a specific endpoint next.
2011-02-28 00:07:13 +00:00
DEFUN(set_last_endp, set_last_endp_cmd,
"set bsc last-used-endpoint <0-9999999999> <0-1024>",
"Set a value\n" "Operate on a BSC\n"
"Last used endpoint for an assignment\n" "BSC configuration number\n"
"Endpoint number used\n")
{
struct bsc_connection *con;
int nr = atoi(argv[0]);
int endp = atoi(argv[1]);
llist_for_each_entry(con, &_nat->bsc_connections, list_entry) {
if (!con->cfg)
continue;
if (con->cfg->nr != nr)
continue;
con->last_endpoint = endp;
vty_out(vty, "Updated the last endpoint for %d to %d.%s",
con->cfg->nr, con->last_endpoint, VTY_NEWLINE);
}
return CMD_SUCCESS;
}
nat: Introduce a block on the NAT to slowly get rid of BSCs For restarting the NAT we can now block it, it will not accept new connections and for existing connections it will attempt to drop them over time. A blocked NAT will end up with no BSC connections left and then can be safely restarted.
2011-04-23 21:55:14 +00:00
DEFUN(block_new_conn, block_new_conn_cmd,
"nat-block (block|unblock)",
"Block the NAT for new connections\n"
"Block\n" "Unblock\n")
{
_nat->blocked = argv[0][0] == 'b';
vty_out(vty, "%%Going to %s the NAT.%s",
_nat->blocked ? "block" : "unblock", VTY_NEWLINE);
return CMD_SUCCESS;
}
nat: Create a Paging Group that BSCs can refer to Introduce a paging group that a BSC can refer to and is used during the LAC lookup. This way paging can be flooded through the network and just filtered at the last element in the core.
2011-05-02 17:16:13 +00:00
/* paging group */
DEFUN(cfg_nat_pgroup, cfg_nat_pgroup_cmd,
"paging-group <0-1000>",
"Create a Paging Group\n" "Number of the Group\n")
{
int group = atoi(argv[0]);
struct bsc_nat_paging_group *pgroup;
pgroup = bsc_nat_paging_group_num(_nat, group);
if (!pgroup)
pgroup = bsc_nat_paging_group_create(_nat, group);
if (!pgroup) {
vty_out(vty, "Failed to create the group.%s", VTY_NEWLINE);
return CMD_WARNING;
}
vty->index = pgroup;
vty->node = PGROUP_NODE;
return CMD_SUCCESS;
}
DEFUN(cfg_nat_no_pgroup, cfg_nat_no_pgroup_cmd,
"no paging-group <0-1000>",
nat: Document all parameters of the VTY commands
2012-07-28 14:14:04 +00:00
NO_STR "Delete paging-group\n" "Paging-group number\n")
nat: Create a Paging Group that BSCs can refer to Introduce a paging group that a BSC can refer to and is used during the LAC lookup. This way paging can be flooded through the network and just filtered at the last element in the core.
2011-05-02 17:16:13 +00:00
{
int group = atoi(argv[0]);
struct bsc_nat_paging_group *pgroup;
pgroup = bsc_nat_paging_group_num(_nat, group);
if (!pgroup) {
vty_out(vty, "No such paging group %d.%s", group, VTY_NEWLINE);
return CMD_WARNING;
}
bsc_nat_paging_group_delete(pgroup);
return CMD_SUCCESS;
}
DEFUN(cfg_pgroup_lac, cfg_pgroup_lac_cmd,
"location_area_code <0-65535>",
"Add the Location Area Code (LAC)\n" "LAC\n")
{
struct bsc_nat_paging_group *pgroup = vty->index;
int lac = atoi(argv[0]);
if (lac == GSM_LAC_RESERVED_DETACHED || lac == GSM_LAC_RESERVED_ALL_BTS) {
vty_out(vty, "%% LAC %d is reserved by GSM 04.08%s",
lac, VTY_NEWLINE);
return CMD_WARNING;
}
bsc_nat_paging_group_add_lac(pgroup, lac);
return CMD_SUCCESS;
}
DEFUN(cfg_pgroup_no_lac, cfg_pgroup_no_lac_cmd,
"no location_area_code <0-65535>",
NO_STR "Remove the Location Area Code (LAC)\n" "LAC\n")
{
int lac = atoi(argv[0]);
struct bsc_nat_paging_group *pgroup = vty->index;
bsc_nat_paging_group_del_lac(pgroup, lac);
return CMD_SUCCESS;
}
nat/ussd: Add 'show ussd-connection' vty command This command returns the current state of the connection to the USSD side channel provider. It shows whether a provider has been connected and authorized or not. Fixes: OW#953
2013-08-14 09:10:34 +00:00
DEFUN(show_ussd_connection,
show_ussd_connection_cmd,
"show ussd-connection",
SHOW_STR "USSD connection related information\n")
{
vty_out(vty, "The USSD side channel provider is %sconnected and %sauthorized.%s",
_nat->ussd_con ? "" : "not ",
_nat->ussd_con && _nat->ussd_con->authorized? "" : "not ",
VTY_NEWLINE);
return CMD_SUCCESS;
}
nat: Fix the documentation issue with the osmux command Documentation error (missing docs): <command id='osmux (on|off)'> <param name='off' doc='(null)' />
2014-07-04 18:09:55 +00:00
#define OSMUX_STR "RTP multiplexing\n"
mgcp: add voice muxer support This patch adds the voice muxer. You can use this to batch RTP traffic to reduce bandwidth comsuption. Basically, osmux transforms RTP flows to a compact batch format, that is later on decompacted to its original form. Port UDP/1984 is used for the muxer traffic between osmo-bsc_nat and osmo-bsc_mgcp (in the BSC side). This feature depends on libosmo-netif, which contains the osmux core support. Osmux is requested on-demand via the MGCP CRCX/MDCX messages (using the vendor-specific extension X-Osmux: on) coming from the BSC-NAT, so you can selectively enable osmux per BSC from one the bsc-nat.cfg file, so we have a centralized point to enable/disable osmux. First thing you need to do is to accept requests to use Osmux, this can be done from VTY interface of osmo-bsc_nat and osmo-bsc_mgcp by adding the following line: mgcp ... osmux on osmux batch-factor 4 This just initializes the osmux engine. You still have to specify what BSC uses osmux from osmo-bsc_nat configuration file: ... bsc 1 osmux on bsc 2 ... bsc 3 osmux on In this case, bsc 1 and 3 should use osmux if possible, bsc 2 does not have osmux enabled. Thus, you can selectively enable osmux depending on the BSC, and we have a centralized point for configuration from the bsc-nat to enable osmux on demand, as suggested by Holger. At this moment, this patch contains heavy debug logging for each RTP packet that can be removed later to save cycles. The RTP ssrc/seqnum/timestamp is randomly allocated for each MDCX that is received to configure an endpoint.
2014-02-05 17:56:17 +00:00
DEFUN(cfg_bsc_osmux,
cfg_bsc_osmux_cmd,
osmux: Enforce Osmux only global and per BSC configuration Extend the osmux only setting from the MGCP MGW to the NAT. This is applied when an endpoint is allocated and/or when the allocation is confirmed by the remote system. Not tested. The impact should only be when the new option is being used. Fixes: OW#1492
2015-10-02 16:15:18 +00:00
"osmux (on|off|only)",
OSMUX_STR "Enable OSMUX\n" "Disable OSMUX\n" "Only OSMUX\n")
mgcp: add voice muxer support This patch adds the voice muxer. You can use this to batch RTP traffic to reduce bandwidth comsuption. Basically, osmux transforms RTP flows to a compact batch format, that is later on decompacted to its original form. Port UDP/1984 is used for the muxer traffic between osmo-bsc_nat and osmo-bsc_mgcp (in the BSC side). This feature depends on libosmo-netif, which contains the osmux core support. Osmux is requested on-demand via the MGCP CRCX/MDCX messages (using the vendor-specific extension X-Osmux: on) coming from the BSC-NAT, so you can selectively enable osmux per BSC from one the bsc-nat.cfg file, so we have a centralized point to enable/disable osmux. First thing you need to do is to accept requests to use Osmux, this can be done from VTY interface of osmo-bsc_nat and osmo-bsc_mgcp by adding the following line: mgcp ... osmux on osmux batch-factor 4 This just initializes the osmux engine. You still have to specify what BSC uses osmux from osmo-bsc_nat configuration file: ... bsc 1 osmux on bsc 2 ... bsc 3 osmux on In this case, bsc 1 and 3 should use osmux if possible, bsc 2 does not have osmux enabled. Thus, you can selectively enable osmux depending on the BSC, and we have a centralized point for configuration from the bsc-nat to enable osmux on demand, as suggested by Holger. At this moment, this patch contains heavy debug logging for each RTP packet that can be removed later to save cycles. The RTP ssrc/seqnum/timestamp is randomly allocated for each MDCX that is received to configure an endpoint.
2014-02-05 17:56:17 +00:00
{
struct bsc_config *conf = vty->index;
osmux: move osmux socket initialization out of osmux_enable_endpoint() In the bsc-nat side, the osmux socket initialization can be done from the vty. This ensure that the osmux socket is available by the time the bsc-nt receives the dummy load that confirms that the osmux flow has been set up. This change is required by the follow up patch. This change ensures that the Osmux socket in the bsc-nat is already in place by the time this receives the dummy load.
2014-08-27 12:58:43 +00:00
int old = conf->osmux;
mgcp: add voice muxer support This patch adds the voice muxer. You can use this to batch RTP traffic to reduce bandwidth comsuption. Basically, osmux transforms RTP flows to a compact batch format, that is later on decompacted to its original form. Port UDP/1984 is used for the muxer traffic between osmo-bsc_nat and osmo-bsc_mgcp (in the BSC side). This feature depends on libosmo-netif, which contains the osmux core support. Osmux is requested on-demand via the MGCP CRCX/MDCX messages (using the vendor-specific extension X-Osmux: on) coming from the BSC-NAT, so you can selectively enable osmux per BSC from one the bsc-nat.cfg file, so we have a centralized point to enable/disable osmux. First thing you need to do is to accept requests to use Osmux, this can be done from VTY interface of osmo-bsc_nat and osmo-bsc_mgcp by adding the following line: mgcp ... osmux on osmux batch-factor 4 This just initializes the osmux engine. You still have to specify what BSC uses osmux from osmo-bsc_nat configuration file: ... bsc 1 osmux on bsc 2 ... bsc 3 osmux on In this case, bsc 1 and 3 should use osmux if possible, bsc 2 does not have osmux enabled. Thus, you can selectively enable osmux depending on the BSC, and we have a centralized point for configuration from the bsc-nat to enable osmux on demand, as suggested by Holger. At this moment, this patch contains heavy debug logging for each RTP packet that can be removed later to save cycles. The RTP ssrc/seqnum/timestamp is randomly allocated for each MDCX that is received to configure an endpoint.
2014-02-05 17:56:17 +00:00
if (strcmp(argv[0], "on") == 0)
osmux: Enforce Osmux only global and per BSC configuration Extend the osmux only setting from the MGCP MGW to the NAT. This is applied when an endpoint is allocated and/or when the allocation is confirmed by the remote system. Not tested. The impact should only be when the new option is being used. Fixes: OW#1492
2015-10-02 16:15:18 +00:00
conf->osmux = OSMUX_USAGE_ON;
mgcp: add voice muxer support This patch adds the voice muxer. You can use this to batch RTP traffic to reduce bandwidth comsuption. Basically, osmux transforms RTP flows to a compact batch format, that is later on decompacted to its original form. Port UDP/1984 is used for the muxer traffic between osmo-bsc_nat and osmo-bsc_mgcp (in the BSC side). This feature depends on libosmo-netif, which contains the osmux core support. Osmux is requested on-demand via the MGCP CRCX/MDCX messages (using the vendor-specific extension X-Osmux: on) coming from the BSC-NAT, so you can selectively enable osmux per BSC from one the bsc-nat.cfg file, so we have a centralized point to enable/disable osmux. First thing you need to do is to accept requests to use Osmux, this can be done from VTY interface of osmo-bsc_nat and osmo-bsc_mgcp by adding the following line: mgcp ... osmux on osmux batch-factor 4 This just initializes the osmux engine. You still have to specify what BSC uses osmux from osmo-bsc_nat configuration file: ... bsc 1 osmux on bsc 2 ... bsc 3 osmux on In this case, bsc 1 and 3 should use osmux if possible, bsc 2 does not have osmux enabled. Thus, you can selectively enable osmux depending on the BSC, and we have a centralized point for configuration from the bsc-nat to enable osmux on demand, as suggested by Holger. At this moment, this patch contains heavy debug logging for each RTP packet that can be removed later to save cycles. The RTP ssrc/seqnum/timestamp is randomly allocated for each MDCX that is received to configure an endpoint.
2014-02-05 17:56:17 +00:00
else if (strcmp(argv[0], "off") == 0)
osmux: Enforce Osmux only global and per BSC configuration Extend the osmux only setting from the MGCP MGW to the NAT. This is applied when an endpoint is allocated and/or when the allocation is confirmed by the remote system. Not tested. The impact should only be when the new option is being used. Fixes: OW#1492
2015-10-02 16:15:18 +00:00
conf->osmux = OSMUX_USAGE_OFF;
else if (strcmp(argv[0], "only") == 0)
conf->osmux = OSMUX_USAGE_ONLY;
mgcp: add voice muxer support This patch adds the voice muxer. You can use this to batch RTP traffic to reduce bandwidth comsuption. Basically, osmux transforms RTP flows to a compact batch format, that is later on decompacted to its original form. Port UDP/1984 is used for the muxer traffic between osmo-bsc_nat and osmo-bsc_mgcp (in the BSC side). This feature depends on libosmo-netif, which contains the osmux core support. Osmux is requested on-demand via the MGCP CRCX/MDCX messages (using the vendor-specific extension X-Osmux: on) coming from the BSC-NAT, so you can selectively enable osmux per BSC from one the bsc-nat.cfg file, so we have a centralized point to enable/disable osmux. First thing you need to do is to accept requests to use Osmux, this can be done from VTY interface of osmo-bsc_nat and osmo-bsc_mgcp by adding the following line: mgcp ... osmux on osmux batch-factor 4 This just initializes the osmux engine. You still have to specify what BSC uses osmux from osmo-bsc_nat configuration file: ... bsc 1 osmux on bsc 2 ... bsc 3 osmux on In this case, bsc 1 and 3 should use osmux if possible, bsc 2 does not have osmux enabled. Thus, you can selectively enable osmux depending on the BSC, and we have a centralized point for configuration from the bsc-nat to enable osmux on demand, as suggested by Holger. At this moment, this patch contains heavy debug logging for each RTP packet that can be removed later to save cycles. The RTP ssrc/seqnum/timestamp is randomly allocated for each MDCX that is received to configure an endpoint.
2014-02-05 17:56:17 +00:00
osmux: Enforce Osmux only global and per BSC configuration Extend the osmux only setting from the MGCP MGW to the NAT. This is applied when an endpoint is allocated and/or when the allocation is confirmed by the remote system. Not tested. The impact should only be when the new option is being used. Fixes: OW#1492
2015-10-02 16:15:18 +00:00
if (old == 0 && conf->osmux > 0 && !conf->nat->mgcp_cfg->osmux_init) {
osmux: Initialize the socket only once The per BSC code didn't guard against the init already having been executed. This lead to: Adding a osmo_fd that is already in the list. <000b> bsc_nat_vty.c:1200 Setting up OSMUX socket So a new socket got created and the old one leaked. Luckily Linux appears to allow to bind multiple times so we were able to just read from the new one. Use the same guard that is used on the MGCP MGW. Re-order the log message to say "Setting up" before we actually do that. I manually verified that osmux_init is called at most once. The log message was spotted by Roch
2015-01-21 15:53:53 +00:00
LOGP(DMGCP, LOGL_NOTICE, "Setting up OSMUX socket\n");
osmux: move osmux socket initialization out of osmux_enable_endpoint() In the bsc-nat side, the osmux socket initialization can be done from the vty. This ensure that the osmux socket is available by the time the bsc-nt receives the dummy load that confirms that the osmux flow has been set up. This change is required by the follow up patch. This change ensures that the Osmux socket in the bsc-nat is already in place by the time this receives the dummy load.
2014-08-27 12:58:43 +00:00
if (osmux_init(OSMUX_ROLE_BSC_NAT, conf->nat->mgcp_cfg) < 0) {
LOGP(DMGCP, LOGL_ERROR, "Cannot init OSMUX\n");
osmux: Initialize the socket only once The per BSC code didn't guard against the init already having been executed. This lead to: Adding a osmo_fd that is already in the list. <000b> bsc_nat_vty.c:1200 Setting up OSMUX socket So a new socket got created and the old one leaked. Luckily Linux appears to allow to bind multiple times so we were able to just read from the new one. Use the same guard that is used on the MGCP MGW. Re-order the log message to say "Setting up" before we actually do that. I manually verified that osmux_init is called at most once. The log message was spotted by Roch
2015-01-21 15:53:53 +00:00
vty_out(vty, "%% failed to create Osmux socket%s",
VTY_NEWLINE);
return CMD_WARNING;
osmux: move osmux socket initialization out of osmux_enable_endpoint() In the bsc-nat side, the osmux socket initialization can be done from the vty. This ensure that the osmux socket is available by the time the bsc-nt receives the dummy load that confirms that the osmux flow has been set up. This change is required by the follow up patch. This change ensures that the Osmux socket in the bsc-nat is already in place by the time this receives the dummy load.
2014-08-27 12:58:43 +00:00
}
osmux: Enforce Osmux only global and per BSC configuration Extend the osmux only setting from the MGCP MGW to the NAT. This is applied when an endpoint is allocated and/or when the allocation is confirmed by the remote system. Not tested. The impact should only be when the new option is being used. Fixes: OW#1492
2015-10-02 16:15:18 +00:00
} else if (old > 0 && conf->osmux == 0) {
osmux: move osmux socket initialization out of osmux_enable_endpoint() In the bsc-nat side, the osmux socket initialization can be done from the vty. This ensure that the osmux socket is available by the time the bsc-nt receives the dummy load that confirms that the osmux flow has been set up. This change is required by the follow up patch. This change ensures that the Osmux socket in the bsc-nat is already in place by the time this receives the dummy load.
2014-08-27 12:58:43 +00:00
LOGP(DMGCP, LOGL_NOTICE, "Disabling OSMUX socket\n");
/* Don't stop the socket, we may already have ongoing voice
* flows already using Osmux. This just switch indicates that
* new upcoming flows should use RTP.
*/
}
mgcp: add voice muxer support This patch adds the voice muxer. You can use this to batch RTP traffic to reduce bandwidth comsuption. Basically, osmux transforms RTP flows to a compact batch format, that is later on decompacted to its original form. Port UDP/1984 is used for the muxer traffic between osmo-bsc_nat and osmo-bsc_mgcp (in the BSC side). This feature depends on libosmo-netif, which contains the osmux core support. Osmux is requested on-demand via the MGCP CRCX/MDCX messages (using the vendor-specific extension X-Osmux: on) coming from the BSC-NAT, so you can selectively enable osmux per BSC from one the bsc-nat.cfg file, so we have a centralized point to enable/disable osmux. First thing you need to do is to accept requests to use Osmux, this can be done from VTY interface of osmo-bsc_nat and osmo-bsc_mgcp by adding the following line: mgcp ... osmux on osmux batch-factor 4 This just initializes the osmux engine. You still have to specify what BSC uses osmux from osmo-bsc_nat configuration file: ... bsc 1 osmux on bsc 2 ... bsc 3 osmux on In this case, bsc 1 and 3 should use osmux if possible, bsc 2 does not have osmux enabled. Thus, you can selectively enable osmux depending on the BSC, and we have a centralized point for configuration from the bsc-nat to enable osmux on demand, as suggested by Holger. At this moment, this patch contains heavy debug logging for each RTP packet that can be removed later to save cycles. The RTP ssrc/seqnum/timestamp is randomly allocated for each MDCX that is received to configure an endpoint.
2014-02-05 17:56:17 +00:00
return CMD_SUCCESS;
}
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
int bsc_nat_vty_init(struct bsc_nat *nat)
{
_nat = nat;
/* show commands */
nat: Attempt to update the VTY usage to the latest version * Install the show commands to be available in the enable mode as well * Provide a copyright header..
2010-06-15 12:14:08 +00:00
install_element_ve(&show_sccp_cmd);
install_element_ve(&show_bsc_cmd);
NAT: vty command to display number of BSCs Add command 'show nat num-bscs-configured' to display number of configured BSCs. Sponsored-by: On-Waves ehf
2016-04-06 15:25:44 +00:00
install_element_ve(&show_nat_bsc_cmd);
nat: Attempt to update the VTY usage to the latest version * Install the show commands to be available in the enable mode as well * Provide a copyright header..
2010-06-15 12:14:08 +00:00
install_element_ve(&show_bsc_cfg_cmd);
install_element_ve(&show_stats_cmd);
nat: Introduce a show statistics-by-lac LAC Currently show show statistics only work by given the internal configuration number, add a version that is working by LAC of the BSC.
2010-07-22 12:26:10 +00:00
install_element_ve(&show_stats_lac_cmd);
nat: Attempt to update the VTY usage to the latest version * Install the show commands to be available in the enable mode as well * Provide a copyright header..
2010-06-15 12:14:08 +00:00
install_element_ve(&close_bsc_cmd);
install_element_ve(&show_msc_cmd);
install_element_ve(&test_regex_cmd);
nat: Add vty command to show the endpoint allocation status
2010-08-28 10:33:34 +00:00
install_element_ve(&show_bsc_mgcp_cmd);
NAT: move BSC config into separate file Introduce new configuration option bscs-config-file which includes BSC configuration from the given file. Both absolute and relative (to the main config file) paths are supported. Add 'show bscs-config' command to display current BSC configuration. Note: it is still possible to have BSC configuration in the main file (provided proper index number is used) and in runtime but BSC configuration is no longer saved automatically. The management of included configuration file is left to external tools. Update configuration examples. Fixes: OS#1669 Sponsored-by: On-Waves ehf
2016-04-12 14:59:25 +00:00
install_element_ve(&show_bscs_cmd);
nat: Introduce a global IMSI barr list using red-black trees
2013-01-01 10:25:09 +00:00
install_element_ve(&show_bar_lst_cmd);
nat: Allow to use the prefix lookup to rewrite numbers * Increase the rewritten rule to five digits (this is the easiest for the unit test). This will add another 40kb to the runtime size. * Create a unit test that tests adding and removing the prefix rules. * Use the regexp match to replace from one package
2013-06-25 09:44:01 +00:00
install_element_ve(&show_prefix_tree_cmd);
nat/ussd: Add 'show ussd-connection' vty command This command returns the current state of the connection to the USSD side channel provider. It shows whether a provider has been connected and authorized or not. Fixes: OW#953
2013-08-14 09:10:34 +00:00
install_element_ve(&show_ussd_connection_cmd);
nat: Add logging commands for the nat as well.
2010-04-06 10:01:15 +00:00
nat: For debugging make it possible to set the last used endpoint This will influence the allocator from where to search for the next free endpoint. This can be used to force it to allocate a specific endpoint next.
2011-02-28 00:07:13 +00:00
install_element(ENABLE_NODE, &set_last_endp_cmd);
nat: Introduce a block on the NAT to slowly get rid of BSCs For restarting the NAT we can now block it, it will not accept new connections and for existing connections it will attempt to drop them over time. A blocked NAT will end up with no BSC connections left and then can be safely restarted.
2011-04-23 21:55:14 +00:00
install_element(ENABLE_NODE, &block_new_conn_cmd);
nat: For debugging make it possible to set the last used endpoint This will influence the allocator from where to search for the next free endpoint. This can be used to force it to allocate a specific endpoint next.
2011-02-28 00:07:13 +00:00
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
/* nat group */
install_element(CONFIG_NODE, &cfg_nat_cmd);
install_node(&nat_node, config_write_nat);
vty: Use vty_install_default() instead of bsc_install_default() Remove ournode_exit_cmd, ournode_end_cmd, and bsc_install_default() since this functionality is provided by the current libosmocore. Replace calls to bsc_install_default() by call to vty_install_default() with the following semantic patch: @rule1@ expression N; @@ - bsc_install_default(N); + vty_install_default(N); Ticket: OW#952 Sponsored-by: On-Waves ehf
2013-10-29 08:30:30 +00:00
vty_install_default(NAT_NODE);
nat: Move MSC ip address into the config.. The address can still be specified on the cli and it will overwrite the config in the config file.
2010-06-15 10:51:04 +00:00
install_element(NAT_NODE, &cfg_nat_msc_ip_cmd);
nat: Make the MSC configurable.
2010-04-17 05:48:45 +00:00
install_element(NAT_NODE, &cfg_nat_msc_port_cmd);
nat: Make ping/pong timeout configurable.
2010-05-05 08:57:38 +00:00
install_element(NAT_NODE, &cfg_nat_auth_time_cmd);
install_element(NAT_NODE, &cfg_nat_ping_time_cmd);
install_element(NAT_NODE, &cfg_nat_pong_time_cmd);
[nat] Add a token to the nat config and handle ID GET This allows to chain a nat with a nat by answering to the id get code and sending the token.
2010-05-14 16:14:58 +00:00
install_element(NAT_NODE, &cfg_nat_token_cmd);
nat: Rename ip-tos to ip-dscp and provide an alias...
2010-07-27 11:21:53 +00:00
install_element(NAT_NODE, &cfg_nat_bsc_ip_dscp_cmd);
[nat] Add ip-tos option to the nat. This is applied to all incoming BSC connections.
2010-05-31 02:36:35 +00:00
install_element(NAT_NODE, &cfg_nat_bsc_ip_tos_cmd);
[nat] Introduce the concept of access-list One can set one access-list to one BSC and one access-list to one NAT. The matching of IMSIs remains the same for now, also applying the white/blacklist. Access lists can not be deleted for now and no perf opt is done (e.g. one could cache the result of the last lookup in the bsc struct).
2010-05-31 17:03:13 +00:00
install_element(NAT_NODE, &cfg_nat_acc_lst_name_cmd);
nat: Add commands to remove access-list from NAT and BSC config
2011-03-29 15:14:34 +00:00
install_element(NAT_NODE, &cfg_nat_no_acc_lst_name_cmd);
NAT: move BSC config into separate file Introduce new configuration option bscs-config-file which includes BSC configuration from the given file. Both absolute and relative (to the main config file) paths are supported. Add 'show bscs-config' command to display current BSC configuration. Note: it is still possible to have BSC configuration in the main file (provided proper index number is used) and in runtime but BSC configuration is no longer saved automatically. The management of included configuration file is left to external tools. Update configuration examples. Fixes: OS#1669 Sponsored-by: On-Waves ehf
2016-04-12 14:59:25 +00:00
install_element(NAT_NODE, &cfg_nat_include_cmd);
nat: Introduce a global IMSI barr list using red-black trees
2013-01-01 10:25:09 +00:00
install_element(NAT_NODE, &cfg_nat_imsi_black_list_fn_cmd);
install_element(NAT_NODE, &cfg_nat_no_imsi_black_list_fn_cmd);
nat: Provide a USSD access list to check for which to play HLR.
2010-10-10 15:29:20 +00:00
install_element(NAT_NODE, &cfg_nat_ussd_lst_name_cmd);
nat: Add an option to set the query string to match Allow the query string to be set. The ussd matching code will check for this string and then forward it to the bypass.
2010-10-11 08:06:39 +00:00
install_element(NAT_NODE, &cfg_nat_ussd_query_cmd);
nat: Keep a ussd token in the config We will have the USSD provider connecting to us and we will use the IPA protocol, including the auth mechanism.
2010-10-12 16:25:52 +00:00
install_element(NAT_NODE, &cfg_nat_ussd_token_cmd);
install_element(NAT_NODE, &cfg_nat_ussd_local_cmd);
vty: Rename 'mgcp-through-msc-ipa' command to 'use-msc-ipa-for-mgcp' Currently the 'mgcp' command fails in the 'config-nat' node, because it get confused with 'mgcp-through-msc-ipa' which is executed instead because of the prefix based command selection. Thus the latter command is renamed by this patch to avoid the common prefix. The workaround in the test suite is removed.
2013-09-02 11:17:17 +00:00
install_element(NAT_NODE, &cfg_nat_use_ipa_for_mgcp_cmd);
[nat] Introduce the concept of access-list One can set one access-list to one BSC and one access-list to one NAT. The matching of IMSIs remains the same for now, also applying the white/blacklist. Access lists can not be deleted for now and no perf opt is done (e.g. one could cache the result of the last lookup in the bsc struct).
2010-05-31 17:03:13 +00:00
filter: Remove nat from bsc_nat_acc_lst and replace with msg
2015-04-04 20:40:12 +00:00
bsc_msg_lst_vty_init(nat, &nat->access_lists, NAT_NODE);
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
nat: Add vty option for number rewriting Parse a msg file in case we do have a list.
2010-10-21 08:59:54 +00:00
/* number rewriting */
install_element(NAT_NODE, &cfg_nat_number_rewrite_cmd);
nat: Add a no number-rewrite command and call it through a VTY test The test is just testing the invocation but does not verify that the side effect of this call. It is good enought for now.
2013-06-25 07:08:02 +00:00
install_element(NAT_NODE, &cfg_nat_no_number_rewrite_cmd);
nat: Implement a post-routing for the NAT software * The post-routing is applied after the first re-writing. To do this the new number is copied back into the called data structure. * Add a testcase that goes from 0172 to 0049 and then back to 0049 using the post rule with a table lookup.
2013-06-25 13:38:31 +00:00
install_element(NAT_NODE, &cfg_nat_number_rewrite_post_cmd);
install_element(NAT_NODE, &cfg_nat_no_number_rewrite_post_cmd);
nat: Add VTY code to configure the SMSC rewriting
2011-05-30 22:35:46 +00:00
install_element(NAT_NODE, &cfg_nat_smsc_addr_cmd);
install_element(NAT_NODE, &cfg_nat_smsc_tpdest_cmd);
nat: Implement clearing of TP-SRR flags from TPDUs Match IMSI and destination address against a set of entries, if it is matching the header will be modified and no sender report will be requested. Change the test case to request the sender report and then verify that this bit is reset to 0.
2012-01-10 21:39:07 +00:00
install_element(NAT_NODE, &cfg_nat_sms_clear_tpsrr_cmd);
install_element(NAT_NODE, &cfg_nat_no_sms_clear_tpsrr_cmd);
nat: Add VTY command for the TP-DA rewriting.
2012-01-18 19:40:01 +00:00
install_element(NAT_NODE, &cfg_nat_sms_number_rewrite_cmd);
install_element(NAT_NODE, &cfg_nat_no_sms_number_rewrite_cmd);
nat: Allow to use the prefix lookup to rewrite numbers * Increase the rewritten rule to five digits (this is the easiest for the unit test). This will add another 40kb to the runtime size. * Create a unit test that tests adding and removing the prefix rules. * Use the regexp match to replace from one package
2013-06-25 09:44:01 +00:00
install_element(NAT_NODE, &cfg_nat_prefix_trie_cmd);
install_element(NAT_NODE, &cfg_nat_no_prefix_trie_cmd);
nat: Add vty option for number rewriting Parse a msg file in case we do have a list.
2010-10-21 08:59:54 +00:00
nat: Make mode-set patching optional
2015-04-24 00:25:17 +00:00
install_element(NAT_NODE, &cfg_nat_sdp_amr_mode_set_cmd);
install_element(NAT_NODE, &cfg_nat_no_sdp_amr_mode_set_cmd);
nat: Create a Paging Group that BSCs can refer to Introduce a paging group that a BSC can refer to and is used during the LAC lookup. This way paging can be flooded through the network and just filtered at the last element in the core.
2011-05-02 17:16:13 +00:00
install_element(NAT_NODE, &cfg_nat_pgroup_cmd);
install_element(NAT_NODE, &cfg_nat_no_pgroup_cmd);
install_node(&pgroup_node, config_write_pgroup);
vty: Use vty_install_default() instead of bsc_install_default() Remove ournode_exit_cmd, ournode_end_cmd, and bsc_install_default() since this functionality is provided by the current libosmocore. Replace calls to bsc_install_default() by call to vty_install_default() with the following semantic patch: @rule1@ expression N; @@ - bsc_install_default(N); + vty_install_default(N); Ticket: OW#952 Sponsored-by: On-Waves ehf
2013-10-29 08:30:30 +00:00
vty_install_default(PGROUP_NODE);
nat: Create a Paging Group that BSCs can refer to Introduce a paging group that a BSC can refer to and is used during the LAC lookup. This way paging can be flooded through the network and just filtered at the last element in the core.
2011-05-02 17:16:13 +00:00
install_element(PGROUP_NODE, &cfg_pgroup_lac_cmd);
install_element(PGROUP_NODE, &cfg_pgroup_no_lac_cmd);
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
/* BSC subgroups */
install_element(NAT_NODE, &cfg_bsc_cmd);
NAT: move BSC config into separate file Introduce new configuration option bscs-config-file which includes BSC configuration from the given file. Both absolute and relative (to the main config file) paths are supported. Add 'show bscs-config' command to display current BSC configuration. Note: it is still possible to have BSC configuration in the main file (provided proper index number is used) and in runtime but BSC configuration is no longer saved automatically. The management of included configuration file is left to external tools. Update configuration examples. Fixes: OS#1669 Sponsored-by: On-Waves ehf
2016-04-12 14:59:25 +00:00
install_node(&bsc_node, NULL);
vty: Use vty_install_default() instead of bsc_install_default() Remove ournode_exit_cmd, ournode_end_cmd, and bsc_install_default() since this functionality is provided by the current libosmocore. Replace calls to bsc_install_default() by call to vty_install_default() with the following semantic patch: @rule1@ expression N; @@ - bsc_install_default(N); + vty_install_default(N); Ticket: OW#952 Sponsored-by: On-Waves ehf
2013-10-29 08:30:30 +00:00
vty_install_default(NAT_BSC_NODE);
nat: Rename BSC_NODE to NAT_BSC_NODE to avoid future issues.
2010-06-17 06:42:20 +00:00
install_element(NAT_BSC_NODE, &cfg_bsc_token_cmd);
nat: After we identified the bsc check the key We are using the token to find the right bsc_config and then we can use the last_rand of the bsc_connection to calculate the expected result and try to compare it with a time constant(???) memcmp.
2015-06-08 16:33:28 +00:00
install_element(NAT_BSC_NODE, &cfg_bsc_auth_key_cmd);
install_element(NAT_BSC_NODE, &cfg_bsc_no_auth_key_cmd);
nat: Rename BSC_NODE to NAT_BSC_NODE to avoid future issues.
2010-06-17 06:42:20 +00:00
install_element(NAT_BSC_NODE, &cfg_bsc_lac_cmd);
nat: Allow a BSC to have multiple LACs Make it possible that one BSC is serving multiple cells. Introduce a list of lacs, add functions to manipulate the lists. The current test cases for paging by lac continue to work.
2010-10-08 14:08:29 +00:00
install_element(NAT_BSC_NODE, &cfg_bsc_no_lac_cmd);
nat: Rename BSC_NODE to NAT_BSC_NODE to avoid future issues.
2010-06-17 06:42:20 +00:00
install_element(NAT_BSC_NODE, &cfg_bsc_paging_cmd);
install_element(NAT_BSC_NODE, &cfg_bsc_desc_cmd);
install_element(NAT_BSC_NODE, &cfg_bsc_acc_lst_name_cmd);
nat: Add commands to remove access-list from NAT and BSC config
2011-03-29 15:14:34 +00:00
install_element(NAT_BSC_NODE, &cfg_bsc_no_acc_lst_name_cmd);
nat: Change number of multiplexes to the max-endpoints
2011-02-27 10:04:27 +00:00
install_element(NAT_BSC_NODE, &cfg_bsc_max_endps_cmd);
nat: Use 'paging group' because we have paging forbidden. Make paging-group deprecated and introduce the new paging group.
2011-05-17 17:28:07 +00:00
install_element(NAT_BSC_NODE, &cfg_bsc_old_grp_cmd);
nat: Create a Paging Group that BSCs can refer to Introduce a paging group that a BSC can refer to and is used during the LAC lookup. This way paging can be flooded through the network and just filtered at the last element in the core.
2011-05-02 17:16:13 +00:00
install_element(NAT_BSC_NODE, &cfg_bsc_paging_grp_cmd);
install_element(NAT_BSC_NODE, &cfg_bsc_no_paging_grp_cmd);
mgcp: add voice muxer support This patch adds the voice muxer. You can use this to batch RTP traffic to reduce bandwidth comsuption. Basically, osmux transforms RTP flows to a compact batch format, that is later on decompacted to its original form. Port UDP/1984 is used for the muxer traffic between osmo-bsc_nat and osmo-bsc_mgcp (in the BSC side). This feature depends on libosmo-netif, which contains the osmux core support. Osmux is requested on-demand via the MGCP CRCX/MDCX messages (using the vendor-specific extension X-Osmux: on) coming from the BSC-NAT, so you can selectively enable osmux per BSC from one the bsc-nat.cfg file, so we have a centralized point to enable/disable osmux. First thing you need to do is to accept requests to use Osmux, this can be done from VTY interface of osmo-bsc_nat and osmo-bsc_mgcp by adding the following line: mgcp ... osmux on osmux batch-factor 4 This just initializes the osmux engine. You still have to specify what BSC uses osmux from osmo-bsc_nat configuration file: ... bsc 1 osmux on bsc 2 ... bsc 3 osmux on In this case, bsc 1 and 3 should use osmux if possible, bsc 2 does not have osmux enabled. Thus, you can selectively enable osmux depending on the BSC, and we have a centralized point for configuration from the bsc-nat to enable osmux on demand, as suggested by Holger. At this moment, this patch contains heavy debug logging for each RTP packet that can be removed later to save cycles. The RTP ssrc/seqnum/timestamp is randomly allocated for each MDCX that is received to configure an endpoint.
2014-02-05 17:56:17 +00:00
install_element(NAT_BSC_NODE, &cfg_bsc_osmux_cmd);
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
nat: Add MGCP code and parsing to the nat code.. For the nat we will have NAT and MGCP in the same process and this commit starts with that. We are linking in the MGCP code and one can embed MGCP config snippets...
2010-06-15 10:50:26 +00:00
mgcp_vty_init();
[nat] Add VTY support to the BSC nat application * Create struct bsc_nat and move the various lists into this structure * Create the VTY code * Call the VTY init and parsing code * Create functions to create the types.. * Add some stuff into the bsc_connection to be used for the NAT with proper config files. E.g. to close the connection if the BSC does not respond to a given command.
2010-06-15 10:46:11 +00:00
return 0;
}
/* called by the telnet interface... we have our own init above */
vty: remove ignored logging parameters Since ce9fec3e896571835ac5bfd2980d6836f2b29f0d libosmocore ignores parameters to log_vty_command_* functions. Hence parameter of logging_vty_add_cmds() is ignored too. As we depend on much later libosmocore version anyway, we can simplify code somewhat by removing parameters which will be ignored anyway. Change-Id: I62f752fd88f1d8fefa563648f9864c7c31f87991
2017-01-12 18:35:11 +00:00
int bsc_vty_init(struct gsm_network *network)
misc: Compile fixes due 4d54d0b883dcf85cd92290dd4cea51754c70b621
2011-02-24 13:33:09 +00:00
{
vty: remove ignored logging parameters Since ce9fec3e896571835ac5bfd2980d6836f2b29f0d libosmocore ignores parameters to log_vty_command_* functions. Hence parameter of logging_vty_add_cmds() is ignored too. As we depend on much later libosmocore version anyway, we can simplify code somewhat by removing parameters which will be ignored anyway. Change-Id: I62f752fd88f1d8fefa563648f9864c7c31f87991
2017-01-12 18:35:11 +00:00
logging_vty_add_cmds(NULL);
misc: Compile fixes due 4d54d0b883dcf85cd92290dd4cea51754c70b621
2011-02-24 13:33:09 +00:00
return 0;
}