August 2008 - Test - lists.nanog.org

Problems Communicating with Network Solutions
by Johnson, Joe 20 Aug '08

20 Aug '08

Is there anyone at XO or Network Solutions that can help me with a little problem we're having? About two days ago we lost the ability to pass all traffic with Network Solutions hosted email and their main website from our main office. It keeps dying at a router in DC. Here's a trace from our Chicago office: Tracing route to 205.178.149.7 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 38.98.154.1 2 1 ms 1 ms 2 ms fa0-7.na01.b002327-0.ord01.atlas.cogentco.com [38.99.215.81] 3 <1 ms <1 ms 1 ms gi0-7.3542.core01.ord01.atlas.cogentco.com [66.250.11.189] 4 <1 ms 1 ms <1 ms te4-1.mpd01.ord01.atlas.cogentco.com [154.54.1.98] 5 1 ms 1 ms 1 ms vl3488.mpd01.ord03.atlas.cogentco.com [154.54.5.26] 6 <1 ms <1 ms <1 ms xo.ord03.atlas.cogentco.com [154.54.12.230] 7 2 ms 1 ms 1 ms te-3-1-0.rar3.chicago-il.us.xo.net [65.106.1.42] 8 4 ms 1 ms 1 ms ge7-0-0d0.rar1.chicago-il.us.xo.net [65.106.1.41] 9 28 ms 27 ms 28 ms p6-0-0.rar2.washington-dc.us.xo.net [65.106.0.46] 10 * * * Request timed out. (repeats until time-out) Here's one from an external Chicago looking glass: traceroute to 205.178.149.7 (205.178.149.7), 30 hops max, 38 byte packets 1 10.255.255.253 (10.255.255.253) 7.190 ms 5.022 ms 4.763 ms 2 vl-993.gw-core-a.whn.oneandone.net (217.160.229.45) 0.489 ms 0.487 ms 0.392 ms 3 ge-3-2-0-0.bb-a.tla.nyc.us.oneandone.net (217.160.229.65) 0.692 ms 0.655 ms 0.588 ms 4 so-1-0-0-0.bb-a.cr.chi.us.oneandone.net (74.208.1.32) 22.206 ms 22.133 ms 22.070 ms 5 p12-3.IR1.Chicago2-IL.us.xo.net (206.111.2.9) 22.309 ms 22.431 ms 22.723 ms 6 * te-3-1-0.rar3.chicago-il.us.xo.net (65.106.1.42) 24.414 ms 23.019 ms 7 ge7-0-0d0.rar1.chicago-il.us.xo.net (65.106.1.41) 23.002 ms 22.910 ms 22.918 ms 8 p6-0-0.RAR2.Washington-DC.us.xo.net (65.106.0.46) 39.504 ms 39.471 ms 39.363 ms 9 p7-0-0.MAR2.Washington5-DC.us.xo.net (65.106.3.206) 40.099 ms 40.297 ms 40.144 ms 10 71.5.190.110.ptr.us.xo.net (71.5.190.110) 40.350 ms 40.047 ms 40.093 ms 11 64.244.254.238 (64.244.254.238) 41.792 ms 41.528 ms 41.304 ms 12 edg-r-01-vlan12.net.dc2.netsol.com (205.178.191.14) 40.998 ms 41.624 ms 40.978 ms 13 205.178.182.6 (205.178.182.6) 41.389 ms 41.045 ms 41.121 ms 14 mail.networksolutionsemail.com (205.178.149.7) 41.339 ms 41.517 ms 41.291 ms Any thoughts? I also opened a ticket with Cogent, our provider in the main office. Thanks! Joe Johnson Senior Systems Engineer InnerWorkings, Inc. Managed Print & Promotional Solutions 600 West Chicago Avenue, Suite 850 Chicago, IL 60654 Phone: 312.676.6873 Fax: 312.604.5487 joe.johnson(a)inwk.com www.inwk.com NASDAQ: INWK

1 1

RE: IP Fragmentation (correction)
by John Lee 20 Aug '08

20 Aug '08

