Re: Wireless bridge

[Justin Sharp]

I didn't read through all of the replies to see if this was suggested, 
apologies if it was.


http://www.solectek.com/products.php?prod=sw7k&page=feat

I implemented a PTP link at about 3 miles using these Solectek radios. I 
get 40Mbps consistently with TCP traffic and ~100Mbps UDP. This PTP link 
has literally been up for 3 years (in 2 weeks) without failing. I live 
in a 4 seaons state, so its seen all sorts of weather over those years. 
I have clean line of site down the freeway for what its worth. Its 
natively powered via POE, power injector included. We run all sorts of 
usual business application over this link, including about 30 
simultaneous VOIP channels, and have not had one issue with stability. I 
was also told by the VAR that sold us the product that a city nearby 
(can't remember which one) connects all of its municipal buildings with 
Solectek stuff and runs its VOIP infrastructure over it as well.


We run it in bridged mode with routers on each end, but it does support 
some rudimentary L3 stuff, static routing and RIP.


IIRC, they were not "cheap" (couple of 1k), but for us have definitely 
been much cheaper than private circuits from carriers of comparable 
throughput capacity.


Hope its helpful.

--Justin

Re: XO Outage

[Justin Sharp]

Seems like Savvis/XO routes have been restored, albeit through an 
unusual Dallas route (usually takes an XO Los Angeles route)..


1. scrubbed 
  
0.0%   2040.4   0.7   0.3   7.0   0.9
2. 
ip65-44-114-97.z114-44-65.customer.algx.net 
0.0%   2041.8   1.8   1.1   8.4   1.2
3. 
ip65-46-48-29.z48-46-65.customer.algx.net   
0.0%   2043.3   6.3   2.8  96.4   9.0
4. 
p6-0-0-0.mar1.saltlake-ut.us.xo.net 
0.5%   2048.1  14.4   3.1 161.0  26.3
5. 
p4-1-0-0.rar1.denver-co.us.xo.net   
0.0%   204   15.5  25.6  15.3 191.4  26.7
6. 
p0-0-0d0.rar2.denver-co.us.xo.net   
0.0%   204   16.2  22.4  16.1 129.2  14.4
7. 
p1-0-0.rar2.dallas-tx.us.xo.net 
0.0%   204   45.3  38.3  29.9 201.3  21.3
8. 
te-3-4-0.rar3.dallas-tx.us.xo.net  
66.0%   204   30.3  34.2  29.6 116.2  11.6
9. 
207.88.12.146.ptr.us.xo.net 
0.0%   204   33.1  32.7  29.4 106.7   8.5
10. 
208.175.175.89  
0.0%   204   29.8  35.7  29.5 195.4  20.0
11. 
dpr1-ge-2-0-0.dallasequinix.savvis.net  
0.0%   204   34.3  33.8  29.6 115.2  10.5
12. 
cr2-tengige0-7-5-0.dallas.savvis.net
1.5%   204   30.2  33.3  29.7  68.6   5.4
13. 
cr2-loopback.sfo.savvis.net 
0.0%   203   75.1 209.8  74.0 3270. 493.7
14. 
er1-te-2-0-1.sanjose3equinix.savvis.net 
0.0%   203   71.8  75.6  71.7 219.5  11.7
15. 
hr1-te-2-0-0.santaclarasc5.savvis.net   
0.0%   203   72.1  75.5  72.0 194.0   9.4
16. 
216.34.2.226
0.0%   203   72.3 105.4  72.1 723.7 102.5
17. 
64.41.199.140  
28.6%   203   77.5  74.9  72.0 183.1   9.7
18. scrubbed 
   
0.0%   203   73.8  76.0  72.4 207.9  11.3


Hop 8 looks busy..

--Justin

Mike Lyon wrote:

Also seeing some issues with XO out here:

Tracing route to yahoo.com [68.180.206.184]
over a maximum of 30 hops:

  1 2 ms 1 ms 1 ms  10.100.20.1
  2 2 ms 1 ms 2 ms  sjcisr01-int.wyse.com [10.100.1.15]
  3 3 ms 2 ms 2 ms  132.237.245.1
  4 3 ms 3 ms 2 ms  207.88.3.37.ptr.us.xo.net [207.88.3.37]
  5 7 ms 3 ms 3 ms  p3-0-0.mar2.fremont-ca.us.xo.net [207.88.80.181]

  616 ms 5 ms 3 ms  p4-0-0.rar2.sanjose-ca.us.xo.net [65.106.5.137]

  712 ms14 ms11 ms  p6-0-0.rar1.la-ca.us.xo.net [65.106.0.17]
  817 ms11 ms11 ms  p0-0-0d0.rar2.la-ca.us.xo.net [65.106.1.50]
  944 ms50 ms52 ms  p6-0-0.rar1.dallas-tx.us.xo.net [65.106.0.13]
 10 *** Request timed out.
 1144 ms44 ms44 ms  207.88.12.150.ptr.us.xo.net [207.88.12.150]
 1253 ms85 ms52 ms  206.111.5.42.ptr.us.xo.net [206.111.5.42]
^C



On Mon, Sep 22, 2008 at 2:35 PM, Justin Sharp <[EMAIL PROTECTED]> wrote:
  

We are seeing some issues w/ XO/Savvis peering..

Trace from XO to Savvis IP space (64.75.10.151)

Keys:  Help   Display mode   Restart statistics   Order of fields   quit

   Packets   Pings
Host
 Loss%   Snt   Last   Avg  Best  Wrst StDev
1. scrubbed
 0.0% 60.6   0.5   0.4   0.6   0.1
2. ip65-44-114-97.z114-44-65.customer.algx.net
  0.0% 61.3   1.3   1.2   1.4   0.1
3. ???


Trace from Savvis to XO IP space (65.44.114.97)

1. scrubbed
 0.0%380.4   0.4   0.3   0.5   0.1
2. 64.41.199.129
  0.0%371.0  24.0   0.6 330.2  80.4
3. hr1-ge-7-47.santaclarasc5.savvis.net
   0.0%370.7   1.4   0.6  27.3   4.4
4. er1-te-1-0-0.sanjose3equinix.savvis.net
  0.0%370.7   5.2   0.6 140.3  23.2
5. cr1-tenge-0-7-5-0.sanfrancisco.savvis.net
  2.7%372.9   4.0   2.6  16.6   2.5
6. cr2-pos-0-0-3-3.dallas.savvis.net
  0.0%37   42.6  43.1  42.3  51.4   1.4
7. dpr1-ge-4-0-0.dallasequinix.savv

XO Outage

[Justin Sharp]

We are seeing some issues w/ XO/Savvis peering..

Trace from XO to Savvis IP space (64.75.10.151)

Keys:  Help   Display mode   Restart statistics   Order of fields   quit

Packets   Pings
Host  
Loss%   Snt   Last   Avg  Best  Wrst StDev
1. scrubbed 
  
0.0% 60.6   0.5   0.4   0.6   0.1
2. 
ip65-44-114-97.z114-44-65.customer.algx.net 
0.0% 61.3   1.3   1.2   1.4   0.1

3. ???


Trace from Savvis to XO IP space (65.44.114.97)

1. scrubbed 
  
0.0%380.4   0.4   0.3   0.5   0.1
2. 
64.41.199.129   
0.0%371.0  24.0   0.6 330.2  80.4
3. 
hr1-ge-7-47.santaclarasc5.savvis.net
0.0%370.7   1.4   0.6  27.3   4.4
4. 
er1-te-1-0-0.sanjose3equinix.savvis.net 
0.0%370.7   5.2   0.6 140.3  23.2
5. 
cr1-tenge-0-7-5-0.sanfrancisco.savvis.net   
2.7%372.9   4.0   2.6  16.6   2.5
6. 
cr2-pos-0-0-3-3.dallas.savvis.net   
0.0%37   42.6  43.1  42.3  51.4   1.4
7. 
dpr1-ge-4-0-0.dallasequinix.savvis.net  
0.0%37   43.1  44.8  42.9  76.9   6.7
8. 
er1-te-2-1.dallasequinix.savvis.net 
0.0%37   43.3  49.2  42.8 233.6  31.6
9. 
208.175.175.90  
0.0%37   43.0  42.8  42.6  43.6   0.2
10. 
65.106.1.102   
75.0%37   43.5  46.5  43.4  62.9   6.3
11. 
65.106.1.101
0.0%37   43.4  47.8  43.2 112.3  12.5
12. 
65.106.0.41 
0.0%37   57.5  65.1  57.1 177.3  21.0
13. 
65.106.1.73 
0.0%37   57.4  66.5  57.1 162.1  24.2

14. ???

Trying to call into XO and they aren't even taking calls, they mention 
something about network issues in Spokane. Any ideas as to what is going 
on/ETA to fix?


--Justin

Re: Software router state of the art

[Justin Sharp]

[EMAIL PROTECTED] wrote:
but knowing how bad Linux is at being a router and that their 
products are Linux-based, I'm afraid to give one a try. J 
products are based on a competing non-Linux platform that has 
a better reputation for routing.



Enough with the bipartisan politics. There are more choices than 
just Linux and FreeBSD for software routing.


Click for instance 

--Michael Dillon

  
Anyone have experience with RouterOS (http://www.mikrotik.com/)? Created 
mostly to run on these guys I think 
(http://www.routerboard.com/comparison.html) which generally don't get 
above 200k pps on the higher models.. But will RouterOS run on bigger boxen?

Re: Software router state of the art

[Justin Sharp]

Yes. We put in some Vyatta routers to extend our corporate network into 
another building as a temporary solution (the building had a very short 
lease, so our boss didn't want to spend any money on Juniper which is 
our usual net gear vendor). Consequently, we are still there.. go figure.


When we started w/ them, they were still using the XORP routing engine 
(and we haven't upgraded to the new platform yet). My experience wasn't 
terribly good. The first issue was a bad memory leak in the router 
manager process when VRRP hello times were set to 1 second. The first 
indication of something wrong is that our master router crashed, 
followed by his backup. Had to physically reboot the boxes to get them 
back online, which involved driving there as no one onsite had access to 
the cage at the office. All voice and data ran through these routers, 
basically rendering every employee useless until we got it back online. 
It wasn't a happy day. After that we had to monitor memory and do 
controlled reboots every month or so. We eventually convinced Vyatta of 
this memory leak and they were able to fix it, but that was a very 
frustrating process, and time consuming for us, which is why the next 
problems I describe, we have just found our own workarounds.


The next problem was a combination of a problem with the Vyatta and a 
problem w/ our IP phones. The Vyatta was sending garp's for the data 
vrrp address out the voice vlan (same 2 routers are default gate on both 
data and voice vlans). All of the workstations run through the phones 
(which sit tagged on voice vlan, and pass traffic from workstation 
untagged to data vlan). The phone, seeing the arp for the data vrrp 
address on its voice vlan, would send traffic to that address out the 
voice vlan, effectively taking that workstation off the net for anything 
other than local traffic. That was a bugger to figure out, and basically 
we solved it with an arptables rule on the vyatta's. That was the one 
advantage of using a Linux (debian) based router platform, was that we 
could load other 'unsupported' packages to solve problems like this.


The last thing is that OSPF never really converges correctly. You can 
view the OSPF database, and see which default the routers should 
converge to, but they do not. They will sit converged to one path for a 
while, and if you reboot the other router that generates default, they 
will reconverge to it for a while. This hasn't been a big enough problem 
for me to worry about it.


Last thing to say is, I haven't tried upgrading since Vyatta abandoned 
the XORP platform and moved to the Quagga platform, but I'm guessing 
(based on experience w/ Quagga) that they have a lot fewer of these 
quirks that I've described.


IMHO, YMMV, etc

--Justin

Tim Sanderson wrote:

Is anyone using Vyatta for routing? I sure would like to know about any 
experience with it in production.

http://www.vyatta.com/

--
Tim Sanderson, network administrator
[EMAIL PROTECTED]


-Original Message-
From: randal k [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 23, 2008 1:46 PM
To: Adrian Chadd
Cc: [EMAIL PROTECTED]
Subject: Re: Software router state of the art

That is a very interesting paper. Seriously, 7mpps with an
off-the-shelf Dell 2950? Even if it were -half- that throughput, for a
pure ethernet forwarding solution that is incredible. Shoot, buy a
handful of them as hot spares and still save a bundle.

Highly recommended reading, even if (like me) you're anti-commodity routing.

Cheers,
Randal

On Wed, Jul 23, 2008 at 10:17 AM, Adrian Chadd <[EMAIL PROTECTED]> wrote:
  

On Wed, Jul 23, 2008, Charles Wyble wrote:



This might be of interest:

http://nrg.cs.ucl.ac.uk/mjh/tmp/vrouter-perf.pdf
  

Various FreeBSD related guys are working on parallelising the forwarding
layer enough to use the multiple tx/rx queues in some chipsets such as the
Intel gig/10ge stuff.

1 mil pps has been broken that way, but it uses lots of cores to get there.
(8, I think?)

Linux apparently is/has headed down this path.




  

Re: Savvis outage

[Justin Sharp]

Same old story.. Savvis points finger at XO, XO points finger at 
Savvis.. Neither side actually finds out and tells me who/what fixed the 
issue, but at least its fixed.


--Justin

Justin Sharp wrote:

Anyone know what might be up w/ XO to Savvis peering?

This is a trace to netsuite.com, notice 80% packet loss at bpr2 in Los 
Angeles


HostLoss%   Snt   Last   Avg  Best  
Wrst StDev

1. 10.0.0.1  0.0%210.3   0.4   0.3   1.6   0.3
2. ip65-44-114-97.z114-44-65.custom  0.0%211.2   1.2   1.1   
1.8   0.2
3. ip65-46-48-29.z48-46-65.customer  0.0%202.8   3.1   2.7   
5.6   0.6
4. p6-0-0d0.mar2.saltlake-ut.us.xo. 10.0%203.0   7.0   3.0  
68.5  15.4
5. p3-1-0d0.rar2.la-ca.us.xo.net 0.0%20   90.2  31.3  16.8 
114.1  32.1
6. p0-0-0d0.rar1.la-ca.us.xo.net 5.0%20   17.9  18.8  17.7  
26.2   2.6
7. te-4-1-0.rar3.la-ca.us.xo.net 0.0%20   19.5  20.0  18.6  
27.9   1.9
8. 207.88.12.154.ptr.us.xo.net   0.0%20   16.9  17.4  16.8  
22.4   1.3
9. bpr2-so-6-1-0.losangeles.savvis. 57.9%20   85.9  85.9  84.9  
90.4   1.8
10. cr1-gig-0-7-5-3.LosAngeles.savvi 78.9%20  1040. 349.8 105.6 
1040. 460.6

   cr2-gig-0-7-5-3.losangeles.savvis.net
11. cr2-pos-0-0-5-0.sanfrancisco.sav 84.2%20  133.0 406.4  94.7 
991.5 507.1

   cr1-loopback.sfo.savvis.net
12. er1-te-1-0-1.sanjose3equinix.sav 68.4%20   94.2  94.8  94.2  
95.7   0.5

   er1-te-2-0-1.SanJose3Equinix.savvis.net
13. hr1-te-2-0-0.santaclarasc5.savvi 78.9%20   94.3  95.2  94.3  
95.8   0.7
14. hr1-te-2-0-0.santaclarasc8.savvi 70.0%20   94.3  94.7  94.0  
95.7   0.6
15. 66.35.192.2  75.0%20   96.2  95.4  94.5  
96.2   0.8
16. 167.216.129.12   78.9%20   95.0  95.4  94.4  
96.9   1.1



Thanks,
--Justin

Savvis outage

[Justin Sharp]

Anyone know what might be up w/ XO to Savvis peering?

This is a trace to netsuite.com, notice 80% packet loss at bpr2 in Los 
Angeles


HostLoss%   Snt   Last   Avg  Best  Wrst 
StDev

1. 10.0.0.1  0.0%210.3   0.4   0.3   1.6   0.3
2. ip65-44-114-97.z114-44-65.custom  0.0%211.2   1.2   1.1   
1.8   0.2
3. ip65-46-48-29.z48-46-65.customer  0.0%202.8   3.1   2.7   
5.6   0.6
4. p6-0-0d0.mar2.saltlake-ut.us.xo. 10.0%203.0   7.0   3.0  
68.5  15.4
5. p3-1-0d0.rar2.la-ca.us.xo.net 0.0%20   90.2  31.3  16.8 
114.1  32.1
6. p0-0-0d0.rar1.la-ca.us.xo.net 5.0%20   17.9  18.8  17.7  
26.2   2.6
7. te-4-1-0.rar3.la-ca.us.xo.net 0.0%20   19.5  20.0  18.6  
27.9   1.9
8. 207.88.12.154.ptr.us.xo.net   0.0%20   16.9  17.4  16.8  
22.4   1.3
9. bpr2-so-6-1-0.losangeles.savvis. 57.9%20   85.9  85.9  84.9  
90.4   1.8
10. cr1-gig-0-7-5-3.LosAngeles.savvi 78.9%20  1040. 349.8 105.6 
1040. 460.6

   cr2-gig-0-7-5-3.losangeles.savvis.net
11. cr2-pos-0-0-5-0.sanfrancisco.sav 84.2%20  133.0 406.4  94.7 
991.5 507.1

   cr1-loopback.sfo.savvis.net
12. er1-te-1-0-1.sanjose3equinix.sav 68.4%20   94.2  94.8  94.2  
95.7   0.5

   er1-te-2-0-1.SanJose3Equinix.savvis.net
13. hr1-te-2-0-0.santaclarasc5.savvi 78.9%20   94.3  95.2  94.3  
95.8   0.7
14. hr1-te-2-0-0.santaclarasc8.savvi 70.0%20   94.3  94.7  94.0  
95.7   0.6
15. 66.35.192.2  75.0%20   96.2  95.4  94.5  
96.2   0.8
16. 167.216.129.12   78.9%20   95.0  95.4  94.4  
96.9   1.1



Thanks,
--Justin

Re: [NANOG] Routing table for BGP

[Justin Sharp]

Your questions depend on several details specific to your organization, 
which you haven't really devulged.

There are several decent books on the subject which I recommend that you 
invest in.
see: *
ISBN-10:* 0321127005
*ISBN-10:* 0596002548

http://www.oreilly.com/catalog/bgp/chapter/ch06.html -- this is a 
chapter from the second book which should wet your appetite a bit.

Regards,
--Justin

devang patel wrote:
> Hi,
>
>
> I would like to know what route should i accept from internet full or
> partial?
> if Partial then what routes should i accept? and how many route does my
> router have if i will go for Partial routing table?
>
> actually I am trying to understand it by concept... my organization is small
> but I want to know if it is large organization or small provider then what
> kind of routes do i need in my routing table?
>
> regards
> Devang Patel
> ___
> NANOG mailing list
> NANOG@nanog.org
> http://mailman.nanog.org/mailman/listinfo/nanog
>   

___
NANOG mailing list
NANOG@nanog.org
http://mailman.nanog.org/mailman/listinfo/nanog

[NANOG] [EMAIL PROTECTED]

[Justin Sharp]

Hello,

Forgive me if this has been covered previously.

I have recently discovered this list and have found it a gold mine of 
information. I've now traded 3 hours of my life reading through archives 
and have even found reference to specific recent outages that my company 
suffered to which we never really did get a RFO from the ISP.

In the archives, I have read of another list which I am interested in at 
[EMAIL PROTECTED] I've tried visiting the site, and subscribing at 
http://www.isotf.org/mailman/listinfo/outages (as mentioned in several 
archived messages) but it doesn't seem to exist there anymore. Also 
tried to search this list for information as to whether it had moved or 
been discontinued, etc (google site searches, etc). Has this list been 
discontinued? If not, is it still open to the public, and what is its 
new location, that I might subscribe?

Regards,

--Justin

___
NANOG mailing list
NANOG@nanog.org
http://mailman.nanog.org/mailman/listinfo/nanog