From lynxis at fe80.eu  Fri Aug  9 17:15:55 2019
From: lynxis at fe80.eu (Alexander Couzens)
Date: Fri, 9 Aug 2019 19:15:55 +0200
Subject: [osmocom-event-orga] Telefonica GSM/LTE frequency/arfcn
Message-ID: <20190809191555.6a2f66fd@lazus.yip>

Hi,

thanks to Telefonica, we can use the following GSM & LTE arfcn.
The paperwork with the BNetzA is not yet done, but we're working on it.

         Chaos Communication Camp
         Ziegeleipark Mildenberg, 16792 Mildenberg, Brandenburg
         vom 18.-27.08.2019


1800 MHz (max. 0,2 W)
        680 (1838,8/1743,8 MHz)
        683 (1839,4/1744,4 MHz)
        686 (1840,0/1745,0 MHz)
        689 (1840,6/1745,6 MHz)
        692 (1841,2/1746,2 MHz)
        695 (1841,8/1746,8 MHz)

2600 MHz (max. 2 W)
         10 MHz Bandbreite: 2660-2670/2540-2550 MHz


Best,
lynxis

-- 
Alexander Couzens

mail: lynxis at fe80.eu
jabber: lynxis at fe80.eu
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: <https://lists.osmocom.org/mailman/private/osmocom-event-orga/attachments/20190809/f167b4c7/attachment.bin>

From laforge at gnumonks.org  Fri Aug  9 17:56:37 2019
From: laforge at gnumonks.org (Harald Welte)
Date: Fri, 9 Aug 2019 19:56:37 +0200
Subject: [osmocom-event-orga] Telefonica GSM/LTE frequency/arfcn
In-Reply-To: <20190809191555.6a2f66fd@lazus.yip>
References: <20190809191555.6a2f66fd@lazus.yip>
Message-ID: <20190809175637.GW6081@nataraja>

Hi Lynxis,

On Fri, Aug 09, 2019 at 07:15:55PM +0200, Alexander Couzens wrote:
> thanks to Telefonica, we can use the following GSM & LTE arfcn.

congratulations for getting this done, and thanks to Telefonica!

> 2600 MHz (max. 2 W)
>          10 MHz Bandbreite: 2660-2670/2540-2550 MHz

Ok, I'll probably use that in chunks of 5MHz for my LTE expermental network,
resulting in the following two EARFCN:

EARFCN 3175: 2662.50 / 2542.50
EARFCN 3225: 2667.50 / 2547.50

FYI: In a 5MHz carrier, 25-50 Mbps raw aggregate throughput can be
achieved, depending on whether or not 2x2 MIMO is active or not.  The
eNodeB I want to deploy support it...

Worst case is 4 MBps (QPSK, no MIMO)

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)


From keith at rhizomatica.org  Mon Aug 12 08:46:17 2019
From: keith at rhizomatica.org (Keith)
Date: Mon, 12 Aug 2019 10:46:17 +0200
Subject: [osmocom-event-orga] Telefonica GSM/LTE frequency/arfcn
In-Reply-To: <20190809191555.6a2f66fd@lazus.yip>
References: <20190809191555.6a2f66fd@lazus.yip>
Message-ID: <13265273-801b-50ba-632f-352435da33f4@rhizomatica.org>


On 09/08/2019 19:15, Alexander Couzens wrote:
>
>
> 1800 MHz (max. 0,2 W)
>         680 (1838,8/1743,8 MHz)
>         683 (1839,4/1744,4 MHz)
>         686 (1840,0/1745,0 MHz)
>         689 (1840,6/1745,6 MHz)
>         692 (1841,2/1746,2 MHz)
>         695 (1841,8/1746,8 MHz)

Great! weird though, how it is laid out like that.

Given unusable adjacent ARFCNs, They are essentially giving us 1838.7 to
1841.9 (DL), so there are 8 usable AFRCNs in there.

Why space them like that?

Anyway, I guess this means we can deploy plenty of BTS. Do we have any
interest in the 1800Mhz sysmoBTS 2050? (with power output reduced way
way down, of course!) or should I just leave that heavy monster at home?


k/









From nhofmeyr at sysmocom.de  Mon Aug 12 11:58:49 2019
From: nhofmeyr at sysmocom.de (Neels Hofmeyr)
Date: Mon, 12 Aug 2019 13:58:49 +0200
Subject: [osmocom-event-orga] Telefonica GSM/LTE frequency/arfcn
In-Reply-To: <20190809191555.6a2f66fd@lazus.yip>
References: <20190809191555.6a2f66fd@lazus.yip>
Message-ID: <20190812115849.GC9995@my.box>

