Dear Osmocom community,
today our mailing list server lists.osmocom.org has finally been migrated
from mailman2-on-freebsd to mailman3-on-linux. This also included a variety
of changes to DNS. I'll spare you the details, but everything _should_ be up
and running now.
* The List-Id headers should not have changed.
* all list subscriptions + user accounts have been converted.
* old 'static html' archives are still available (read only) at URLs like
https://lists.osmocom.org/pipermail/baseband-devel/
* old List URLs like https://lists.osmocom.org/mailman/listinfo/baseband-devel
are redirected to their respective modern counterparts
In case you notice any mailing list related problem, please don't hesitate to
contact me.
Happy hacking,
Harald
--
- Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
RLC/MAC layer in real networks is always used in acknowledged/reliable
mode, and LLC is always only used in unreliable (UI) mode. The reason
for this is that TCP cannot deal with the enormous packet loss that GPRS
or similar radio links pose. If TCP would be exposed to the real packet
loss, it would stall way too much.
So my rationale was to use the same while creating osmo-sgsn. We use
LLC in UI mode.
Or are we talking about something completely else?
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
* With multiple TBF assignment the tbf_by_tlli will return a list
anyway.
* For the multiple RACH cases we could it probably handle it more
nicely.
E.g. avoid this:
<0005> bts.cpp:1035 Got RACH from TLLI=0xcf7611f6 while TBF(TFI=0 TLLI=0xcf7611f6 DIR=DL) still exists. Killing pending DL TBF
<0002> bts.cpp:359 Got IMM.ASS confirm, but TLLI=cf7611f6 does not exit
--
- Holger Freyther <hfreyther(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Schivelbeiner Str. 5
* 10439 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Directors: Holger Freyther, Harald Welte
if we should use more C++ features (I am not talking STL, operator
overloading)?
Any opinions?
holger
PS: I think we should find a more nice solution to extern "C".. I
spent various minutes trying to figure out which parts of the pcu
have C linkage and which C++.. For things from libosmocore it is
obvious.. but then we have the vty_info...
--
- Holger Freyther <hfreyther(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Schivelbeiner Str. 5
* 10439 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Directors: Holger Freyther, Harald Welte
bug fixes. Ideally I'd love to see Andreas developing them on top of
the current 'master' and submitting them to the mailing list as soon
as he push them. This way Ivan (and everyone else) would be able to
review them and merge as soon as possible. I hate the situation when
fixes are stored in a private branch and are not merged into mainline.
On Mon, Nov 26, 2012 at 5:02 PM, Ivan Kluchnikov
<Ivan.Kluchnikov(a)fairwaves.ru> wrote:
> Hi, all!
>
> I absolutely agree with Harald and I am ready to use described life-cycle
> model for osmo-pcu.
> Before that time I merged branch 'jolly', when the differences between
> master and jolly become critical.
> I didn't coordinate merges with Andreas and jolly branch wasn't rebased
> before merges. I think, it was my mistake.
> Now I am ready to merge jolly branch at any time, when Andreas indicates
> that his branch is ready for merge.
>
>
> 2012/11/25 Harald Welte <laforge(a)gnumonks.org>
>>
>> Dear all,
>>
>> it is a pity to see that since many weeks there has been no progress on
>> merging any of Andreas' work. I think everyone involved is to be
>> blamed to some extent. Andreas because the provided branches are not
>> kept clean, Ivan probably for lack of time, and me for not paying more
>> attention and helping this process along.
>>
>> The general life-cycle in any project, including osmo-pcu, should be as
>> follows:
>>
>> * contributor starts on some improvements, creates private branch
>> * master advances meanwhile
>> * contributor rebases (not merges!) his changes on top of more recent
>> master
>> * contributor indicates that his branch is ready for merge
>> * maintainer merges (some of?) the commits of the contributor branch
>> * contributor re-bases remaining commits on new master
>> * contributor requests merge of remaing patches
>> ...
>>
>> If I open 'gitk' on any of the branches (master / jolly / jolly_dsp) I
>> get grey hair (to say the least). One would normally expect:
>>
>> 1) 'jolly' to be based on some (maybe not current) master
>>
>> 2) 'jolly_dsp' to be based on 'jolly'
>>
>> Neither of the two is the case. I've tried to
>> * rebase jolly on top of master
>> as well as
>> * rebase jolly_dsp on top of jolly
>>
>> and both are impossible due to the series of merges and the unclear
>> ancestry / relationship of the branches. Or, just for fun, try 'git
>> diff origin/jolly..origin/jolly_dsp. It shows you anything else but
>> what one would expect
>>
>> Andreas: Please take some time to clean up the mess. Your 'jolly'
>> branch should contain a series of clean per-feature commit's on top of
>> current master, and 'jolly_dsp' should be a set of few patches on top of
>> 'jolly'.
>>
>> This way there is always a clean queue of changesets that Ivan can merge
>> (or cherry-pick). I can understand that if I was in Ivan's place, I
>> would not really know where to even start merging some of those
>> contributions.
>>
>> Thanks for everyone's attention. Please take some time to get this
>> resolved. Let me know if you have some questions. There are plenty of
>> people with lots of git experience around (Holger, Pablo, myself) who
>> can help if something is unclear.
>>
>> Regards,
>> Harald
>>
>> --
>> - Harald Welte <laforge(a)gnumonks.org>
>> http://laforge.gnumonks.org/
>>
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
>> "Privacy in residential applications is a desirable marketing option."
>> (ETSI EN 300 175-7 Ch.
>> A6)
>>
>
>
>
> --
> Regards,
> Ivan Kluchnikov.
> http://fairwaves.ru
>
--=20
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / =D0=9E=D0=9E=D0=9E =D0=A3=D0=BC=D0=A0=D0=B0=D0=B4=D0=
=B8=D0=BE
http://fairwaves.ru
Dear all,
I am pleased to announce new tagged releases for Osmocom Cellular
Network Infrastructure components.
Find more information about the release here [1].
Osmocom "Latest" repositories in OBS [2] should already contain packages
for the new versions.
OpenEmbedded related meta-layers such as meta-telephony usual
stable/testing branch "201705" [3] have also been updated to build
recipes for new versions.
Regards,
Pau
[1] https://osmocom.org/news/152
[2] https://osmocom.org/projects/cellular-infrastructure/wiki/Latest_Builds
[3] https://git.osmocom.org/meta-telephony/log/?h=201705
--
- Pau Espin Pedrol <pespin(a)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
* Geschaeftsfuehrer / Managing Director: Harald Welte
Hi, Osmonians,
I don't know where to write for MME TTCN-3, so I chose to write to it
closet relative - SGSN.
I was trying to do slight modification to TTCN-3 code, modifing
S1AP_Templates.ttcn.
I embedded enodeb name for all tests with new protoc-IE = id-eNBname :
##################################
template (value) S1AP_PDU
ts_S1AP_SetupReq(template (value) Global_ENB_ID p_global_ENB_ID,
template (value) SupportedTAs p_supportedTAs,
template (value) PagingDRX p_pagingDRXs) := {
initiatingMessage := {
procedureCode := id_S1Setup,
criticality := reject,
value_ := {
S1SetupRequest := {
protocolIEs := {
{
id := S1AP_Constants.id_Global_ENB_ID,
criticality := ignore,
value_ := { Global_ENB_ID := p_global_ENB_ID }
},
{
id := S1AP_Constants.id_SupportedTAs,
criticality := reject,
value_ := {SupportedTAs := p_supportedTAs}
},
{
id := S1AP_Constants.id_eNBname,//id-eNBname
criticality := ignore,
value_ := {ENBname := "OsmoEnodeb"}
} /* HACK: work around nextepc bug
, {
id := S1AP_Constants.id_pagingDRX,
criticality := ignore,
value_ := {PagingDRX := p_pagingDRXs}
} */
}
}
}
}
}
########################
Code compiles, but PDU is not encoded well.
I attached Wireshark preview.
Can you help me with this issue ?
--
Puno pozdrava,
Mirko Kovacevic
Dear Osmocom community,
today we finally upgraded our redmine installation from the unmaintained
3.4.x to the latest 4.2.3. The upgrade had been overdue for years,
but today we (actually, Kevin) finally managed to find out how to make
the openid_provider plugin to work with modern rails 5.x.
In any case, I'm just informing you in case there is some unexpected fallout.
I've verified that at least the following appears working:
* logging into redmine
* openid authentication from gerrit.osmocom.org (also after logout/relogin)
* graphviz rendering
* mscgen rendering
There could however still be unexpected problems, particularly in features
such as
* e-mail notifications from redmine
* updating redmine issues via e-mail
* git integration ("Closes: OS#xxxx")
If you run into any troubles, pleas report to https://osmocom.org/projects/osmocom-servers
or if that also fails, feel free to send e-mails.
Regards,
Harald
--
- Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
