Accelerate3g5 -- blobb » History » Revision 16
Revision 15 (blobb, 03/15/2017 10:04 PM) → Revision 16/153 (blobb, 03/15/2017 10:25 PM)
h1. Accelerate3g5 -- blobb h2. Summary Trying to come up with a fuzzing interface. h3. Participants * André Boddenberg (email: dr.blobb@gmail.com) h2. Details First setting up the femtocell and understand basics of UMTS communication. Collecting information e.g. slides, talks, docu about fuzzing of wireless protocols. Writing some code to craft requests and run fuzz tests against subscriber. Note: first time fuzzing. h2. Journal _2017-03-07_ pick up package at the sysmocom office. having an informative conversation with Neels about jenkins.osmocom. _2017-03-12_ Set up wiki page. Seeing femtocell on network interface and knocking ports: > 22/tcp open ssh > 8089/tcp open http > 8090/tcp open telnet > 10002/tcp open documentum (needs investigation) Compiled source as described, but couldn't configure/launch CN successfully (yet). Next time trying Neels' launch script and same IP range. Note: Feeling the need for an additional LAN port to not interfere with eth0. _2017-03-15_ Reading "data sheet":http://www.ipaccess.com/uploads/wysiwyg_editor/files/2017/S8_S16-Datasheet-v1.0.pdf data sheet about ip.access nano3G S8. Configuring femtocell via telnet (dry run). Running in HLR issue mentioned in wiki when invoking run.sh. h2. Conclusions - additional LAN port dedicated for femtocell is great. - network LED does not indicate whether IP has been assigned by DHCP server.