Correction. TTL needs to be set to sufficiently large number of hops to allow the packet to get through the number of hops and the timers need to be set to allow the packet to transit the network and the low speed links before timing out and retransmitting the packet. John (ISDN) Lee ________________________________________ From: John Lee [john(a)internetassociatesllc.com] Sent: Wednesday, August 20, 2008 2:10 PM To: Glen Kent; OPS Gurus Subject: RE: IP Fragmentation Glen, With the v4 networks that I have worked on in the past, they did not do end to end MTU discovery before sending packets. The TTL had to be set appropriately so that if you had low speed links, for example, the packet and response would get through in time. On our DS3 (T3) and OC-3c packet links we did 4k, 9k, and 16k packet sizes for video and file transfers. At the other end of the spectrum are civilian and military systems with tactical links, both wired and radio, with low bit rates and header compression on IP and TCP packets. Speeds range from 300 -9,600 bps, 16k, 32k, 64k and Nx64k bps links that can do packet fragmentation and adding proprietary ECC codes for the radio links. Some systems strip the IP packet and use standard or non-standard link layer protocols across the mediums. Some of these systems are store and forward so that the computer/router that is connected to the low speed link will ack the packet for the high speed network connection and buffer it up until it can be sent on the lower speed system. IMHO current IPv6 protocols ignore the lower end segment by specifying the lowest MTU for the circuit be the MTU for the entire circuit and not allow fragmentation. I do not see this as an efficient use of high speed network resources and local link management can handle fragmentation just fine. John (ISDN) Lee A slightly different History Channel. ________________________________________ From: Glen Kent [glen.kent(a)gmail.com] Sent: Wednesday, August 20, 2008 12:13 PM To: OPS Gurus Subject: IP Fragmentation Hi, Do transit routers in the wild actually get to do IP fragmentation these days? I was wondering if routers actually do it or not, because the source usually discovers the path MTU and sends its data with the least supported MTU. Is this true? Even if this is, then this would break for multicast IP. The source cannot determine which receivers would get interested in the traffic and what capacities the links connecting them would support. So, a source would send IP packets with some size, and theres a chance that one of the routers *may* have to fragment those IP packets before passing it on to the next router. I would wager that the vendors and operators would want to avoid IP fragmentation since thats usually done in SW (unless you've got a very powerful ASIC or your box is NP based). Thanks, Glen

1 0

uTorrent, IPv6
by Nathan Ward 20 Aug '08

20 Aug '08

Sit up and pay attention, even if you don't now run IPv6, or even if you don't ever intend to run IPv6. Your off-net bandwidth is going to increase, unless you put some relays in. As a friend of mine just said to me: "Welcome to your v6-enabled transit network, whether you like it or not ;-)". uTorrent 1.8 is out, as of Aug 9. uTorrent actively enables IPv6 on XP SP2 and Vista machines in the install process (by default, it can be turned off). IPv6 is turned on, on lots of PCs. uTorrent does DHT, so that uTorrent users will talk to eachother to exchange peers - IPv6 does not require tracker support. uTorrent (as far as I understand) knows how to set IPV6_PROTECTION_LEVEL appropriately on sockets, so that Teredo is actually used. What does this mean? It means that many uTorrent end users will have Teredo addresses, and many will have 6to4 addresses. As we roll out IPv6 globally, more and more uTorrent users will have non-tunnelled IPv6 addresses. uTorrent users move **LOTS** of data. This means relay load. There are very few 6to4 relays around the world. There are fewer Teredo relays. If you run a network today and do not have 6to4 and Teredo relays, traffic between a 6to4 end user and a Teredo end user will go off-net. That costs you money. So, if you run a network today, deploy 6to4 and Teredo relays, regardless of whether you have customer facing IPv6 or not. If you serve IPv6 content, you are already running Teredo and 6to4 relays, so that Windows Vista users get near to IPv4-speed access to your IPv6 content, right? Right... Azureus does IPv6 now, but does not turn on IPv6, and does not set the IPV6_PROTECTION_LEVEL (as far as I understand), so Teredo is not used. Windows uses 6to4 if you have a non-RFC1918 address, and it uses Teredo if you do not (typically, this means you are behind NAT). With the huge amount of end users behind NAT, this means that uTorrent will have a much wider effect than Azureus has had. Running a relay *does not* mean that people outside your network can use it. - Who uses your 6to4 relay is controlled by how far you advertise the well known IPv4 and IPv6 prefixes. - Your Teredo relay is used only by Teredo clients trying to get to your non-Teredo connected users (ie your 6to4 or natively connected users). 6to4 relays can be Cisco boxes, Juniper NetScreen, FreeBSD, Linux, etc. OpenBSD does not have 6to4 support. Teredo relays can be Windows boxes, or Linux/FreeBSD/etc. boxes running `Miredo'. I have pre-built FreeBSD images that run both 6to4 and Teredo relays, and can talk BGP to your network. They are about 30MB, so will run on a compact flash card, and will happily run on anything from a 133Mhz 468 (ie. Soekris net4501) through to whatever top of the line server you have. They can also optionally do this "Tui" thing, which uses 6to4 and BGP to build direct IPv6 over IPv4 tunnels to everyone else with one of these boxes, without you having to configure each tunnel manually - I have some central route-servers. Optional, experimental, YMMV, etc. Thankfully, both Teredo and 6to4 use anycast for relay discovery, so if you have load problems you can deploy more of these for the cost of a server. As per usual, I'm giving it away free, see the following URL, or contact me off list: http://www.braintrust.co.nz/tui/ If you don't care about the "Tui" stuff, ignore those parts of the document, the rest will work just fine. ps. I'm looking at packet dumps of things right now, captured from torrent clients from the last wee while. I'll be rambling about this and pointing at pretty graphs in about a week at APNIC26. -- Nathan Ward

6 11

Open Source CA / PKI
by Jon Kibler 20 Aug '08

20 Aug '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings, I am looking at deploying an open source CA/PKI for a client. It would be only for internal users and systems. It would have to manage a few hundred certificates against the organization's self-signed root cert. It would be installed on a CentOS 5.x platform. I have looked at OpenCA and Dogtag. Any other packages I should look at? Does anyone have any opinions as to the pros and cons of either of these packages or thoughts/comments/experience with other similar packages? I would especially be interested in your experience with building / installing the package and your opinion of the documentation available. TIA for your help! Jon Kibler - -- Jon R. Kibler Chief Technical Officer Advanced Systems Engineering Technology, Inc. Charleston, SC USA o: 843-849-8214 c: 843-224-2494 s: 843-564-4224 My PGP Fingerprint is: BAA2 1F2C 5543 5D25 4636 A392 515C 5045 CF39 4253 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkiqkSQACgkQUVxQRc85QlPlGACgoAFitZXNLnEJfxKXgah00Vi8 dl4AniBPAJ3zy6krTKkFY3JQRdHAU6b9 =PGoy -----END PGP SIGNATURE-----

2 1

Smallest netblock that providers will accept?
by Mike Lyon 19 Aug '08

19 Aug '08

Hello All, I am curious as to the routing polices of the bigger providers such as ATT, L3, Internap, Qwest, Etc Etc... Is there a standard size netblock that these providers will accept? For instance, if customer "A" gets a /22 from ARIN and his upstream provider is ATT and L3, what would the smallest block be that those providers would accept from customer "A"? Would they accept something as small as a /24? Thanks, Mike

5 4

OT: Again, sorry for the noise
by Joe Blanchard 19 Aug '08

19 Aug '08

Hughes Net DNS issue. I am 72.169.156.122. Notice the Source is port 53, destination is 20xx. Because I am not a large company like McDonalds this apparently cannot be resolved. No. Time Source Destination Protocol Info 190 51.553317 72.169.156.121 72.169.156.122 DNS Standard query response[Packet size limited during capture] Frame 190 (122 bytes on wire, 96 bytes captured) Ethernet II, Src: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a), Dst: Intel_a6:bb:04 (00:d0:b7:a6:bb:04) Internet Protocol, Src: 72.169.156.121 (72.169.156.121), Dst: 72.169.156.122 (72.169.156.122) User Datagram Protocol, Src Port: domain (53), Dst Port: raid-sf (2014) Domain Name System (response) [Packet size limited during capture: DNS truncated] No. Time Source Destination Protocol Info 191 51.553759 72.169.156.122 72.169.156.121 ICMP Destination unreachable (Port unreachable)[Packet size limited during capture] Frame 191 (150 bytes on wire, 96 bytes captured) Ethernet II, Src: Intel_a6:bb:04 (00:d0:b7:a6:bb:04), Dst: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a) Internet Protocol, Src: 72.169.156.122 (72.169.156.122), Dst: 72.169.156.121 (72.169.156.121) Internet Control Message Protocol [Packet size limited during capture: IP truncated] No. Time Source Destination Protocol Info 192 51.643105 194.72.238.11 72.169.156.122 DNS Standard query response A 83.138.190.203 Frame 192 (96 bytes on wire, 96 bytes captured) Ethernet II, Src: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a), Dst: Intel_a6:bb:04 (00:d0:b7:a6:bb:04) Internet Protocol, Src: 194.72.238.11 (194.72.238.11), Dst: 72.169.156.122 (72.169.156.122) User Datagram Protocol, Src Port: domain (53), Dst Port: 11603 (11603) Domain Name System (response) No. Time Source Destination Protocol Info 193 51.648410 192.168.1.20 83.138.190.203 TCP vsat-control > http [SYN] Seq=0 Win=65535 Len=0 MSS=1460 Frame 193 (62 bytes on wire, 62 bytes captured) Ethernet II, Src: Intel_a6:bb:04 (00:d0:b7:a6:bb:04), Dst: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a) Internet Protocol, Src: 192.168.1.20 (192.168.1.20), Dst: 83.138.190.203 (83.138.190.203) Transmission Control Protocol, Src Port: vsat-control (1880), Dst Port: http (80), Seq: 0, Len: 0 No. Time Source Destination Protocol Info 194 51.650140 83.138.190.203 72.169.156.122 TCP http > 23230 [SYN, ACK] Seq=0 Ack=0 Win=8192 Len=0 MSS=1460 Frame 194 (64 bytes on wire, 64 bytes captured) Ethernet II, Src: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a), Dst: Intel_a6:bb:04 (00:d0:b7:a6:bb:04) Internet Protocol, Src: 83.138.190.203 (83.138.190.203), Dst: 72.169.156.122 (72.169.156.122) Transmission Control Protocol, Src Port: http (80), Dst Port: 23230 (23230), Seq: 0, Ack: 0, Len: 0 No. Time Source Destination Protocol Info 195 51.650489 192.168.1.20 83.138.190.203 TCP vsat-control > http [ACK] Seq=1 Ack=1 Win=65535 Len=0 Frame 195 (54 bytes on wire, 54 bytes captured) Ethernet II, Src: Intel_a6:bb:04 (00:d0:b7:a6:bb:04), Dst: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a) Internet Protocol, Src: 192.168.1.20 (192.168.1.20), Dst: 83.138.190.203 (83.138.190.203) Transmission Control Protocol, Src Port: vsat-control (1880), Dst Port: http (80), Seq: 1, Ack: 1, Len: 0 No. Time Source Destination Protocol Info 196 51.651024 192.168.1.20 83.138.190.203 HTTP GET /site_report?url=http://www.rocknyou.c [Packet size limited during capture] Frame 196 (728 bytes on wire, 96 bytes captured) Ethernet II, Src: Intel_a6:bb:04 (00:d0:b7:a6:bb:04), Dst: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a) Internet Protocol, Src: 192.168.1.20 (192.168.1.20), Dst: 83.138.190.203 (83.138.190.203) Transmission Control Protocol, Src Port: vsat-control (1880), Dst Port: http (80), Seq: 1, Ack: 1, Len: 674 Hypertext Transfer Protocol [Packet size limited during capture: HTTP truncated] No. Time Source Destination Protocol Info 197 51.753050 83.138.190.203 72.169.156.122 TCP http > 23230 [ACK] Seq=1 Ack=674 Win=8192 Len=0 Frame 197 (64 bytes on wire, 64 bytes captured) Ethernet II, Src: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a), Dst: Intel_a6:bb:04 (00:d0:b7:a6:bb:04) Internet Protocol, Src: 83.138.190.203 (83.138.190.203), Dst: 72.169.156.122 (72.169.156.122) Transmission Control Protocol, Src Port: http (80), Dst Port: 23230 (23230), Seq: 1, Ack: 674, Len: 0 No. Time Source Destination Protocol Info 198 51.882510 72.169.156.121 72.169.156.122 DNS Standard query response[Packet size limited during capture] Frame 198 (122 bytes on wire, 96 bytes captured) Ethernet II, Src: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a), Dst: Intel_a6:bb:04 (00:d0:b7:a6:bb:04) Internet Protocol, Src: 72.169.156.121 (72.169.156.121), Dst: 72.169.156.122 (72.169.156.122) User Datagram Protocol, Src Port: domain (53), Dst Port: bootclient (2017) Domain Name System (response) [Packet size limited during capture: DNS truncated] No. Time Source Destination Protocol Info 199 51.882889 72.169.156.122 72.169.156.121 ICMP Destination unreachable (Port unreachable)[Packet size limited during capture] Frame 199 (150 bytes on wire, 96 bytes captured) Ethernet II, Src: Intel_a6:bb:04 (00:d0:b7:a6:bb:04), Dst: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a) Internet Protocol, Src: 72.169.156.122 (72.169.156.122), Dst: 72.169.156.121 (72.169.156.121) Internet Control Message Protocol [Packet size limited during capture: IP truncated] No. Time Source Destination Protocol Info 200 52.292437 72.169.156.121 72.169.156.122 DNS Standard query response[Packet size limited during capture] Frame 200 (111 bytes on wire, 96 bytes captured) Ethernet II, Src: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a), Dst: Intel_a6:bb:04 (00:d0:b7:a6:bb:04) Internet Protocol, Src: 72.169.156.121 (72.169.156.121), Dst: 72.169.156.122 (72.169.156.122) User Datagram Protocol, Src Port: domain (53), Dst Port: rellpack (2018) Domain Name System (response) [Packet size limited during capture: DNS truncated] No. Time Source Destination Protocol Info 201 52.292895 72.169.156.122 72.169.156.121 ICMP Destination unreachable (Port unreachable)[Packet size limited during capture] Frame 201 (139 bytes on wire, 96 bytes captured) Ethernet II, Src: Intel_a6:bb:04 (00:d0:b7:a6:bb:04), Dst: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a) Internet Protocol, Src: 72.169.156.122 (72.169.156.122), Dst: 72.169.156.121 (72.169.156.121) Internet Control Message Protocol [Packet size limited during capture: IP truncated] No. Time Source Destination Protocol Info 202 53.168141 192.168.1.52 64.233.179.9 DNS Standard query A sb.l.google.com Frame 202 (86 bytes on wire, 86 bytes captured) Ethernet II, Src: Intel_a6:bb:04 (00:d0:b7:a6:bb:04), Dst: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a) Internet Protocol, Src: 192.168.1.52 (192.168.1.52), Dst: 64.233.179.9 (64.233.179.9) User Datagram Protocol, Src Port: 32876 (32876), Dst Port: domain (53) Domain Name System (query) No. Time Source Destination Protocol Info 203 53.302397 72.169.156.121 72.169.156.122 DNS Standard query response[Packet size limited during capture] Frame 203 (111 bytes on wire, 96 bytes captured) Ethernet II, Src: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a), Dst: Intel_a6:bb:04 (00:d0:b7:a6:bb:04) Internet Protocol, Src: 72.169.156.121 (72.169.156.121), Dst: 72.169.156.122 (72.169.156.122) User Datagram Protocol, Src Port: domain (53), Dst Port: raid-cs (2015) Domain Name System (response) [Packet size limited during capture: DNS truncated] No. Time Source Destination Protocol Info 204 53.302775 72.169.156.122 72.169.156.121 ICMP Destination unreachable (Port unreachable)[Packet size limited during capture] Frame 204 (139 bytes on wire, 96 bytes captured) Ethernet II, Src: Intel_a6:bb:04 (00:d0:b7:a6:bb:04), Dst: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a) Internet Protocol, Src: 72.169.156.122 (72.169.156.122), Dst: 72.169.156.121 (72.169.156.121) Internet Control Message Protocol [Packet size limited during capture: IP truncated] No. Time Source Destination Protocol Info 205 53.313593 72.169.156.121 72.169.156.122 DNS Standard query response[Packet size limited during capture] Frame 205 (122 bytes on wire, 96 bytes captured) Ethernet II, Src: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a), Dst: Intel_a6:bb:04 (00:d0:b7:a6:bb:04) Internet Protocol, Src: 72.169.156.121 (72.169.156.121), Dst: 72.169.156.122 (72.169.156.122) User Datagram Protocol, Src Port: domain (53), Dst Port: about (2019) Domain Name System (response) [Packet size limited during capture: DNS truncated] No. Time Source Destination Protocol Info 206 53.313916 72.169.156.122 72.169.156.121 ICMP Destination unreachable (Port unreachable)[Packet size limited during capture] Frame 206 (150 bytes on wire, 96 bytes captured) Ethernet II, Src: Intel_a6:bb:04 (00:d0:b7:a6:bb:04), Dst: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a) Internet Protocol, Src: 72.169.156.122 (72.169.156.122), Dst: 72.169.156.121 (72.169.156.121) Internet Control Message Protocol [Packet size limited during capture: IP truncated] No. Time Source Destination Protocol Info 207 53.972359 72.169.156.121 72.169.156.122 DNS Standard query response[Packet size limited during capture] Frame 207 (122 bytes on wire, 96 bytes captured) Ethernet II, Src: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a), Dst: Intel_a6:bb:04 (00:d0:b7:a6:bb:04) Internet Protocol, Src: 72.169.156.121 (72.169.156.121), Dst: 72.169.156.122 (72.169.156.122) User Datagram Protocol, Src Port: domain (53), Dst Port: emce (2004) Domain Name System (response) [Packet size limited during capture: DNS truncated] No. Time Source Destination Protocol Info 208 53.972751 72.169.156.122 72.169.156.121 ICMP Destination unreachable (Port unreachable)[Packet size limited during capture] Frame 208 (150 bytes on wire, 96 bytes captured) Ethernet II, Src: Intel_a6:bb:04 (00:d0:b7:a6:bb:04), Dst: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a) Internet Protocol, Src: 72.169.156.122 (72.169.156.122), Dst: 72.169.156.121 (72.169.156.121) Internet Control Message Protocol [Packet size limited during capture: IP truncated] No. Time Source Destination Protocol Info 209 53.992561 64.233.179.9 72.169.156.122 DNS Standard query response A 209.85.135.136 Frame 209 (91 bytes on wire, 91 bytes captured) Ethernet II, Src: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a), Dst: Intel_a6:bb:04 (00:d0:b7:a6:bb:04) Internet Protocol, Src: 64.233.179.9 (64.233.179.9), Dst: 72.169.156.122 (72.169.156.122) User Datagram Protocol, Src Port: domain (53), Dst Port: 11604 (11604) Domain Name System (response) No. Time Source Destination Protocol Info 210 53.994612 192.168.1.20 209.85.135.136 TCP ibm-mqseries2 > http [SYN] Seq=0 Win=65535 Len=0 MSS=1460 Frame 210 (62 bytes on wire, 62 bytes captured) Ethernet II, Src: Intel_a6:bb:04 (00:d0:b7:a6:bb:04), Dst: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a) Internet Protocol, Src: 192.168.1.20 (192.168.1.20), Dst: 209.85.135.136 (209.85.135.136) Transmission Control Protocol, Src Port: ibm-mqseries2 (1881), Dst Port: http (80), Seq: 0, Len: 0 No. Time Source Destination Protocol Info 211 53.996267 209.85.135.136 72.169.156.122 TCP http > 23231 [SYN, ACK] Seq=0 Ack=0 Win=8192 Len=0 MSS=1460 Frame 211 (64 bytes on wire, 64 bytes captured) Ethernet II, Src: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a), Dst: Intel_a6:bb:04 (00:d0:b7:a6:bb:04) Internet Protocol, Src: 209.85.135.136 (209.85.135.136), Dst: 72.169.156.122 (72.169.156.122) Transmission Control Protocol, Src Port: http (80), Dst Port: 23231 (23231), Seq: 0, Ack: 0, Len: 0 No. Time Source Destination Protocol Info 212 53.996581 192.168.1.20 209.85.135.136 TCP ibm-mqseries2 > http [ACK] Seq=1 Ack=1 Win=65535 Len=0 Frame 212 (54 bytes on wire, 54 bytes captured) Ethernet II, Src: Intel_a6:bb:04 (00:d0:b7:a6:bb:04), Dst: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a) Internet Protocol, Src: 192.168.1.20 (192.168.1.20), Dst: 209.85.135.136 (209.85.135.136) Transmission Control Protocol, Src Port: ibm-mqseries2 (1881), Dst Port: http (80), Seq: 1, Ack: 1, Len: 0 No. Time Source Destination Protocol Info 213 53.997152 192.168.1.20 209.85.135.136 HTTP GET /safebrowsing/update?client=navclient- [Packet size limited during capture] Frame 213 (858 bytes on wire, 96 bytes captured) Ethernet II, Src: Intel_a6:bb:04 (00:d0:b7:a6:bb:04), Dst: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a) Internet Protocol, Src: 192.168.1.20 (192.168.1.20), Dst: 209.85.135.136 (209.85.135.136) Transmission Control Protocol, Src Port: ibm-mqseries2 (1881), Dst Port: http (80), Seq: 1, Ack: 1, Len: 804 Hypertext Transfer Protocol [Packet size limited during capture: HTTP truncated] No. Time Source Destination Protocol Info 214 54.092336 209.85.135.136 72.169.156.122 TCP http > 23231 [ACK] Seq=1 Ack=804 Win=8192 Len=0 Frame 214 (64 bytes on wire, 64 bytes captured) Ethernet II, Src: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a), Dst: Intel_a6:bb:04 (00:d0:b7:a6:bb:04) Internet Protocol, Src: 209.85.135.136 (209.85.135.136), Dst: 72.169.156.122 (72.169.156.122) Transmission Control Protocol, Src Port: http (80), Dst Port: 23231 (23231), Seq: 1, Ack: 804, Len: 0 No. Time Source Destination Protocol Info 215 54.242631 72.169.156.121 72.169.156.122 DNS Standard query response[Packet size limited during capture] Frame 215 (111 bytes on wire, 96 bytes captured) Ethernet II, Src: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a), Dst: Intel_a6:bb:04 (00:d0:b7:a6:bb:04) Internet Protocol, Src: 72.169.156.121 (72.169.156.121), Dst: 72.169.156.122 (72.169.156.122) User Datagram Protocol, Src Port: domain (53), Dst Port: wizard (2001) Domain Name System (response) [Packet size limited during capture: DNS truncated] No. Time Source Destination Protocol Info 216 54.242992 72.169.156.122 72.169.156.121 ICMP Destination unreachable (Port unreachable)[Packet size limited during capture] Frame 216 (139 bytes on wire, 96 bytes captured) Ethernet II, Src: Intel_a6:bb:04 (00:d0:b7:a6:bb:04), Dst: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a) Internet Protocol, Src: 72.169.156.122 (72.169.156.122), Dst: 72.169.156.121 (72.169.156.121) Internet Control Message Protocol [Packet size limited during capture: IP truncated] No. Time Source Destination Protocol Info 217 55.342315 72.169.156.121 72.169.156.122 DNS Standard query response[Packet size limited during capture] Frame 217 (111 bytes on wire, 96 bytes captured) Ethernet II, Src: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a), Dst: Intel_a6:bb:04 (00:d0:b7:a6:bb:04) Internet Protocol, Src: 72.169.156.121 (72.169.156.121), Dst: 72.169.156.122 (72.169.156.122) User Datagram Protocol, Src Port: domain (53), Dst Port: raid-ac (2012) Domain Name System (response) [Packet size limited during capture: DNS truncated] No. Time Source Destination Protocol Info 218 55.342717 72.169.156.122 72.169.156.121 ICMP Destination unreachable (Port unreachable)[Packet size limited during capture] Frame 218 (139 bytes on wire, 96 bytes captured) Ethernet II, Src: Intel_a6:bb:04 (00:d0:b7:a6:bb:04), Dst: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a) Internet Protocol, Src: 72.169.156.122 (72.169.156.122), Dst: 72.169.156.121 (72.169.156.121) Internet Control Message Protocol [Packet size limited during capture: IP truncated] No. Time Source Destination Protocol Info 219 55.352865 72.169.156.121 72.169.156.122 DNS Standard query response[Packet size limited during capture] Frame 219 (111 bytes on wire, 96 bytes captured) Ethernet II, Src: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a), Dst: Intel_a6:bb:04 (00:d0:b7:a6:bb:04) Internet Protocol, Src: 72.169.156.121 (72.169.156.121), Dst: 72.169.156.122 (72.169.156.122) User Datagram Protocol, Src Port: domain (53), Dst Port: raid-cd (2006) Domain Name System (response) [Packet size limited during capture: DNS truncated] No. Time Source Destination Protocol Info 220 55.353181 72.169.156.122 72.169.156.121 ICMP Destination unreachable (Port unreachable)[Packet size limited during capture] Frame 220 (139 bytes on wire, 96 bytes captured) Ethernet II, Src: Intel_a6:bb:04 (00:d0:b7:a6:bb:04), Dst: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a) Internet Protocol, Src: 72.169.156.122 (72.169.156.122), Dst: 72.169.156.121 (72.169.156.121) Internet Control Message Protocol [Packet size limited during capture: IP truncated] No. Time Source Destination Protocol Info 221 55.702595 83.138.189.101 72.169.156.122 TCP http > 23229 [FIN, ACK] Seq=641 Ack=489 Win=8192 Len=0 Frame 221 (64 bytes on wire, 64 bytes captured) Ethernet II, Src: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a), Dst: Intel_a6:bb:04 (00:d0:b7:a6:bb:04) Internet Protocol, Src: 83.138.189.101 (83.138.189.101), Dst: 72.169.156.122 (72.169.156.122) Transmission Control Protocol, Src Port: http (80), Dst Port: 23229 (23229), Seq: 641, Ack: 489, Len: 0 No. Time Source Destination Protocol Info 222 55.702868 192.168.1.20 83.138.189.101 TCP nettgain-nms > http [ACK] Seq=490 Ack=642 Win=64895 Len=0 Frame 222 (54 bytes on wire, 54 bytes captured) Ethernet II, Src: Intel_a6:bb:04 (00:d0:b7:a6:bb:04), Dst: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a) Internet Protocol, Src: 192.168.1.20 (192.168.1.20), Dst: 83.138.189.101 (83.138.189.101) Transmission Control Protocol, Src Port: nettgain-nms (1879), Dst Port: http (80), Seq: 490, Ack: 642, Len: 0 No. Time Source Destination Protocol Info 223 55.927018 209.85.135.136 72.169.156.122 HTTP HTTP/1.1 200 OK [Packet size limited during capture] Frame 223 (277 bytes on wire, 96 bytes captured) Ethernet II, Src: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a), Dst: Intel_a6:bb:04 (00:d0:b7:a6:bb:04) Internet Protocol, Src: 209.85.135.136 (209.85.135.136), Dst: 72.169.156.122 (72.169.156.122) Transmission Control Protocol, Src Port: http (80), Dst Port: 23231 (23231), Seq: 1, Ack: 804, Len: 223 Hypertext Transfer Protocol [Packet size limited during capture: HTTP truncated] No. Time Source Destination Protocol Info 224 56.102125 192.168.1.20 209.85.135.136 TCP ibm-mqseries2 > http [ACK] Seq=805 Ack=224 Win=65312 Len=0 Frame 224 (54 bytes on wire, 54 bytes captured) Ethernet II, Src: Intel_a6:bb:04 (00:d0:b7:a6:bb:04), Dst: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a) Internet Protocol, Src: 192.168.1.20 (192.168.1.20), Dst: 209.85.135.136 (209.85.135.136) Transmission Control Protocol, Src Port: ibm-mqseries2 (1881), Dst Port: http (80), Seq: 805, Ack: 224, Len: 0 No. Time Source Destination Protocol Info 225 56.549076 Intel_a6:bb:04 HughesNe_b1:d4:3a ARP Who has 72.169.156.121? Tell 72.169.156.122 Frame 225 (42 bytes on wire, 42 bytes captured) Ethernet II, Src: Intel_a6:bb:04 (00:d0:b7:a6:bb:04), Dst: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a) Address Resolution Protocol (request) No. Time Source Destination Protocol Info 226 56.549636 HughesNe_b1:d4:3a Intel_a6:bb:04 ARP 72.169.156.121 is at 00:80:ae:b1:d4:3a Frame 226 (64 bytes on wire, 64 bytes captured) Ethernet II, Src: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a), Dst: Intel_a6:bb:04 (00:d0:b7:a6:bb:04) Address Resolution Protocol (reply) No. Time Source Destination Protocol Info 227 56.739182 192.168.1.20 83.138.189.101 TCP nettgain-nms > http [FIN, ACK] Seq=490 Ack=642 Win=64895 Len=0 Frame 227 (54 bytes on wire, 54 bytes captured) Ethernet II, Src: Intel_a6:bb:04 (00:d0:b7:a6:bb:04), Dst: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a) Internet Protocol, Src: 192.168.1.20 (192.168.1.20), Dst: 83.138.189.101 (83.138.189.101) Transmission Control Protocol, Src Port: nettgain-nms (1879), Dst Port: http (80), Seq: 490, Ack: 642, Len: 0 No. Time Source Destination Protocol Info 228 56.740833 83.138.189.101 72.169.156.122 TCP http > 23229 [ACK] Seq=642 Ack=490 Win=8192 Len=0 Frame 228 (64 bytes on wire, 64 bytes captured) Ethernet II, Src: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a), Dst: Intel_a6:bb:04 (00:d0:b7:a6:bb:04) Internet Protocol, Src: 83.138.189.101 (83.138.189.101), Dst: 72.169.156.122 (72.169.156.122) Transmission Control Protocol, Src Port: http (80), Dst Port: 23229 (23229), Seq: 642, Ack: 490, Len: 0 No. Time Source Destination Protocol Info 229 57.422373 72.169.156.121 72.169.156.122 DNS Standard query response[Packet size limited during capture] Frame 229 (111 bytes on wire, 96 bytes captured) Ethernet II, Src: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a), Dst: Intel_a6:bb:04 (00:d0:b7:a6:bb:04) Internet Protocol, Src: 72.169.156.121 (72.169.156.121), Dst: 72.169.156.122 (72.169.156.122) User Datagram Protocol, Src Port: domain (53), Dst Port: terminaldb (2008) Domain Name System (response) [Packet size limited during capture: DNS truncated] No. Time Source Destination Protocol Info 230 57.422849 72.169.156.122 72.169.156.121 ICMP Destination unreachable (Port unreachable)[Packet size limited during capture] Frame 230 (139 bytes on wire, 96 bytes captured) Ethernet II, Src: Intel_a6:bb:04 (00:d0:b7:a6:bb:04), Dst: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a) Internet Protocol, Src: 72.169.156.122 (72.169.156.122), Dst: 72.169.156.121 (72.169.156.121) Internet Control Message Protocol [Packet size limited during capture: IP truncated] No. Time Source Destination Protocol Info 231 57.536738 192.168.1.52 192.203.230.10 DNS Standard query PTR 9.179.233.64.in-addr.arpa Frame 231 (96 bytes on wire, 96 bytes captured) Ethernet II, Src: Intel_a6:bb:04 (00:d0:b7:a6:bb:04), Dst: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a) Internet Protocol, Src: 192.168.1.52 (192.168.1.52), Dst: 192.203.230.10 (192.203.230.10) User Datagram Protocol, Src Port: 32876 (32876), Dst Port: domain (53) Domain Name System (query) No. Time Source Destination Protocol Info 232 57.537106 192.168.1.52 192.203.230.10 DNS Standard query PTR 136.135.85.209.in-addr.arpa[Packet size limited during capture] Frame 232 (98 bytes on wire, 96 bytes captured) Ethernet II, Src: Intel_a6:bb:04 (00:d0:b7:a6:bb:04), Dst: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a) Internet Protocol, Src: 192.168.1.52 (192.168.1.52), Dst: 192.203.230.10 (192.203.230.10) User Datagram Protocol, Src Port: 32876 (32876), Dst Port: domain (53) Domain Name System (query) [Packet size limited during capture: DNS truncated] No. Time Source Destination Protocol Info 233 58.242859 192.203.230.10 72.169.156.122 DNS Standard query response[Packet size limited during capture] Frame 233 (265 bytes on wire, 96 bytes captured) Ethernet II, Src: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a), Dst: Intel_a6:bb:04 (00:d0:b7:a6:bb:04) Internet Protocol, Src: 192.203.230.10 (192.203.230.10), Dst: 72.169.156.122 (72.169.156.122) User Datagram Protocol, Src Port: domain (53), Dst Port: 11583 (11583) Domain Name System (response) [Packet size limited during capture: DNS truncated] No. Time Source Destination Protocol Info 234 58.452318 192.203.230.10 72.169.156.122 DNS Standard query response[Packet size limited during capture] Frame 234 (244 bytes on wire, 96 bytes captured) Ethernet II, Src: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a), Dst: Intel_a6:bb:04 (00:d0:b7:a6:bb:04) Internet Protocol, Src: 192.203.230.10 (192.203.230.10), Dst: 72.169.156.122 (72.169.156.122) User Datagram Protocol, Src Port: domain (53), Dst Port: 11583 (11583) Domain Name System (response) [Packet size limited during capture: DNS truncated] No. Time Source Destination Protocol Info 235 58.453303 192.168.1.52 216.239.36.10 DNS Standard query PTR 136.135.85.209.in-addr.arpa[Packet size limited during capture] Frame 235 (98 bytes on wire, 96 bytes captured) Ethernet II, Src: Intel_a6:bb:04 (00:d0:b7:a6:bb:04), Dst: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a) Internet Protocol, Src: 192.168.1.52 (192.168.1.52), Dst: 216.239.36.10 (216.239.36.10) User Datagram Protocol, Src Port: 32876 (32876), Dst Port: domain (53) Domain Name System (query) [Packet size limited during capture: DNS truncated] No. Time Source Destination Protocol Info 236 59.262026 216.239.36.10 72.169.156.122 DNS Standard query response[Packet size limited during capture] Frame 236 (269 bytes on wire, 96 bytes captured) Ethernet II, Src: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a), Dst: Intel_a6:bb:04 (00:d0:b7:a6:bb:04) Internet Protocol, Src: 216.239.36.10 (216.239.36.10), Dst: 72.169.156.122 (72.169.156.122) User Datagram Protocol, Src Port: domain (53), Dst Port: 11598 (11598) Domain Name System (response) [Packet size limited during capture: DNS truncated] No. Time Source Destination Protocol Info 237 59.461851 72.169.156.121 72.169.156.122 DNS Standard query response[Packet size limited during capture] Frame 237 (111 bytes on wire, 96 bytes captured) Ethernet II, Src: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a), Dst: Intel_a6:bb:04 (00:d0:b7:a6:bb:04) Internet Protocol, Src: 72.169.156.121 (72.169.156.121), Dst: 72.169.156.122 (72.169.156.122) User Datagram Protocol, Src Port: domain (53), Dst Port: raid-am (2007) Domain Name System (response) [Packet size limited during capture: DNS truncated] No. Time Source Destination Protocol Info 238 59.462284 72.169.156.122 72.169.156.121 ICMP Destination unreachable (Port unreachable)[Packet size limited during capture] Frame 238 (139 bytes on wire, 96 bytes captured) Ethernet II, Src: Intel_a6:bb:04 (00:d0:b7:a6:bb:04), Dst: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a) Internet Protocol, Src: 72.169.156.122 (72.169.156.122), Dst: 72.169.156.121 (72.169.156.121) Internet Control Message Protocol [Packet size limited during capture: IP truncated] No. Time Source Destination Protocol Info 239 59.471614 72.169.156.121 72.169.156.122 DNS Standard query response[Packet size limited during capture] Frame 239 (122 bytes on wire, 96 bytes captured) Ethernet II, Src: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a), Dst: Intel_a6:bb:04 (00:d0:b7:a6:bb:04) Internet Protocol, Src: 72.169.156.121 (72.169.156.121), Dst: 72.169.156.122 (72.169.156.122) User Datagram Protocol, Src Port: domain (53), Dst Port: bootserver (2016) Domain Name System (response) [Packet size limited during capture: DNS truncated] No. Time Source Destination Protocol Info 240 59.471954 72.169.156.122 72.169.156.121 ICMP Destination unreachable (Port unreachable)[Packet size limited during capture] Frame 240 (150 bytes on wire, 96 bytes captured) Ethernet II, Src: Intel_a6:bb:04 (00:d0:b7:a6:bb:04), Dst: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a) Internet Protocol, Src: 72.169.156.122 (72.169.156.122), Dst: 72.169.156.121 (72.169.156.121) Internet Control Message Protocol [Packet size limited during capture: IP truncated] No. Time Source Destination Protocol Info 241 60.921159 209.85.135.136 72.169.156.122 TCP http > 23231 [FIN, ACK] Seq=224 Ack=804 Win=8192 Len=0 Frame 241 (64 bytes on wire, 64 bytes captured) Ethernet II, Src: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a), Dst: Intel_a6:bb:04 (00:d0:b7:a6:bb:04) Internet Protocol, Src: 209.85.135.136 (209.85.135.136), Dst: 72.169.156.122 (72.169.156.122) Transmission Control Protocol, Src Port: http (80), Dst Port: 23231 (23231), Seq: 224, Ack: 804, Len: 0 No. Time Source Destination Protocol Info 242 60.921564 192.168.1.20 209.85.135.136 TCP ibm-mqseries2 > http [ACK] Seq=805 Ack=225 Win=65312 Len=0 Frame 242 (54 bytes on wire, 54 bytes captured) Ethernet II, Src: Intel_a6:bb:04 (00:d0:b7:a6:bb:04), Dst: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a) Internet Protocol, Src: 192.168.1.20 (192.168.1.20), Dst: 209.85.135.136 (209.85.135.136) Transmission Control Protocol, Src Port: ibm-mqseries2 (1881), Dst Port: http (80), Seq: 805, Ack: 225, Len: 0 No. Time Source Destination Protocol Info 243 61.351603 72.169.156.121 72.169.156.122 DNS Standard query response[Packet size limited during capture] Frame 243 (111 bytes on wire, 96 bytes captured) Ethernet II, Src: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a), Dst: Intel_a6:bb:04 (00:d0:b7:a6:bb:04) Internet Protocol, Src: 72.169.156.121 (72.169.156.121), Dst: 72.169.156.122 (72.169.156.122) User Datagram Protocol, Src Port: domain (53), Dst Port: globe (2002) Domain Name System (response) [Packet size limited during capture: DNS truncated] No. Time Source Destination Protocol Info 244 61.352031 72.169.156.122 72.169.156.121 ICMP Destination unreachable (Port unreachable)[Packet size limited during capture] Frame 244 (139 bytes on wire, 96 bytes captured) Ethernet II, Src: Intel_a6:bb:04 (00:d0:b7:a6:bb:04), Dst: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a) Internet Protocol, Src: 72.169.156.122 (72.169.156.122), Dst: 72.169.156.121 (72.169.156.121) Internet Control Message Protocol [Packet size limited during capture: IP truncated] No. Time Source Destination Protocol Info 245 61.361436 72.169.156.121 72.169.156.122 DNS Standard query response[Packet size limited during capture] Frame 245 (126 bytes on wire, 96 bytes captured) Ethernet II, Src: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a), Dst: Intel_a6:bb:04 (00:d0:b7:a6:bb:04) Internet Protocol, Src: 72.169.156.121 (72.169.156.121), Dst: 72.169.156.122 (72.169.156.122) User Datagram Protocol, Src Port: domain (53), Dst Port: raid-cd (2013) Domain Name System (response) [Packet size limited during capture: DNS truncated] No. Time Source Destination Protocol Info 246 61.361771 72.169.156.122 72.169.156.121 ICMP Destination unreachable (Port unreachable)[Packet size limited during capture] Frame 246 (154 bytes on wire, 96 bytes captured) Ethernet II, Src: Intel_a6:bb:04 (00:d0:b7:a6:bb:04), Dst: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a) Internet Protocol, Src: 72.169.156.122 (72.169.156.122), Dst: 72.169.156.121 (72.169.156.121) Internet Control Message Protocol [Packet size limited during capture: IP truncated] No. Time Source Destination Protocol Info 247 61.381786 72.169.156.121 72.169.156.122 DNS Standard query response[Packet size limited during capture] Frame 247 (122 bytes on wire, 96 bytes captured) Ethernet II, Src: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a), Dst: Intel_a6:bb:04 (00:d0:b7:a6:bb:04) Internet Protocol, Src: 72.169.156.121 (72.169.156.121), Dst: 72.169.156.122 (72.169.156.122) User Datagram Protocol, Src Port: domain (53), Dst Port: servserv (2011) Domain Name System (response) [Packet size limited during capture: DNS truncated] No. Time Source Destination Protocol Info 248 61.382100 72.169.156.122 72.169.156.121 ICMP Destination unreachable (Port unreachable)[Packet size limited during capture] Frame 248 (150 bytes on wire, 96 bytes captured) Ethernet II, Src: Intel_a6:bb:04 (00:d0:b7:a6:bb:04), Dst: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a) Internet Protocol, Src: 72.169.156.122 (72.169.156.122), Dst: 72.169.156.121 (72.169.156.121) Internet Control Message Protocol [Packet size limited during capture: IP truncated] No. Time Source Destination Protocol Info 249 63.311326 72.169.156.121 72.169.156.122 DNS Standard query response[Packet size limited during capture] Frame 249 (126 bytes on wire, 96 bytes captured) Ethernet II, Src: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a), Dst: Intel_a6:bb:04 (00:d0:b7:a6:bb:04) Internet Protocol, Src: 72.169.156.121 (72.169.156.121), Dst: 72.169.156.122 (72.169.156.122) User Datagram Protocol, Src Port: domain (53), Dst Port: oracle (2005) Domain Name System (response) [Packet size limited during capture: DNS truncated] No. Time Source Destination Protocol Info 250 63.311777 72.169.156.122 72.169.156.121 ICMP Destination unreachable (Port unreachable)[Packet size limited during capture] Frame 250 (154 bytes on wire, 96 bytes captured) Ethernet II, Src: Intel_a6:bb:04 (00:d0:b7:a6:bb:04), Dst: HughesNe_b1:d4:3a (00:80:ae:b1:d4:3a) Internet Protocol, Src: 72.169.156.122 (72.169.156.122), Dst: 72.169.156.121 (72.169.156.121) Internet Control Message Protocol [Packet size limited during capture: IP truncated]

2 1

SLAAC(autoconfig) vs DHCPv6
by Scott Weeks 19 Aug '08

19 Aug '08

---------- trejrco(a)gmail.com wrote: ------------ From: "TJ" <trejrco(a)gmail.com> As a general rule, most clients are following the "If we gave them static IPv4 addresses we will give them static IPv6 addresses" (infrastructure, servers, etc). The whole SLAAC(autoconfig) vs DHCPv6 is a separate (albeit related) conversation ... ---------------------------------------------------- I'm still an IPv6 wussie and would like to learn more before moving forward, so would anyone care to share info on experiences with this decision? scott

12 19

RouterOS performance?
by William Pitcock 19 Aug '08

19 Aug '08

Hi, We're looking at using Mikrotik's RouterOS for some some sort of software routing solution as part of our network in combination with supervised layer3 switching doing most likely some sort of limited BGP. Does anyone else here run it? Is it any good? Is it better than e.g. vyatta? If RouterOS and Vyatta both suck, is there any decent software routing solution? Our network is small (4 /24s) and we only need to push roughly 1-2gbit at the moment. Experiences with both would be appreciated. Thanks! William

8 10

RE: SLAAC(autoconfig) vs DHCPv6 vs IP Address Lifecycle Management
by John Lee 19 Aug '08

19 Aug '08

Scott, There are solutions that support both static, quasi-static, also driving DHCPv6 servers and Dynamic DNS updates. There are networks that have deployed IPal to automate and consolidate their IPv4 and IPv6 block allocations and interface assignments. Router Prefix delegation, SLAAC and DHCPv6 were implemented to have a more automated method of IPv6 address assignments because of the large potential number of IPv6 addresses to be assigned in a next generation network. IPal does address block assignments for Prefix delegation, SLAAC and DHCPv6 support. It does IPv6 interface assignments of /64 EUI-64, /64 random, /126, /127 and /128 and generate the Dynamic DNS updates for those assignments. E-mail me off list if you want any additional information. John (ISDN) Lee ________________________________________ From: Howard C. Berkowitz [hcb(a)netcases.net] Sent: Monday, August 18, 2008 3:42 PM To: nanog(a)nanog.org Subject: RE: SLAAC(autoconfig) vs DHCPv6 To try to stay operational about this, I have a reality testing question I've used in IPv4 and, for that matter, bridged networks: If you want to test a resource, be it the end user or an infrastructure interface, how do you know how to foo it (foo being some value of ping, traceroute, look it up in SNMP/NetFlow, etc)? I submit that if you use dynamic assignment of any sort, you really have to have DNS dynamic update, so you can use a known name to query the function that's indexed by address. Otherwise, static addresses become rather necessary if you want to check a resource. This was especially a question when L2 was "in" and routing was out: how do you ping a MAC address? Howard -----Original Message----- From: Scott Weeks [mailto:surfer@mauigateway.com] Sent: Monday, August 18, 2008 3:34 PM To: nanog(a)nanog.org Subject: SLAAC(autoconfig) vs DHCPv6 ---------- trejrco(a)gmail.com wrote: ------------ From: "TJ" <trejrco(a)gmail.com> As a general rule, most clients are following the "If we gave them static IPv4 addresses we will give them static IPv6 addresses" (infrastructure, servers, etc). The whole SLAAC(autoconfig) vs DHCPv6 is a separate (albeit related) conversation ... ---------------------------------------------------- I'm still an IPv6 wussie and would like to learn more before moving forward, so would anyone care to share info on experiences with this decision? scott

1 0

labovitz: "The End is Near, but is IPv6?" (seen on slashdot today)
by Paul Vixie 19 Aug '08

19 Aug '08

http://asert.arbornetworks.com/2008/08/the-end-is-near-but-is-ipv6/ -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

1 0