v6

Mailman List Mirror (Read Only)
1

so i have a local address

    # ifconfig wi0
    wi0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
      inet6 fe80::260:1dff:fe23:c352%wi0 prefixlen 64 scopeid 0x6
      inet 192.35.167.202 netmask 0xfffffc00 broadcast 192.35.167.255
      ether 00:60:1d:23:c3:52
      media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps)
      status: associated
      ssid nanog 1:""
      stationname roam.psg.com
      channel 11 authmode OPEN powersavemode OFF powersavesleep 100
      wepmode OFF weptxkey 1

and can ping the local exit

    # ping6 fe80::208:a3ff:fe8b:b5c2%wi0
    PING6(56=40+8+8 bytes) fe80::260:1dff:fe23:c352%wi0 --> fe80::208:a3ff:fe8b:b5c2%wi0
    16 bytes from fe80::208:a3ff:fe8b:b5c2%wi0, icmp_seq=0 hlim=64 time=55.512 ms
    16 bytes from fe80::208:a3ff:fe8b:b5c2%wi0, icmp_seq=1 hlim=64 time=3.012 ms

though the rtt is a bit scary

but i am not getting a global address

randy

2

Hi,
I can get a global address.

$ ping6 www.kame.net

Pinging kame220.kame.net [2001:200:0:4819:210:f3ff:fe03:4d0]
from 2001:468:1000:1:4094:f5ea:dce8:bca0 with 32 bytes of data:

Reply from 2001:200:0:4819:210:f3ff:fe03:4d0: bytes=32 time=255ms
Reply from 2001:200:0:4819:210:f3ff:fe03:4d0: bytes=32 time=198ms

Ping statistics for 2001:200:0:4819:210:f3ff:fe03:4d0:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 198ms, Maximum = 255ms, Average = 226ms
Control-C

In article <E17HP1O-0001Mw-00@roam.psg.com>

3

IPv6 became operational around 10:50. Let us know if you continue to see
problems.

Thanks

    Bob Stovall
    MichNet Operations
    Merit Network, Inc.

4

I can get a global address.

i can now too!

it was the merit router.

randy

5

IPv6 became operational around 10:50. Let us know if you continue to see
problems.

i can see the dancing kame at http://www.kame.net

randy

6

Hey there I am writing a paper for slamming ICANN a little more - how many
protocols are you folks actually routing today? 10, 20, and what are they?
Is there a standard list of protocols that all carriers support?

Todd

7

Hmm.. *all* carriers?

The IPv4 variants of TCP, UDP, and ICMP.

Even IPv6 and multicast coverage are spotty at best, and anything else better
have an IPv4 encapsulation if you want it to actually go end-to-end.

