July 2000 - Test - lists.nanog.org

Re: Strange things which should never happen (was Re: RFC 1918)
by Patrick W. Gilmore 06 Aug '00

06 Aug '00

At 03:15 PM 7/15/00 -0700, Joe Rhett wrote: >> >I don't know my TCP/IP stack well enough, but what happens when a host >> >with multiple interfaces, one of which is assigned an RFC1918 address, >> >receives an packet through another interface with a source address the >> >same RFC1918 address. Are the stacks smart enough to realize the packet >> >is really an external packet, or will they assume the packet came from >> >inside. > >> Nope - at least none of the ones I have seen. > >Hate to disagree, but all modern security-aware OSes can now be configured >to validate which interface a packet should be received on. If the packet >comes from a different interface it is generally dropped. > >In solaris, the option are: > > ip_strict_dst_multihoming > and > ip6_strict_dst_multihoming I was under the impression that hosts only check the *destination* IP address. Feel free to correct me if I am mistaken (as I am sure 472 of you will do :). Sean was asking about packets with a *source* address in a subnet which is on another one of their interfaces. So we are looking at a host which has, for instance, 1.1.1.1/24 on e0 and 2.2.2.2/24 on e1. If a packet hits e0 with a destination address of 1.1.1.1 and a source address of 2.2.2.10, why would the host reject it? The destination address is correct, and the packet was routed to the correct interface. I think Sean is worried about the response to that packet. The host might send the reply/ACK/return/whatever packet out the second interface. If the e1 is addressed with RFC1918 space, and the packet were sourced from an RFC1918 address in another network, the reply would obviously go to the wrong location. If someone knew your internal network well enough, this might even be used as a form of DoS attack. >Joe Rhett Chief Technology Officer TTFN, patrick

2 1

07/21/00 Internet Routing Problems
by Randy Bush 04 Aug '00

04 Aug '00

ok boys and girls. second day. would people please clean up their announcements so the rest of us can see if we have any bugs? thanks. randy --- From: stats(a)merit.edu Date: Sat, 22 Jul 2000 10:00:04 -0400 (EDT) Reserved Network and Host Announcements --------------------------------------- 10.0.0.0/8 at Mae-East from NetRail (AS4006) ASPATH=4006 INCOMPLETE 10.0.0.0/8 at Mae-West from NetRail (AS4006) ASPATH=4006 INCOMPLETE 10.0.0.0/8 at Paix from NetRail (AS4006) ASPATH=4006 INCOMPLETE 128.88.250.0/27 at Mae-East from BBN-Planet (AS1) ASPATH=1 5727 2915 151 IGP 128.88.250.32/29 at Mae-East from BBN-Planet (AS1) ASPATH=1 5727 2915 151 IGP 137.236.241.0/28 at Mae-East from BBN-Planet (AS1) ASPATH=1 IGP 137.236.241.0/28 at Mae-West from BBN-Planet (AS1) ASPATH=1 IGP 140.32.132.128/27 at Mae-East from ATT-DISC (AS7170) ASPATH=7170 1655 IGP 140.32.132.128/27 at Mae-West from ATT-DISC (AS7170) ASPATH=7170 1655 IGP 192.108.209.0/27 at Mae-East from BBN-Planet (AS1) ASPATH=1 1755 1755 1755 1880 1877 IGP 192.108.209.0/27 at Mae-West from BBN-Planet (AS1) ASPATH=1 1755 1755 1755 1880 1877 IGP 192.108.213.16/28 at Mae-East from BBN-Planet (AS1) ASPATH=1 1755 1755 1755 1880 1877 IGP 192.108.213.16/28 at Mae-West from BBN-Planet (AS1) ASPATH=1 1755 1755 1755 1880 1877 IGP 192.76.71.32/27 at Mae-East from BBN-Planet (AS1) ASPATH=1 IGP 193.122.136.4/30 at Mae-East from CableInet (AS5462) ASPATH=5462 IGP 193.133.206.64/28 at Mae-East from BBN-Planet (AS1) ASPATH=1 2856 8718 IGP 193.133.206.64/28 at Mae-West from BBN-Planet (AS1) ASPATH=1 2856 8718 IGP 193.58.0.16/29 at Mae-East from CableInet (AS5462) ASPATH=5462 IGP 194.251.192.96/27 at Mae-East from BBN-Planet (AS1) ASPATH=1 1755 1759 5574 IGP 194.251.192.96/27 at Mae-West from BBN-Planet (AS1) ASPATH=1 1755 1759 5574 IGP 195.89.15.160/27 at Mae-East from INS (AS6660) ASPATH=6660 5378 5378 12359 IGP 195.89.15.160/27 at Mae-East from INS (AS6660) ASPATH=6660 5378 5378 12359 IGP 198.41.0.12/32 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.12/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.12/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.12/32 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.128/27 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.128/27 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.128/27 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.128/27 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.16/32 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.16/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.16/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.16/32 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.160/27 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.160/27 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.160/27 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.160/27 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.17/32 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.17/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.17/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.17/32 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.192/28 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.192/28 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.192/28 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.192/28 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.22/32 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.22/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.22/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.22/32 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.224/27 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.224/27 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.224/27 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.224/27 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.24/32 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.24/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.24/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.24/32 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.29/32 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.29/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.29/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.29/32 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.30/32 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.30/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.30/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.30/32 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.4/32 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.4/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.4/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.4/32 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.6/32 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.6/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.6/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.6/32 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.64/27 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.64/27 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.64/27 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.64/27 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.7/32 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.7/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.7/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.7/32 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.8/32 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.8/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.8/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.8/32 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.9/32 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.9/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.9/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.9/32 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.96/27 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.96/27 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.96/27 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.96/27 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.1.13/32 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.1.13/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.1.13/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.1.13/32 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.1.14/32 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.1.14/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.1.14/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.1.14/32 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.1.15/32 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.1.15/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.1.15/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.1.15/32 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.1.224/27 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.1.224/27 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.1.224/27 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.1.224/27 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.2.32/27 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.2.32/27 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.2.32/27 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.2.32/27 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 207.175.63.128/28 at Mae-East from BBN-Planet (AS1) ASPATH=1 IGP 207.82.242.48/28 at Mae-West from Exodus (AS3967) ASPATH=3967 13362 IGP 208.151.16.96/28 at Mae-East from Comstor (AS6082) ASPATH=6082 IGP 208.208.6.200/32 at Mae-East from Comstor (AS6082) ASPATH=6082 IGP 209.1.49.160/27 at Mae-West from Exodus (AS3967) ASPATH=3967 13362 IGP 209.141.222.96/27 at Mae-East from GoodNet (AS5696) ASPATH=5696 INCOMPLETE ***** Too many entries. List Truncated! *****

