All, My name is David Lemon, and I work within the same group as Shai. We're still in dire need of assistance from this list as we still have many complaints from residential customers that cannot reach certain sites. Shai has provided a few /32's from blocks that we have currently started to provision. Unfortunately we cannot swap these blocks for different blocks with ARIN. As you can see we do indeed own these blocks: whois 99.245.135.129 [whois.arin.net] OrgName: Rogers Cable Communications Inc. OrgID: RCC-99 Address: One Mount Pleasant City: Toronto StateProv: ON PostalCode: M4Y-2Y5 Country: CA NetRange: 99.224.0.0 - 99.253.159.255 CIDR: 99.224.0.0/12, 99.240.0.0/13, 99.248.0.0/14, 99.252.0.0/16, 99.253.0.0/17, 99.253.128.0/19 NetName: ROGERS-CAB-99 We also have these blocks within RADB as well: whois -h whois.radb.net 99.240.0.0/13 [whois.radb.net] route: 99.240.0.0/13 descr: ROGERS-13-BLOCK origin: AS812 notify: radb-notify@rogers.wave.ca mnt-by: MAINT-AS812 changed: radb-maint@rogers.wave.ca 20070412 source: RADB etc.. If anyone has any questions, or I can provide any additional information which anyone may require, please feel free to email me directly or call our TAC @ 416.935.5700. Thanks in advance for your support, -David -----Original Message----- Sent: Friday, April 20, 2007 14:38 PM To: 'nanog@merit.edu' Subject: IP Block 99/8 We recently started to assign these blocks. So all the ranges are not assigned yet. Following are some... 99.245.135.129 99.246.224.1 99.244.192.1 -----Original Message----- From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu] On Behalf Of Frank Bulk Sent: Friday, April 20, 2007 2:14 PM To: nanog@merit.edu Subject: RE: IP Block 99/8 Please provide a pingable IP address on each block so that we can check. Thanks, Frank -----Original Message----- Sent: Friday, April 20, 2007 1:09 PM To: 'nanog@merit.edu' Subject: IP Block 99/8 Hi, I am Shai from Rogers Cable Inc. ISP in Canada. We have IP block 99.x.x.x assigned to our customers. Which happened to be bogons block in the past and was given to ARIN in Oct 2006. As we have recently started using this block, we are getting complaints from our customers who are unable to surf some web sites. After investigation we found that there are still some prefix lists/acls blocks this IP block. We own the following blocks: 99.224.0.0/12 99.240.0.0/13 99.248.0.0/14 99.252.0.0/16 99.253.128.0/19 Please update your bogons list. Shai. end
On 4/23/07, David Lemon <David.Lemon@rci.rogers.com> wrote:
still in dire need of assistance from this list as we still have many complaints from residential customers that cannot reach certain sites.
Naming those sites / ASs would probably have some effect. And there's the peeringdb / inoc-dba to contact several AS operators.
As you can see we do indeed own these blocks:
When Bill Manning said this he was being more than a little sarcastic.
Own? ARIN gave you title?
ARIN assigns you those blocks. They dont give you ownership of those, as such. regards srs -- Suresh Ramasubramanian (ops.lists@gmail.com)
As you can see we do indeed own these blocks:
Nope, you do NOT own these blocks: OrgName: Rogers Cable Communications Inc. OrgID: RCC-99 Address: One Mount Pleasant City: Toronto StateProv: ON PostalCode: M4Y-2Y5 Country: CA NetRange: 99.224.0.0 - 99.253.159.255 CIDR: 99.224.0.0/12, 99.240.0.0/13, 99.248.0.0/14, 99.252.0.0/16, 99.253.0.0/17, 99.253.128.0/19 NetName: ROGERS-CAB-99 NetHandle: NET-99-224-0-0-1 Parent: NET-99-0-0-0-0 NetType: Direct Allocation In my book, Direct Allocation means that they were set aside for you to use, but you do NOT own them.
If anyone has any questions, or I can provide any additional information which anyone may require,
We can't do your job for you. You need to set up a server, or servers, with IP addresses in each of the blocks that are causing you grief. Then when a customer says that they cannot reach something in network X, you must contact the NOC of network X, and ask them to traceroute to the IP address that you KNOW is functioning. If they can't directly fix the problem, then ask them to email you the traceroute so that you can figure out where the problem is (probably a 3rd party newtork upstream of network X) and contact them yourself. Rinse and repeat. That's generally how operational problems get fixed. And that's how networks have been dealing with this specific issue for the past two or three (or more) years. --Michael Dillon
participants (3)
-
David Lemon -
michael.dillon＠bt.com -
Suresh Ramasubramanian