From m.tzamtzi at gmail.com Thu Dec 6 07:37:22 2012 From: m.tzamtzi at gmail.com (Maria Tzamtzi) Date: Thu, 6 Dec 2012 07:37:22 +0000 (UTC) Subject: Several questions References: <20100810034251.GZ3736@prithivi.gnumonks.org> Message-ID: Harald Welte gnumonks.org> writes: > > Responding to the only question that zecke did not respond to: > > On Mon, Aug 09, 2010 at 06:07:28PM +0300, jason mercury wrote: > > > 3) Could I send SMS in which extension of the sender is text not integer. > > no, this doesn't work with the current architecture. We also don't want > to work on a quick fix but rather "outsource" the full SMS processing into > a separate process. For that we need a clean API/interface/protocol how > the MSC-part of bsc_hack and that external process interact, and that again > will probably be based on our TCAP/MAP implementation, which is under active > development. I would like to ask you about the "quick fix" you mention when there is text in the extension field. Does this fix affect the gsm_subscriber or the gsm_sms structure? Is it something that affects only a few files or it is necessary to make major modifications? From zero-kelvin at gmx.de Mon Dec 3 10:30:17 2012 From: zero-kelvin at gmx.de (dexter) Date: Mon, 03 Dec 2012 11:30:17 +0100 Subject: Osmocom Berlin User Group meeting In-Reply-To: <20120818115942.GV29525@prithivi.gnumonks.org> References: <502d01a9.mirider@mirider.augusta.de> <20120818115942.GV29525@prithivi.gnumonks.org> Message-ID: <50BC7F39.3020107@gmx.de> Hi folks. This is the announcement for the next Osmocom Berlin meeting. Dec 05, 8pm @ CCC Berlin, Marienstr. 11, 10113 Berlin There is no formal presentation scheduled for this meeting. If you are interested to show up, feel free to do so. There is no registration required. The meeting is free as in "free beer", despite no actual free beer being around. Regards, Philipp Maier From peter at stuge.se Mon Dec 3 18:10:21 2012 From: peter at stuge.se (Peter Stuge) Date: Mon, 3 Dec 2012 19:10:21 +0100 Subject: 29c3 GSM planning [was: Osmocom Berlin User Group meeting] In-Reply-To: <50BC7F39.3020107@gmx.de> References: <502d01a9.mirider@mirider.augusta.de> <20120818115942.GV29525@prithivi.gnumonks.org> <50BC7F39.3020107@gmx.de> Message-ID: <20121203181021.14684.qmail@stuge.se> dexter wrote: > Dec 05, 8pm @ CCC Berlin, Marienstr. 11, 10113 Berlin > > There is no formal presentation scheduled for this meeting. There will however be some discussion of the 29c3 field test of OpenBSC[1] and maybe even a bit of work done on the system that we used both at the last CCC Camp and at 28c3. For those who will participate at 29c3 but can't make it to CCCB on Wednesday we'll try to bridge between the meeting and the internets. //Peter [1] http://openbsc.osmocom.org/trac/wiki/FieldTests/29c3 (The wiki page will get some more updates in the next days.) From zero-kelvin at gmx.de Tue Dec 18 09:02:47 2012 From: zero-kelvin at gmx.de (dexter) Date: Tue, 18 Dec 2012 10:02:47 +0100 Subject: Osmocom Berlin User Group meeting In-Reply-To: <20120818115942.GV29525@prithivi.gnumonks.org> References: <502d01a9.mirider@mirider.augusta.de> <20120818115942.GV29525@prithivi.gnumonks.org> Message-ID: <50D03137.4020805@gmx.de> Hi folks. This is the announcement for the next Osmocom Berlin meeting. Dec 19, 8pm @ CCC Berlin, Marienstr. 11, 10113 Berlin There is no formal presentation scheduled for this meeting. If you are interested to show up, feel free to do so. There is no registration required. The meeting is free as in "free beer", despite no actual free beer being around. Regards, Philipp Maier From holger at freyther.de Sat Dec 1 09:58:46 2012 From: holger at freyther.de (Holger Hans Peter Freyther) Date: Sat, 1 Dec 2012 10:58:46 +0100 Subject: [PATH] Selecting the latest nanoBTS firmware on connect Re: nanoBTS bring up problem In-Reply-To: References: <20121025145947.GD9520@xiaoyu.lan> <20121122181703.GG25233@xiaoyu.lan> Message-ID: <20121201095846.GO16672@xiaoyu.lan> On Thu, Nov 22, 2012 at 11:26:44PM +0400, Alexander Chemeris wrote: > I already disconnected everything, but I'll try to give it a shot at > the weekend or next week. Ping me if I forget to do that. ping, or too early? :) From alexander.chemeris at gmail.com Sat Dec 1 18:13:10 2012 From: alexander.chemeris at gmail.com (Alexander Chemeris) Date: Sat, 1 Dec 2012 22:13:10 +0400 Subject: [PATH] Selecting the latest nanoBTS firmware on connect Re: nanoBTS bring up problem In-Reply-To: <20121201095846.GO16672@xiaoyu.lan> References: <20121025145947.GD9520@xiaoyu.lan> <20121122181703.GG25233@xiaoyu.lan> <20121201095846.GO16672@xiaoyu.lan> Message-ID: On Sat, Dec 1, 2012 at 1:58 PM, Holger Hans Peter Freyther wrote: > On Thu, Nov 22, 2012 at 11:26:44PM +0400, Alexander Chemeris wrote: >> I already disconnected everything, but I'll try to give it a shot at >> the weekend or next week. Ping me if I forget to do that. > > ping, or too early? :) I apologize - it seems I no longer have a power cable I used for PoE injector for my nanoBTS. I'll try to find a new one, but it'll take some time. -- Regards, Alexander Chemeris. CEO, Fairwaves LLC / ??? ??????? http://fairwaves.ru From holger at freyther.de Mon Dec 3 08:41:53 2012 From: holger at freyther.de (Holger Hans Peter Freyther) Date: Mon, 3 Dec 2012 09:41:53 +0100 Subject: [PATH] Selecting the latest nanoBTS firmware on connect Re: nanoBTS bring up problem In-Reply-To: References: <20121025145947.GD9520@xiaoyu.lan> <20121122181703.GG25233@xiaoyu.lan> <20121201095846.GO16672@xiaoyu.lan> Message-ID: <20121203084153.GA8968@xiaoyu.lan> On Sat, Dec 01, 2012 at 10:13:10PM +0400, Alexander Chemeris wrote: > > I apologize - it seems I no longer have a power cable I used for PoE > injector for my nanoBTS. I'll try to find a new one, but it'll take > some time. hehe, please tell me when to ping you next time. From mailabolfazl83 at gmail.com Mon Dec 3 07:24:05 2012 From: mailabolfazl83 at gmail.com (AD) Date: Mon, 03 Dec 2012 10:54:05 +0330 Subject: RNC Support Message-ID: <50BC5395.1070309@gmail.com> An HTML attachment was scrubbed... URL: From 246tnt at gmail.com Mon Dec 3 09:22:32 2012 From: 246tnt at gmail.com (Sylvain Munaut) Date: Mon, 3 Dec 2012 10:22:32 +0100 Subject: RNC Support In-Reply-To: <50BC5395.1070309@gmail.com> References: <50BC5395.1070309@gmail.com> Message-ID: Hi, > Can your openBSC software support RNC ( Radio Network Controller) for UMTS > Network? No. > Is there any project that implement RNC for UMTS Network? Sure .. All the big manufacturer have RNC implementation for their equipment. > Is there any opensource project that implement RNC for UMTS Network? Not that I know of. (but then again, that doesn't mean there aren't ... ) Cheers, Sylvain From wojsed at gmail.com Tue Dec 4 22:23:35 2012 From: wojsed at gmail.com (Wojciech Sedlaczek) Date: Tue, 4 Dec 2012 23:23:35 +0100 Subject: Problem with running OsmoSGSN and OsmoNITB Message-ID: Hi, I have a problem with running 2 software programs OpenBSC (osmo-nitb and osmo-sgsn). When I run osmo-nitb: ROOT: /media/obsc_gprs/gitrep/openbsc/openbsc/src/osmo-nitb# ./osmo-nitb There is no such command. Error occurred during reading below line: logging level mi notice <0005> bsc_init.c:496 Failed to parse the config file: 'openbsc.cfg' ______________________________________________________________ However, when I run osmo-sgsn: ROOT: /media/obsc_gprs/gitrep/openbsc/openbsc/src/gprs# ./osmo-sgsn <0011> gprs_ns.c:171 NSVCI=65534 Creating NS-VC <0010> sgsn_libgtp.c:571 Failed to create GTP: -1 <0010> sgsn_main.c:348 Cannot bind/listen on GTP socket Anybody help? From stuart at bluewave.im Thu Dec 6 08:49:58 2012 From: stuart at bluewave.im (Stuart Baggs) Date: Thu, 6 Dec 2012 08:49:58 +0000 Subject: nanoBTS New Stock Available Message-ID: <8E5BE4D8-7EDF-484E-95FD-9793D33A9C11@bluewave.im> Dear List We've just taken delivery of a few more pico cells from our partners (who are moving everything over to 3g). For sale we now have: 3 x Model 139 (1800 MHz) GPRS 2 x Model 139 (1900 MHz) GPRS 1 x Model 165CU (900 MHz) GPRS / EDGE We have amplifiers and diversity receiver units for all models as well as external antenna connection kits for the model 139 (165 has built in SMA connectors). All models available for Express worldwide delivery within 2 days. Credit / Debit cards accepted. Kind Regards Stuart Baggs Managing Director BlueWave Communications Ltd From laforge at gnumonks.org Thu Dec 6 10:48:00 2012 From: laforge at gnumonks.org (Harald Welte) Date: Thu, 6 Dec 2012 11:48:00 +0100 Subject: Poll: Do list subscribers like to see BTS-for-sale postings? In-Reply-To: <8E5BE4D8-7EDF-484E-95FD-9793D33A9C11@bluewave.im> References: <8E5BE4D8-7EDF-484E-95FD-9793D33A9C11@bluewave.im> Message-ID: <20121206104800.GO7055@prithivi.gnumonks.org> Hi Stuart, while so far we have been open to the occasional posting of available BTSs at this list, I'm not entirely sure if ther recent increas in frequency of your postings are still appreciated. As I may be considered partial due to my involvement in sysmocom (who is bulding + selling sysmoBTS), I would like to hereby solicit comments from the list subscribers to see if they would like to see this kind of postings, even if they're as frequent as your recent posts, or if they prefer to keep this list technical and only see non-commercial offers of BTS equipment. Whatever is the result of that feedback we shuold adopt as a list policy. Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From stuart at bwc.im Thu Dec 6 10:54:31 2012 From: stuart at bwc.im (Stuart Baggs) Date: Thu, 6 Dec 2012 10:54:31 +0000 Subject: Poll: Do list subscribers like to see BTS-for-sale postings? In-Reply-To: <20121206104800.GO7055@prithivi.gnumonks.org> References: <8E5BE4D8-7EDF-484E-95FD-9793D33A9C11@bluewave.im> <20121206104800.GO7055@prithivi.gnumonks.org> Message-ID: <30234288-C548-4EE1-8584-674DA2CCD044@bwc.im> HI Harald I'll leave it up to list members to decide and of course happy to abide by any decision. What ever decision is reached, I'd like to continue technical involvement in the projects development. As well as selling the hardware, we're also big advocates of openBSC itself. With Kindest Regards Stuart On 6 Dec 2012, at 10:48, Harald Welte wrote: > Hi Stuart, > > while so far we have been open to the occasional posting of available > BTSs at this list, I'm not entirely sure if ther recent increas in > frequency of your postings are still appreciated. > > As I may be considered partial due to my involvement in sysmocom (who is > bulding + selling sysmoBTS), I would like to hereby solicit comments > from the list subscribers to see if they would like to see this kind of > postings, even if they're as frequent as your recent posts, or if they > prefer to keep this list technical and only see non-commercial offers of > BTS equipment. > > Whatever is the result of that feedback we shuold adopt as a list > policy. > > Regards, > Harald > > -- > - Harald Welte http://laforge.gnumonks.org/ > ============================================================================ > "Privacy in residential applications is a desirable marketing option." > (ETSI EN 300 175-7 Ch. A6) From peter at stuge.se Thu Dec 6 11:48:47 2012 From: peter at stuge.se (Peter Stuge) Date: Thu, 6 Dec 2012 12:48:47 +0100 Subject: Poll: Do list subscribers like to see BTS-for-sale postings? In-Reply-To: <20121206104800.GO7055@prithivi.gnumonks.org> References: <8E5BE4D8-7EDF-484E-95FD-9793D33A9C11@bluewave.im> <20121206104800.GO7055@prithivi.gnumonks.org> Message-ID: <20121206114847.31937.qmail@stuge.se> Harald Welte wrote: > I would like to hereby solicit comments from the list subscribers > to see if they would like to see this kind of postings, even if > they're as frequent as your recent posts Since these particular units aren't completely trivial to acquire I think it's nice to spread information efficiently within the project when there are opportunities to buy one, both when it's a commercial offer and when it's a not-for-profit developer offer. I think it's nice if list subscribers can have some head start before gear goes onto eBay or other sales channels. Since it's very low volume posting I'm personally not annoyed, even if it's as frequent as recently. There are of course other ways to keep people updated about hardware availability - one idea would be a wiki page which anyone who is interested could subscribe to in order to receive updates - off list. (That shouldn't require a wiki account though. Maybe RSS is a good solution. And a wiki account would still be needed to post offers, which means slightly more effort than simply posting an email.) Very generally speaking I think it's valuable for the project to show that various companies are not afraid to openly offer both services and products related to the software. //Peter From t-openbsc at tobias.org Thu Dec 6 14:38:46 2012 From: t-openbsc at tobias.org (Tobias Engel) Date: Thu, 06 Dec 2012 15:38:46 +0100 Subject: Poll: Do list subscribers like to see BTS-for-sale postings? In-Reply-To: <20121206114847.31937.qmail@stuge.se> References: <8E5BE4D8-7EDF-484E-95FD-9793D33A9C11@bluewave.im> <20121206104800.GO7055@prithivi.gnumonks.org> <20121206114847.31937.qmail@stuge.se> Message-ID: <50C0ADF6.3030000@tobias.org> >> I would like to hereby solicit comments from the list subscribers >> to see if they would like to see this kind of postings, even if >> they're as frequent as your recent posts > > Since these particular units aren't completely trivial to acquire I > think it's nice to spread information efficiently within the project > when there are opportunities to buy one, both when it's a commercial > offer and when it's a not-for-profit developer offer. I agree with Peter. As long as the postings don't get too frequent, I am ok with them. -Tobias From pablo at gnumonks.org Tue Dec 11 14:59:51 2012 From: pablo at gnumonks.org (Pablo Neira Ayuso) Date: Tue, 11 Dec 2012 15:59:51 +0100 Subject: Poll: Do list subscribers like to see BTS-for-sale postings? In-Reply-To: <50C0ADF6.3030000@tobias.org> References: <8E5BE4D8-7EDF-484E-95FD-9793D33A9C11@bluewave.im> <20121206104800.GO7055@prithivi.gnumonks.org> <20121206114847.31937.qmail@stuge.se> <50C0ADF6.3030000@tobias.org> Message-ID: <20121211145951.GA7775@1984> On Thu, Dec 06, 2012 at 03:38:46PM +0100, Tobias Engel wrote: > >> I would like to hereby solicit comments from the list subscribers > >> to see if they would like to see this kind of postings, even if > >> they're as frequent as your recent posts > > > > Since these particular units aren't completely trivial to acquire I > > think it's nice to spread information efficiently within the project > > when there are opportunities to buy one, both when it's a commercial > > offer and when it's a not-for-profit developer offer. > > I agree with Peter. > As long as the postings don't get too frequent, I am ok with them. They are not frequent, yes, but in my case I don't like "advertisements". When I need anything, just go where I can get the stuff I need. Probably, we can add some page in the trac with pointers to webpages of people selling equipment in case people want to acquire anything? From 246tnt at gmail.com Thu Dec 6 12:46:49 2012 From: 246tnt at gmail.com (Sylvain Munaut) Date: Thu, 6 Dec 2012 13:46:49 +0100 Subject: Poll: Do list subscribers like to see BTS-for-sale postings? In-Reply-To: <20121206104800.GO7055@prithivi.gnumonks.org> References: <8E5BE4D8-7EDF-484E-95FD-9793D33A9C11@bluewave.im> <20121206104800.GO7055@prithivi.gnumonks.org> Message-ID: Hi Stuart and all, > while so far we have been open to the occasional posting of available > BTSs at this list, I'm not entirely sure if ther recent increas in > frequency of your postings are still appreciated. Actually I had the same tought this morning when seeing that mail _again_. And here the "again" part is critical. Although I don't mind the occasional mail when a source of hard to find items become available, I think a single mail is enough. To me it seems pretty clear that you'll have several units available and that anyone looking for one could contact you, no need to post each time ... People can contact you in private to ask for your inventory (or you could just use a dedicated page on your site for that or whatever to take it off the list). Now of course this is to be left to appreciations ... if you happen to have an unlimited supply of 50$ LTE+3G+GSM base stations with full tech docs, feel free to tell us about it. Cheers, Sylvain From zero-kelvin at gmx.de Fri Dec 7 10:40:09 2012 From: zero-kelvin at gmx.de (dexter) Date: Fri, 07 Dec 2012 11:40:09 +0100 Subject: Poll: Do list subscribers like to see BTS-for-sale postings? In-Reply-To: References: <8E5BE4D8-7EDF-484E-95FD-9793D33A9C11@bluewave.im> <20121206104800.GO7055@prithivi.gnumonks.org> Message-ID: <50C1C789.80207@gmx.de> Hi Folks > And here the "again" part is critical. I do not understand why it is critical. Is there any legal problem with that? At least for me i am ok with such offers since it is the only known way to get my hands on such scarce hardware. But there is another problem i see. If you buy from the list, there is no security. You have to trust the seller absolutely. I am a bit scared to send that much money to a foreign country. No, no, my nanoBTS is somewhere in germany and i will come personally and pick it up ;-) regards. Philipp Maier From 246tnt at gmail.com Fri Dec 7 11:37:18 2012 From: 246tnt at gmail.com (Sylvain Munaut) Date: Fri, 7 Dec 2012 12:37:18 +0100 Subject: Poll: Do list subscribers like to see BTS-for-sale postings? In-Reply-To: <50C1C789.80207@gmx.de> References: <8E5BE4D8-7EDF-484E-95FD-9793D33A9C11@bluewave.im> <20121206104800.GO7055@prithivi.gnumonks.org> <50C1C789.80207@gmx.de> Message-ID: Hi, >> And here the "again" part is critical. > > I do not understand why it is critical. Is there any legal problem with > that? legal ? No ... what in my message made you think I was expressing a legal opinion ? Harald was asking for the personal opinion of people on the list, I was just expressing mine and the reason why I felt that way, but it's obviously all subjective (by pretty much the definition of "personal opinion"). Cheers, Sylvain From zero-kelvin at gmx.de Fri Dec 7 13:47:06 2012 From: zero-kelvin at gmx.de (dexter) Date: Fri, 07 Dec 2012 14:47:06 +0100 Subject: Poll: Do list subscribers like to see BTS-for-sale postings? In-Reply-To: References: <8E5BE4D8-7EDF-484E-95FD-9793D33A9C11@bluewave.im> <20121206104800.GO7055@prithivi.gnumonks.org> <50C1C789.80207@gmx.de> Message-ID: <50C1F35A.5010300@gmx.de> Hi Sylvain, > > legal ? No ... what in my message made you think I was expressing a > legal opinion ? As far as i remember, some years ago we were advised not to trade stuff here. Thats all i know. I just thought it could be also a leagal issue in some way. regards. Philipp From holger at freyther.de Thu Dec 6 14:36:23 2012 From: holger at freyther.de (Holger Hans Peter Freyther) Date: Thu, 6 Dec 2012 15:36:23 +0100 Subject: Poll: Do list subscribers like to see BTS-for-sale postings? In-Reply-To: <20121206104800.GO7055@prithivi.gnumonks.org> References: <8E5BE4D8-7EDF-484E-95FD-9793D33A9C11@bluewave.im> <20121206104800.GO7055@prithivi.gnumonks.org> Message-ID: <20121206143623.GC17828@xiaoyu.lan> On Thu, Dec 06, 2012 at 11:48:00AM +0100, Harald Welte wrote: > As I may be considered partial due to my involvement in sysmocom (who is > bulding + selling sysmoBTS), I would like to hereby solicit comments > from the list subscribers to see if they would like to see this kind of > postings, even if they're as frequent as your recent posts, or if they > prefer to keep this list technical and only see non-commercial offers of > BTS equipment. This should be a technical list. From Max.Suraev at fairwaves.ru Fri Dec 7 14:58:21 2012 From: Max.Suraev at fairwaves.ru (=?UTF-8?B?4piO?=) Date: Fri, 07 Dec 2012 15:58:21 +0100 Subject: Poll: Do list subscribers like to see BTS-for-sale postings? In-Reply-To: <20121206104800.GO7055@prithivi.gnumonks.org> References: <8E5BE4D8-7EDF-484E-95FD-9793D33A9C11@bluewave.im> <20121206104800.GO7055@prithivi.gnumonks.org> Message-ID: <50C2040D.9090808@fairwaves.ru> Personally I'm ok with commercial postings as long as we establish some reasonable "rate-limit" on them - say no more than 1 in 2 weeks per person/company. -- best regards, Max, http://fairwaves.ru From rp.labs at gmx.ch Fri Dec 7 18:34:20 2012 From: rp.labs at gmx.ch (Labs) Date: Fri, 07 Dec 2012 19:34:20 +0100 Subject: Poll: Do list subscribers like to see BTS-for-sale postings? In-Reply-To: <20121206104800.GO7055@prithivi.gnumonks.org> References: <8E5BE4D8-7EDF-484E-95FD-9793D33A9C11@bluewave.im> <20121206104800.GO7055@prithivi.gnumonks.org> Message-ID: <50C236AC.1050504@gmx.ch> Hello, Considering that there were not so many emails regarding sales of hardware and this kind of hardware is hard to source in normal shops or even ebay I am OK to receive them. I remember a few months ago I was waiting for such emails when I wanted to buy a nanoBTS and nothing... Regards, R. From admin at manateeshome.com Thu Dec 6 13:52:44 2012 From: admin at manateeshome.com (Pierre Kim) Date: Thu, 6 Dec 2012 22:52:44 +0900 Subject: OpenBSC + LCR + Asterisk Message-ID: <193201cdd3b8$f92076f0$eb6164d0$@manateeshome.com> Can someone share their configuration files used to run openbsc with new LCR? The newest LCR branch jolly/new does not seem to be understanding old configurations on openbsc wiki. Remote application=asterisk context=xyz does not work. Please help me with configuring LCR Thank you, -------------- next part -------------- An HTML attachment was scrubbed... URL: From andreas at eversberg.eu Sat Dec 8 15:41:19 2012 From: andreas at eversberg.eu (Andreas Eversberg) Date: Sat, 08 Dec 2012 16:41:19 +0100 Subject: OpenBSC + LCR + Asterisk Message-ID: <50C35F9F.4040203@eversberg.eu> [ast] remote asterisk context from-lcr earlyb yes tones yes hi pierre, the chan_lcr to asterisk is now an interface. you can define multiple interfaces, if you like to use different contexts. (in this case it is "from-lcr".) exten => _.,1,Dial(LCR/ast/${EXTEN:0}) in order to define what interface to be used, name it in the dial app at extensions.conf. ("ast" in this case.) regards, andreas From alexander.huemer at xx.vu Thu Dec 6 22:09:29 2012 From: alexander.huemer at xx.vu (Alexander Huemer) Date: Thu, 6 Dec 2012 23:09:29 +0100 Subject: [PATCH 0/3] libosmo-crypt-a53 autotools cleanup Message-ID: <1354831772-26187-1-git-send-email-alexander.huemer@xx.vu> This a series of 3 patches for libosmo-crypt-a53, branch master. Former HEAD was 3de78cd69c0594b0903e6cfffab7920c69e2d478. The patches clean up the autotools configuration. The library itself is not changed[1]. Fell free to merge the patches if they seem useful. Kind regards, -Alexander Huemer [1] overall diffstat: configure.ac | 2 +- m4/DUMMY | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) From alexander.huemer at xx.vu Thu Dec 6 22:09:30 2012 From: alexander.huemer at xx.vu (Alexander Huemer) Date: Thu, 6 Dec 2012 23:09:30 +0100 Subject: [PATCH 1/3] copy m4/DUMMY from libosmocore In-Reply-To: <1354831772-26187-1-git-send-email-alexander.huemer@xx.vu> References: <1354831772-26187-1-git-send-email-alexander.huemer@xx.vu> Message-ID: <1354831772-26187-2-git-send-email-alexander.huemer@xx.vu> Otherwise 'autoreconf -i' fails on a fresh clone --- m4/DUMMY | 1 + 1 file changed, 1 insertion(+) create mode 100644 m4/DUMMY diff --git a/m4/DUMMY b/m4/DUMMY new file mode 100644 index 0000000..fda557a --- /dev/null +++ b/m4/DUMMY @@ -0,0 +1 @@ +Dummply placeholder. -- 1.8.0 From alexander.huemer at xx.vu Thu Dec 6 22:09:31 2012 From: alexander.huemer at xx.vu (Alexander Huemer) Date: Thu, 6 Dec 2012 23:09:31 +0100 Subject: [PATCH 2/3] rename configure.in -> configure.ac In-Reply-To: <1354831772-26187-1-git-send-email-alexander.huemer@xx.vu> References: <1354831772-26187-1-git-send-email-alexander.huemer@xx.vu> Message-ID: <1354831772-26187-3-git-send-email-alexander.huemer@xx.vu> configure.in is unsupported starting with automake 1.13 --- configure.ac | 43 +++++++++++++++++++++++++++++++++++++++++++ configure.in | 43 ------------------------------------------- 2 files changed, 43 insertions(+), 43 deletions(-) create mode 100644 configure.ac delete mode 100644 configure.in diff --git a/configure.ac b/configure.ac new file mode 100644 index 0000000..b5b9481 --- /dev/null +++ b/configure.ac @@ -0,0 +1,43 @@ +AC_INIT([libosmo-crypt-a53], + m4_esyscmd([./git-version-gen .tarball-version]), + [openbsc-devel at lists.openbsc.org]) + +AM_INIT_AUTOMAKE([dist-bzip2]) + +dnl kernel style compile messages +m4_ifdef([AM_SILENT_RULES], [AM_SILENT_RULES([yes])]) + +dnl checks for programs +AC_PROG_MAKE_SET +AC_PROG_CC +AC_PROG_INSTALL +LT_INIT +AC_PROG_LIBTOOL + +AC_CONFIG_MACRO_DIR([m4]) + +dnl checks for header files +AC_HEADER_STDC +AC_CHECK_HEADERS(execinfo.h sys/select.h) + +# The following test is taken from WebKit's webkit.m4 +saved_CFLAGS="$CFLAGS" +CFLAGS="$CFLAGS -fvisibility=hidden " +AC_MSG_CHECKING([if ${CC} supports -fvisibility=hidden]) +AC_COMPILE_IFELSE([char foo;], + [ AC_MSG_RESULT([yes]) + SYMBOL_VISIBILITY="-fvisibility=hidden"], + AC_MSG_RESULT([no])) +CFLAGS="$saved_CFLAGS" +AC_SUBST(SYMBOL_VISIBILITY) + +dnl Generate the output +AM_CONFIG_HEADER(config.h) + +AC_OUTPUT( + libosmo-crypt-a53.pc + include/Makefile + include/osmocom/Makefile + include/osmocom/crypt/Makefile + src/Makefile + Makefile) diff --git a/configure.in b/configure.in deleted file mode 100644 index b5b9481..0000000 --- a/configure.in +++ /dev/null @@ -1,43 +0,0 @@ -AC_INIT([libosmo-crypt-a53], - m4_esyscmd([./git-version-gen .tarball-version]), - [openbsc-devel at lists.openbsc.org]) - -AM_INIT_AUTOMAKE([dist-bzip2]) - -dnl kernel style compile messages -m4_ifdef([AM_SILENT_RULES], [AM_SILENT_RULES([yes])]) - -dnl checks for programs -AC_PROG_MAKE_SET -AC_PROG_CC -AC_PROG_INSTALL -LT_INIT -AC_PROG_LIBTOOL - -AC_CONFIG_MACRO_DIR([m4]) - -dnl checks for header files -AC_HEADER_STDC -AC_CHECK_HEADERS(execinfo.h sys/select.h) - -# The following test is taken from WebKit's webkit.m4 -saved_CFLAGS="$CFLAGS" -CFLAGS="$CFLAGS -fvisibility=hidden " -AC_MSG_CHECKING([if ${CC} supports -fvisibility=hidden]) -AC_COMPILE_IFELSE([char foo;], - [ AC_MSG_RESULT([yes]) - SYMBOL_VISIBILITY="-fvisibility=hidden"], - AC_MSG_RESULT([no])) -CFLAGS="$saved_CFLAGS" -AC_SUBST(SYMBOL_VISIBILITY) - -dnl Generate the output -AM_CONFIG_HEADER(config.h) - -AC_OUTPUT( - libosmo-crypt-a53.pc - include/Makefile - include/osmocom/Makefile - include/osmocom/crypt/Makefile - src/Makefile - Makefile) -- 1.8.0 From alexander.huemer at xx.vu Thu Dec 6 22:09:32 2012 From: alexander.huemer at xx.vu (Alexander Huemer) Date: Thu, 6 Dec 2012 23:09:32 +0100 Subject: [PATCH 3/3] configure.ac: add AC_LANG_SOURCE to AC_COMPILE_IFELSE In-Reply-To: <1354831772-26187-1-git-send-email-alexander.huemer@xx.vu> References: <1354831772-26187-1-git-send-email-alexander.huemer@xx.vu> Message-ID: <1354831772-26187-4-git-send-email-alexander.huemer@xx.vu> This is required since autoconf 2.66 for safetly reason --- configure.ac | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/configure.ac b/configure.ac index b5b9481..5e553e4 100644 --- a/configure.ac +++ b/configure.ac @@ -24,7 +24,7 @@ AC_CHECK_HEADERS(execinfo.h sys/select.h) saved_CFLAGS="$CFLAGS" CFLAGS="$CFLAGS -fvisibility=hidden " AC_MSG_CHECKING([if ${CC} supports -fvisibility=hidden]) -AC_COMPILE_IFELSE([char foo;], +AC_COMPILE_IFELSE([AC_LANG_SOURCE([char foo;])], [ AC_MSG_RESULT([yes]) SYMBOL_VISIBILITY="-fvisibility=hidden"], AC_MSG_RESULT([no])) -- 1.8.0 From 246tnt at gmail.com Sat Dec 8 17:21:27 2012 From: 246tnt at gmail.com (Sylvain Munaut) Date: Sat, 8 Dec 2012 18:21:27 +0100 Subject: [PATCH 0/3] libosmo-crypt-a53 autotools cleanup In-Reply-To: <1354831772-26187-1-git-send-email-alexander.huemer@xx.vu> References: <1354831772-26187-1-git-send-email-alexander.huemer@xx.vu> Message-ID: > This a series of 3 patches for libosmo-crypt-a53, branch master. > Former HEAD was 3de78cd69c0594b0903e6cfffab7920c69e2d478. > The patches clean up the autotools configuration. > The library itself is not changed[1]. > Fell free to merge the patches if they seem useful. Applied the batch, thanks. Cheers, Sylvain From raymond.m.chiu at gmail.com Mon Dec 10 03:27:30 2012 From: raymond.m.chiu at gmail.com (Raymond Chiu) Date: Sun, 9 Dec 2012 21:27:30 -0600 Subject: GANC Message-ID: <000601cdd686$49d770b0$dd865210$@gmail.com> I was Googling open source GANC and came across you web page: http://openbsc.osmocom.org/trac/wiki/osmo-ganc I am interested in learning how to program handsets to work with a GANC controller. Because I am new at this, I am not sure if it is possible to add this functionality to an existing platform and would like to learn more about existing implementations. Is there a good resource (code examples) to look view? Thank you. Raymond SMS: (703)828-7168 raymond.m.chiu. at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From t-openbsc at tobias.org Thu Dec 13 14:39:38 2012 From: t-openbsc at tobias.org (Tobias Engel) Date: Thu, 13 Dec 2012 15:39:38 +0100 Subject: Anybody else getting openbsc segfaults on IMSI Detach? Message-ID: <50C9E8AA.1040903@tobias.org> Hi, I pulled a newer openbsc version today for the first time in several months. Now, when a phone sends an IMSI Detach, osmo-nitb segfaults. The reason seems to be: osmo_msc.c:msc_compl_l3 gets called from gsm0408_rcvmsg, which in turn calls gsm0408_dispatch which at some point ends up in gsm48_rx_mm_imsi_detach_ind, which calls msc_release_connection, which calls gsm0808_clear, which sets conn->bts = NULL. Now, back in msc_compl_l3, trans_has_conn is called, which tries to dereference conn->bts->network, which causes the segfault. It might have been introduced with Holger's patch "msc: Attempt to release the lchan immediately on IMSI Detach" (153b13b0), but that was already in July... -Tobias From holger at freyther.de Thu Dec 13 16:37:53 2012 From: holger at freyther.de (Holger Hans Peter Freyther) Date: Thu, 13 Dec 2012 17:37:53 +0100 Subject: Anybody else getting openbsc segfaults on IMSI Detach? In-Reply-To: <50C9E8AA.1040903@tobias.org> References: <50C9E8AA.1040903@tobias.org> Message-ID: <20121213163753.GH8051@xiaoyu.lan> On Thu, Dec 13, 2012 at 03:39:38PM +0100, Tobias Engel wrote: > Now, back in msc_compl_l3, trans_has_conn is called, which tries to > dereference conn->bts->network, which causes the segfault. trans_has_conn is recent (and introduced by me). It was introduced here[1] but the code was accessing conn->bts before as well. I will check with the FakeBTS but I am somehow stuck in paperwork right now. :} holger [1] 70ae5d3000edd12aee38497a6f541595a8c7dee8 From t-openbsc at tobias.org Thu Dec 13 21:14:27 2012 From: t-openbsc at tobias.org (Tobias Engel) Date: Thu, 13 Dec 2012 22:14:27 +0100 Subject: Anybody else getting openbsc segfaults on IMSI Detach? In-Reply-To: <20121213163753.GH8051@xiaoyu.lan> References: <50C9E8AA.1040903@tobias.org> <20121213163753.GH8051@xiaoyu.lan> Message-ID: <50CA4533.1060800@tobias.org> On 13.12.12 17:37, Holger Hans Peter Freyther wrote: > On Thu, Dec 13, 2012 at 03:39:38PM +0100, Tobias Engel wrote: > >> Now, back in msc_compl_l3, trans_has_conn is called, which tries to >> dereference conn->bts->network, which causes the segfault. > > trans_has_conn is recent (and introduced by me). It was introduced > here[1] but the code was accessing conn->bts before as well. It was, but not in msc_compl_l3. It was/is also accessed in msc_release_connection, but before calling gsm0808_clear, so that is not a problem. -Tobias From holger at freyther.de Fri Dec 14 13:05:47 2012 From: holger at freyther.de (Holger Hans Peter Freyther) Date: Fri, 14 Dec 2012 14:05:47 +0100 Subject: Anybody else getting openbsc segfaults on IMSI Detach? In-Reply-To: <50CA4533.1060800@tobias.org> References: <50C9E8AA.1040903@tobias.org> <20121213163753.GH8051@xiaoyu.lan> <50CA4533.1060800@tobias.org> Message-ID: <20121214130547.GG22131@xiaoyu.lan> On Thu, Dec 13, 2012 at 10:14:27PM +0100, Tobias Engel wrote: > It was, but not in msc_compl_l3. It was/is also accessed in > msc_release_connection, but before calling gsm0808_clear, so that is not > a problem. Sorry, I didn't read it carefully enough. I prepared a very simple testcase and it is crashing the the NITB. I will apply a patch like the one below and the rule would be that msc_release_connection may only be called from a timer or from the trans_free command. The test case is attached to this email. diff --git a/openbsc/src/libmsc/gsm_04_08.c b/openbsc/src/libmsc/gsm_04_08.c index 9816174..fd482e0 100644 --- a/openbsc/src/libmsc/gsm_04_08.c +++ b/openbsc/src/libmsc/gsm_04_08.c @@ -965,7 +965,6 @@ static int gsm48_rx_mm_imsi_detach_ind(struct gsm_subscriber_connection *co * imagine an IMSI DETACH happening during an active call! */ release_anchor(conn); - msc_release_connection(conn); return 0; } -------------- next part -------------- " (C) 2012 by Holger Hans Peter Freyther All Rights Reserved This program is free software: you can redistribute it and/or modify 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 (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 GNU Affero General Public License for more details. You should have received a copy of the GNU Affero General Public License along with this program. If not, see . " PackageLoader fileInPackage: #FakeBTS. FakeBTS.OpenBSCTest subclass: IMSIDetach [ startTest [ "1. Connect to the BTS" self createAndConnectBTS: '1801/0/0'. self testIMSIDetach. ] testIMSIDetach [ | lchan detach tmsi | tmsi := self allocateTmsi: '901010000001111'. "2. Get a LCHAN" lchan := self requireAnyChannel. "3. Send a IMSI Detach" detach := GSM48IMSIDetachInd new. detach mi tmsi: tmsi. lchan sendGSM: detach toMessage. "Wait for the channel to be released.." [ | msg | "Read all messages until the end on SAPI=0. Ignore SAPI=3" "If we send another SAPI=3 Release Indication we get a double RF Channel Release from the NITB." [ msg := GSM48MSG decode: lchan nextSapi0Msg readStream. (msg isKindOf: GSM48RRChannelRelease) ifTrue: [lchan releaseAllSapis. ^true] ] on: Exception do: [Transcript nextPutAll: 'GSM decoding error'; nl.]. ] repeat. ] ] Eval [ | test | test := IMSIDetach new startTest; stopBts; yourself. ] From holger at freyther.de Sun Dec 16 16:43:34 2012 From: holger at freyther.de (Holger Hans Peter Freyther) Date: Sun, 16 Dec 2012 17:43:34 +0100 Subject: Please review and test zecke/channel-release Message-ID: <20121216164334.GM30319@xiaoyu.lan> Hi, I have rebased, extended and fixed the channel assignment and release. It brings us closer to the GSM 04.08 specification but there are still sime minor violations for the abnormal handling. I have tested (using the FakeBTS) a phone not acting on the SACCH deactivate/RF Channel Release and the signalling link will be released (T3109). I have a manual SMS submit test and I can make the nanoBTS crash easily. I have rebased through each individual change and couldn't reproduce the crash. I think it is either something in the RF setup (the modem bank being too close to the BTS), the older modem firmware, etc. Anyway, please review and test the branch. I plan to merge it by Wednesday. thanks holger From jluebbe at debian.org Tue Dec 25 18:09:37 2012 From: jluebbe at debian.org (Jan Luebbe) Date: Tue, 25 Dec 2012 19:09:37 +0100 Subject: [PATCH] gsm_subscriber: change subscr_bsc_active_subscriber to plural Message-ID: <1356458977-4707-1-git-send-email-jluebbe@debian.org> This was requested by Holger Freyther . --- openbsc/src/libbsc/gsm_subscriber_base.c | 10 +++++----- openbsc/src/libmsc/gsm_subscriber.c | 10 +++++----- 2 files changed, 10 insertions(+), 10 deletions(-) diff --git a/openbsc/src/libbsc/gsm_subscriber_base.c b/openbsc/src/libbsc/gsm_subscriber_base.c index 11afb35..747a699 100644 --- a/openbsc/src/libbsc/gsm_subscriber_base.c +++ b/openbsc/src/libbsc/gsm_subscriber_base.c @@ -35,7 +35,7 @@ LLIST_HEAD(active_subscribers); void *tall_subscr_ctx; /* for the gsm_subscriber.c */ -struct llist_head *subscr_bsc_active_subscriber(void) +struct llist_head *subscr_bsc_active_subscribers(void) { return &active_subscribers; } @@ -95,7 +95,7 @@ struct gsm_subscriber *subscr_get_or_create(struct gsm_network *net, { struct gsm_subscriber *subscr; - llist_for_each_entry(subscr, subscr_bsc_active_subscriber(), entry) { + llist_for_each_entry(subscr, subscr_bsc_active_subscribers(), entry) { if (strcmp(subscr->imsi, imsi) == 0 && subscr->net == net) return subscr_get(subscr); } @@ -113,7 +113,7 @@ struct gsm_subscriber *subscr_active_by_tmsi(struct gsm_network *net, uint32_t t { struct gsm_subscriber *subscr; - llist_for_each_entry(subscr, subscr_bsc_active_subscriber(), entry) { + llist_for_each_entry(subscr, subscr_bsc_active_subscribers(), entry) { if (subscr->tmsi == tmsi && subscr->net == net) return subscr_get(subscr); } @@ -125,7 +125,7 @@ struct gsm_subscriber *subscr_active_by_imsi(struct gsm_network *net, const char { struct gsm_subscriber *subscr; - llist_for_each_entry(subscr, subscr_bsc_active_subscriber(), entry) { + llist_for_each_entry(subscr, subscr_bsc_active_subscribers(), entry) { if (strcmp(subscr->imsi, imsi) == 0 && subscr->net == net) return subscr_get(subscr); } @@ -138,7 +138,7 @@ int subscr_purge_inactive(struct gsm_network *net) struct gsm_subscriber *subscr, *tmp; int purged = 0; - llist_for_each_entry_safe(subscr, tmp, subscr_bsc_active_subscriber(), entry) { + llist_for_each_entry_safe(subscr, tmp, subscr_bsc_active_subscribers(), entry) { if (subscr->net == net && subscr->use_count <= 0) { subscr_free(subscr); purged += 1; diff --git a/openbsc/src/libmsc/gsm_subscriber.c b/openbsc/src/libmsc/gsm_subscriber.c index f9eebc8..0889400 100644 --- a/openbsc/src/libmsc/gsm_subscriber.c +++ b/openbsc/src/libmsc/gsm_subscriber.c @@ -39,7 +39,7 @@ void *tall_sub_req_ctx; -extern struct llist_head *subscr_bsc_active_subscriber(void); +extern struct llist_head *subscr_bsc_active_subscribers(void); int gsm48_secure_channel(struct gsm_subscriber_connection *conn, int key_seq, gsm_cbfn *cb, void *cb_data); @@ -272,7 +272,7 @@ struct gsm_subscriber *subscr_get_by_tmsi(struct gsm_network *net, struct gsm_subscriber *subscr; /* we might have a record in memory already */ - llist_for_each_entry(subscr, subscr_bsc_active_subscriber(), entry) { + llist_for_each_entry(subscr, subscr_bsc_active_subscribers(), entry) { if (tmsi == subscr->tmsi) return subscr_get(subscr); } @@ -286,7 +286,7 @@ struct gsm_subscriber *subscr_get_by_imsi(struct gsm_network *net, { struct gsm_subscriber *subscr; - llist_for_each_entry(subscr, subscr_bsc_active_subscriber(), entry) { + llist_for_each_entry(subscr, subscr_bsc_active_subscribers(), entry) { if (strcmp(subscr->imsi, imsi) == 0) return subscr_get(subscr); } @@ -299,7 +299,7 @@ struct gsm_subscriber *subscr_get_by_extension(struct gsm_network *net, { struct gsm_subscriber *subscr; - llist_for_each_entry(subscr, subscr_bsc_active_subscriber(), entry) { + llist_for_each_entry(subscr, subscr_bsc_active_subscribers(), entry) { if (strcmp(subscr->extension, ext) == 0) return subscr_get(subscr); } @@ -314,7 +314,7 @@ struct gsm_subscriber *subscr_get_by_id(struct gsm_network *net, char buf[32]; sprintf(buf, "%llu", id); - llist_for_each_entry(subscr, subscr_bsc_active_subscriber(), entry) { + llist_for_each_entry(subscr, subscr_bsc_active_subscribers(), entry) { if (subscr->id == id) return subscr_get(subscr); } -- 1.7.10.4 From jluebbe at debian.org Thu Dec 27 21:41:13 2012 From: jluebbe at debian.org (Jan Luebbe) Date: Thu, 27 Dec 2012 22:41:13 +0100 Subject: [PATCH] libmsc: vty: Channel Requests statistics are already printed by openbsc_vty_print_statistics Message-ID: <1356644473-31253-1-git-send-email-jluebbe@debian.org> We don't need the same line two times. --- openbsc/src/libmsc/vty_interface_layer3.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/openbsc/src/libmsc/vty_interface_layer3.c b/openbsc/src/libmsc/vty_interface_layer3.c index eeeb51f..2b70cad 100644 --- a/openbsc/src/libmsc/vty_interface_layer3.c +++ b/openbsc/src/libmsc/vty_interface_layer3.c @@ -728,9 +728,6 @@ DEFUN(show_stats, struct gsm_network *net = gsmnet_from_vty(vty); openbsc_vty_print_statistics(vty, net); - vty_out(vty, "Channel Requests : %lu total, %lu no channel%s", - osmo_counter_get(net->stats.chreq.total), - osmo_counter_get(net->stats.chreq.no_channel), VTY_NEWLINE); vty_out(vty, "Location Update : %lu attach, %lu normal, %lu periodic%s", osmo_counter_get(net->stats.loc_upd_type.attach), osmo_counter_get(net->stats.loc_upd_type.normal), -- 1.7.10.4 From jluebbe at lasnet.de Thu Dec 27 22:32:37 2012 From: jluebbe at lasnet.de (Jan Luebbe) Date: Thu, 27 Dec 2012 23:32:37 +0100 Subject: [PATCH] libmsc: vty: Channel Requests statistics are already printed by openbsc_vty_print_statistics Message-ID: <1356647557-4032-1-git-send-email-jluebbe@lasnet.de> From: Jan Luebbe We don't need the same line two times. --- openbsc/src/libmsc/vty_interface_layer3.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/openbsc/src/libmsc/vty_interface_layer3.c b/openbsc/src/libmsc/vty_interface_layer3.c index eeeb51f..2b70cad 100644 --- a/openbsc/src/libmsc/vty_interface_layer3.c +++ b/openbsc/src/libmsc/vty_interface_layer3.c @@ -728,9 +728,6 @@ DEFUN(show_stats, struct gsm_network *net = gsmnet_from_vty(vty); openbsc_vty_print_statistics(vty, net); - vty_out(vty, "Channel Requests : %lu total, %lu no channel%s", - osmo_counter_get(net->stats.chreq.total), - osmo_counter_get(net->stats.chreq.no_channel), VTY_NEWLINE); vty_out(vty, "Location Update : %lu attach, %lu normal, %lu periodic%s", osmo_counter_get(net->stats.loc_upd_type.attach), osmo_counter_get(net->stats.loc_upd_type.normal), -- 1.7.10.4 From laforge at gnumonks.org Mon Dec 31 17:37:36 2012 From: laforge at gnumonks.org (Harald Welte) Date: Mon, 31 Dec 2012 18:37:36 +0100 Subject: OsmoDevCon 2013 brainstorming Message-ID: <20121231173736.GD21955@prithivi.gnumonks.org> Hi all, as the year 2012 has already ended or will soon end depending on your timezone, it might be a good occasion to start thinking of an OsmoDevCon 2013. I personally percevied OsmoDevCon 2012 as a big success, and it was fun to bring everyone together. Generally, I prefer to keep the spirit of an invitation-only developer+contributor-only event of those involved in Osmocom. At the same time, I would consider it a good idea to add a one day user-conference to the schedule, where we try to get interested users up to speed with the various projects, possibly including some workshops and the like. So schedule-wise, I would suggest something like: * one day user conference * two day developer/contributor event * optionally: 1-2 "hacking days". The concept of "hacking days" has proven to be quite useful for the netfilter project in the past (Pablo and I can acknowledge to that fact). I'm not sure how many people would be able to spend even more days of their schedule, but even if it's a much smaller group it would still be useful, IMHO. I'd like you to 1) provide feedback on the ideas about the one-day user event and the hacking days 2) consider whether late march (like 2012) would be a good schedule again 3) what we can improve from the last event In terms of improvements, I so far have noted down: * larger venue needs to be found * complaints about the venue not having sufficient heating Venue-wise, I would again suggest to hold it in Berlin, as it's reasonbly well connected, has lots of low-cost flights to it, accomodation is not too expensive and holger/me/sysmocom can take care of local organization related activities. Hoewver, if somebody has a strong opinion against berlin _and_ is willing to organize it, I'm not completely against another venue. Regards and happy new year, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)