Accelerate3g5 -- blobb » History » Version 24
blobb, 04/20/2017 04:48 PM
| 1 | 1 | blobb | h1. Accelerate3g5 -- blobb |
|---|---|---|---|
| 2 | 2 | blobb | |
| 3 | h2. Summary |
||
| 4 | |||
| 5 | 3 | blobb | Trying to come up with a fuzzing interface. |
| 6 | |||
| 7 | 2 | blobb | h3. Participants |
| 8 | |||
| 9 | * André Boddenberg (email: dr.blobb@gmail.com) |
||
| 10 | |||
| 11 | h2. Details |
||
| 12 | 3 | blobb | |
| 13 | First setting up the femtocell and understand basics of UMTS communication. |
||
| 14 | Collecting information e.g. slides, talks, docu about fuzzing of wireless protocols. |
||
| 15 | 6 | blobb | Writing some code to craft requests and run fuzz tests against subscriber. |
| 16 | 3 | blobb | |
| 17 | 4 | blobb | Note: first time fuzzing. |
| 18 | 2 | blobb | |
| 19 | h2. Journal |
||
| 20 | |||
| 21 | 7 | blobb | _2017-03-07_ |
| 22 | pick up package at the sysmocom office. |
||
| 23 | having an informative conversation with Neels about jenkins.osmocom. |
||
| 24 | |||
| 25 | 2 | blobb | _2017-03-12_ |
| 26 | Set up wiki page. |
||
| 27 | 10 | blobb | Seeing femtocell on network interface and knocking ports: |
| 28 | 2 | blobb | |
| 29 | 8 | blobb | > 22/tcp open ssh |
| 30 | > 8089/tcp open http |
||
| 31 | 11 | blobb | > 8090/tcp open telnet |
| 32 | 8 | blobb | > 10002/tcp open documentum (needs investigation) |
| 33 | 7 | blobb | |
| 34 | 8 | blobb | Compiled source as described, but couldn't configure/launch CN successfully (yet). |
| 35 | 13 | blobb | Next time trying Neels' launch script and same IP range. |
| 36 | 7 | blobb | |
| 37 | 8 | blobb | Note: Feeling the need for an additional LAN port to not interfere with eth0. |
| 38 | 1 | blobb | |
| 39 | 10 | blobb | _2017-03-15_ |
| 40 | 20 | blobb | Reading "data sheet [overview]":http://www.ipaccess.com/uploads/wysiwyg_editor/files/2017/S8_S16-Datasheet-v1.0.pdf "data sheet [details]":https://fccid.io/pdf.php?id=1462491 about ip.access nano3G S8. |
| 41 | 12 | blobb | Configuring femtocell via telnet (dry run). |
| 42 | Running in HLR issue mentioned in wiki when invoking run.sh. |
||
| 43 | |||
| 44 | 22 | blobb | _2017-04-19_ |
| 45 | 24 | blobb | resolved HLR issue and set all IPs correct in *.cfg files. |
| 46 | hNodeB connects to owmo-hnbgw, but no phone connects. |
||
| 47 | 1 | blobb | |
| 48 | 24 | blobb | _2017-04-20_ |
| 49 | TD1 and TD2 successfully connected to the femtocell!!! \o/ |
||
| 50 | voice call work, data is not working (wip). |
||
| 51 | 7 | blobb | |
| 52 | 24 | blobb | |
| 53 | 1 | blobb | h2. Conclusions |
| 54 | |||
| 55 | 21 | blobb | - network LED does not indicate whether IP has been assigned by DHCP server. |
| 56 | 24 | blobb | - umts LED does indicate whether cell is connected to hnbgw, etc pp. |
