Re: What Should an Engineer Address when 'Selling' IPv6 to Executives?
On Tue, 2013-03-05 at 17:41 -0800, Owen DeLong wrote: 3.We've actually been through this before. In some cases more than once. e.g.: Novell - TCP/IP Windows Networking - TCP/IP Appletalk - TCP/IP NCP - TCP/IP In some ways, this change is less profound than many of those. Lest we forget one of the more profound ones whose memory could be the source of much resistance. Assuming this industry had any memory... TCP/IP - MAP/TOP/GOSIP - TCP/IP Complete with government mandates, dual stacking, and RFP inclusion. Been there, done that, been burnt... Vincent Jones
Re: iCloud - Is it going to hurt access providers?
--- br...@bryanfields.net wrote: From: Bryan Fields br...@bryanfields.net I would love a world where engineering was consulted by marketing :( - WAKE UP You're dreaming out loud... ;-) Not necessarily...I've been in computer networking going on 40 years and I've only had one employer where engineering was NOT consulted by marketing, and that was the military, which did not have marketing :-) Of course, my case may be a few sigma away from normal, because I've only had two other employers since then-- Hewlett Packard back when they were still a techie company and myself. As an independent consultant, I am marketing, so I can only blame myself if marketing does not consult engineering :-D Vince -- Vincent C. Jones Networking Unlimited, Inc. Phone: +1 201 568-7810 v.jo...@networkingunlimited.com
RE: useful bgp example
On Wed, 2010-05-19 at 13:37 -0500, Jeff Harper wrote: From: Jared Mauch [mailto:ja...@puck.nether.net] Sent: Wednesday, May 19, 2010 1:29 PM To: Jeff Harper Cc: Deric Kwok; nanog@nanog.org Subject: Re: useful bgp example Nice, but you don't show it as-path filtering your transits out. I frequently see people take something learned from transit A and sending it to transit B, and if it happens to be the backup path in-use for your customer, your transits will accept it and likely pick you as best-path and hairpin through your network. - Jared Yeah, I left out the actual prefix-list contents, in hindsight I should have added it, so here it is. Also, a typo in the network statement, lol. network 1.1.1.0 mask 255.255.0.0 ip prefix-list NETZ description The networks we advertise via BGP ip prefix-list NETZ seq 10 permit 1.1.1.0/16 ip prefix-list NETZ seq 1000 deny 0.0.0.0/0 le 32 FYI: It's got to be either 1.1.1.0/24 or 1.1.0.0/16. And there is plenty more that belongs in an appropriate setup for a realistic usage scenario. This is why we are all advising the OP to get some knowledgeable help. Vince -- Vincent C. Jones Networking Unlimited, Inc. Phone: +1 201 568-7810 v.jo...@networkingunlimited.com
Re: useful bgp example
On Mon, 2010-05-17 at 21:04 -0400, valdis.kletni...@vt.edu wrote: On Mon, 17 May 2010 19:15:01 EDT, Deric Kwok said: My company will get 2 upstream provider. We will plan 2 routers and each router to connect one provider to use bgp for redundant. Do you have any useful bgp example and website to set it up? If your BGP clue is that low, I believe the entire NANOG community would advise you hire (even short-term if you can't afford a permanent) somebody who has successfully done this before to walk you through it and teach all the details to your staff. With the current tanking of the economy, I'm sure there's plenty of qualified BGP experts out there who would *love* even a 3-month contract to get this all working for you. At the risk of tooting my own horn, I concur with the recommendation to hire some help, but if all you are lacking is BGP clue-full-ness your challenge in getting help is finding someone clueful who is willing to take a quick and dirty assignment which will barely cover the cost of setting up a new client. The configuration itself is a one day task at most, of which most will be spent grilling you to find out what your _REAL_ requirements are to allow picking the appropriate canned solution that can be adapted to meet your true needs. If you need hand holding applying configurations, negotiating with service provider, filling out paper work, testing without downtime infliction, etc., then add more hours/days. Ditto if you've unfamiliar with basic high availability concepts like single point of failure and physical diversity. Ditto if your systems are not already set up in paranoid mode from a security viewpoint (hint, if you can log directly into your Internet facing router from where ever you are when on the road, you are at an unacceptable level of risk). Good luck and have fun! -- Vincent C. Jones Networking Unlimited, Inc. Phone: +1 201 568-7810 v.jo...@networkingunlimited.com DISCLAIMER: My business is built around helping my clients understand that there is a lot more to improving network availability than just getting a second service provider and turning on BGP. A few years ago I wrote a book about what it takes and barely scratched the surface--the example configurations are still on-line at www.networkingunlimited.com.
Re: Consumer-grade dual-homed connectivity options?
Most of the SOHO router vendors (Netgear, Linksys, etc) have a model targeted at this application. When this class of dual homed router first came out several years ago, they were notoriously unreliable, but I would hope they work better by now. A search on the term ping based routing should give you insight into the current state of affairs, although it will probably take some work because there is no standard terminology to describe the facility, and most implementations no longer rely on ping to do the job of detecting link status. A few limitations to keep in mind: 1 - These routers are targeted at home users, are cheap, and you don't get what you don't pay for. 2 - The job can be done using real routers (Cisco, Juniper, etc), but setup requires work and getting a solution that actually works can be tricky. 3 - Be wary of any advice that you get from anyone who has not actually done it on the box in question! There are many ways a solution which should work will fail miserably. For example, when I looked at this problem a few years ago for a client, the SOHO routers tended to lock up and require a power cycle every few days while Cisco IOS routers would not clear the NAT table when a link failed soft and tended to stop testing a link once it failed, requiring manual recovery. Good luck and have fun! -- Vincent C Jones Networking Unlimited, Inc. www.networkingunlimited.com On Sat, 2010-01-02 at 18:14 -0500, Steven King wrote: You would need at least one router for this. Personally I would connect both DSL modems into a small Cisco router or multi-layer switch. Use that router as the default gateways for each LAN and have two static routes as the default gateway on the router to specify each DSL line. This would allow for load balancing each connection. Although, you run into the issue of needing PAT on both lines. This wouldn't be complex, but would need to be handled by the router as well. I am not sure about asymmetric paths though. Depending on the device, it may handle this differently, and there is no guarantee that the source of your traffic will be from the same connection all the time to the destination. This would cause connectivity issues. There really is no elegant solution to that without having a full routing table of the Internet and 2 separate providers. Others on this list may have a solution to that issue off the top of their heads, or have done this themselves. On 1/2/10 5:48 PM, Scott Weeks wrote: --- paul.w.benn...@gmail.com wrote: From: Paul Bennett paul.w.benn...@gmail.com At home, I currently run two DSL lines. Right now, we just have two separate LANs, one connected to each line, with my wife's devices attached to one, and my devices attached to the other. For a while now, I've been thinking about setting up a load-balancing routing solution to give both of us access to both lines. --- Maybe www.xincom.com/products.php will work? scott
