Ubuntu Touch in Samsung Galaxy S III (GT-I9300) & Roll back to Android JB

A. Install Ubuntu Touch:
1. Fisrt you need to root your GT-I9300. Download and do it with Samsung Galaxy S3 ToolKit. Choose appropriate model and reset the ROM.
2. Download ubuntu-for-i9300 & quantal-preinstalled-phablet-armhf.
3. Copy these file to SD Card.
4. Shutdown Galaxy S III and hold Volume Up + Home + Power simultaneously.
5. Wipe data.
6. First install ubuntu-for-i9300 & then quantal-preinstalled-phablet-armhf.
7. Reboot. Your GT-I9300 will boot into ubuntu touch.

But noting will work. In my case no GSM network, no Wi-Fi. All buttons are not working properly. Even can't lock the phone.

B. Android Jelly Bean:
1. Download latest cyanogenmod from following link:
http://download.cyanogenmod.org/?type=nightly&device=i9300
2. Search for GApps for CM10.1 in search engine. I have download GApps from following link:
http://goo.im/gapps/gapps-jb-20130301-signed.zip
3. Copy these files to SD Card.
4. Shutdown Galaxy S III and hold Volume Up + Home + Power simultaneously.
5. Chose install from sdcard option. First install CM 10.1 and then GApps.
6. Reboot the phone, you are done.

IP address delegated by APNIC (Convert it to CIDR Format)

1. Go to ftp://ftp.apnic.net/pub/stats/apnic/

Download the latest delegated-apnic* file. This file contnet all the IP address and ASN delegated by APNIC to it's region. Open the file and remove the comments and ASN part.

2. Get those IP which are allocated to BD.

# more delegated-apnic-20130506 | grep BD > bdip.txt

Now you have bdip.txt file having following content:

apnic|BD|ipv4|27.0.96.0|8192|20110302|allocated

apnic|BD|ipv4|27.131.12.0|1024|20100421|allocated

apnic|BD|ipv4|27.147.128.0|32768|20100331|allocated

apnic|BD|ipv4|42.0.4.0|1024|20110317|allocated

apnic|BD|ipv4|42.99.116.0|1024|20110322|allocated

apnic|BD|ipv4|49.0.32.0|8192|20101027|allocated

apnic|BD|ipv4|58.65.224.0|2048|20060607|allocated

apnic|BD|ipv4|58.97.128.0|32768|20110107|allocated

apnic|BD|ipv4|58.145.184.0|2048|20060615|allocated

apnic|BD|ipv4|58.147.168.0|2048|20060613|allocated

Team Cymru BOGONS service

We have peered with Team Cymru regarding BOGONS service. As stated in Team Cymru website:

"Bogons are defined as Martians (private and reserved addresses defined by RFC 1918, RFC 5735, and RFC 6598) and netblocks that have not been allocated to a regional internet registry (RIR) by the Internet Assigned Numbers Authority. Fullbogons are a larger set which also includes IP space that has been allocated to an RIR, but not assigned by that RIR to an actual ISP or other end-user."

Technically it's quite easy. You will subscribe to Team Cymru BOGONS service (which is free!!). Team Cymru will allow you to do EBGP with there routers which will basically feed you the BOGONS route (both IPv4 & IPv6). You will tag those routes to a specific community and send them to null route. So traffic for those prefixes are dropped and will not go to the internet.

How to apply:

To to Team Cymru site (http://www.team-cymru.org/Services/Bogons/) and apply for the BOGONS Service.

Findings:

After configuring the EBGP session we start receiving BOGONS prefixes. To my surprise, there are around 73463 IPv6 BOGONS prefixes we are receiving (date 22nd April, 2013) in comparison with only 12258 valid IPv6 prefixes!!! It includes 2001:DB8::/32 which is basically reserver for documentation (RFC 3849).

Hiding MPLS core to the client

In this post we will look at what happens to the TTL value of a packet when it enters the MPLS VPN. We will also see how we can change that behavior to hide the provider network from customers.

C1S1(CE)--R1(PE)--R2(P)--R3(P)--R4(PE)--C1S2(CE)

Before disabling TTL propagation bellow is the trace route:


  1 192.168.10.1 20 msec 16 msec 16 msec
  2 192.168.12.2 [MPLS: Labels 22/25 Exp 0] 112 msec 112 msec 104 msec
  3 192.168.23.2 [MPLS: Labels 22/25 Exp 0] 112 msec 88 msec 84 msec
  4 192.168.11.1 [MPLS: Label 25 Exp 0] 76 msec 80 msec 76 msec
  5 192.168.11.2 64 msec *  120 msec

After putting no mpls ip propagate-ttl forwarded bellow is the trace route output:


  1 192.168.10.1 8 msec 52 msec 20 msec
  2 192.168.11.1 [MPLS: Label 25 Exp 0] 88 msec 88 msec 76 msec
  3 192.168.11.2 116 msec *  160 msec

It hides the P routers from the client. You need put this command in all your PE and P router.

MPLS Layer3 VPN : Part 3 (Configure L3 VPN for CUSTOMER2)

In this phase L3VPN is configured for CUSTOMER2. It is same for CUSTOMER1 but only difference is that between PE router R1 and CE router C2S1 protocol will be OSPF.

PHASE 3: Configure L3 VPN for CUSTOMER2

1. Create Separate VRF for CUSTOMER1
R1(config)#ip vrf CUSTOMER2
R1(config-vrf)#rd 500:2
R1(config-vrf)#route-target export 500:2
R1(config-vrf)#route-target import 500:2

2. MP-BGP with R4, actiavte VPNv4 and redistribute OSPF route to BGP
2.A Configurer MP-BGP/Activate VPNv4
As MP-BGP in place with R1 and R4 (configured in phase 2) do not need configure anything new.