Weeey, nicely done lynxis!!!

~N

On Fri, Aug 09, 2019 at 07:15:55PM +0200, Alexander Couzens wrote:
> Hi,
> 
> thanks to Telefonica, we can use the following GSM & LTE arfcn.
> The paperwork with the BNetzA is not yet done, but we're working on it.
> 
>          Chaos Communication Camp
>          Ziegeleipark Mildenberg, 16792 Mildenberg, Brandenburg
>          vom 18.-27.08.2019
> 
> 
> 1800 MHz (max. 0,2 W)
>         680 (1838,8/1743,8 MHz)
>         683 (1839,4/1744,4 MHz)
>         686 (1840,0/1745,0 MHz)
>         689 (1840,6/1745,6 MHz)
>         692 (1841,2/1746,2 MHz)
>         695 (1841,8/1746,8 MHz)
> 
> 2600 MHz (max. 2 W)
>          10 MHz Bandbreite: 2660-2670/2540-2550 MHz
> 
> 
> Best,
> lynxis
> 
> -- 
> Alexander Couzens
> 
> mail: lynxis at fe80.eu
> jabber: lynxis at fe80.eu
> gpg: 390D CF78 8BF9 AA50 4F8F  F1E2 C29E 9DA6 A0DF 8604



-- 
- Neels Hofmeyr <nhofmeyr at sysmocom.de>          http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Gesch?ftsf?hrer / Managing Directors: Harald Welte
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.osmocom.org/mailman/private/osmocom-event-orga/attachments/20190812/eaf71b67/attachment.bin>

From lynxis at fe80.eu  Mon Aug 12 16:31:06 2019
From: lynxis at fe80.eu (Alexander Couzens)
Date: Mon, 12 Aug 2019 18:31:06 +0200
Subject: [osmocom-event-orga] Telefonica GSM/LTE frequency/arfcn
In-Reply-To: <13265273-801b-50ba-632f-352435da33f4@rhizomatica.org>
References: <20190809191555.6a2f66fd@lazus.yip>
 <13265273-801b-50ba-632f-352435da33f4@rhizomatica.org>
Message-ID: <20190812183106.7939e014@lazus.yip>

On Mon, 12 Aug 2019 10:46:17 +0200
Keith <keith at rhizomatica.org> wrote:

> On 09/08/2019 19:15, Alexander Couzens wrote:
> >
> >
> > 1800 MHz (max. 0,2 W)
> >         680 (1838,8/1743,8 MHz)
> >         683 (1839,4/1744,4 MHz)
> >         686 (1840,0/1745,0 MHz)
> >         689 (1840,6/1745,6 MHz)
> >         692 (1841,2/1746,2 MHz)
> >         695 (1841,8/1746,8 MHz)  
> 
> Great! weird though, how it is laid out like that.
> 
> Given unusable adjacent ARFCNs, They are essentially giving us 1838.7
> to 1841.9 (DL), so there are 8 usable AFRCNs in there.

I would guess, they're using the ARFCN in between themselfs.

> 
> Anyway, I guess this means we can deploy plenty of BTS. Do we have any
> interest in the 1800Mhz sysmoBTS 2050? (with power output reduced way
> way down, of course!) or should I just leave that heavy monster at
> home?

Not sure about it. It's quite heavy. I also don't know what kind of
power consumption it needs. But we'll need a lot BTSen :).

-- 
Alexander Couzens

mail: lynxis at fe80.eu
jabber: lynxis at fe80.eu
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: <https://lists.osmocom.org/mailman/private/osmocom-event-orga/attachments/20190812/be4b46ad/attachment.bin>

From 246tnt at gmail.com  Tue Aug 13 06:34:32 2019
From: 246tnt at gmail.com (Sylvain Munaut)
Date: Tue, 13 Aug 2019 08:34:32 +0200
Subject: [osmocom-event-orga] Telefonica GSM/LTE frequency/arfcn
In-Reply-To: <20190812183106.7939e014@lazus.yip>
References: <20190809191555.6a2f66fd@lazus.yip>
 <13265273-801b-50ba-632f-352435da33f4@rhizomatica.org>
 <20190812183106.7939e014@lazus.yip>
Message-ID: <CAHL+j0-PNwJtDnhzk2g+5dz=go4hseYTx9M2Je9GaYbi7zZAAg@mail.gmail.com>

