Re: [Vyatta-users] Advises on configuring BGP

2008-01-08 Thread Robyn Orosz
Hi,

It's your ISPs responsibility to advertise your prefix to its upstream 
peers.  I don't see your prefix on the Internet so your ISP needs to 
verify that they are advertising your prefix and that they have added it 
in to their prefix lists etc.  So basically, if they are receiving it 
from you, then it's on them to make your prefix available to the rest of 
the world.  You should contact them and let them know that your prefix 
is unavailable beyond their AS.

Thank you,

Robyn

Poh Yong Hwang wrote:
 Hi,

 Sorry for the misunderstanding. The ip 11.11.11.12 
 http://11.11.11.12 is just an example that I stated. My actual ip 
 address is 117.120.0.0/21 http://117.120.0.0/21.  I have check with 
 my upstream regarding this and they said they have recieve 1 prefix 
 from my router:

 sgw-rs1# sh ip bgp nei 202.79.197.25 http://202.79.197.25 
 received-routes BGP table version is 0, local router ID is 
 202.79.197.126 http://202.79.197.126 Status codes: s suppressed, d 
 damped, h history, * valid,  best, i - internal Origin codes: i - 
 IGP, e - EGP, ? - incomplete

  

Network  Next HopMetric LocPrf Weight Path

 * 117.120.0.0/21 http://117.120.0.0/21   202.79.197.25 
 http://202.79.197.250 0 7595 ?

 Total number of prefixes 1

 I see that under the Path, it stated as ? which is incomplete. Could 
 that be the issue for not able to find the path back to my router?

 Thanks

 On Jan 7, 2008 11:07 PM, Robyn Orosz [EMAIL PROTECTED] 
 mailto:[EMAIL PROTECTED] wrote:

 Hi,

 If 11.11.11.12/21 http://11.11.11.12/21 is your own IP space
 (which I doubt because it's
 allocated to the DoD) ;-) and your service provider is receiving
 it via
 BGP and propagating it out to the Internet, then you should be
 able to
 reach it from the outside.  So I guess what I'm not clear on is,
 are you
 literally setting eth1 to 11.11.11.12 http://11.11.11.12?  Or,
 is this number supposed to
 represent your actual IP space?

 If you have your actual owned IP space assigned to eth1 and you are
 unable to reach it externally, then make sure that it is still being
 exported to your BGP peer and that they are advertising it outside of
 their AS to the Internet.  Try performing an external traceroute
 to your
 eth1 IP from somewhere like traceroute.org http://traceroute.org
 or some other external
 location.  You can also access public route servers on
 traceroute.org http://traceroute.org
 and run a 'show ip bgp your-ip-address to see if your prefix has
 been
 advertised out to the Internet.

 Thank you,

 Robyn

 Poh Yong Hwang wrote:
  Hi,
 
  I tried to add a ip address 11.11.11.12 http://11.11.11.12
 http://11.11.11.12 http://11.11.11.12 with
  prefix length of 21 to eth1. But i still cannot remote access or
 ping
  to this ip address from outside. I hope to able to access the
 web gui
  of Vyatta remotely using the eth1 ip address. Also this eth1
 will be
  link to a switch and to the rest of the servers, so am I right
 to set
  all the servers default gateway to be 11.11.11.12
 http://11.11.11.12  http://11.11.11.12
  which is the ip address of the eth1?
 
  thanks for all your patience
 
 
 
  On Jan 4, 2008 10:25 PM, Robyn Orosz  [EMAIL PROTECTED]
 mailto:[EMAIL PROTECTED]
  mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:
 
  Hi,
 
  I'm glad to hear you have it working now.
 
  Since you are exporting your aggregate (/21) via a static
 route to
  your
  loopback interface, you don't have to assign the entire /21
 to eth1.
  You can segment it in whatever way you choose as it will still
  always be
  exported as a /21 based on your existing policy.  Basically, you
  can set
  whatever IP and prefix length you want on your eth1 as long
 as it is a
  valid part of your /21 aggregate prefix.
 
  Thank you,
 
  Robyn
 
  Poh Yong Hwang wrote:
   Hi all,
  
   Sorry for getting back so late as I am tied up with some
 other
   stuffs.. Thanks for all the advice and my upstream managed to
  see my
   prefix. Seems that changing the next hop to my eth0 public ip
  address
   did the trick.
  
   Now as my eth0 is connected to my upstream, what IP
 address should I
   set on my eth1? It will be connected to a layer 3 switch (core
  switch)
   which all our servers will be connected to that switch. I
 have a /21
   range of ip addresses, so should I just use the first ip
 to set on
   eth1? What prefix-length should I set on that as well?
  
   Please advise.
  
   

Re: [Vyatta-users] Fwd: A question on exporting connected routes intoOSPF

2008-01-08 Thread Jonathon Exley
I have also had problems exporting connected routes into OSPF.

Try adding static routes into the export policy:
 
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]  show configuration policy
policy-statement ExportCon
term 10 {
from {
protocol: connected
}
then {
action: accept
}
}
term 20 {
from {
protocol: static
}
then {
action: accept
}
}
 
This seemed to allow the connected interfaces into the OSPF database,
although they were tagged with ASExt-2:

[EMAIL PROTECTED] show ospf4 database
   OSPF link state database, Area 0.0.0.0
 Type   ID   Adv Rtr   Seq  Age  Opt  Cksum
Len
ASExt-2 *192.168.2.0  192.168.101.10x8001   790  0x2  0x4354
36



Jonathon 
 


___
Vyatta-users mailing list
Vyatta-users@mailman.vyatta.com
http://mailman.vyatta.com/mailman/listinfo/vyatta-users


Re: [Vyatta-users] Fwd: A question on exporting connected routes intoOSPF

2008-01-08 Thread Justin Fletcher
And, of course, routes you add outside of the CLI aren't known to XORP.  If
you add the route using protocol static you can then redistribute via
OSPF.

Justin

On Jan 8, 2008 11:57 AM, Jonathon Exley [EMAIL PROTECTED] wrote:

 I have also had problems exporting connected routes into OSPF.

 Try adding static routes into the export policy:

 [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]  show configuration policy
 policy-statement ExportCon
term 10 {
from {
protocol: connected
}
then {
action: accept
}
}
term 20 {
from {
protocol: static
}
then {
action: accept
}
}

 This seemed to allow the connected interfaces into the OSPF database,
 although they were tagged with ASExt-2:

 [EMAIL PROTECTED] show ospf4 database
   OSPF link state database, Area 0.0.0.0
  Type   ID   Adv Rtr   Seq  Age  Opt  Cksum
 Len
 ASExt-2 *192.168.2.0  192.168.101.10x8001   790  0x2  0x4354
 36



 Jonathon



 ___
 Vyatta-users mailing list
 Vyatta-users@mailman.vyatta.com
 http://mailman.vyatta.com/mailman/listinfo/vyatta-users

___
Vyatta-users mailing list
Vyatta-users@mailman.vyatta.com
http://mailman.vyatta.com/mailman/listinfo/vyatta-users