3 2

recent internet packet size samples
by Joe Abley 03 Aug '00

03 Aug '00

I'm interested in seeing the distribution of packet sizes across a 1500-byte-constrained measurement point, with "real internet traffic" going past (for some reasonable interpretation of that phrase). Specifically, I'm looking for the number of IP datagrams of size M for all M encountered throughout a long, contiguous packet stream (say a few hours' worth around the residential surfing busy hour). I can do measurements myself, but I'd prefer not to reinvent the wheel. Could anybody point me at some recent data? Thanks, Joe

5 6

Qwest and US WEST (non) routing problems
by Bessant, Chuck 02 Aug '00

02 Aug '00

I have been working a ticket with Qwest regarding our upstream through them in Portland. I was informed by a Qwest engineer that, as a result of their merger with US West, they are under an FCC mandate not to traffic data directly through AS3908. This AS serves the NW and the Denver area according to this engineer. THE CAVEAT as related by the engineer is as follows: our advertisements should, technically, be propagated out to the Internet...however, all traffic would first hit Qwest's network, then go through the Cable & Wireless network, then back through Qwest to us...in other words, even if our routes *were* being propagated properly, we would probably have to do some kind of prepending or other preferencing to get traffic flowing in Qwest's direction and even then it would certainly not be an optimal path through the network. Has anyone experienced this problem with AS3908 & Qwest? Thanks. Chuck

3 2

Compression based on Throughput or Source Clock
by Mufti Ahmed 31 Jul '00

31 Jul '00

Is there any one who is running point to point Frame Relay compression whether it is from one point of your network to another or from your POP to a client? Is your compression based on throughput or Source Clock on the interfaces? Thanks Mufti Nayeem Ahmed Network Systems Engineer Market Data Networks Reuters America Inc. (212)-603-3595 ----------------------------------------------------------------- Visit our Internet site at http://www.reuters.com Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Reuters Ltd.

1 0

NSI at it still/again
by David Lesher 31 Jul '00

31 Jul '00

Anyone recall the old scan about getting bills for advertising in Telex directories, ones you never ASKED to be in [cuz they don't exist...]? Looks to me like NSI has gone into that business. I transferred a domain name out of their grasp. Come renewal time, they still bill me repeatedly for same. Hmmm.. After 30 minutes on hold, 30 minutes full of ads, I reach a human. "Oh, that must be a mistake..." Has anyone ELSE gotten billed by NSI for un-services? Wonder if the FTC would care....? -- A host is a host from coast to coast.................wb8foz(a)nrk.com & no one will talk to a host that's close........[v].(301) 56-LINUX Unless the host (that isn't close).........................pob 1433 is busy, hung or dead....................................20915-1433

2 1

Re: NSI at it still/again
by Michael Shields 31 Jul '00

31 Jul '00

In article <200007311823.OAA04069(a)sigma.nrk.com>, David Lesher <wb8foz(a)nrk.com> wrote: > Has anyone ELSE gotten billed by NSI for un-services? Yes. View the threads starting at http://www.opensrs.org/archives/discuss-list/0005/0492.html http://www.opensrs.org/archives/discuss-list/0006/0241.html http://www.opensrs.org/archives/discuss-list/0006/0786.html among others. However, since they are unable to shut off your domain for nonpayment when they are not the registrar, I don't think this can cause operational problems. Correct? > Wonder if the FTC would care....? There's only one way to find out. -- Shields.

1 0

Is the list alive
by Scott McGrath 31 Jul '00

31 Jul '00

I have not seen any traffic from the list recently and I usually get 50+ messages per day Thanks - Scott

2 1

ORBS IS BUSY
by Henry R. Linneweh 31 Jul '00

31 Jul '00

Telstra And Optus Blacklisted By ORBS http://www.internetnews.com/intl-news/article/0,2171,6_425981,00.html -- Thank you; |--------------------------------| | Thinking is a learned process. | | ICANN member @large | | Gigabit over IP, ieee 802.17 | |--------------------------------| Henry R. Linneweh

1 0

Beermaker?
by Alex 31 Jul '00

31 Jul '00

Anyone else seeing peermaker not working properly?

1 0