DevEX - reference for building teams, processes, and platforms
17-Pete_Vickers-IPv6-in-the-Mobile-Net
1. in the Mobile Net
Pete Vickers, Network Norway AS.
1
tirsdag 24. mai 2011
2. Introduction
Scope Eye Candy
Challenges Hall of Fame
Mobile Architecture Hall of Shame
Imp. Methodology Questions
Preparation
Connectivity options
2
tirsdag 24. mai 2011
3. Scope
Attempt to avoid overly technical
focus on mobile net differences
Innovation stifled by 3GPP / IETF friction.
Frustrated by telco sector’s CS vs. PS rationale
3
tirsdag 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.
4
tirsdag 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)
5
tirsdag 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 ?
6
tirsdag 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).
7
tirsdag 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
8
tirsdag 24. mai 2011
9. more preparation ...
IGPs: OSPFv3 or ISIS
prefixes 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 ;)
9
tirsdag 24. mai 2011
10. Quick Rant
•but seriously, let the client O/S &
applications ‘manage’ multipath
connectivity (& name resolution) ?
•Support nightmare. ‘NxN unfixable’
handset problems. (OTA reconfig
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 fix it ! Hint: P2Ps
enjoy IPv6 end-end connectivity.
10
tirsdag 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
11
tirsdag 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 <addr fe80::d69a:20ff:fe0f:3e1e>]
Tue May 10 11:29:13 2011 : rcvd [IPV6CP ConfNak id=0x1 <addr fe80::0000:0007:73a7:6501>]
Tue May 10 11:29:13 2011 : sent [IPV6CP ConfReq id=0x2 <addr fe80::0000:0007:73a7:6501>]
Tue May 10 11:29:13 2011 : rcvd [IPV6CP ConfAck id=0x2 <addr fe80::0000:0007:73a7:6501>]
$ ifconfig ppp0
ppp0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500
! inet6 fe80::8:f11f:a601%ppp0 prefixlen 64 scopeid 0x9
! inet6 2a00:e18:8000:15::8:f11f:a601 prefixlen 64 autoconf
12
tirsdag 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, + netflow logging
13
tirsdag 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 ?
14
tirsdag 24. mai 2011
15. Questions ?
Pete Vickers
pete@systemnet.no
(+47) 48179100
15
tirsdag 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
16
tirsdag 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: any,
ge-2/0/0.0:2a00:e18:8000:25:0:8:5889:2601:33500 -> 64:ff9b:0:0:0:0:3e3d:45d9:80,
creating forward or watch flow ; source address and port translate to
89.254.77.118:1788 ; destination address translates to 62.61.69.217
May 19 15:57:55 mx240-nat64-re0 (FPC Slot 1, PIC Slot 0) {SET_O}[FWNAT]:
ASP_NAT_RULE_MATCH: proto 6 (TCP) application: any,
ge-2/0/0.0:2a00:e18:8000:25:0:8:5889:2601:54369 -> 64:ff9b:0:0:0:0:42dc:950c:80,
Match NAT rule-set: , rule: NAT64, term: INSIDE
17
tirsdag 24. mai 2011
18. References
3gv6 mailing list:
https://www.ietf.org/mailman/listinfo/3gv6
Handset HotSpot:
http://www.joiku.com/ - please hassle them for IPv6 WWAN->WLAN
No IPv6 on Android:
http://code.google.com/p/android/issues/detail?id=3389
other pres:
http://ipv6ws.arkko.com/report.html#presentations
18
tirsdag 24. mai 2011