> > Anyway, I guess this means we can deploy plenty of BTS. Do we have any
> > interest in the 1800Mhz sysmoBTS 2050? (with power output reduced way
> > way down, of course!) or should I just leave that heavy monster at
> > home?
>
> Not sure about it. It's quite heavy. I also don't know what kind of
> power consumption it needs. But we'll need a lot BTSen :).

Not sure if you have a deployment plan yet, but it would probably make
sense to have a coverage layer and a capacity layer.
>From what I remember from the site, there was a pretty good high point
available overlooking the whole camp,

Cheers,

    Sylvain


From nhofmeyr at sysmocom.de  Wed Aug 14 14:57:42 2019
From: nhofmeyr at sysmocom.de (Neels Hofmeyr)
Date: Wed, 14 Aug 2019 16:57:42 +0200
Subject: [osmocom-event-orga] Telefonica GSM/LTE frequency/arfcn
In-Reply-To: <CAHL+j0-PNwJtDnhzk2g+5dz=go4hseYTx9M2Je9GaYbi7zZAAg@mail.gmail.com>
References: <20190809191555.6a2f66fd@lazus.yip>
 <13265273-801b-50ba-632f-352435da33f4@rhizomatica.org>
 <20190812183106.7939e014@lazus.yip>
 <CAHL+j0-PNwJtDnhzk2g+5dz=go4hseYTx9M2Je9GaYbi7zZAAg@mail.gmail.com>
Message-ID: <20190814145742.GB27905@my.box>

On Tue, Aug 13, 2019 at 08:34:32AM +0200, Sylvain Munaut wrote:
> From what I remember from the site, there was a pretty good high point
> available overlooking the whole camp,

Keith and I were at that early visiting day and I took some pictures of this
high spot:

http://people.osmocom.org/neels/ohyoo5Bo/

Apparently POC is planning a DECT there so they should already plan to put
power and network up there.

~N
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.osmocom.org/mailman/private/osmocom-event-orga/attachments/20190814/c7b363eb/attachment.bin>

From holger at layer-acht.org  Sun Aug 18 11:33:46 2019
From: holger at layer-acht.org (Holger Levsen)
Date: Sun, 18 Aug 2019 11:33:46 +0000
Subject: [osmocom-event-orga] 2G BTS wanted
Message-ID: <20190818113346.422efcmwtgaulbst@layer-acht.org>

moin,

for the cccamp we need some more 2G BTS, can someone bring some more?
If so, please reply here or on IRC. If not, sad.


-- 
cheers,
	Holger

-------------------------------------------------------------------------------
               holger@(debian|reproducible-builds|layer-acht).org
       PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.osmocom.org/mailman/private/osmocom-event-orga/attachments/20190818/c025f473/attachment.bin>

From keith at rhizomatica.org  Sun Aug 18 12:24:46 2019
From: keith at rhizomatica.org (Keith Whyte)
Date: Sun, 18 Aug 2019 12:24:46 +0000
Subject: [osmocom-event-orga] 2G BTS wanted
In-Reply-To: <20190818113346.422efcmwtgaulbst@layer-acht.org>
References: <20190818113346.422efcmwtgaulbst@layer-acht.org>
Message-ID: <6B7C6CD0-9FB9-4072-8CAD-BCCC1CD22D7C@rhizomatica.org>

I'll bring 1x 1002. There is 1 x 2050 in Neel's bus. Not sure now when i get there.. i hope tomorrow.. anybody else travelling tomorrow?

On August 18, 2019 11:33:46 AM UTC, Holger Levsen <holger at layer-acht.org> wrote:
>moin,
>
>for the cccamp we need some more 2G BTS, can someone bring some more?
>If so, please reply here or on IRC. If not, sad.
>
>
>-- 
>cheers,
>	Holger
>
>-------------------------------------------------------------------------------
>               holger@(debian|reproducible-builds|layer-acht).org
>     PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.osmocom.org/mailman/private/osmocom-event-orga/attachments/20190818/d692a9a0/attachment.htm>

From philip at balister.org  Sun Aug 18 16:02:33 2019
From: philip at balister.org (Philip Balister)
Date: Sun, 18 Aug 2019 18:02:33 +0200
Subject: [osmocom-event-orga] 2G BTS wanted
In-Reply-To: <20190818113346.422efcmwtgaulbst@layer-acht.org>
References: <20190818113346.422efcmwtgaulbst@layer-acht.org>
Message-ID: <49c9b5ef-38c2-bfba-27d4-ec8bcbb08808@balister.org>

On 8/18/19 7:33 AM, Holger Levsen wrote:
> moin,
> 
> for the cccamp we need some more 2G BTS, can someone bring some more?
> If so, please reply here or on IRC. If not, sad.
> 
> 

