IPv6 i det mobile nettet: Pete Vickers, Network Engineer, Network Norway

Click here to load reader

  • date post

    29-Nov-2014
  • Category

    Technology

  • view

    1.191
  • download

    1

Embed Size (px)

description

IPv6 i det mobile nettet: Pete Vickers, Network Engineer, Network NorwayIKT-Norge IPv6 forum IPV6 konferanse 23 & 24 mai 2011

Transcript of IPv6 i det mobile nettet: Pete Vickers, Network Engineer, Network Norway

  • 1. in the Mobile Net Pete Vickers, Network Norway AS. 1tirsdag 24. mai 2011
  • 2. Introduction Scope Eye Candy Challenges Hall of Fame Mobile Architecture Hall of Shame Imp. Methodology Questions Preparation Connectivity options 2tirsdag 24. mai 2011
  • 3. Scope Attempt to avoid overly technical focus on mobile net differences Innovation stied by 3GPP / IETF friction. Frustrated by telco sectors CS vs. PS rationale 3tirsdag 24. mai 2011
  • 4. Challenges air/freq. is a shared medium, SIM card + $random terminal type. $vendor terminal support Roaming = guest status. telco vendors license models discourage IPv6. radio resources. 4tirsdag 24. mai 2011
  • 5. Mobile Net architecture SKIP - E/ /s Fredrick did it with much better graphics 20mins ago. / 2/3/4 G GPRS PDP context - GTP tunnel SGSN(local) GGSN(home) 5tirsdag 24. mai 2011
  • 6. BTW: here we go again... IPv4 to IPv6 ~= IPX, LAT, ISO, X.25, (or whatever) to IPv4. your oldest staff might be your best asset ? 6tirsdag 24. mai 2011
  • 7. Implementation methodology started at outside layer, work inwards towards customer less customer breakage easy to verify along way Management plane, AAA, licensing, logging, security etc. SSH, radius, NTP, DNS, syslog, h/w ACLs. multi-vendor hybrid (E///, Cisco, Juniper, Opensource). 7tirsdag 24. mai 2011
  • 8. Preparation MPLS core... 6VPE ( individual PEs & RRs only, no P changes) s/w upgrades, licensing, labbing. Establishing IPv6 BGP peerings (NIX: 50xIPv4 vs. 16xIPv6) # show bgp vpnv6 unicast vrf internet regexp _39029$ BGP table version is 1238870, local router ID is 89.254.100.3 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure, S Stale Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path Route Distinguisher: 41483:1002 (default for vrf internet) *> 2001:67C:21E0::/48 2001:7F8:12:1::3:9029 0 39029 i *> 2A02:C0::/32 2001:7F8:12:1::3:9029 0 39029 i 8tirsdag 24. mai 2011
  • 9. more preparation ... IGPs: OSPFv3 or ISIS prexes obviously not easily memorable or uniquely displayed (cf. IPv4 or E.164) those who static route IPv4 should lose their jobs those who static route IPv6 will lose their jobs ;) 9tirsdag 24. mai 2011
  • 10. Quick Rant but seriously, let the client O/S & applications manage multipath connectivity (& name resolution) ? Support nightmare. NxN unxable handset problems. (OTA recong limited) Sane approach: pure IPv6. (w/ Stateful NAT64 for legacy IPv4 content) Dual Stack car ? It breaks your App ? well maybe you hardcoded stuff, so x it ! Hint: P2Ps enjoy IPv6 end-end connectivity. 10tirsdag 24. mai 2011
  • 11. connectivity options 1. IPv4 APN (today) 2. IPv6 APN 3. IPv4v6 APN A dual stack client can use either : (3) Release8/9 (1)+(2) on Release4 [Ole T. w/Nokia MT does this]. where (2). optional complemented w/NAT64 for legacy IPv4 access 11tirsdag 24. mai 2011
  • 12. Eye Candy... $ tail /var/log/ppp.log Tue May 10 11:28:59 2011 : Apple Base Script.ccl Version 3.3 Tue May 10 11:29:05 2011 : Using interface ppp0 Tue May 10 11:29:05 2011 : Connect: ppp0 /dev/cu.Bluetooth-Modem Tue May 10 11:29:11 2011 : sent [IPV6CP ConfReq id=0x1 ] Tue May 10 11:29:13 2011 : rcvd [IPV6CP ConfNak id=0x1 ] Tue May 10 11:29:13 2011 : sent [IPV6CP ConfReq id=0x2 ] Tue May 10 11:29:13 2011 : rcvd [IPV6CP ConfAck id=0x2 ] $ ifconfig ppp0 ppp0: flags=8051 mtu 1500 ! inet6 fe80::8:f11f:a601%ppp0 prefixlen 64 scopeid 0x9 ! inet6 2a00:e18:8000:15::8:f11f:a601 prefixlen 64 autoconf 12tirsdag 24. mai 2011
  • 13. Hall of Fame Nokia handsets. e.g. E71 (4 years old !) Juniper early hardware NAT64 solution (stable & scaleable) (sys)logging not suitable for DLD ? Cisco early NAT-PT (not scalable) NAT64 in EFT, + netow logging 13tirsdag 24. mai 2011
  • 14. Hall of Shame Apple - iOS no PDPv6 support Google - Android no PDPv6 support ZTE, Option, Nokia, Huawei - no dongle PDPv6 support ? Ericsson - unable to verify. Apparently MMDM support ? discouraging licensing (IPv6 extra). All - feature parity ? 14tirsdag 24. mai 2011
  • 15. Questions ? Pete Vickers [email protected] (+47) 48179100 15tirsdag 24. mai 2011
  • 16. Example of typical problem $ screen /dev/tty.Mobile-Modem 9600 at+cgdcont=? +CGDCONT: (1-16),"IP",,,(0-2),(0-4) +CGDCONT: (1-16),"PPP",,,(0-2),(0-4) +CGDCONT: (1-16),"IPV6",,,(0-2),(0-4)) OK => so PDP type IPV6 is listed. => can we can select it ? See ETSI TR 127 007 for at+cgdcont=1,"IPV6","v6",,0,0 commands overview OK => great. => and verify it took it: at+cgdcont? +CGDCONT: 1,"IPV6","v6","0.0.0.0",0,0 ...Opps, notice the 0.0.0.0 not ::/0 => try to dial ATD*99***1# ERROR 16tirsdag 24. mai 2011
  • 17. NAT64 logging example May 19 15:57:53 mx240-nat64-re0 (FPC Slot 1, PIC Slot 0) {SET_O}[FWNAT]: ASP_SFW_CREATE_ACCEPT_FLOW: proto 6 (TCP) application: an