(Yes, I know BGP gets around - but that's not routed so much as relayed peer-to-peer).

8

IP. :slight_smile:

9

I'm all for slamming ICANN, so maybe you could elaborate on your approach
a little more?

I'm not sure where you're going with this...and I don't think you're
asking the question you intend to ask. By "protocols" do you mean to
include services such as DNS, SMTP, etc?

Because, to answer your question directly, the list of protocols that all
carries support includes IP, TCP, UDP, and ICMP. Some might do IPv6, but
don't count on it. So how do you get to 10 or 20?

Andy

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Andy Dills 301-682-9972
Xecunet, LLC www.xecu.net
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Dialup * Webhosting * E-Commerce * High-Speed Access

10

Date: Wed, 12 Jun 2002 09:33:09 -0700
From: todd glassey

Hey there I am writing a paper for slamming ICANN a little
more - how many protocols are you folks actually routing
today? 10, 20, and what are they? Is there a standard list
of protocols that all carriers support?

I'd guess that many route:

IPv4, IPv6, ICMP, UDP, TCP, IGMP, OSPF, RSVP, IPIP, ESP, AH,
EIGRP, L2TP, ISIS.

That's 14 or so... of course, I may have missed some or put too
much faith in another.

Eddy

11

What do you mean by protocols? Most people just route IPv4 (tcp/udp/icmp)a
few folks route IPv6. Or do you mean the protocols for services that run
over tcp/udp? I don't think anyone routes that, filter it possibly but not
route it.

Sameer

12

Routing protocols or routed protocols?

13

Don't feed the trolls. Been done already:
http://www1.ietf.org/mail-archive/ietf/Current/msg15816.html

-Hank

14

I wouldn't call it an isp if they only allowed tcp, udp and icmp.
It should be all ip protocols.

There can be a maximum of 256 of them. The isp shouldn't care what
the ipheader->protocol field is set to.

Regards
Magnus

15

Thus spake "Magnus Boden" <mb@ozaba.cx>

I wouldn't call it an isp if they only allowed tcp, udp and icmp.
It should be all ip protocols.

There can be a maximum of 256 of them. The isp shouldn't care what
the ipheader->protocol field is set to.

There is at least one ISP here in the US that filters protocol 50 (IPsec ESP).
Does that mean they're really not an ISP?

S

16

Those networks are announcing >/29 prefixes... I see about 109 /32
networks... Could their uplinks/peers take care about filtering them?

The worst case is AS17175 which is announcing 222 prefixes and has ONE
SINGLE route-object?!?
Why are those routes comming across the Internet? They should not be
announced at all!

SOURCE: http://tools.swinog.ch/wwwbin/lookingglass

regards,
Pascal

17

How can you forget the king of all protocols, RIP? :slight_smile:

But seriously, I still don't understand the semantics. If you're "routing"
those protocols, you're also routing SMTP, DNS, POP, IMAP, HTTP,
HTTPS...wacky multiplayer game protocols...anything that runs on IP,
basically.

So you're either routing IP, or you're routing `wc -l /etc/services`
number of services plus possibly infinite more.

Andy

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Andy Dills 301-682-9972
Xecunet, LLC www.xecu.net
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Dialup * Webhosting * E-Commerce * High-Speed Access

18

Date: Mon, 10 Jun 2002 14:21:59 -0400 (EDT)
From: Andy Dills

How can you forget the king of all protocols, RIP? :slight_smile:

RIP isn't an IP protocol. :slight_smile:

But seriously, I still don't understand the semantics. If
you're "routing" those protocols, you're also routing SMTP,
DNS, POP, IMAP, HTTP, HTTPS...wacky multiplayer game
protocols...anything that runs on IP, basically.

They run on TCP or UDP, which represent _two_ IP protocols.

So you're either routing IP, or you're routing
`wc -l /etc/services` number of services plus possibly
infinite more.

I interpretted the question to be, "who actively routes real-
world traffic from what protocols on /etc/services"?

Eddy

19

> Date: Mon, 10 Jun 2002 14:21:59 -0400 (EDT)
> From: Andy Dills

> How can you forget the king of all protocols, RIP? :slight_smile:

RIP isn't an IP protocol. :slight_smile:

No, but UDP is, and RIP runs on top of UDP. Oh, so you mean there IS some
sort of solid definition of 'protocol' for this discussion? See below...

> But seriously, I still don't understand the semantics. If
> you're "routing" those protocols, you're also routing SMTP,
> DNS, POP, IMAP, HTTP, HTTPS...wacky multiplayer game
> protocols...anything that runs on IP, basically.

They run on TCP or UDP, which represent _two_ IP protocols.

Note my quotes around the word routing. The only protocol that people
route is IP. Therefore, if you "route" all of the other protocols you
mentioned, you must inherently route all protocols L4 on up that run on
IP. Routing is done at L3. Therefore, if you want to talk about things
running L4 and up, the question should be about filtering and not routing.

That's my point...that if we're talking about which protocols are being
routed, it's either "IP and IPv6" or "everything from L4 up that runs on
IP", depending on how you take the question.

Andy

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Andy Dills 301-682-9972
Xecunet, LLC www.xecu.net
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Dialup * Webhosting * E-Commerce * High-Speed Access

20

Now that you've cleared that up, can someone enlighten me as to what this
has to do with "slamming ICANN?" I'm still not seeing the connection.