I've got a Pi-3 and a b200 :)

Yes, I know about Harald's talk.

Philip


From stsp at stsp.name  Sun Aug 18 17:21:36 2019
From: stsp at stsp.name (Stefan Sperling)
Date: Sun, 18 Aug 2019 19:21:36 +0200
Subject: [osmocom-event-orga] 2G BTS wanted
In-Reply-To: <20190818113346.422efcmwtgaulbst@layer-acht.org>
References: <20190818113346.422efcmwtgaulbst@layer-acht.org>
Message-ID: <20190818172136.GF14213@ted.stsp.name>

On Sun, Aug 18, 2019 at 11:33:46AM +0000, Holger Levsen wrote:
> moin,
> 
> for the cccamp we need some more 2G BTS, can someone bring some more?
> If so, please reply here or on IRC. If not, sad.

I will try to throw a spare nanoBTS 165AU (012) V55 into Neels' bus.
Would that help?


From lynxis at fe80.eu  Sun Aug 18 19:51:29 2019
From: lynxis at fe80.eu (Alexander Couzens)
Date: Sun, 18 Aug 2019 21:51:29 +0200
Subject: [osmocom-event-orga] 2G BTS wanted
In-Reply-To: <6B7C6CD0-9FB9-4072-8CAD-BCCC1CD22D7C@rhizomatica.org>
References: <20190818113346.422efcmwtgaulbst@layer-acht.org>
 <6B7C6CD0-9FB9-4072-8CAD-BCCC1CD22D7C@rhizomatica.org>
Message-ID: <20190818215129.136a7596@lazus.yip>

On Sun, 18 Aug 2019 12:24:46 +0000
Keith Whyte <keith at rhizomatica.org> wrote:

> I'll bring 1x 1002. There is 1 x 2050 in Neel's bus. Not sure now
> when i get there.. i hope tomorrow.. anybody else travelling tomorrow?

great. thanks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.osmocom.org/mailman/private/osmocom-event-orga/attachments/20190818/e7715303/attachment.bin>

From lynxis at fe80.eu  Sun Aug 18 19:57:42 2019
From: lynxis at fe80.eu (Alexander Couzens)
Date: Sun, 18 Aug 2019 21:57:42 +0200
Subject: [osmocom-event-orga] 2G BTS wanted
In-Reply-To: <20190818172136.GF14213@ted.stsp.name>
References: <20190818113346.422efcmwtgaulbst@layer-acht.org>
 <20190818172136.GF14213@ted.stsp.name>
Message-ID: <20190818215742.1884cc49@lazus.yip>

On Sun, 18 Aug 2019 19:21:36 +0200
Stefan Sperling <stsp at stsp.name> wrote:

> On Sun, Aug 18, 2019 at 11:33:46AM +0000, Holger Levsen wrote:
> > moin,
> > 
> > for the cccamp we need some more 2G BTS, can someone bring some
> > more? If so, please reply here or on IRC. If not, sad.  
> 
> I will try to throw a spare nanoBTS 165AU (012) V55 into Neels' bus.
> Would that help?

Thanks for the offer. But I don't have good experience with them and wouldn't
use them at the camp. We still have 3 of them here which we don't
plan to use.

Best,
lynxis
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.osmocom.org/mailman/private/osmocom-event-orga/attachments/20190818/292ae4b0/attachment.bin>

From lynxis at fe80.eu  Sun Aug 18 20:08:26 2019
From: lynxis at fe80.eu (Alexander Couzens)
Date: Sun, 18 Aug 2019 22:08:26 +0200
Subject: [osmocom-event-orga] 2G BTS wanted
In-Reply-To: <49c9b5ef-38c2-bfba-27d4-ec8bcbb08808@balister.org>
References: <20190818113346.422efcmwtgaulbst@layer-acht.org>
 <49c9b5ef-38c2-bfba-27d4-ec8bcbb08808@balister.org>
Message-ID: <20190818220826.5245d50a@lazus.yip>

> I've got a Pi-3 and a b200 :)
> 
> Yes, I know about Harald's talk.

Thanks for your offer. But I don't think we will deploy it as
regular BTS.
However for testing it might be interesting to see how good it performs.

best,
lynxis
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.osmocom.org/mailman/private/osmocom-event-orga/attachments/20190818/f38bbd78/attachment.bin>

From bibor at syscallofduty.org  Thu Aug 29 14:26:51 2019
From: bibor at syscallofduty.org (bibor)
Date: Thu, 29 Aug 2019 16:26:51 +0200
Subject: [osmocom-event-orga] Camp After-Meeting
Message-ID: <bf9fdfcb-46a7-564f-b192-f5d4a8a4a31a@syscallofduty.org>

