The problem we have now is that we got our /22 from arin to do multihoming. If we dump tlb, no more multihoming? No /22. Is that correct? We also have a contract with tlb. $$$ 1.5yrs left... 2009/2/13, Seth Mattinen <sethm@rollernet.us>:
Charles Regan wrote:
Isp2 is vtl not bell
2009/2/13, Seth Mattinen <sethm@rollernet.us>:
Charles Regan wrote:
Just got final confirmation from ISP1 that they will not do BGP with us.
ISP1 is Telebec. http://www.iptools.com/dnstools.php?tool=ipwhois&user_data=142.217.0.0&submit=Go
My subnet http://www.iptools.com/dnstools.php?tool=ipwhois&user_data=204.144.60.0&submit=Go
What can we do now ? Any suggestions ?
Do you know who is upstream of ISP2? We've established that Telebec is only connected to Bell Canada. If ISP2 also has a connection to Bell then you don't gain anything with Telebec except this huge mess and horrible hacks to work around their lack of BGP.
~Seth
Also, VTL peers with Sprint and SAVVIS. Based on this information I'd just drop Telebec completely. They only have one upstream. You won't get any redundancy with them since they're just giving you a connection to Bell, which VTL already gives you. Here's the view from my SAVVIS router with Sprint as the preferred path:
routy-border0>show ip bgp 216.113.0.0/17 BGP routing table entry for 216.113.0.0/17, version 78286019 Paths: (3 available, best #1, table Default-IP-Routing-Table) Not advertised to any peer 1239 5769, (received & used) 208.79.242.129 (metric 3) from 208.79.242.129 (208.79.242.129) Origin IGP, metric 439, localpref 100, valid, internal, best Community: 11170:1239 3561 5769 216.88.158.93 from 216.88.158.93 (206.24.210.102) Origin IGP, localpref 90, valid, external Community: 3561:11840 11170:3561 3561 5769, (received-only) 216.88.158.93 from 216.88.158.93 (206.24.210.102) Origin IGP, localpref 90, valid, external Community: 3561:11840
-- Seth Mattinen sethm@rollernet.us Roller Network LLC
-- Envoyé avec mon mobile
Charles Regan wrote:
The problem we have now is that we got our /22 from arin to do multihoming. If we dump tlb, no more multihoming? No /22. Is that correct?
We also have a contract with tlb. $$$ 1.5yrs left...
There's something in there about non-multihomed sites, but I'm not familiar with it. Telebec doesn't appear to be multihomed, though. The only other thing I can think of to avoid horrible hackery is to convince them to colo a router for you to do eBGP to. Honestly, I wouldn't recommend multihoming *without* BGP. One day you'll end up with some really ugly failure mode. ~Seth
The rule with ARIN is that you only need to demonstrate that you WANT do do multihoming, not that you WILL do multihoming. That question would be better asked on the ARIN policy mailing list. I'm also on that list. That was cleared with ARIN as part of the process to get that /22 I guess ARIN rightly assumes that most ISPs do want to do BGP with their customers... F. -- François D. Ménard francois@menards.ca On 13-Feb-09, at 6:48 PM, Charles Regan wrote:
The problem we have now is that we got our /22 from arin to do multihoming. If we dump tlb, no more multihoming? No /22. Is that correct?
We also have a contract with tlb. $$$ 1.5yrs left...
2009/2/13, Seth Mattinen <sethm@rollernet.us>:
Charles Regan wrote:
Isp2 is vtl not bell
2009/2/13, Seth Mattinen <sethm@rollernet.us>:
Charles Regan wrote:
Just got final confirmation from ISP1 that they will not do BGP with us.
ISP1 is Telebec. http://www.iptools.com/dnstools.php?tool=ipwhois&user_data=142.217.0.0&submit=Go
My subnet http://www.iptools.com/dnstools.php?tool=ipwhois&user_data=204.144.60.0&submit=Go
What can we do now ? Any suggestions ?
Do you know who is upstream of ISP2? We've established that Telebec is only connected to Bell Canada. If ISP2 also has a connection to Bell then you don't gain anything with Telebec except this huge mess and horrible hacks to work around their lack of BGP.
~Seth
Also, VTL peers with Sprint and SAVVIS. Based on this information I'd just drop Telebec completely. They only have one upstream. You won't get any redundancy with them since they're just giving you a connection to Bell, which VTL already gives you. Here's the view from my SAVVIS router with Sprint as the preferred path:
routy-border0>show ip bgp 216.113.0.0/17 BGP routing table entry for 216.113.0.0/17, version 78286019 Paths: (3 available, best #1, table Default-IP-Routing-Table) Not advertised to any peer 1239 5769, (received & used) 208.79.242.129 (metric 3) from 208.79.242.129 (208.79.242.129) Origin IGP, metric 439, localpref 100, valid, internal, best Community: 11170:1239 3561 5769 216.88.158.93 from 216.88.158.93 (206.24.210.102) Origin IGP, localpref 90, valid, external Community: 3561:11840 11170:3561 3561 5769, (received-only) 216.88.158.93 from 216.88.158.93 (206.24.210.102) Origin IGP, localpref 90, valid, external Community: 3561:11840
-- Seth Mattinen sethm@rollernet.us Roller Network LLC
-- Envoyé avec mon mobile
Could Charlie do long haul microwave to someone who can do BGP? On 2/14/09, Francois Menard <francois@menards.ca> wrote:
The rule with ARIN is that you only need to demonstrate that you WANT do do multihoming, not that you WILL do multihoming.
That question would be better asked on the ARIN policy mailing list. I'm also on that list.
That was cleared with ARIN as part of the process to get that /22
I guess ARIN rightly assumes that most ISPs do want to do BGP with their customers...
F. -- François D. Ménard francois@menards.ca
On 13-Feb-09, at 6:48 PM, Charles Regan wrote:
The problem we have now is that we got our /22 from arin to do multihoming. If we dump tlb, no more multihoming? No /22. Is that correct?
We also have a contract with tlb. $$$ 1.5yrs left...
2009/2/13, Seth Mattinen <sethm@rollernet.us>:
Charles Regan wrote:
Isp2 is vtl not bell
2009/2/13, Seth Mattinen <sethm@rollernet.us>:
Charles Regan wrote:
Just got final confirmation from ISP1 that they will not do BGP with us.
ISP1 is Telebec. http://www.iptools.com/dnstools.php?tool=ipwhois&user_data=142.217.0.0&submit=Go
My subnet http://www.iptools.com/dnstools.php?tool=ipwhois&user_data=204.144.60.0&submit=Go
What can we do now ? Any suggestions ?
Do you know who is upstream of ISP2? We've established that Telebec is only connected to Bell Canada. If ISP2 also has a connection to Bell then you don't gain anything with Telebec except this huge mess and horrible hacks to work around their lack of BGP.
~Seth
Also, VTL peers with Sprint and SAVVIS. Based on this information I'd just drop Telebec completely. They only have one upstream. You won't get any redundancy with them since they're just giving you a connection to Bell, which VTL already gives you. Here's the view from my SAVVIS router with Sprint as the preferred path:
routy-border0>show ip bgp 216.113.0.0/17 BGP routing table entry for 216.113.0.0/17, version 78286019 Paths: (3 available, best #1, table Default-IP-Routing-Table) Not advertised to any peer 1239 5769, (received & used) 208.79.242.129 (metric 3) from 208.79.242.129 (208.79.242.129) Origin IGP, metric 439, localpref 100, valid, internal, best Community: 11170:1239 3561 5769 216.88.158.93 from 216.88.158.93 (206.24.210.102) Origin IGP, localpref 90, valid, external Community: 3561:11840 11170:3561 3561 5769, (received-only) 216.88.158.93 from 216.88.158.93 (206.24.210.102) Origin IGP, localpref 90, valid, external Community: 3561:11840
-- Seth Mattinen sethm@rollernet.us Roller Network LLC
-- Envoyé avec mon mobile
-- Sent from my mobile device Brandon Galbraith Voice: 630.400.6992 Email: brandon.galbraith@gmail.com
participants (4)
-
Brandon Galbraith -
Charles Regan -
Francois Menard -
Seth Mattinen