From lynxis at fe80.eu Tue Oct 16 01:25:15 2018 From: lynxis at fe80.eu (Alexander Couzens) Date: Tue, 16 Oct 2018 03:25:15 +0200 Subject: [osmocom-event-orga] 35c3 preparation meeting: Sunday 16:00 @afra Message-ID: <20181016032322.73c736d2@lazus.yip> Hi, the congress is less than 100 days ahead. Let's start preparing the gsm/umts network at AfRA on Sunday, 21. Oct, 16:00 https://afra-berlin.de/ todos: * create a todo list ;) * send mail to NOC & POC Here is a short list of the last year's pads. I think they can be used as good reference to the last year. https://cccb.pads.ccc.de/84 [34c3 planning] https://cccb.pads.ccc.de/85 [34c3 blog post] https://cccb.pads.ccc.de/86 [after 34c3, contains planing for this year] All pads are password protected, if you don't remember the pw, send me an email, because this list has a public accessable archive. Best, lynxis PS: We have received 35c3 tokens to buy tickets. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From lynxis at fe80.eu Fri Oct 19 20:53:49 2018 From: lynxis at fe80.eu (Alexander Couzens) Date: Fri, 19 Oct 2018 22:53:49 +0200 Subject: [osmocom-event-orga] 35c3: LOC asks what do we need? Message-ID: <20181019225349.78f6fc47@lazus.yip> hi osmocom's, we got a mail from the LOC (Logisitic Openration Center). They ask us: - do we need any space from the LOC? - do we need any stuff? expentable materials? Gaffa/Tape, Zipties? - do we need any tables? It would be nice if we can answer their mail after Sunday. I'm not yet sure how we get the GSM Room (again)? Best, lynxis --- german mail --- Liebe Teams, OCs und Infrastruktur Leute, liebes Team GSM, es ist wieder so weit. Die ersten Mumbles wurden bereits abgehalten, die Spezialexperten aus der Kryokammer haben die Orga fachgerecht aufgetaut und die Kongressplannung nimmt somit langsam Fahrt auf. Wir vom Logistic Operation Center sind auch schon flei?ig am Planen und brauchen jetzt eure Unterst?tzung. Um Hallen- und Transportlogistik zu planen brauchen wir von euch Angaben zu Platz- und Materialbedarf. Im gro?en Ganzen hat sich der Modus des letzten Jahres bew?hrt und wird vom Ablauf dieses Jahr auch wieder so ?hnlich stattfinden, aber es gibt eine extrem wichtige ?nderung dieses Jahr:?Es wird w?hrend der Veranstaltung (26.12 bis 30.12)?KEIN?Lager in Halle 4 geben.?Halle 4 ist diesmal Teil der Veranstaltung und muss deshalb w?hrend des Veranstaltungszeitraumes?brandlastfrei?sein. Es ist nur sehr bedingt m?glich, w?hrenddessen Dinge in Halle 4 zu tun, es wird dort keinen Lagerplatz f?r leere Flightcases, Kunst, Baumaterial, ?briggebliebenes ? geben. Sprecht uns unbedingt an, falls ihr Lagerplatz ben?tigt, an den ihr w?hrend der Veranstaltung heran m?sst. Alles andere werden wir am 26. aus den Hallen und erst am 30. wieder zur?ck r?umen. Wir bitten euch das bei eurer Planung zu ber?cksichtigen und ?berfl?ssiges Material zu Hause zu lassen. Auch die Werkst?tten m?ssen w?hrend der Veranstaltung aus der Halle ger?umt werden. Voraussichtlich gibt es aber eine kleine Werkstatt in einem Hallennebenraum, die vor und auch w?hrend der Verstalltung genutzt werden kann. Wir brauchen eure Infos und Planungen: * Plant ihr, gro?e Dinge mitzubringen? * Plant ihr, Dinge mitzubringen, die schwer zu verladen/bewegen sind? * Braucht ihr LOCkedspace? Wenn ja wie viel und von wann bis wann? * Wann werden eure Sachen wieder abgeholt? * Plant ihr gro?e Mengen (Sonder?) M?ll zu erzeugen? * Braucht ihr Platz in der Halle, um Dinge zu bauen/vorzubereiten? * Braucht ihr Werkst?tten? Meldet euch bitte sp?testens bis zum 31. Oktober bei uns indem ihr einfach auf diese E-Mail antwortet, damit wir euch verpeilungsfrei in unsere Planung mit einbeziehen k?nnen :) N?chste Baustelle: Braucht ihr Verbrauchsmaterial? * Gaffa, B?romaterialen, Holz, Baumaterial, Molton, Messeteppich, Kabelbinder, etc. * Wenn ja, welches? Macht bitte Angaben zu Fabrikat und/oder Gr??e. Hint: ?Schrauben? ist keine Bestellung (?Tackernadeln? erfahrungsgem?? auch nicht) * Gaffa?!? * Weltfrieden? * Hier k?nnte Ihre Werbung stehen! Wir bitten euch euren Bedarf an Verbrauchsmaterial direkt unter [1] https://orga.cccv.de/doku/35c3/bestellungen?einzutragen. F?r Fragen oder spezielle W?nsche stehen wir euch unter?35c3 at c3loc.de zur Verf?gung. F?r den Tischbedarf wendet euch bitte wie letztes Jahr an die entsprechende Wiki Seite:?[2] https://orga.cccv.de/doku/35c3/raeume/tischplanung. F?r Strombedarf meldet euch bitte direkt bei Fengel unter:?35c3 at c3power.de Vielen Dank f?r Ihre gesch?tzte Aufmerksamkeit, Euer LOC P.S: Niemand hat die Absicht einen Kongress zu planen! -- Alexander Couzens mail: lynxis at fe80.eu jabber: lynxis at fe80.eu mobile: +4915123277221 gpg: 390D CF78 8BF9 AA50 4F8F F1E2 C29E 9DA6 A0DF 8604 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From peter at stuge.se Sat Oct 20 11:32:08 2018 From: peter at stuge.se (Peter Stuge) Date: Sat, 20 Oct 2018 11:32:08 +0000 Subject: [osmocom-event-orga] 35c3: LOC asks what do we need? In-Reply-To: <20181019225349.78f6fc47@lazus.yip> References: <20181019225349.78f6fc47@lazus.yip> Message-ID: <20181020113208.25737.qmail@stuge.se> Alexander Couzens wrote: > we got a mail from the LOC (Logisitic Openration Center). Thanks a lot for forwarding their mail! > They ask us: > > - do we need any space from the LOC? > - do we need any stuff? expentable materials? Gaffa/Tape, Zipties? > - do we need any tables? They also inform us that nothing can be stored in the LOC hall (4) during the event, because the hall will be used by participants, ie. also part of the event, and must be clear of anything flammable. LOC will have to play Towers of Hanoi with any material in storage, so ask that we bring nothing more to Leipzig than is actually needed for deployment. AFAIK we haven't relied on LOC for storage during the event, so I don't think we have a problem. I think we should try to arrange transport of equipment from Berlin to Leipzig along with all the other stuff going that route, so we could ask LOC by when we would need to deliver material to them in Berlin, for it to arrive in Leipzig by the time we start setup. It seems our team will be on site a bit earlier this year than last, which means we may also need to deliver equipment to LOC in Berlin earlier, for it to be on site by the time we arrive. > I'm not yet sure how we get the GSM Room (again)? I guess that it has already been reserved for us, but I'll verify that until Sunday. I'll probably come to AfrA a bit late, around 18:00 or so. See you then! //Peter From peter at stuge.se Sat Oct 20 12:10:24 2018 From: peter at stuge.se (Peter Stuge) Date: Sat, 20 Oct 2018 12:10:24 +0000 Subject: [osmocom-event-orga] SIM artwork In-Reply-To: <20180118140429.GA8458@coil> References: <1a208ae4-987d-378e-fefc-3684e18d916d@nerdkeller.org> <20180118140429.GA8458@coil> Message-ID: <20181020121024.26567.qmail@stuge.se> I think we should continue to assume that license(s) will work out and not wait for confirmation on that before moving ahead with preparations. K?vin Redon wrote: > SIM card corresponding to the congress design, but I am not sure this > is required for the next congress since a lot of white SIM card are > remaining from the last congress White cards are timeless and are really great to have as backup for a long time to come! But I think it's valuable to have cards with artwork for each C3. We can get SIM artwork from the graphic designer if we want, and I think it's good if we have one thing less to do ourselves, but we have to provide a deadline and a template, so: What is the deadline for ordering printed SIMs? Is there a template from the manufacturer? //Peter From 246tnt at gmail.com Sat Oct 20 12:13:19 2018 From: 246tnt at gmail.com (Sylvain Munaut) Date: Sat, 20 Oct 2018 14:13:19 +0200 Subject: [osmocom-event-orga] SIM artwork In-Reply-To: <20181020121024.26567.qmail@stuge.se> References: <1a208ae4-987d-378e-fefc-3684e18d916d@nerdkeller.org> <20180118140429.GA8458@coil> <20181020121024.26567.qmail@stuge.se> Message-ID: On Sat, Oct 20, 2018, 14:10 Peter Stuge wrote: > I think we should continue to assume that license(s) will work out and > not wait for confirmation on that before moving ahead with preparations. > even in the unlikely event it doesn't, they would still be programmable sim card with a collector design on them and I am pretty sure we would still sell them . Cheers, Sylvain -------------- next part -------------- An HTML attachment was scrubbed... URL: From ml at mail.tsaitgaist.info Sat Oct 20 21:58:18 2018 From: ml at mail.tsaitgaist.info (=?iso-8859-1?Q?K=E9vin?= Redon) Date: Sat, 20 Oct 2018 23:58:18 +0200 Subject: [osmocom-event-orga] SIM artwork In-Reply-To: <20181020121024.26567.qmail@stuge.se> References: <1a208ae4-987d-378e-fefc-3684e18d916d@nerdkeller.org> <20180118140429.GA8458@coil> <20181020121024.26567.qmail@stuge.se> Message-ID: <20181020215818.GB20959@coil> I'm happy to do the design (it does not take long). Does anyone have the contact details of the designer? If he wants to do it himself I can still provide the template and constraints. Do we know how many: - we sold - are left over - we want to produce On Sat, Oct 20, 2018 at 12:10:24PM +0000, Peter Stuge wrote: > I think we should continue to assume that license(s) will work out and > not wait for confirmation on that before moving ahead with preparations. > > > K?vin Redon wrote: > > SIM card corresponding to the congress design, but I am not sure this > > is required for the next congress since a lot of white SIM card are > > remaining from the last congress > > White cards are timeless and are really great to have as backup for a > long time to come! > > But I think it's valuable to have cards with artwork for each C3. > > We can get SIM artwork from the graphic designer if we want, and > I think it's good if we have one thing less to do ourselves, but > we have to provide a deadline and a template, so: > > What is the deadline for ordering printed SIMs? > > Is there a template from the manufacturer? > > > //Peter From ml at mail.tsaitgaist.info Sun Oct 21 07:14:51 2018 From: ml at mail.tsaitgaist.info (=?iso-8859-1?Q?K=E9vin?= Redon) Date: Sun, 21 Oct 2018 09:14:51 +0200 Subject: [osmocom-event-orga] 35c3 preparation meeting: Sunday 16:00 @afra In-Reply-To: <20181016032322.73c736d2@lazus.yip> References: <20181016032322.73c736d2@lazus.yip> Message-ID: <20181021071451.GA28451@coil> I won't be able to join the meeting, but please share the 35c3 at the end so I can check what has been discussed. On Tue, Oct 16, 2018 at 03:25:15AM +0200, Alexander Couzens wrote: > Hi, > > the congress is less than 100 days ahead. > Let's start preparing the gsm/umts network at > > AfRA on Sunday, 21. Oct, 16:00 > https://afra-berlin.de/ > > todos: > * create a todo list ;) > * send mail to NOC & POC > > Here is a short list of the last year's pads. I think they can be used > as good reference to the last year. > > https://cccb.pads.ccc.de/84 [34c3 planning] > https://cccb.pads.ccc.de/85 [34c3 blog post] > https://cccb.pads.ccc.de/86 [after 34c3, contains planing for this year] > > All pads are password protected, if you don't remember the pw, send me > an email, because this list has a public accessable archive. > > Best, > lynxis > > PS: We have received 35c3 tokens to buy tickets. From nhofmeyr at sysmocom.de Sun Oct 21 13:49:25 2018 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Sun, 21 Oct 2018 15:49:25 +0200 Subject: [osmocom-event-orga] 35c3 preparation meeting: Sunday 16:00 @afra In-Reply-To: <20181016032322.73c736d2@lazus.yip> References: <20181016032322.73c736d2@lazus.yip> Message-ID: <20181021134924.GA21100@my.box> We're almost on our way, will be arriving late, but we will come! ~N + stsp From nhofmeyr at sysmocom.de Sat Oct 27 17:52:35 2018 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Sat, 27 Oct 2018 19:52:35 +0200 Subject: [osmocom-event-orga] 35c3: LOC asks what do we need? In-Reply-To: <20181020113208.25737.qmail@stuge.se> References: <20181019225349.78f6fc47@lazus.yip> <20181020113208.25737.qmail@stuge.se> Message-ID: <20181027175235.GA14737@my.box> It would be great if all of us can come to #c3-gsm on hackint.org and read/write the roadmap pad (9) as often as possible, so that we don't end up with several lossy communication streams... thanks! > - do we need any tables? We had a meeting last sunday and made some conclusions about tables. IIUC someone already communicated the amount of tables needed ... please come to #c3-gsm on hackint.org and ask ... bibor probably. I need a place to put a camper car, is that related to LOC? > It seems our team will be on site a bit earlier this year than last, On our roadmap pad, I invite everyone to note the dates of arrival (see "### Who's coming when?" on pad 9) https://gsm.pads.ccc.de/9 <-- General roadmap pad https://gsm.pads.ccc.de/8 <-- for the meeting last sunday Password same as last year. Ping me on irc if you forgot. I see this problem: already now we have information spread across pad 8 and pad 9, I think we should completely dissolve pad 8 and put all the interesting info in the roadmap pad (9) to avoid fragmentation. Yes? > which means we may also need to deliver equipment to LOC in Berlin > earlier, for it to be on site by the time we arrive. Added notes to pad 9 "### Transportation" ~N -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From nhofmeyr at sysmocom.de Sat Oct 27 18:20:46 2018 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Sat, 27 Oct 2018 20:20:46 +0200 Subject: [osmocom-event-orga] update from POC Message-ID: <20181027182046.GB14737@my.box> I added some info to pad 9 about the POC; some of which is: * POC offers to locate the prod core in a VM on their machine * a POC core machine is set up and running already now, before congress * neels will get VPN access (we can test against that) * POC now use several Yate instances, one per realm (DECT, SIP, GSM,...) * we use osmo-sip-connector to hook up POC suggests: * We can ask Lime to send us the LimeSDR devices used on EFR camp (ask POC, via neels) to use them as GSM BTS * Idea: share one secure network segment with the POC See pad 9 for more details. Any opinions? ~N -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From nhofmeyr at sysmocom.de Sat Oct 27 18:24:25 2018 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Sat, 27 Oct 2018 20:24:25 +0200 Subject: [osmocom-event-orga] initial MSISDN Message-ID: <20181027182425.GC14737@my.box> How do we designate the initial MSISDN in the HLR, "before tokens"? I think we had a 5digit number starting with 9... POC would like to officially allocate a specific number segment to that. Though I'm not sure whether it matters much, we might as well do that. How did it work in previous years? Does some script allocate MSISDN? ~N -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From 246tnt at gmail.com Sat Oct 27 18:34:07 2018 From: 246tnt at gmail.com (Sylvain Munaut) Date: Sat, 27 Oct 2018 20:34:07 +0200 Subject: [osmocom-event-orga] initial MSISDN In-Reply-To: <20181027182425.GC14737@my.box> References: <20181027182425.GC14737@my.box> Message-ID: Hi, > Though I'm not sure whether it matters much, we might as well do that. > How did it work in previous years? Does some script allocate MSISDN? AFAIR Yes, the script importing the SIM data from the csv to the HLR also made up an MSISDN. Then the POC routed all those with that 'prefix' to us and we dispatched internally. Cheers, Sylvain From peter at stuge.se Sat Oct 27 22:50:07 2018 From: peter at stuge.se (Peter Stuge) Date: Sat, 27 Oct 2018 22:50:07 +0000 Subject: [osmocom-event-orga] update from POC In-Reply-To: <20181027182046.GB14737@my.box> References: <20181027182046.GB14737@my.box> Message-ID: <20181027225007.7901.qmail@stuge.se> Thanks for the update! Neels Hofmeyr wrote: > * POC offers to locate the prod core in a VM on their machine NOC has also offered a VM for many years. Can do isn't always == should do. The problem with the cloud is that there is no cloud, only other peoples' computers. I trust that both NOC and POC run VMs like a boss, but I quite like having our own server, if only for the ability to do stuff like sticking a 3G dongle into it and immediately being able to reach it from hotel and wherever, without depending on support from another crew (ie. delay). This was a somehow critical feature at least once in the past. > * a POC core machine is set up and running already now, before congress > * neels will get VPN access (we can test against that) Cool! It's a great idea to set the server up in ASAP! :) I'll start doing that and ping when it is online (in CCCB). > POC suggests: > * We can ask Lime to send us the LimeSDR devices used on EFR camp > (ask POC, via neels) to use them as GSM BTS I've heard mixed reports about EMF camp GSM. And at OsmoCon it sounded like the Lime stack is quite thick - does it actually work well enough to be worth the complexity? > * Idea: share one secure network segment with the POC The "worst" part is probably that NOC would then have to decommission the GSM L3 VLAN. :) I don't feel strongly either way. The server has sometimes also been directly on their L3 VLAN, It's trivial to arrange for that again if we want. //Peter From peter at stuge.se Sat Oct 27 22:54:38 2018 From: peter at stuge.se (Peter Stuge) Date: Sat, 27 Oct 2018 22:54:38 +0000 Subject: [osmocom-event-orga] initial MSISDN In-Reply-To: <20181027182425.GC14737@my.box> References: <20181027182425.GC14737@my.box> Message-ID: <20181027225438.8030.qmail@stuge.se> Neels Hofmeyr wrote: > How do we designate the initial MSISDN in the HLR, "before tokens"? Different. As Sylvain said they are set once on initial import, but then they are usually all reset at start of each event setup. I remember doing this together with Stephan last year, as part of our merging exercise. > POC would like to officially allocate a specific number segment to that. Cool. Can they simply pick a prefix that suits them and let us work with that? Ie. allow arbitrary length (well, at least 6, maybe 7)? //Peter From peter at stuge.se Sat Oct 27 22:55:47 2018 From: peter at stuge.se (Peter Stuge) Date: Sat, 27 Oct 2018 22:55:47 +0000 Subject: [osmocom-event-orga] 35c3: LOC asks what do we need? In-Reply-To: <20181027175235.GA14737@my.box> References: <20181019225349.78f6fc47@lazus.yip> <20181020113208.25737.qmail@stuge.se> <20181027175235.GA14737@my.box> Message-ID: <20181027225547.8079.qmail@stuge.se> Neels Hofmeyr wrote: > I need a place to put a camper car, is that related to LOC? Probably no. I'll dig around. //Peter From axilirator at gmail.com Sat Oct 27 23:08:58 2018 From: axilirator at gmail.com (Vadim Yanitskiy) Date: Sun, 28 Oct 2018 06:08:58 +0700 Subject: [osmocom-event-orga] update from POC In-Reply-To: <20181027182046.GB14737@my.box> References: <20181027182046.GB14737@my.box> Message-ID: Hi all, > POC suggests: > * We can ask Lime to send us the LimeSDR devices used on EFR camp > (ask POC, via neels) to use them as GSM BTS IMHO using LimeSDR is a bad idea - from my experience, it's extremely unstable with OsmoTRX, even in lab environment. I think even hackish CalypsoBTS (e.g. a Motorola C1XX) would work better than LimeSDR :P With best regards, Vadim Yanitskiy. From peter at stuge.se Sat Oct 27 23:42:08 2018 From: peter at stuge.se (Peter Stuge) Date: Sat, 27 Oct 2018 23:42:08 +0000 Subject: [osmocom-event-orga] 35c3: LOC asks what do we need? In-Reply-To: <20181027225547.8079.qmail@stuge.se> References: <20181019225349.78f6fc47@lazus.yip> <20181020113208.25737.qmail@stuge.se> <20181027175235.GA14737@my.box> <20181027225547.8079.qmail@stuge.se> Message-ID: <20181027234208.10432.qmail@stuge.se> Peter Stuge wrote: > Neels Hofmeyr wrote: > > I need a place to put a camper car, is that related to LOC? > > Probably no. I'll dig around. Definitely not LOC. Details are not yet clear, but there will eventually be tickets for visitors for the period 25.12-31.12 at: https://tickets.events.ccc.de/35c3camping/ //Peter From stsp at stsp.name Sun Oct 28 07:57:11 2018 From: stsp at stsp.name (Stefan Sperling) Date: Sun, 28 Oct 2018 08:57:11 +0100 Subject: [osmocom-event-orga] No time for 35c3 gsm after all Message-ID: <20181028075711.GE12047@ted.stsp.name> I am sorry about this, but I realised that I won't have time to help out with the GSM team after all. I have too many other voluntary commitments to meet, both in open source work I'm doing and in helping friends who need support in "real life". Running a GSM network at congress is a fun exercise but I can't commit to it at the expense of my other commitments. I took on one task during the kick-off meeting, which was to find 850-band BTS hardware in sysmocom's pool. I have already asked Harald about this. Unfortunately it looks like there won't be a lot of equipment that can do 850 band after all. The Nano3Gs used last year can apparently do it, but they only support 8 concurrent calls per BTS. There's some other similar Nano3G equipment (can't recall the name right now) which can support 16 voice calls. But these have never been tested, and it's unclear if they will work. Someone needs to try running these with the osmocom stack. I suppose Lynxis, Kevin and Neels should be able to get access to those devices. Cheers, and have fun! Stefan From nhofmeyr at sysmocom.de Mon Oct 29 12:51:06 2018 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Mon, 29 Oct 2018 13:51:06 +0100 Subject: [osmocom-event-orga] update from POC In-Reply-To: References: <20181027182046.GB14737@my.box> Message-ID: <20181029125106.GA4028@my.box> On Sun, Oct 28, 2018 at 06:08:58AM +0700, Vadim Yanitskiy wrote: > Hi all, > > > POC suggests: > > * We can ask Lime to send us the LimeSDR devices used on EFR camp > > (ask POC, via neels) to use them as GSM BTS > > IMHO using LimeSDR is a bad idea - from my experience, it's extremely > unstable with OsmoTRX, even in lab environment. I think even hackish > CalypsoBTS (e.g. a Motorola C1XX) would work better than LimeSDR :P For me, it would just be an idea to also try to hook up those in one or two places besides our stable BTSes... But my general feeling with all SDR solutions is "too flaky to be fun", so I won't push in that direction. ~N -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From axilirator at gmail.com Mon Oct 29 13:16:59 2018 From: axilirator at gmail.com (Vadim Yanitskiy) Date: Mon, 29 Oct 2018 20:16:59 +0700 Subject: [osmocom-event-orga] update from POC In-Reply-To: <20181029125106.GA4028@my.box> References: <20181027182046.GB14737@my.box> <20181029125106.GA4028@my.box> Message-ID: Hi, > But my general feeling with all SDR solutions is "too flaky to be fun", so I > won't push in that direction. Well, not all SDR solutions are that bad for running a GSM network. I am talking exactly about LimeSDR: either we are missing something in OsmoTRX (some dead bug in the lms implementation), or the firmware provided by Lime is not stable enough itself. Other devices, such as USRP (I personally prefer them) are working quite good, and widely used in some production networks. Anyway, the situation with freq. bands remains unknown. Let's hope we get more than one band in 850... With best regards, Vadim Yanitskiy. From laforge at gnumonks.org Tue Oct 30 07:34:28 2018 From: laforge at gnumonks.org (Harald Welte) Date: Tue, 30 Oct 2018 08:34:28 +0100 Subject: [osmocom-event-orga] No time for 35c3 gsm after all In-Reply-To: <20181028075711.GE12047@ted.stsp.name> References: <20181028075711.GE12047@ted.stsp.name> Message-ID: <20181030073428.GS31654@nataraja> On Sun, Oct 28, 2018 at 08:57:11AM +0100, Stefan Sperling wrote: > The Nano3Gs used last year can apparently do it, but they only support > 8 concurrent calls per BTS. There's some other similar Nano3G equipment > (can't recall the name right now) which can support 16 voice calls. nano3G-E16. Most importantly, they have (IIRC) 10 times more transmit power than the nano3G-S8. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From laforge at gnumonks.org Tue Oct 30 07:35:56 2018 From: laforge at gnumonks.org (Harald Welte) Date: Tue, 30 Oct 2018 08:35:56 +0100 Subject: [osmocom-event-orga] update from POC In-Reply-To: References: <20181027182046.GB14737@my.box> <20181029125106.GA4028@my.box> Message-ID: <20181030073556.GT31654@nataraja> On Mon, Oct 29, 2018 at 08:16:59PM +0700, Vadim Yanitskiy wrote: > Other devices, such as USRP (I personally prefer them) are working > quite good, and widely used in some production networks. yes, but always keep in mind it's not just the SDR, but you need proper clocking (GPS-DO won't work indoor), rx and tx band filtering, power amplifier, ... and the need to properly test and adjust the various gains before having built an actual BTS from a SDR. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From laforge at gnumonks.org Tue Oct 30 07:32:18 2018 From: laforge at gnumonks.org (Harald Welte) Date: Tue, 30 Oct 2018 08:32:18 +0100 Subject: [osmocom-event-orga] update from POC In-Reply-To: <20181027182046.GB14737@my.box> References: <20181027182046.GB14737@my.box> Message-ID: <20181030073218.GR31654@nataraja> Hi Neels, On Sat, Oct 27, 2018 at 08:20:46PM +0200, Neels Hofmeyr wrote: > POC suggests: > * We can ask Lime to send us the LimeSDR devices used on EFR camp (ask POC, via neels) > to use them as GSM BTS Not sure that's a great idea, considering that those have GPS disciplined oscillators, which are intended for outdoor usage. You'd need something that has an internal stable OCXO that's calibrated ahead of the event. But feel free to inquire for details. Also, I don't think anyone has yet reported on actual benchmarking on a RPi3 core in terms of using it with maximum load (14 half-rate AMR channels concurrently, ...) -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From nhofmeyr at sysmocom.de Tue Oct 30 15:29:41 2018 From: nhofmeyr at sysmocom.de (Neels Hofmeyr) Date: Tue, 30 Oct 2018 16:29:41 +0100 Subject: [osmocom-event-orga] BTS for 850 In-Reply-To: <20181028075711.GE12047@ted.stsp.name> References: <20181028075711.GE12047@ted.stsp.name> Message-ID: <20181030152941.GB14951@ass40.box> On Sun, Oct 28, 2018 at 08:57:11AM +0100, Stefan Sperling wrote: > Unfortunately it looks like there won't be a lot of equipment > that can do 850 band after all. I'm a bit worried that we won't actually have GSM equipment for the band we are allowed to run in... The fallback would be running only 3G... and try to get IuUP to work for voice? ~N -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From push at ninja-netz.de Tue Oct 30 16:14:24 2018 From: push at ninja-netz.de (Ulrich Kalloch) Date: Tue, 30 Oct 2018 17:14:24 +0100 Subject: [osmocom-event-orga] BTS for 850 In-Reply-To: <20181030152941.GB14951@ass40.box> References: <20181028075711.GE12047@ted.stsp.name> <20181030152941.GB14951@ass40.box> Message-ID: <8D3F1388-44BE-4EAE-8A97-F3932AF937B5@ninja-netz.de> Hmm than we must rename the Team. Maybe ... MFG Sokrates Am 30. Oktober 2018 16:29:41 MEZ, schrieb Neels Hofmeyr : >On Sun, Oct 28, 2018 at 08:57:11AM +0100, Stefan Sperling wrote: >> Unfortunately it looks like there won't be a lot of equipment >> that can do 850 band after all. > >I'm a bit worried that we won't actually have GSM equipment for the >band >we are allowed to run in... > >The fallback would be running only 3G... and try to get IuUP to work >for >voice? > >~N -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet. -------------- next part -------------- An HTML attachment was scrubbed... URL: From laforge at gnumonks.org Wed Oct 31 22:17:40 2018 From: laforge at gnumonks.org (Harald Welte) Date: Wed, 31 Oct 2018 23:17:40 +0100 Subject: [osmocom-event-orga] Nano3G-E16 Re: No time for 35c3 gsm after all In-Reply-To: <20181030073428.GS31654@nataraja> References: <20181028075711.GE12047@ted.stsp.name> <20181030073428.GS31654@nataraja> Message-ID: <20181031221740.GJ27112@nataraja> On Tue, Oct 30, 2018 at 08:34:28AM +0100, Harald Welte wrote: > On Sun, Oct 28, 2018 at 08:57:11AM +0100, Stefan Sperling wrote: > > > The Nano3Gs used last year can apparently do it, but they only support > > 8 concurrent calls per BTS. There's some other similar Nano3G equipment > > (can't recall the name right now) which can support 16 voice calls. > > nano3G-E16. Most importantly, they have (IIRC) 10 times more transmit power > than the nano3G-S8. I've quickly played with one of the units and no luck at all so far. It's completely quiet after obtaining a DHCP lease, and the existing DHCP-based exploit that we know for the nano3G-S8 didn't work. There are plenty of suspicious headers on the circuit board. One of them might give us a serial console, who knows. My opinion is that unless somebody with significant knowledge on femtocell hacking (Kevin?) has time to work on this, the nano3G-E16 are not going to in any shape where they can be used at an event, sorry. -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)