2008/12/2 Daniele Guazzoni <[EMAIL PROTECTED]>: > To reply to the "static routes" part of your problem: > > I know the situation in ZA and I suggest you to use BGP information (even > through a route server) to get rid of those static. > PfSense comes with RIP and BGP packages, use them and save yourself a lot of > time to manually sort out routes. All you need is to setup a BGP peer to get > the prefixes belonging to ZA Autonomous Systems from a route server and pass > it to pfSense via RIP2 or BGP. I know this may not be a BGP howto forum, but since it's relevant to the thread, could you give me a quick howto in getting the BGP routes please? I did this stuff during last century (yes, it feels and is that log ago!) and haven't used it since.
I would be much appreciated. regards >> >> In South Africa we have very expensive traffic charges for internet >> and other network links, mainly because we had a government protected >> telco monopoly, headed by the US STC telco and Telcom Malaysia (STC >> has this rape and escape litigation heavy history). So are using a >> local (za) only link to pipe all traffic through that stays in South >> Africa. 30GB of traffic through that costs R130, whereas otherwise >> one can pay up to R170 for 1GB. So I have a list of all local >> networks and want to tell pfSense to use those. > > > -- > This message has been scanned for viruses and > dangerous content by MailGate, and is > believed to be clean. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > Commercial support available - https://portal.pfsense.org > > -- Roland Giesler Green Tree Systems cc, Stellenbosch, South Africa Mobile: 072-450-2817 http://www.thegreentree.za.net If a nation expects to be ignorant and free, in a state of civilization, it expects what never was and never will be… - Thomas Jefferson, Jan 6th, 1816