Hi people,

we want to do a camp post-mortem  meeting to discuss what was running
well, what bad and how we can improve for the coming events.

A non representative survey lead to the date

	Monday, 2nd September at the c-base beach.

In case of bad weather we can relocate to Cadus, just across the river.

Please let us know if you can make it.

In hope for a productive and fun evening,
bibor



From axilirator at gmail.com  Thu Aug 29 15:48:45 2019
From: axilirator at gmail.com (Vadim Yanitskiy)
Date: Thu, 29 Aug 2019 17:48:45 +0200
Subject: [osmocom-event-orga] Camp After-Meeting
In-Reply-To: <bf9fdfcb-46a7-564f-b192-f5d4a8a4a31a@syscallofduty.org>
References: <bf9fdfcb-46a7-564f-b192-f5d4a8a4a31a@syscallofduty.org>
Message-ID: <CAPEnp=b3s7a_Ha97-m=-b6sBuvWGriP3K3TKXBmZCENEG=WsHg@mail.gmail.com>

Hi all,

> Monday, 2nd September at the c-base beach.
> Please let us know if you can make it.

Fine with me. See you there!

With best regards,
Vadim Yanitskiy.


From laforge at gnumonks.org  Thu Aug 29 19:42:54 2019
From: laforge at gnumonks.org (Harald Welte)
Date: Thu, 29 Aug 2019 21:42:54 +0200
Subject: [osmocom-event-orga] Camp After-Meeting
In-Reply-To: <bf9fdfcb-46a7-564f-b192-f5d4a8a4a31a@syscallofduty.org>
References: <bf9fdfcb-46a7-564f-b192-f5d4a8a4a31a@syscallofduty.org>
Message-ID: <20190829194254.GP3458@nataraja>

Hi!

On Thu, Aug 29, 2019 at 04:26:51PM +0200, bibor wrote:
> A non representative survey lead to the date
> 	Monday, 2nd September at the c-base beach.

I'm not available then, sorry.

My feedback in terms of possible areas of improvement is:

* automatic saving coredumps and corresponding binaries/libraries is a must on the server

* there should be clear procedures about how to roll out patches during
  the event, stopping the systemd service and running a custom-built
  binary from a branch that's not rebased on what was running before is
  not the best approach. It's not a desaster either, but we should know
  better, IMHO

* LTE core network needs introspection (like our VTY).  I'm currently
  discussing with Sukchan what's the best approach here.

* SMS over LTE should have been possible (via SGs interface, implemented
  by both OsmoMSC and nextepc-mmed) but I had no energy left to try.
  Should be rather straight-forward in any future installation.

* next logical step in terms of 4G <-> 2G/3G integration would be a
  combined GGSN and P-GW, i.e. something speaking both GTPv1 and GTPv2.
  Not sure if we'll find any time to implement that soon (or try ergw),
  but it would be the precondition to mobility (cell reselection or even
  handover) between 4G and other technologies

* LTE core network shouldn't run on a laptop whose lid can be closed
  (and as a result, suspended).  I simply dind't have any non-laptop
  machine available.  Given that LTE has actual user data throughput
  that's worth mentioning, we cannot use APU/Atom/Raspi for it.


Also some news that maybe haven't reached wider circulation yet:

1) sipgate (a German MVNO whom I know from some previous consulting
   work) has indicated interest to have their SIM cards roam into our
   event networks in the future.  There are technical details to be
   sorted out, but at least mobile data could be relatively easy with
   the new GSUP/diameter translator.

2) One of the sysmocom customers (a small MNO) has offered to provide us
   with diameter access to GRX, which would technically allow us to have
   virtually any user roam to our network. The problem is that diameter
   is signaling only, and we would basically disrupt voice and/or SMS
   services for such users, which clearly is not a great idea.  If we
   want to do something like that, there would have to be an explicit
   white-list to ensure only people who know the consequences will be on
   the event network, and not uninformed bystanders.

I will stay in touch with those operators and keep this list posted
about plans. I don't forsee any significant changes to the existing
Osmocom network structure to enable any of the above.  It's basically
a question of either using OsmoHLR to route GSUP messages based on IMSI
prefixes, or to have a dedicated GSUP router in between OsmoHLR and
OsmoMSC/SGSN.  The router would then make sure that only 26242 ends up
in the OsmoHLR, while other prefixes (MCC/MNC) are treated by the
diameter translator and possibly routed to other operators.

Regards,
	Harald
-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)