From riddhi.shah at einfochips.com  Mon Dec  1 00:54:41 2008
From: riddhi.shah at einfochips.com (Riddhi Shah)
Date: Mon, 1 Dec 2008 14:24:41 +0530 (IST)
Subject: [Xorp-users] Issue in BGP Configuration
In-Reply-To: <49242229.6040300@incunabulum.net>
References: <32997.10.100.3.228.1227077987.squirrel@indiamail.einfochips.com>
	<49242229.6040300@incunabulum.net>
Message-ID: <55006.10.100.3.228.1228121681.squirrel@indiamail.einfochips.com>

Hi Bruce,

I had done debugging steps according to your suggestions.
Whatever output came , i have attached logs herewith.
I attached two following files.

1)Log.txt - Which contains logs when configuration file was runnig with
debugging steps.
2)Execution_Of_ConfigurationFile - Which contains execution of configuration file


Regards & Thanks,
Riddhi Shah,
e-Infochips.

> Hi,
>
> That looks very strange, it appears your xorp_bgp process is listening
> on 127.0.0.1:19999, which is normally reserved for the Finder. DNS
> resolution does not appear to be the issue.
>
> To go back to the original issue:
>     What you reported in logs normally happens if the Router Manager is
> not able to deal with an incoming XORPSH session right away, usually
> because it's busy dealing with bringing up processes such as xorp_bgp.
>
>     I think you are going to need to build XORP with debugging symbols,
> and forcibly grab a core dump when xorp_bgp wedges like this.
>
>     To do this, you'd run the router as normal. When the BGP process
> hangs, use 'gdb xorp_bgp <pid>'  to attach to the process. Execute
> command 'bt' and send the output to the list, so it is known where
> exactly in the code BGP is hanging.
>
> thanks
> BMS
>
>
> Email Scanned for Virus & Dangerous Content by : www.CleanMailGateway.com
>
>

-- 
_____________________________________________________________________
Disclaimer: This e-mail message and all attachments transmitted with it
are intended solely for the use of the addressee and may contain legally
privileged and confidential information. If the reader of this message
is not the intended recipient, or an employee or agent responsible for
delivering this message to the intended recipient, you are hereby
notified that any dissemination, distribution, copying, or other use of
this message or its attachments is strictly prohibited. If you have
received this message in error, please notify the sender immediately by
replying to this message and please delete it from your computer. Any
views expressed in this message are those of the individual sender
unless otherwise stated.Company has taken enough precautions to prevent
the spread of viruses. However the company accepts no liability for any
damage caused by any virus transmitted by this email.
__________________________________________________________________________
 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Log.txt
Url: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20081201/91ca9226/attachment.txt 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Execution_Of_ConfigurationFile.txt
Url: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20081201/91ca9226/attachment-0001.txt 

From lists at traxx.ch  Tue Dec  2 04:59:05 2008
From: lists at traxx.ch (Pascal Spring)
Date: Tue, 02 Dec 2008 13:59:05 +0100
Subject: [Xorp-users] ospf6 on linux 2.6.26
Message-ID: <49353119.3020407@traxx.ch>

hello

is there some special requirement to run ospf6 on linux (sysctl settings
a.s.o)?
i'm not able to set up a simple ospf6 config of two routers connected
via eth, neither a connection via sit-tunnel.
tpcdump doesn't show any multicast-packets between the neighbors, 'run
show ospf6 neighbor' shows no neighboring routers.

what is the hint on ospf6?

thanks
p.


From bms at incunabulum.net  Tue Dec  2 21:28:02 2008
From: bms at incunabulum.net (Bruce M Simpson)
Date: Wed, 03 Dec 2008 05:28:02 +0000
Subject: [Xorp-users] XORP-EBGP
In-Reply-To: <007c01c94ac9$0aabc140$b602a8c0@BESHWDEVP1>
References: <007c01c94ac9$0aabc140$b602a8c0@BESHWDEVP1>
Message-ID: <493618E2.2030003@incunabulum.net>

Hi,

NS.GEETHANJALI wrote:
>  Dear Sir
>
> > I have one doubt regarding EBGP configuration.
> > The localpref,med,and as-path prepend algorithm are valid for
> > connected routes or not.
> > Since i am exporting connected routes in to ebgp. So what ever
> > localpref, med values have no effect on best path selection
> > So please kindly advise me

Please post your XORP configuration to the list so that someone can give 
more specific advice about this issue.

thanks
BMS


From bms at incunabulum.net  Tue Dec  2 21:50:00 2008
From: bms at incunabulum.net (Bruce M Simpson)
Date: Wed, 03 Dec 2008 05:50:00 +0000
Subject: [Xorp-users] Issue in BGP Configuration
In-Reply-To: <55006.10.100.3.228.1228121681.squirrel@indiamail.einfochips.com>
References: <32997.10.100.3.228.1227077987.squirrel@indiamail.einfochips.com>
	<49242229.6040300@incunabulum.net>
	<55006.10.100.3.228.1228121681.squirrel@indiamail.einfochips.com>
Message-ID: <49361E08.4000400@incunabulum.net>

Hi,

Thanks for this.

I'm afraid this backtrace looks quite normal on its own -- the xorp_bgp 
process is sitting in the EventLoop, presumably processing inbound 
traffic. If it is waiting for something, it isn't clear what it is 
waiting for.

Riddhi Shah wrote:
> I had done debugging steps according to your suggestions.
> Whatever output came , i have attached logs herewith.
> I attached two following files.
>
> 1)Log.txt - Which contains logs when configuration file was runnig with
> debugging steps.
> 2)Execution_Of_ConfigurationFile - Which contains execution of configuration file
>   

Based on the logs, it looks like you didn't continue the BGP process 
after breaking into it to get the backtrace, so I am guessing that the 
rest of the log entries are just collateral damage from this -- however 
-- it is very similar to the original issue you reported.

When the BGP daemon gets into this state, you might want to try firing 
basic XRLs at it from common.xif using the call_xrl tool to see if it's 
alive.

In your original configuration you are running only BGP, FIB2MRIB, the 
FEA, and the MFEA -- you are not running policy.

This is a bit of a long shot, but I still can't figure out what the real 
underlying problem is there: There have been recent changes in this 
area, as there were historical hacks necessary to get policy and bgp to 
start in the correct order. You might want to try configuring an empty 
policy {} block in the protocols {} block, and see if BGP still 'hangs'.

thanks
BMS


From bms at incunabulum.net  Tue Dec  2 22:03:13 2008
From: bms at incunabulum.net (Bruce M Simpson)
Date: Wed, 03 Dec 2008 06:03:13 +0000
Subject: [Xorp-users] ospf6 on linux 2.6.26
In-Reply-To: <49353119.3020407@traxx.ch>
References: <49353119.3020407@traxx.ch>
Message-ID: <49362121.20803@incunabulum.net>

Hi,

Pascal Spring wrote:
> hello
>
> is there some special requirement to run ospf6 on linux (sysctl settings
> a.s.o)?
> i'm not able to set up a simple ospf6 config of two routers connected
> via eth, neither a connection via sit-tunnel.
> tpcdump doesn't show any multicast-packets between the neighbors, 'run
> show ospf6 neighbor' shows no neighboring routers.
>   

I'm not aware of any special configuration needed to run XORP's OSPFv3 
over IPv6, although I haven't tried it myself.

It may also be helpful if you post your XORP configuration to the list, 
as well as the log contents from the router(s) affected, and possibly 
also your Linux kernel configuration.

If you are using sit.ko, can you please provide full details of how you 
are configuring the tunnel (presumably using iproute2 'ip' command) ?

Sometimes just doing this alone is enough to discover a typo, etc.

You may wish to double check that the appropriate multicast groups have 
actually been set up and joined at driver level, by looking in /proc:
    /proc/net/igmp
    /proc/net/igmp6
    /proc/net/mcfilter
    /proc/net/mcfilter6

I've had problems with Linux in the past where the kernel didn't support 
multicast socket options due to the appropriate kernel options being 
missing, with non-obvious error messages.

OSPFv3 has fairly complete regression test coverage as far as I'm aware, 
although obviously we can't simulate the entire host stack. If OSPFv3 is 
misbehaving on Linux then obviously we need to see evidence of the 
failure and the failure mode.

thanks
BMS


From bms at incunabulum.net  Tue Dec  2 22:30:46 2008
From: bms at incunabulum.net (Bruce M Simpson)
Date: Wed, 03 Dec 2008 06:30:46 +0000
Subject: [Xorp-users] iBGP routes not being used/forwarded
In-Reply-To: <f9d2a5e10811241413w2101aeebnbb8a54cca2368750@mail.gmail.com>
References: <f9d2a5e10811241401l6fbacd92w4ed88ea814e8bf84@mail.gmail.com>
	<f9d2a5e10811241413w2101aeebnbb8a54cca2368750@mail.gmail.com>
Message-ID: <49362796.7090104@incunabulum.net>

Russ,

We need to see what the RIB thinks about the routes you're introducing 
from your collector daemon.

Russ Dill wrote:
> ...
>
> However, no local routes are added:
>
> ip route
> 192.168.1.0/24 <http://192.168.1.0/24> dev eth0  proto kernel  scope 
> link  src 192.168.1.136 <http://192.168.1.136>  metric 2
> 169.254.0.0/16 <http://169.254.0.0/16> dev eth0  scope link  metric 1000
> 10.0.0.0/8 <http://10.0.0.0/8> dev mea0  scope link
> default via 192.168.1.1 <http://192.168.1.1> dev eth0
>
> And no updates are sent to the backhaul peer.
>
> Both peers are running XORP 1.5-6 from debian.
>   

The most likely explanation for the behaviour you are seeing, is that 
the updates are present in the BGP routing table, but the RIB is not 
selecting them as the candidate paths because of that 10.0.0.0/8 entry, 
which the RIB will learn about from the FEA as a 'connected' route. 
That's pretty clear from the output you've provided.

Note that whilst the iBGP routes are "valid", they are not "best", 
therefore there is absolutely no reason for iBGP to propagate them in 
updates -- unless you do some very specific tweaking using LOCAL_PREF 
and import policies, to cause those routes to win BGP's internal lookup.

You're also going to have to do some tricks with administrative distance 
to get the RIB to choose the iBGP learned routes with the /24 prefixes. 
XORP defaults to an admin distance of 200 for iBGP and 0 for "connected" 
routes, so clearly, the iBGP routes will lose the RIB lookup every time.

I believe the features to control admin distance on a per-protocol basis 
got added in the run up to the 1.5 release -- OLSR certainly makes use 
of them -- although they may not be fully documented until 1.6.

thanks
BMS




From russ.dill at gmail.com  Tue Dec  2 23:01:52 2008
From: russ.dill at gmail.com (Russ Dill)
Date: Wed, 3 Dec 2008 00:01:52 -0700
Subject: [Xorp-users] iBGP routes not being used/forwarded
In-Reply-To: <49362796.7090104@incunabulum.net>
References: <f9d2a5e10811241401l6fbacd92w4ed88ea814e8bf84@mail.gmail.com>
	<f9d2a5e10811241413w2101aeebnbb8a54cca2368750@mail.gmail.com>
	<49362796.7090104@incunabulum.net>
Message-ID: <f9d2a5e10812022301u5235b4fenb1ed7e7cabcb883c@mail.gmail.com>

I figured out my issue, I needed to include an empty AS list with my route
instead of including my own AS.

On Tue, Dec 2, 2008 at 11:30 PM, Bruce M Simpson <bms at incunabulum.net>wrote:

> Russ,
>
> We need to see what the RIB thinks about the routes you're introducing from
> your collector daemon.
>
> Russ Dill wrote:
>
>> ...
>>
>> However, no local routes are added:
>>
>> ip route
>> 192.168.1.0/24 <http://192.168.1.0/24> dev eth0  proto kernel  scope link
>>  src 192.168.1.136 <http://192.168.1.136>  metric 2
>> 169.254.0.0/16 <http://169.254.0.0/16> dev eth0  scope link  metric 1000
>> 10.0.0.0/8 <http://10.0.0.0/8> dev mea0  scope link
>> default via 192.168.1.1 <http://192.168.1.1> dev eth0
>>
>> And no updates are sent to the backhaul peer.
>>
>> Both peers are running XORP 1.5-6 from debian.
>>
>>
>
> The most likely explanation for the behaviour you are seeing, is that the
> updates are present in the BGP routing table, but the RIB is not selecting
> them as the candidate paths because of that 10.0.0.0/8 entry, which the
> RIB will learn about from the FEA as a 'connected' route. That's pretty
> clear from the output you've provided.
>
> Note that whilst the iBGP routes are "valid", they are not "best",
> therefore there is absolutely no reason for iBGP to propagate them in
> updates -- unless you do some very specific tweaking using LOCAL_PREF and
> import policies, to cause those routes to win BGP's internal lookup.
>
> You're also going to have to do some tricks with administrative distance to
> get the RIB to choose the iBGP learned routes with the /24 prefixes. XORP
> defaults to an admin distance of 200 for iBGP and 0 for "connected" routes,
> so clearly, the iBGP routes will lose the RIB lookup every time.
>
> I believe the features to control admin distance on a per-protocol basis
> got added in the run up to the 1.5 release -- OLSR certainly makes use of
> them -- although they may not be fully documented until 1.6.
>
> thanks
> BMS
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20081203/26654824/attachment.html 

From lists at traxx.ch  Thu Dec  4 04:38:16 2008
From: lists at traxx.ch (Pascal Spring)
Date: Thu, 04 Dec 2008 13:38:16 +0100
Subject: [Xorp-users] ospf6 on linux 2.6.26
In-Reply-To: <49362121.20803@incunabulum.net>
References: <49353119.3020407@traxx.ch> <49362121.20803@incunabulum.net>
Message-ID: <4937CF38.2090606@traxx.ch>

Hello Bruce

well, here is the config

        ospf6 10 {
            router-id: xxx.xxx.xxx.xxx
            ip-router-alert: false
            traceoptions {
            }
            area 0.0.0.3 {
                area-type: "normal"
                interface vpn0 {
                    link-type: "p2p"
                }
                interface br0 {
                    link-type: "broadcast"
                }
                interface eth1 {
                    link-type: "broadcast"
                }
            }
        }

vpn0 is a sit-tunnel made with ip tunnel add vpn0 mode sit local
xxx.xxx.xxx.xxx  remote yyy.yyy.yyy.yyy ttl 64, mtu is set on 1280,
multicast is turned on
i tried to set up an ospf6 neighborhood over eth1 and br0 with another
router of the same type and config as well - without success.

the relevant parts from igmp6 proc is not showing a ospf group membership:

3    eth1            ff0200000000000000000001ff000000     1 00000004 0
3    eth1            ff020000000000000000000000000002     1 00000004 0
3    eth1            ff0200000000000000000001ff15dbbd     1 00000004 0
3    eth1            ff020000000000000000000000000001     1 0000000C 0
13   sit0            ff020000000000000000000000000001     1 0000000C 0

on the other side if i check igmp proc with running and working ospf4 i
cannot see the equivalent ospf group membership as well:

4       eth2      :     8      V3
                                060000E0     1 0:00000000               0
                                050000E0     1 0:00000000               0
                                010000E0     1 0:00000000               0

both proc mcfilter and mcfilter6 are empty

to the kernel config i can say that everything needed is set - since
running as stable environment testing and experimental codes are
disabled, so there is no ipv6-multicast-routing (what should not have
influence) activated,
regular (ipv4) multicasting and multicast-routing support are enabled

well,  so long
p.

Bruce M Simpson wrote:
> Hi,
>
> Pascal Spring wrote:
>> hello
>>
>> is there some special requirement to run ospf6 on linux (sysctl settings
>> a.s.o)?
>> i'm not able to set up a simple ospf6 config of two routers connected
>> via eth, neither a connection via sit-tunnel.
>> tpcdump doesn't show any multicast-packets between the neighbors, 'run
>> show ospf6 neighbor' shows no neighboring routers.
>>   
>
> I'm not aware of any special configuration needed to run XORP's OSPFv3
> over IPv6, although I haven't tried it myself.
>
> It may also be helpful if you post your XORP configuration to the
> list, as well as the log contents from the router(s) affected, and
> possibly also your Linux kernel configuration.
>
> If you are using sit.ko, can you please provide full details of how
> you are configuring the tunnel (presumably using iproute2 'ip' command) ?
>
> Sometimes just doing this alone is enough to discover a typo, etc.
>
> You may wish to double check that the appropriate multicast groups
> have actually been set up and joined at driver level, by looking in
> /proc:
>    /proc/net/igmp
>    /proc/net/igmp6
>    /proc/net/mcfilter
>    /proc/net/mcfilter6
>
> I've had problems with Linux in the past where the kernel didn't
> support multicast socket options due to the appropriate kernel options
> being missing, with non-obvious error messages.
>
> OSPFv3 has fairly complete regression test coverage as far as I'm
> aware, although obviously we can't simulate the entire host stack. If
> OSPFv3 is misbehaving on Linux then obviously we need to see evidence
> of the failure and the failure mode.
>
> thanks
> BMS
>


From strauss69 at gmail.com  Thu Dec  4 06:28:41 2008
From: strauss69 at gmail.com (L Janovszki)
Date: Thu, 4 Dec 2008 15:28:41 +0100
Subject: [Xorp-users] XORP OSPFv3 not functional
Message-ID: <5eeb8b90812040628l570270b1g1bb319fda58ca8ee@mail.gmail.com>

Hi,

I've OSPFv3 in a triangle router setup (R1,R2,R3) and R4 (cisco) connected
to R3. See picture:

                  LAN1
                   |
                  R1
                 /  \
                /    \
       LAN2---R2-----R3 ---- R4 ----FW

Xorp (1.5~cvs.20080128) is running under ubuntu hardy. Segments
R1-LAN1,R1-R2,R2-LAN are not seen in the cisco.
I also downloaded the 1.5 latest and compiled which looks better I see every
segment distributed from R3 to R4 but after shut down R2 completely routing
messed  up. When the network is changing routing get unstable, segments are
missing again.

Config files are the same, only router-ids are different (10.4.6.1, 10.4.6.2,
10.4.6.3, 10.4.6.4) for the routers.

   protocols {
        ospf6 0 {
            router-id: 10.4.6.1
            area 0.0.0.0 {
                interface eth0 {
                    vif eth0 {
                    }
                }
                interface eth1 {
                    vif eth1 {
                    }
                }
                interface eth2 {
                    vif eth2 {
                    }
                }
            }
        }
    }
    fea {
        unicast-forwarding6 {
        }
    }
    interfaces {
        interface eth0 {
            description: "Ethernet"
            default-system-config
        }
        interface eth1 {
            description: "Ethernet"
            default-system-config
        }
        interface eth2 {
            description: "Ethernet"
            default-system-config {
            }
        }
    }


Was it tested before? For me it looks early implementation.
Any help would be appreciated !

Regards,
Levente
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20081204/973aa93f/attachment.html 

From atanu at xorp.org  Thu Dec  4 09:30:57 2008
From: atanu at xorp.org (Atanu Ghosh)
Date: Thu, 04 Dec 2008 09:30:57 -0800
Subject: [Xorp-users] ospf6 on linux 2.6.26
In-Reply-To: Message from Pascal Spring <lists@traxx.ch> 
	of "Thu, 04 Dec 2008 13:38:16 +0100." <4937CF38.2090606@traxx.ch> 
Message-ID: <47175.1228411857@xorps.icir.org>

Hi,

In order for OSPFv3 to run you will need to add the the IPv6 link local
address for each interface that is being used in the interfaces
block. The number after "ospf6" 10 in your case is the instance ID this
value needs to be the same for each OSPFv3 instance.

      Atanu.

>>>>> "Pascal" == Pascal Spring <lists at traxx.ch> writes:

    Pascal> Hello Bruce
    Pascal> well, here is the config

    Pascal> ospf6 10 {
    Pascal> router-id: xxx.xxx.xxx.xxx
    Pascal> ip-router-alert: false
    Pascal> traceoptions {
    Pascal> }
    Pascal> area 0.0.0.3 {
    Pascal> area-type: "normal"
    Pascal> interface vpn0 {
    Pascal> link-type: "p2p"
    Pascal> }
    Pascal> interface br0 {
    Pascal> link-type: "broadcast"
    Pascal> }
    Pascal> interface eth1 {
    Pascal> link-type: "broadcast"
    Pascal> }
    Pascal> }
    Pascal> }

    Pascal> vpn0 is a sit-tunnel made with ip tunnel add vpn0 mode sit local
    Pascal> xxx.xxx.xxx.xxx  remote yyy.yyy.yyy.yyy ttl 64, mtu is set on 1280,
    Pascal> multicast is turned on
    Pascal> i tried to set up an ospf6 neighborhood over eth1 and br0 with another
    Pascal> router of the same type and config as well - without success.

    Pascal> the relevant parts from igmp6 proc is not showing a ospf group membership:

    Pascal> 3    eth1            ff0200000000000000000001ff000000     1 00000004 0
    Pascal> 3    eth1            ff020000000000000000000000000002     1 00000004 0
    Pascal> 3    eth1            ff0200000000000000000001ff15dbbd     1 00000004 0
    Pascal> 3    eth1            ff020000000000000000000000000001     1 0000000C 0
    Pascal> 13   sit0            ff020000000000000000000000000001     1 0000000C 0

    Pascal> on the other side if i check igmp proc with running and working ospf4 i
    Pascal> cannot see the equivalent ospf group membership as well:

    Pascal> 4       eth2      :     8      V3
    Pascal> 060000E0     1 0:00000000               0
    Pascal> 050000E0     1 0:00000000               0
    Pascal> 010000E0     1 0:00000000               0

    Pascal> both proc mcfilter and mcfilter6 are empty

    Pascal> to the kernel config i can say that everything needed is set - since
    Pascal> running as stable environment testing and experimental codes are
    Pascal> disabled, so there is no ipv6-multicast-routing (what should not have
    Pascal> influence) activated,
    Pascal> regular (ipv4) multicasting and multicast-routing support are enabled

    Pascal> well,  so long
    Pascal> p.

    Pascal> Bruce M Simpson wrote:
    >> Hi,
    >> 
    >> Pascal Spring wrote:
    >>> hello
    >>> 
    >>> is there some special requirement to run ospf6 on linux (sysctl settings
    >>> a.s.o)?
    >>> i'm not able to set up a simple ospf6 config of two routers connected
    >>> via eth, neither a connection via sit-tunnel.
    >>> tpcdump doesn't show any multicast-packets between the neighbors, 'run
    >>> show ospf6 neighbor' shows no neighboring routers.
    >>> 
    >> 
    >> I'm not aware of any special configuration needed to run XORP's OSPFv3
    >> over IPv6, although I haven't tried it myself.
    >> 
    >> It may also be helpful if you post your XORP configuration to the
    >> list, as well as the log contents from the router(s) affected, and
    >> possibly also your Linux kernel configuration.
    >> 
    >> If you are using sit.ko, can you please provide full details of how
    >> you are configuring the tunnel (presumably using iproute2 'ip' command) ?
    >> 
    >> Sometimes just doing this alone is enough to discover a typo, etc.
    >> 
    >> You may wish to double check that the appropriate multicast groups
    >> have actually been set up and joined at driver level, by looking in
    >> /proc:
    >> /proc/net/igmp
    >> /proc/net/igmp6
    >> /proc/net/mcfilter
    >> /proc/net/mcfilter6
    >> 
    >> I've had problems with Linux in the past where the kernel didn't
    >> support multicast socket options due to the appropriate kernel options
    >> being missing, with non-obvious error messages.
    >> 
    >> OSPFv3 has fairly complete regression test coverage as far as I'm
    >> aware, although obviously we can't simulate the entire host stack. If
    >> OSPFv3 is misbehaving on Linux then obviously we need to see evidence
    >> of the failure and the failure mode.
    >> 
    >> thanks
    >> BMS
    >> 

    Pascal> _______________________________________________
    Pascal> Xorp-users mailing list
    Pascal> Xorp-users at xorp.org
    Pascal> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


From andreas.voellmy at gmail.com  Thu Dec  4 14:03:03 2008
From: andreas.voellmy at gmail.com (Andreas Voellmy)
Date: Thu, 4 Dec 2008 17:03:03 -0500
Subject: [Xorp-users] Regular expressions in BGP policy
Message-ID: <6d3800770812041403p729ed52cq9e95bc0f778444f3@mail.gmail.com>

Hi,

I'm not sure how to match routes against an as-list regular expression
in bgp policy. I have a simple example that is not behaving as I
expect. In my example I have a single import policy, like this:

policy-statement imppol {
	term impterm {
		from {
			as-path: "34567"
		}
		then {
			trace: 4
			reject
		}
	}
}


and I've connected this xorp router to another router, with AS 34567,
exporting a single route. I would expect that this route would match
the term in imppol, would be rejected, and would not be installed in
the bgp table of the receiver. From the tracing messages, it does look
like the route matches the term, and that the result is to reject the
route. HOWEVER, the route show up in my bgp table. Here is the trace
message when the route is received:

SubnetRoute:
  Net: 10.10.11.0/24
  PAList:
        Next Hop Attribute 128.36.229.113
        Origin Path Attribute - IGP
        AS Path Attribute AsPath: [AS/34567]
        Multiple Exit Descriminator Attribute: MED=0
        Local Preference Attribute - 100: rejected
Basic VarRW trace:
Read 14: AsPath: [AS/34567]
Write 0: 4
Read 14: AsPath: [AS/34567]
Write 0: 4
Execution trace:
Running policy: imppol
Running term: impterm
PUSH txt 34567
LOAD 14: AsPath: [AS/34567]
REGEX
ONFALSE_EXIT: true
PUSH u32 4
STORE 0: 4
REJECT
Outcome of term: Reject
Outcome of policy: Reject
Outcome of whole filter: Reject
End of trace

And Here is my BGP route table:

> show bgp routes
Status Codes: * valid route, > best route
Origin Codes: i IGP, e EGP, ? incomplete

   Prefix                Nexthop                    Peer            AS Path
   ------                -------                    ----            -------
*  10.10.11.0/24         128.36.229.113             128.36.229.113  34567 i

I would greatly appreciate it if someone could point out what I've
done wrong here. Thanks!

Regards,
Andreas Voellmy


From lists at traxx.ch  Thu Dec  4 14:55:06 2008
From: lists at traxx.ch (Pascal Spring)
Date: Thu, 04 Dec 2008 23:55:06 +0100
Subject: [Xorp-users] ospf6 on linux 2.6.26
In-Reply-To: <47175.1228411857@xorps.icir.org>
References: <47175.1228411857@xorps.icir.org>
Message-ID: <49385FCA.4070404@traxx.ch>

hi atanu

well, so far thanks for the information - i discovered it in the release
note from xorp 1.4 in the meanwhile - i'll try it out more detailed
tomorrow,
as far as i already tried out tonight, something in the mcast group
membership changes for ethernets, but for sit-interfaces no change -
but hear from me tomorrow.

to the www.xorg.net-maintainers: would be maybe worth to mention the
requirement for explicitly configured link-local addresses to run
ripng/ospfv3 in the 'getting started'

p.

Atanu Ghosh wrote:
> Hi,
>
> In order for OSPFv3 to run you will need to add the the IPv6 link local
> address for each interface that is being used in the interfaces
> block. The number after "ospf6" 10 in your case is the instance ID this
> value needs to be the same for each OSPFv3 instance.
>
>       Atanu.
>
>   
>>>>>> "Pascal" == Pascal Spring <lists at traxx.ch> writes:
>>>>>>             
>
>     Pascal> Hello Bruce
>     Pascal> well, here is the config
>
>     Pascal> ospf6 10 {
>     Pascal> router-id: xxx.xxx.xxx.xxx
>     Pascal> ip-router-alert: false
>     Pascal> traceoptions {
>     Pascal> }
>     Pascal> area 0.0.0.3 {
>     Pascal> area-type: "normal"
>     Pascal> interface vpn0 {
>     Pascal> link-type: "p2p"
>     Pascal> }
>     Pascal> interface br0 {
>     Pascal> link-type: "broadcast"
>     Pascal> }
>     Pascal> interface eth1 {
>     Pascal> link-type: "broadcast"
>     Pascal> }
>     Pascal> }
>     Pascal> }
>
>     Pascal> vpn0 is a sit-tunnel made with ip tunnel add vpn0 mode sit local
>     Pascal> xxx.xxx.xxx.xxx  remote yyy.yyy.yyy.yyy ttl 64, mtu is set on 1280,
>     Pascal> multicast is turned on
>     Pascal> i tried to set up an ospf6 neighborhood over eth1 and br0 with another
>     Pascal> router of the same type and config as well - without success.
>
>     Pascal> the relevant parts from igmp6 proc is not showing a ospf group membership:
>
>     Pascal> 3    eth1            ff0200000000000000000001ff000000     1 00000004 0
>     Pascal> 3    eth1            ff020000000000000000000000000002     1 00000004 0
>     Pascal> 3    eth1            ff0200000000000000000001ff15dbbd     1 00000004 0
>     Pascal> 3    eth1            ff020000000000000000000000000001     1 0000000C 0
>     Pascal> 13   sit0            ff020000000000000000000000000001     1 0000000C 0
>
>     Pascal> on the other side if i check igmp proc with running and working ospf4 i
>     Pascal> cannot see the equivalent ospf group membership as well:
>
>     Pascal> 4       eth2      :     8      V3
>     Pascal> 060000E0     1 0:00000000               0
>     Pascal> 050000E0     1 0:00000000               0
>     Pascal> 010000E0     1 0:00000000               0
>
>     Pascal> both proc mcfilter and mcfilter6 are empty
>
>     Pascal> to the kernel config i can say that everything needed is set - since
>     Pascal> running as stable environment testing and experimental codes are
>     Pascal> disabled, so there is no ipv6-multicast-routing (what should not have
>     Pascal> influence) activated,
>     Pascal> regular (ipv4) multicasting and multicast-routing support are enabled
>
>     Pascal> well,  so long
>     Pascal> p.
>
>     Pascal> Bruce M Simpson wrote:
>     >> Hi,
>     >> 
>     >> Pascal Spring wrote:
>     >>> hello
>     >>> 
>     >>> is there some special requirement to run ospf6 on linux (sysctl settings
>     >>> a.s.o)?
>     >>> i'm not able to set up a simple ospf6 config of two routers connected
>     >>> via eth, neither a connection via sit-tunnel.
>     >>> tpcdump doesn't show any multicast-packets between the neighbors, 'run
>     >>> show ospf6 neighbor' shows no neighboring routers.
>     >>> 
>     >> 
>     >> I'm not aware of any special configuration needed to run XORP's OSPFv3
>     >> over IPv6, although I haven't tried it myself.
>     >> 
>     >> It may also be helpful if you post your XORP configuration to the
>     >> list, as well as the log contents from the router(s) affected, and
>     >> possibly also your Linux kernel configuration.
>     >> 
>     >> If you are using sit.ko, can you please provide full details of how
>     >> you are configuring the tunnel (presumably using iproute2 'ip' command) ?
>     >> 
>     >> Sometimes just doing this alone is enough to discover a typo, etc.
>     >> 
>     >> You may wish to double check that the appropriate multicast groups
>     >> have actually been set up and joined at driver level, by looking in
>     >> /proc:
>     >> /proc/net/igmp
>     >> /proc/net/igmp6
>     >> /proc/net/mcfilter
>     >> /proc/net/mcfilter6
>     >> 
>     >> I've had problems with Linux in the past where the kernel didn't
>     >> support multicast socket options due to the appropriate kernel options
>     >> being missing, with non-obvious error messages.
>     >> 
>     >> OSPFv3 has fairly complete regression test coverage as far as I'm
>     >> aware, although obviously we can't simulate the entire host stack. If
>     >> OSPFv3 is misbehaving on Linux then obviously we need to see evidence
>     >> of the failure and the failure mode.
>     >> 
>     >> thanks
>     >> BMS
>     >> 
>
>     Pascal> _______________________________________________
>     Pascal> Xorp-users mailing list
>     Pascal> Xorp-users at xorp.org
>     Pascal> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
>   


From james.dutton at gmail.com  Fri Dec  5 02:21:39 2008
From: james.dutton at gmail.com (James Courtier-Dutton)
Date: Fri, 5 Dec 2008 10:21:39 +0000
Subject: [Xorp-users] Avoiding asynchronous routing with OSPF
In-Reply-To: <141453438E4CF1CFE1CBE487@Dirks-MacBook-Pro.local>
References: <CA7148A9CBB05A7751CAF796@file.wkd-druck.org>
	<ad2655cb0809040836p48295e4amd0b5a3f64f0f91ce@mail.gmail.com>
	<141453438E4CF1CFE1CBE487@Dirks-MacBook-Pro.local>
Message-ID: <ad2655cb0812050221j756e38adk7c4d7d7ca157ebd2@mail.gmail.com>

2008/9/12 Dirk H. Schulz <dirk.schulz at kinzesberg.de>:
> Hi James,
>
> --On 4. September 2008 16:36:42 +0100 James Courtier-Dutton
> <james.dutton at gmail.com> wrote:
>
>> On 12/08/2008, Dirk H. Schulz <dirk.schulz at kinzesberg.de> wrote:
>>>
>>> The problem I have is that packets from servers in subnet B go out via
>>> router2 and answers partially come back via router1. I tried to avoid
>>> this by setting interface costs:
>>> 1. The hightest interface cost is on eth1 which connects my routers
>>> directly (so data traffic between MY routers should be avoided).
>>> 2. The interface ethA without virtual ip address A (that is ethA on
>>> router2) has a significantly higher cost than the other; with ethB it is
>>> similar.
>>>
>> Do you understand the cost setting in OSPF?
>> The ospf cost set on an interface is the cost to SEND packets out.
>> The ospf cost set on an interface has no affect on incoming packets.
>> I only ask in case you have set the cost on the wrong end of the link.
>
> I did not understand that detail yet, but it does not make any difference in
> my scenario - I have recalculated the path costs with that information.
>
> Seems that my problem is a bit more complicated:
>              -------------                  -------------
>              |      1     |-----------------|      2     |
> upstream routers            |                 |            |
>              |            |                 |            |
>              -------------                  -------------
>                     |                              |
>                     |                              |
>                     |                              |
>              -------------                  -------------
>              |      1     |-----------------|      2     |
> my routers (connected via eth1)               |            |
>              |            |                 |            |
>              -------------                  -------------
>                 |      |                        |      |
>                 |      |                        |      |
>                 |      |     -----------        |      |
>                  -----------|          |--------       |
> switch A (subnet A)           |          |
>                        |    |          |               |
>                        |     -----------               |
>                        |                               |
>                        |     -----------               |
>                        -----|          |---------------|
> switch B (subnet B)           |          |
>                             |          |
>                              -----------
>
> I want packets destined for subnet B always to come in on my router nr. 2
> (and subnet A vice versa). But if a packet for subnet B arrives on upstream
> router 1, that means it has to do one more hop using upstream router 2 to
> reach my router 2 (compared to going via my router 1).
>
> Can I configure OSPF so that path costs are weighed higher than hop count?
>
> Dirk
>

OSPF does not care about hop count. It is purely cost.
Just make the outgoing cost on interface 1 -> B high, and 2 -> A high.
OSPF will then prefer 1 -> 2 -> B over 1 -> B.
and prefer 2 -> 1 -> A over 2 -> A.


From Jean.Cao at gdcanada.com  Tue Dec  9 15:32:08 2008
From: Jean.Cao at gdcanada.com (Cao, Jean)
Date: Tue, 9 Dec 2008 16:32:08 -0700
Subject: [Xorp-users] One XORP instance output to multiple tables?
Message-ID: <0843D0F1EEBB2E49A2156C6981B4A17E052D8223@CGYSVW100.gdcan.com>

Is that possible to run one XORP instance and output the routes to
multiple tables?  For example, run OSFP, and output the results (same)
in both table 100 and table 200?  I guess if run two XORP instance with
the same config.boot, one write to table 100, and one write to 200, it
can give me what I need.  But this way, the routing messages are
doubled.  Is there a solution for this??
 
Thanks,
Jean

The information contained in this e-mail message is PRIVATE. It may contain confidential information and may be legally privileged. It is intended for the exclusive use of the addressee(s). If you are not the intended recipient, you are hereby notified that any dissemination, distribution or reproduction of this communication is strictly prohibited. If the intended recipient(s) cannot be reached or if a transmission problem has occurred, please notify the sender immediately by return e-mail and destroy all copies of this message. 
Thank you. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20081209/3b65d116/attachment.html 

From atanu at xorp.org  Wed Dec 10 10:36:08 2008
From: atanu at xorp.org (Atanu Ghosh)
Date: Wed, 10 Dec 2008 10:36:08 -0800
Subject: [Xorp-users] Regular expressions in BGP policy
In-Reply-To: Message from "Andreas Voellmy" <andreas.voellmy@gmail.com> 
	of "Thu, 04 Dec 2008 17:03:03 EST."
	<6d3800770812041403p729ed52cq9e95bc0f778444f3@mail.gmail.com> 
Message-ID: <16726.1228934168@xorps.icir.org>

Hi,

The "show bgp routes" command shows the routes in the BGP RIB-IN we don't
remove filtered routes from the RIB-IN. The routes are left in the
RIB-IN to allow the user the change a policy, in which case all the
routes in the RIB-IN are refiltered. It is true that we should probably
annotate the route so that "show bgp routes" marks filtered routes.

If a route has been filtered then it won't be sent to the RIB or the BGP
peers, so the simple way to check is to run "show route table ipv4
unicast ibgp" or "show route table ipv4 unicast ebgp" depending on the
type of peering.

     Atanu.

>>>>> "Andreas" == Andreas Voellmy <andreas.voellmy at gmail.com> writes:

    Andreas> Hi,
    Andreas> I'm not sure how to match routes against an as-list regular expression
    Andreas> in bgp policy. I have a simple example that is not behaving as I
    Andreas> expect. In my example I have a single import policy, like this:

    Andreas> policy-statement imppol {
    Andreas> term impterm {
    Andreas> from {
    Andreas> as-path: "34567"
    Andreas> }
    Andreas> then {
    Andreas> trace: 4
    Andreas> reject
    Andreas> }
    Andreas> }
    Andreas> }


    Andreas> and I've connected this xorp router to another router, with AS 34567,
    Andreas> exporting a single route. I would expect that this route would match
    Andreas> the term in imppol, would be rejected, and would not be installed in
    Andreas> the bgp table of the receiver. From the tracing messages, it does look
    Andreas> like the route matches the term, and that the result is to reject the
    Andreas> route. HOWEVER, the route show up in my bgp table. Here is the trace
    Andreas> message when the route is received:

    Andreas> SubnetRoute:
    Andreas> Net: 10.10.11.0/24
    Andreas> PAList:
    Andreas> Next Hop Attribute 128.36.229.113
    Andreas> Origin Path Attribute - IGP
    Andreas> AS Path Attribute AsPath: [AS/34567]
    Andreas> Multiple Exit Descriminator Attribute: MED=0
    Andreas> Local Preference Attribute - 100: rejected
    Andreas> Basic VarRW trace:
    Andreas> Read 14: AsPath: [AS/34567]
    Andreas> Write 0: 4
    Andreas> Read 14: AsPath: [AS/34567]
    Andreas> Write 0: 4
    Andreas> Execution trace:
    Andreas> Running policy: imppol
    Andreas> Running term: impterm
    Andreas> PUSH txt 34567
    Andreas> LOAD 14: AsPath: [AS/34567]
    Andreas> REGEX
    Andreas> ONFALSE_EXIT: true
    Andreas> PUSH u32 4
    Andreas> STORE 0: 4
    Andreas> REJECT
    Andreas> Outcome of term: Reject
    Andreas> Outcome of policy: Reject
    Andreas> Outcome of whole filter: Reject
    Andreas> End of trace

    Andreas> And Here is my BGP route table:

    >> show bgp routes
    Andreas> Status Codes: * valid route, > best route
    Andreas> Origin Codes: i IGP, e EGP, ? incomplete

    Andreas> Prefix                Nexthop                    Peer            AS Path
    Andreas> ------                -------                    ----            -------
    Andreas> *  10.10.11.0/24         128.36.229.113             128.36.229.113  34567 i

    Andreas> I would greatly appreciate it if someone could point out what I've
    Andreas> done wrong here. Thanks!

    Andreas> Regards,
    Andreas> Andreas Voellmy

    Andreas> _______________________________________________
    Andreas> Xorp-users mailing list
    Andreas> Xorp-users at xorp.org
    Andreas> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


From karnik.jain at einfochips.com  Wed Dec 17 01:07:00 2008
From: karnik.jain at einfochips.com (karnik)
Date: Wed, 17 Dec 2008 14:37:00 +0530
Subject: [Xorp-users] [OSPFv2] XORP ospf can't receive hello packet from
	other OSPF router
Message-ID: <4948C134.2070302@einfochips.com>

system configuration:
Ubuntu 8.04.1 ( as per /etc/issue.net)
kernal : 2.6.24-19-server
GCC vesion: gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)

-------------------------------------------------------------------------------
root at ubuntu:/usr/local/xorp/bin# uname -a
Linux ubuntu 2.6.24-19-server #1 SMP Wed Jun 18 15:18:00 UTC 2008 i686
GNU/Linux

*XORP version:* which is currently on XORP cvs

-------------------------------------------------------------------------------

*BUG:* XORP can't receive hello packet from other ospf router having same area, same lan segment ,hello and dead interval.

*reason: message displayed on XORP log.*
xorp error : Failed to joined multicast group 224.0.0.5: Address already in use.

And when i do /etc/init.d/networking restart at that time all routers run well, but after some time as it is. 
When i again start all routers at that time i faced same above mentioned error.

tell me what is wrong with XORP.

Test setup:

router 1 -------- router 2
eth0		  eth0




-- 
_____________________________________________________________________
Disclaimer: This e-mail message and all attachments transmitted with it
are intended solely for the use of the addressee and may contain legally
privileged and confidential information. If the reader of this message
is not the intended recipient, or an employee or agent responsible for
delivering this message to the intended recipient, you are hereby
notified that any dissemination, distribution, copying, or other use of
this message or its attachments is strictly prohibited. If you have
received this message in error, please notify the sender immediately by
replying to this message and please delete it from your computer. Any
views expressed in this message are those of the individual sender
unless otherwise stated.Company has taken enough precautions to prevent
the spread of viruses. However the company accepts no liability for any
damage caused by any virus transmitted by this email.
__________________________________________________________________________
 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: karnik_jain.vcf
Type: text/x-vcard
Size: 328 bytes
Desc: not available
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20081217/97fb2523/attachment.vcf 

From karnik.jain at einfochips.com  Wed Dec 17 06:56:23 2008
From: karnik.jain at einfochips.com (karnik)
Date: Wed, 17 Dec 2008 20:26:23 +0530
Subject: [Xorp-users] [OSPFv2] XORP ospf can't receive hello packet from
 other OSPF router
In-Reply-To: <c48427780812170355p7f58893ex2a88fa225734b8@mail.gmail.com>
References: <4948C134.2070302@einfochips.com>	
	<c48427780812170343v315d6e30m861246cc034166c7@mail.gmail.com>
	<c48427780812170355p7f58893ex2a88fa225734b8@mail.gmail.com>
Message-ID: <49491317.8080802@einfochips.com>

No , It is not related with 813

I am facing this problem not every time so i can not tell you
it is a bug or something else.


Syed Khalid wrote:
>
> Hi Karnik
>   Is this related to 813? From what I can read into your e-mail you 
> have 2 ubuntu PC's. When re-starting the networking on eth0, you get 
> adjacency - however, after a while it fails giving the error message.
> Is there a way we can login into your system to take a look?
> Syed
>
>
>     ---------- Forwarded message ----------
>     From: *karnik* <karnik.jain at einfochips.com
>     <mailto:karnik.jain at einfochips.com>>
>     Date: Wed, Dec 17, 2008 at 1:07 AM
>     Subject: [Xorp-users] [OSPFv2] XORP ospf can't receive hello
>     packet from other OSPF router
>     To: xorp-users at xorp.org <mailto:xorp-users at xorp.org>
>
>
>     system configuration:
>     Ubuntu 8.04.1 ( as per /etc/issue.net <http://issue.net/>)
>     kernal : 2.6.24-19-server
>     GCC vesion: gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)
>
>     -------------------------------------------------------------------------------
>     root at ubuntu:/usr/local/xorp/bin# uname -a
>     Linux ubuntu 2.6.24-19-server #1 SMP Wed Jun 18 15:18:00 UTC 2008 i686
>     GNU/Linux
>
>     *XORP version:* which is currently on XORP cvs
>
>     -------------------------------------------------------------------------------
>
>     *BUG:* XORP can't receive hello packet from other ospf router
>     having same area, same lan segment ,hello and dead interval.
>
>     *reason: message displayed on XORP log.*
>     xorp error : Failed to joined multicast group 224.0.0.5
>     <http://224.0.0.5/>: Address already in use.
>
>     And when i do /etc/init.d/networking restart at that time all
>     routers run well, but after some time as it is. When i again start
>     all routers at that time i faced same above mentioned error.
>
>     tell me what is wrong with XORP.
>
>     Test setup:
>
>     router 1 -------- router 2
>     eth0              eth0
>
>
>
>
>     -- 
>     _____________________________________________________________________
>     Disclaimer: This e-mail message and all attachments transmitted
>     with it
>     are intended solely for the use of the addressee and may contain
>     legally
>     privileged and confidential information. If the reader of this message
>     is not the intended recipient, or an employee or agent responsible for
>     delivering this message to the intended recipient, you are hereby
>     notified that any dissemination, distribution, copying, or other
>     use of
>     this message or its attachments is strictly prohibited. If you have
>     received this message in error, please notify the sender
>     immediately by
>     replying to this message and please delete it from your computer. Any
>     views expressed in this message are those of the individual sender
>     unless otherwise stated.Company has taken enough precautions to
>     prevent
>     the spread of viruses. However the company accepts no liability
>     for any
>     damage caused by any virus transmitted by this email.
>     __________________________________________________________________________
>
>
>     _______________________________________________
>     Xorp-users mailing list
>     Xorp-users at xorp.org <mailto:Xorp-users at xorp.org>
>     http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
>     <http://mailman.icsi.berkeley.edu/mailman/listinfo/xorp-users>
>
>
>
>
>
> *Email Scanned for Virus & Dangerous Content by :* 
> *www.CleanMailGateway.com*
>


-- 
_____________________________________________________________________
Disclaimer: This e-mail message and all attachments transmitted with it
are intended solely for the use of the addressee and may contain legally
privileged and confidential information. If the reader of this message
is not the intended recipient, or an employee or agent responsible for
delivering this message to the intended recipient, you are hereby
notified that any dissemination, distribution, copying, or other use of
this message or its attachments is strictly prohibited. If you have
received this message in error, please notify the sender immediately by
replying to this message and please delete it from your computer. Any
views expressed in this message are those of the individual sender
unless otherwise stated.Company has taken enough precautions to prevent
the spread of viruses. However the company accepts no liability for any
damage caused by any virus transmitted by this email.
__________________________________________________________________________
 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: karnik_jain.vcf
Type: text/x-vcard
Size: 328 bytes
Desc: not available
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20081217/73ce2b96/attachment.vcf 

From dony1985.0729 at yahoo.co.id  Wed Dec 17 07:58:50 2008
From: dony1985.0729 at yahoo.co.id (Dony Tata)
Date: Wed, 17 Dec 2008 23:58:50 +0800 (SGT)
Subject: [Xorp-users] register interface vif
Message-ID: <726933.22304.qm@web76112.mail.sg1.yahoo.com>

somebody know, how to add option "register interfaces vif"  with "xorpsh" console ?
i successfull add "register interface vif" with editing file config.boot, but i can't find this option on xorpsh console
example : 
protocols {
    pimsm4 {
        interface eth0 {
            vif eth0 {
                disable: false
            }
        }
        interface eth1 {
            vif eth1 {
                disable: false
            }
        }
        interface register_vif {
            vif register_vif {
                /* Note: this vif should be always enabled */
                disable: false
            }
        }


      Buat sendiri desain eksklusif Messenger Pingbox Anda sekarang! Membuat tempat chat pribadi di blog Anda sekarang sangatlah mudah. http://id.messenger.yahoo.com/pingbox/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20081217/0a45eff6/attachment.html 

From peirce at maine.edu  Wed Dec 17 08:21:36 2008
From: peirce at maine.edu (Garry Peirce)
Date: Wed, 17 Dec 2008 11:21:36 -0500
Subject: [Xorp-users] register interface vif
In-Reply-To: <726933.22304.qm@web76112.mail.sg1.yahoo.com>
References: <726933.22304.qm@web76112.mail.sg1.yahoo.com>
Message-ID: <007301c96063$885dd790$991986b0$@edu>

I think you have to add it into the plumbing section first. 

 

    plumbing {

        mfea4 {

            disable: false

            interface eth1 {

                vif eth1 {

                    disable: false

                }

            }

            interface "register_vif" {

                vif "register_vif" {

                    disable: false

                }

            }

 

?

 

 

--

Garry Peirce   +1-207-561-3539

Network Analyst,  ITS

University of Maine System

 

From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] On Behalf Of Dony Tata
Sent: Wednesday, December 17, 2008 10:59 AM
To: xorp-users at xorp.org
Subject: [Xorp-users] register interface vif

 

somebody know, how to add option "register interfaces vif"  with "xorpsh" console ?
i successfull add "register interface vif" with editing file config.boot, but i can't find this option on xorpsh console 
example : 
protocols {
    pimsm4 {
        interface eth0 {
            vif eth0 {
                disable: false
            }
        }
        interface eth1 {
            vif eth1 {
                disable: false
            }
        }
        interface register_vif {
            vif register_vif {
                /* Note: this vif should be always enabled */
                disable: false
            }
        }

 

  _____  

Bersenang-senang <http://sg.rd.yahoo.com/id/messenger/trueswitch/mailtagline/*http:/id.messenger.yahoo.com/invite/>  di Yahoo! Messenger dengan semua teman
Tambahkan mereka dari email atau jaringan sosial Anda sekarang!

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20081217/11f85b60/attachment-0001.html 

From syed.khalid at xorp.net  Wed Dec 17 17:52:40 2008
From: syed.khalid at xorp.net (Syed Khalid)
Date: Wed, 17 Dec 2008 17:52:40 -0800
Subject: [Xorp-users] [OSPFv2] XORP ospf can't receive hello packet from
	other OSPF router
In-Reply-To: <49491317.8080802@einfochips.com>
References: <4948C134.2070302@einfochips.com>
	<c48427780812170343v315d6e30m861246cc034166c7@mail.gmail.com>
	<c48427780812170355p7f58893ex2a88fa225734b8@mail.gmail.com>
	<49491317.8080802@einfochips.com>
Message-ID: <c48427780812171752l45e23e7cy3f143b18be9fac38@mail.gmail.com>

Karnik
  We tried to replicate this problem but were not able to. The 2 Ubuntu
machine did form adjacency. The ip addresses were on the same subnet on both
machines. We tried to plug/unplug the link but the adjecency stayed up.
However, if we configued another interace on the same subnet - we see your
problem. Do  not see if we are on a different subnet.
Can you send us the output from:
1) ip addr
2) ifconfig -a
3) show interface from the xorpsh

Also let us know if we can login to your system.

Syed

On Wed, Dec 17, 2008 at 6:56 AM, karnik <karnik.jain at einfochips.com> wrote:

> No , It is not related with 813
>
> I am facing this problem not every time so i can not tell you
> it is a bug or something else.
>
>
> Syed Khalid wrote:
>
>>
>> Hi Karnik
>>  Is this related to 813? From what I can read into your e-mail you have 2
>> ubuntu PC's. When re-starting the networking on eth0, you get adjacency -
>> however, after a while it fails giving the error message.
>> Is there a way we can login into your system to take a look?
>> Syed
>>
>>
>>    ---------- Forwarded message ----------
>>    From: *karnik* <karnik.jain at einfochips.com
>>    <mailto:karnik.jain at einfochips.com>>
>>    Date: Wed, Dec 17, 2008 at 1:07 AM
>>    Subject: [Xorp-users] [OSPFv2] XORP ospf can't receive hello
>>    packet from other OSPF router
>>    To: xorp-users at xorp.org <mailto:xorp-users at xorp.org>
>>
>>
>>    system configuration:
>>    Ubuntu 8.04.1 ( as per /etc/issue.net <http://issue.net/>)
>>    kernal : 2.6.24-19-server
>>    GCC vesion: gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)
>>
>>
>>  -------------------------------------------------------------------------------
>>    root at ubuntu:/usr/local/xorp/bin# uname -a
>>    Linux ubuntu 2.6.24-19-server #1 SMP Wed Jun 18 15:18:00 UTC 2008 i686
>>    GNU/Linux
>>
>>    *XORP version:* which is currently on XORP cvs
>>
>>
>>  -------------------------------------------------------------------------------
>>
>>    *BUG:* XORP can't receive hello packet from other ospf router
>>    having same area, same lan segment ,hello and dead interval.
>>
>>    *reason: message displayed on XORP log.*
>>    xorp error : Failed to joined multicast group 224.0.0.5
>>    <http://224.0.0.5/>: Address already in use.
>>
>>
>>    And when i do /etc/init.d/networking restart at that time all
>>    routers run well, but after some time as it is. When i again start
>>    all routers at that time i faced same above mentioned error.
>>
>>    tell me what is wrong with XORP.
>>
>>    Test setup:
>>
>>    router 1 -------- router 2
>>    eth0              eth0
>>
>>
>>
>>
>>    --
>>  _____________________________________________________________________
>>    Disclaimer: This e-mail message and all attachments transmitted
>>    with it
>>    are intended solely for the use of the addressee and may contain
>>    legally
>>    privileged and confidential information. If the reader of this message
>>    is not the intended recipient, or an employee or agent responsible for
>>    delivering this message to the intended recipient, you are hereby
>>    notified that any dissemination, distribution, copying, or other
>>    use of
>>    this message or its attachments is strictly prohibited. If you have
>>    received this message in error, please notify the sender
>>    immediately by
>>    replying to this message and please delete it from your computer. Any
>>    views expressed in this message are those of the individual sender
>>    unless otherwise stated.Company has taken enough precautions to
>>    prevent
>>    the spread of viruses. However the company accepts no liability
>>    for any
>>    damage caused by any virus transmitted by this email.
>>
>>  __________________________________________________________________________
>>
>>
>>    _______________________________________________
>>    Xorp-users mailing list
>>    Xorp-users at xorp.org <mailto:Xorp-users at xorp.org>
>>    http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users<http://mailman.icsi.berkeley.edu/mailman/listinfo/xorp-users>
>>    <http://mailman.icsi.berkeley.edu/mailman/listinfo/xorp-users>
>>
>>
>>
>>
>>
>> *Email Scanned for Virus & Dangerous Content by :* *
>> www.CleanMailGateway.com <http://www.cleanmailgateway.com/>*
>>
>>
>
> --
> _____________________________________________________________________
> Disclaimer: This e-mail message and all attachments transmitted with it
> are intended solely for the use of the addressee and may contain legally
> privileged and confidential information. If the reader of this message
> is not the intended recipient, or an employee or agent responsible for
> delivering this message to the intended recipient, you are hereby
> notified that any dissemination, distribution, copying, or other use of
> this message or its attachments is strictly prohibited. If you have
> received this message in error, please notify the sender immediately by
> replying to this message and please delete it from your computer. Any
> views expressed in this message are those of the individual sender
> unless otherwise stated.Company has taken enough precautions to prevent
> the spread of viruses. However the company accepts no liability for any
> damage caused by any virus transmitted by this email.
> __________________________________________________________________________
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20081217/4360fbfe/attachment.html 

From pavlin at ICSI.Berkeley.EDU  Wed Dec 17 18:06:49 2008
From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov)
Date: Wed, 17 Dec 2008 18:06:49 -0800
Subject: [Xorp-users] [OSPFv2] XORP ospf can't receive hello packet from
	other OSPF router
In-Reply-To: <c48427780812171752l45e23e7cy3f143b18be9fac38@mail.gmail.com> 
References: <4948C134.2070302@einfochips.com>
	<c48427780812170343v315d6e30m861246cc034166c7@mail.gmail.com>
	<c48427780812170355p7f58893ex2a88fa225734b8@mail.gmail.com>
	<49491317.8080802@einfochips.com>
	<c48427780812171752l45e23e7cy3f143b18be9fac38@mail.gmail.com>
Message-ID: <200812180206.mBI26nqk028253@fruitcake.ICSI.Berkeley.EDU>

Syed Khalid <syed.khalid at xorp.net> wrote:

> Karnik
>   We tried to replicate this problem but were not able to. The 2 Ubuntu
> machine did form adjacency. The ip addresses were on the same subnet on both
> machines. We tried to plug/unplug the link but the adjecency stayed up.
> However, if we configued another interace on the same subnet - we see your
> problem. Do  not see if we are on a different subnet.
> Can you send us the output from:
> 1) ip addr
> 2) ifconfig -a
> 3) show interface from the xorpsh
     ~~~~~~~~~~~~~~

This command should be "show interfaces" .

Pavlin

> Also let us know if we can login to your system.
> 
> Syed
> 
> On Wed, Dec 17, 2008 at 6:56 AM, karnik <karnik.jain at einfochips.com> wrote:
> 
> > No , It is not related with 813
> >
> > I am facing this problem not every time so i can not tell you
> > it is a bug or something else.
> >
> >
> > Syed Khalid wrote:
> >
> >>
> >> Hi Karnik
> >>  Is this related to 813? From what I can read into your e-mail you have 2
> >> ubuntu PC's. When re-starting the networking on eth0, you get adjacency -
> >> however, after a while it fails giving the error message.
> >> Is there a way we can login into your system to take a look?
> >> Syed
> >>
> >>
> >>    ---------- Forwarded message ----------
> >>    From: *karnik* <karnik.jain at einfochips.com
> >>    <mailto:karnik.jain at einfochips.com>>
> >>    Date: Wed, Dec 17, 2008 at 1:07 AM
> >>    Subject: [Xorp-users] [OSPFv2] XORP ospf can't receive hello
> >>    packet from other OSPF router
> >>    To: xorp-users at xorp.org <mailto:xorp-users at xorp.org>
> >>
> >>
> >>    system configuration:
> >>    Ubuntu 8.04.1 ( as per /etc/issue.net <http://issue.net/>)
> >>    kernal : 2.6.24-19-server
> >>    GCC vesion: gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)
> >>
> >>
> >>  -------------------------------------------------------------------------------
> >>    root at ubuntu:/usr/local/xorp/bin# uname -a
> >>    Linux ubuntu 2.6.24-19-server #1 SMP Wed Jun 18 15:18:00 UTC 2008 i686
> >>    GNU/Linux
> >>
> >>    *XORP version:* which is currently on XORP cvs
> >>
> >>
> >>  -------------------------------------------------------------------------------
> >>
> >>    *BUG:* XORP can't receive hello packet from other ospf router
> >>    having same area, same lan segment ,hello and dead interval.
> >>
> >>    *reason: message displayed on XORP log.*
> >>    xorp error : Failed to joined multicast group 224.0.0.5
> >>    <http://224.0.0.5/>: Address already in use.
> >>
> >>
> >>    And when i do /etc/init.d/networking restart at that time all
> >>    routers run well, but after some time as it is. When i again start
> >>    all routers at that time i faced same above mentioned error.
> >>
> >>    tell me what is wrong with XORP.
> >>
> >>    Test setup:
> >>
> >>    router 1 -------- router 2
> >>    eth0              eth0
> >>
> >>
> >>
> >>
> >>    --
> >>  _____________________________________________________________________
> >>    Disclaimer: This e-mail message and all attachments transmitted
> >>    with it
> >>    are intended solely for the use of the addressee and may contain
> >>    legally
> >>    privileged and confidential information. If the reader of this message
> >>    is not the intended recipient, or an employee or agent responsible for
> >>    delivering this message to the intended recipient, you are hereby
> >>    notified that any dissemination, distribution, copying, or other
> >>    use of
> >>    this message or its attachments is strictly prohibited. If you have
> >>    received this message in error, please notify the sender
> >>    immediately by
> >>    replying to this message and please delete it from your computer. Any
> >>    views expressed in this message are those of the individual sender
> >>    unless otherwise stated.Company has taken enough precautions to
> >>    prevent
> >>    the spread of viruses. However the company accepts no liability
> >>    for any
> >>    damage caused by any virus transmitted by this email.
> >>
> >>  __________________________________________________________________________
> >>
> >>
> >>    _______________________________________________
> >>    Xorp-users mailing list
> >>    Xorp-users at xorp.org <mailto:Xorp-users at xorp.org>
> >>    http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users<http://mailman.icsi.berkeley.edu/mailman/listinfo/xorp-users>
> >>    <http://mailman.icsi.berkeley.edu/mailman/listinfo/xorp-users>
> >>
> >>
> >>
> >>
> >>
> >> *Email Scanned for Virus & Dangerous Content by :* *
> >> www.CleanMailGateway.com <http://www.cleanmailgateway.com/>*
> >>
> >>
> >
> > --
> > _____________________________________________________________________
> > Disclaimer: This e-mail message and all attachments transmitted with it
> > are intended solely for the use of the addressee and may contain legally
> > privileged and confidential information. If the reader of this message
> > is not the intended recipient, or an employee or agent responsible for
> > delivering this message to the intended recipient, you are hereby
> > notified that any dissemination, distribution, copying, or other use of
> > this message or its attachments is strictly prohibited. If you have
> > received this message in error, please notify the sender immediately by
> > replying to this message and please delete it from your computer. Any
> > views expressed in this message are those of the individual sender
> > unless otherwise stated.Company has taken enough precautions to prevent
> > the spread of viruses. However the company accepts no liability for any
> > damage caused by any virus transmitted by this email.
> > __________________________________________________________________________
> >
> >
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


From dony1985.0729 at yahoo.co.id  Wed Dec 17 23:15:42 2008
From: dony1985.0729 at yahoo.co.id (Dony Tata)
Date: Thu, 18 Dec 2008 14:15:42 +0700 (ICT)
Subject: [Xorp-users] Bls:  register interface vif
References: <726933.22304.qm@web76112.mail.sg1.yahoo.com>
	<007301c96063$885dd790$991986b0$@edu>
Message-ID: <926653.67507.qm@web76103.mail.sg1.yahoo.com>

I have add in plumbing section, with edit in config.boot, but i can't find option add interface register vif with xorpsh console. Can yo help me ?




________________________________
Dari: Garry Peirce <peirce at maine.edu>
Kepada: Dony Tata <dony1985.0729 at yahoo.co.id>; xorp-users at xorp.org
Terkirim: Rabu, 17 Desember, 2008 23:21:36
Topik: RE: [Xorp-users] register interface vif

 
I think you have to add it into the plumbing section first. 
 
    plumbing {
        mfea4 {
            disable: false
            interface eth1 {
                vif eth1 {
                    disable: false
                }
            }
            interface "register_vif" {
                vif "register_vif" {
                    disable: false
                }
            }
 
?
 
 
--
Garry Peirce   +1-207-561-3539
Network Analyst,  ITS
University of Maine System
 
From:xorp-users-bounces at xorp..org [mailto:xorp-users-bounces at xorp.org] On Behalf
Of Dony Tata
Sent: Wednesday, December 17, 2008 10:59 AM
To: xorp-users at xorp.org
Subject: [Xorp-users] register interface vif
 
somebody know, how to add
option "register interfaces vif"  with "xorpsh"
console ?
i successfull add "register interface vif" with editing file
config.boot, but i can't find this option on xorpsh console 
example : 
protocols {
    pimsm4 {
        interface eth0 {
            vif eth0 {
               
disable: false
            }
        }
        interface eth1 {
            vif eth1 {
               
disable: false
            }
        }
        interface register_vif {
            vif
register_vif {
               
/* Note: this vif should be always enabled */
               
disable: false
            }
        }
 

________________________________
 
Bersenang-senang
di Yahoo! Messenger dengan semua teman
Tambahkan mereka dari email atau jaringan sosial Anda sekarang!


      Yahoo! Toolbar kini dilengkapi Anti-Virus dan Anti-Adware gratis.
Download Yahoo! Toolbar sekarang.
http://id.toolbar.yahoo.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20081218/6774fc90/attachment-0001.html 

From pavlin at ICSI.Berkeley.EDU  Thu Dec 18 09:52:33 2008
From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov)
Date: Thu, 18 Dec 2008 09:52:33 -0800
Subject: [Xorp-users] Bls: register interface vif
In-Reply-To: <926653.67507.qm@web76103.mail.sg1.yahoo.com> 
References: <726933.22304.qm@web76112.mail.sg1.yahoo.com>
	<007301c96063$885dd790$991986b0$@edu>
	<926653.67507.qm@web76103.mail.sg1.yahoo.com>
Message-ID: <200812181752.mBIHqXQ9009121@fruitcake.ICSI.Berkeley.EDU>

Dony Tata <dony1985.0729 at yahoo.co.id> wrote:

> I have add in plumbing section, with edit in config.boot, but i can't find option add interface register vif with xorpsh console. Can yo help me ?

The xorpsh CLI won't give you command-line completion on the
"register_vif" name.
You have to add "register_vif" like any other interface/vif by
explicitly typing the name. E.g.:

set plumbing mfea4 interface register_vif vif register_vif
set protocols pimsm4 interface register_vif vif register_vif

Pavlin

> ________________________________
> Dari: Garry Peirce <peirce at maine.edu>
> Kepada: Dony Tata <dony1985.0729 at yahoo.co.id>; xorp-users at xorp.org
> Terkirim: Rabu, 17 Desember, 2008 23:21:36
> Topik: RE: [Xorp-users] register interface vif
> 
>  
> I think you have to add it into the plumbing section first. 
>  
>     plumbing {
>         mfea4 {
>             disable: false
>             interface eth1 {
>                 vif eth1 {
>                     disable: false
>                 }
>             }
>             interface "register_vif" {
>                 vif "register_vif" {
>                     disable: false
>                 }
>             }
>  
> ?
>  
>  
> --
> Garry Peirce   +1-207-561-3539
> Network Analyst,  ITS
> University of Maine System
>  
> From:xorp-users-bounces at xorp..org [mailto:xorp-users-bounces at xorp.org] On Behalf
> Of Dony Tata
> Sent: Wednesday, December 17, 2008 10:59 AM
> To: xorp-users at xorp.org
> Subject: [Xorp-users] register interface vif
>  
> somebody know, how to add
> option "register interfaces vif"  with "xorpsh"
> console ?
> i successfull add "register interface vif" with editing file
> config.boot, but i can't find this option on xorpsh console 
> example : 
> protocols {
>     pimsm4 {
>         interface eth0 {
>             vif eth0 {
>                
> disable: false
>             }
>         }
>         interface eth1 {
>             vif eth1 {
>                
> disable: false
>             }
>         }
>         interface register_vif {
>             vif
> register_vif {
>                
> /* Note: this vif should be always enabled */
>                
> disable: false
>             }
>         }
>  
> 
> ________________________________
>  
> Bersenang-senang
> di Yahoo! Messenger dengan semua teman
> Tambahkan mereka dari email atau jaringan sosial Anda sekarang!
> 
> 
>       Yahoo! Toolbar kini dilengkapi Anti-Virus dan Anti-Adware gratis.
> Download Yahoo! Toolbar sekarang.
> http://id.toolbar.yahoo.com_______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


From psinha at ipolicynetworks.com  Wed Dec 24 03:04:13 2008
From: psinha at ipolicynetworks.com (Sinha, Priyaranjan)
Date: Wed, 24 Dec 2008 16:34:13 +0530
Subject: [Xorp-users] Unable to run the xorpsh - reports wating for
	confgiuration.
Message-ID: <D269C7CBDF116A48982D4DC51F111BE304AF82B9@nsezhpmail01.india.ipolicynet.com>


 

Hello,

 

 

 

I have successfully compiled and test run using gmake check.

 

I have configured one single interface (also have put bgp in the
config.boot apart from one single interface) and executed the rtgmgr.

 

However on running the xorpsh, the rtmgr throw following debug output

 

[2008/12/24 15:30:53 ERROR xorp_rtmgr:14077 RTRMGR + 326
xrt_rtrmgr_interface.cc finder_register_done] Failed to register with
finder about XRL xorpsh-14126-localhost.localdomain (err: Reply timed
out)

 

As I am now unable to post all the log - however can do it if its
required. Authentication and insertion of client is ok, I mean both,
xorpsh and rtmgr  are able to communicate however in subsequent event
registration failed (it seems from the log) and a little bit of debug.

 

Xorpsh throw debug output as: waiting for configuration from rtmgr.

 

 

May you please suggest what is required to overcome this problem.

 

 

Best regards,

priyaranjan 



"DISCLAIMER: 
This message is proprietary to iPolicy Networks-Security Products division of Tech Mahindra Limited and is intended solely for the use of the individuals to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. iPolicy Networks-Security Products division of Tech Mahindra Limited accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20081224/0f67dfb3/attachment.html 
-------------- next part --------------
"DISCLAIMER: This message is proprietary to iPolicy Networks Limited and is intended solely for the use of the individuals to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. iPolicy Networks Limited accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."

From psinha at ipolicynetworks.com  Wed Dec 24 04:02:23 2008
From: psinha at ipolicynetworks.com (Sinha, Priyaranjan)
Date: Wed, 24 Dec 2008 17:32:23 +0530
Subject: [Xorp-users] FW: Unable to run the xorpsh - reports wating for
	confgiuration.
Message-ID: <D269C7CBDF116A48982D4DC51F111BE304AF82BB@nsezhpmail01.india.ipolicynet.com>


 

Oops, Syed and All,

 

Please find the OS and xorp versions.

 

 

Best Regards,

Priyaranjan

 

________________________________

From: Sinha, Priyaranjan 
Sent: Wednesday, December 24, 2008 5:15 PM
To: 'Syed Khalid'
Subject: RE: [Xorp-users] Unable to run the xorpsh - reports wating for
confgiuration.

 

 

 

Using Linux Fedora Linux Kernel 2.6.15.

 

I am using xorp 1.5 stable version.

 

I have already taken care of the interface to be made eth0 and currently
using only interface and bgp in the config.boot.

 

 

 

 

________________________________

From: Syed Khalid [mailto:syed.khalid at xorp.net] 
Sent: Wednesday, December 24, 2008 5:06 PM
To: Sinha, Priyaranjan
Subject: Re: [Xorp-users] Unable to run the xorpsh - reports wating for
confgiuration.

 

Hello 

  Which OS are you using and which version of Xorp are you using?

Syed

On Wed, Dec 24, 2008 at 3:04 AM, Sinha, Priyaranjan
<psinha at ipolicynetworks.com> wrote:

 

Hello,

 

 

 

I have successfully compiled and test run using gmake check.

 

I have configured one single interface (also have put bgp in the
config.boot apart from one single interface) and executed the rtgmgr.

 

However on running the xorpsh, the rtmgr throw following debug output

 

[2008/12/24 15:30:53 ERROR xorp_rtmgr:14077 RTRMGR + 326
xrt_rtrmgr_interface.cc finder_register_done] Failed to register with
finder about XRL xorpsh-14126-localhost.localdomain (err: Reply timed
out)

 

As I am now unable to post all the log - however can do it if its
required. Authentication and insertion of client is ok, I mean both,
xorpsh and rtmgr  are able to communicate however in subsequent event
registration failed (it seems from the log) and a little bit of debug.

 

Xorpsh throw debug output as: waiting for configuration from rtmgr.

 

 

May you please suggest what is required to overcome this problem.

 

 

Best regards,

priyaranjan 

"DISCLAIMER: 
This message is proprietary to iPolicy Networks-Security Products
division of Tech Mahindra Limited and is intended solely for the use of
the individuals to whom it is addressed. It may contain privileged or
confidential information and should not be circulated or used for any
purpose other than for what is intended. If you have received this
message in error, please notify the originator immediately. If you are
not the intended recipient, you are notified that you are strictly
prohibited from using, copying, altering, or disclosing the contents of
this message. iPolicy Networks-Security Products division of Tech
Mahindra Limited accepts no responsibility for loss or damage arising
from the use of the information transmitted by this email including
damage from virus."


_______________________________________________
Xorp-users mailing list
Xorp-users at xorp.org
http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users

 



"DISCLAIMER: 
This message is proprietary to iPolicy Networks-Security Products division of Tech Mahindra Limited and is intended solely for the use of the individuals to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. iPolicy Networks-Security Products division of Tech Mahindra Limited accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20081224/4d2f60f9/attachment-0001.html 
-------------- next part --------------
"DISCLAIMER: This message is proprietary to iPolicy Networks Limited and is intended solely for the use of the individuals to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. iPolicy Networks Limited accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."

From atanu at xorp.org  Wed Dec 24 18:59:49 2008
From: atanu at xorp.org (Atanu Ghosh)
Date: Wed, 24 Dec 2008 18:59:49 -0800
Subject: [Xorp-users] Announcing XORP Release Candidate 1.6
Message-ID: <51866.1230173989@xorps.icir.org>

Dear XORP developers,

We are pleased to announce availability of the release candidate (RC)
for version 1.6. The XORP team and contributors have worked very
hard over the last 6 months and 1.6 is a huge milestone in the
history of the XORP project. Please download and use it and provide
us with feedback. We are targeting January 7th as the general
availability date of this release.

Per my announcement in July, XORP is now commercially backed by two
well-known and highly-respected venture capitalists, and one of
the benefits for all of us in the XORP community is the additional
amount of resources we have been able to bring to the project.
These increased resources have resulted in our ability to release
1.6 just months after our announcement of XORP, Inc and release 1.5.

In terms of project milestones, 1.6 marks the first time
we have put the codebase through a comprehensive and rigorous QA
process, using some of the leading test tools in the market for
layer 3 testing. Of course, there will be areas where we have
not completely tested the codebase and we are looking forward to
hearing from the development community once you've had the
opportunity to try out release 1.6.

Here are some of the key improvements in 1.6, based on your
contributions and user feedback:

- Significantly improved memory performance on the BGP code
 (especially in scenarios with many peers)

- XRL performance improvements

- Improved policy code

- *NEW* VRRP support

- Numerous bug fixes (entire list is in 1.6 Release Notes
 available at http://www.xorp.org/releases/1.6-RC/docs/RELEASE_NOTES

To file bugs, please visit http://bugzilla.xorp.org/

Of late, we have noticed more users incorporating XORP into
their projects, both non-profit and commercial and want to
continue to encourage the community to do so. With the recent
world financial crisis, organizations will be looking more
to open-source as a cost-effective alternative to the
high premiums other networking vendors charge, so help us
spread the word about XORP.org and help all of us build the
momentum behind open-source networking!

Thank you very much for your interest and continued participation
in the XORP open networking platform project. We appreciate
the help and support the community has shown us over the years and
hope that you will enjoy this latest release. If you have any
questions, please feel free to contact us at info at xorp.net.

--The XORP Team

P.S.
Release notes included below.

------------------------------------------------------------------
		XORP RELEASE NOTES

Release 1.6-RC (12/24/2008)
============================
  ALL:
    - XORP now builds on Linux CentOS 5.2, Linux openSUSE-11.0,
      Linux Debian-5.0 (lenny, unreleased), Linux Ubuntu 8.10,
      Linux Red Hat Enterprise Linux Server release 5 (Tikanga),
      Linux Fedora 10, and OpenBSD-4.4.

    - XORP now builds on Linux systems with kernel 2.6.26 which is the
      first one to support IPv6 multicast routing.

  CONFIGURATION:
    - If a PIM-SM router is suppose to receive and process the PIM-SM
      Bootstrap messages, the configuration must have the "bootstrap {}"
      block included (even if it is empty):

      protocols {
          pimsm4 {
              bootstrap {
              }
          }
      }

      protocols {
          pimsm6 {
              bootstrap {
              }
          }
      }

      Previously, the Bootstrap messages were unconditionally processed
      even if the "bootstrap {}" block contained "disable: true"
      statement.

    - The following CLI operational command prefix has been changed:
      OLD: "show route admin distances"
      NEW: "show route admin distance"
     
    - The CLI "show version" command is supported

    - Addition of run-time configuration trace options for RIP/RIPng:

      protocols {
          rip {
              traceoptions {
                  disable: false
              }
          }
      }

  LIBXORP:
    - Class EtherMac is removed and is replaced/superseded by the
      existing class Mac.

    - Performance improvements and various bug fixes in the EventLoop
      and SelectorList implementation.

  LIBXIPC:
    - XRL performance enhancements. (Bug 808)

    - Issues that might be triggered under heavy system load have been fixed
      (Bug 800)

  LIBFEACLIENT:
    - No significant changes.

  XRL:
    - See LIBXIPC

  RTRMGR:
    - No significant changes.

  XORPSH:
    - Incorrect help "show bgp peers detail" command  (Bug 280)

    - Xorpsh exiting immediately on error doesn't work  (Bug 763)

    - "Show version" CLI supported  (Bug 789)

    -  Show route admin distance not working (Bug 812)

  POLICY:
    - Tag per route is not reset in case the policies are removed (Bug 567)

    - Implement per-peer BGP import/export policies  (Bug 667)

    - Enhance policy network-lists to included prefix length (Bug 674)

  FEA/MFEA:
    - Bug fix for OpenBSD when transmitting IGMP packets.

  RIB:
    - No significant changes

  RIP/RIPng:
    - Added traceoption support 

  OLSR:
    - 

  OSPF:
    - When the designated router was restarted the MaxAge LSAs that it
      generated when reflected back would be responded to with a MaxAge LSA,
      this process could continue indefinitely, leaving the neighbor state in
      EXCHANGE. (Bug 785)
	
  BGP:
    - Support for Red Hat Linux (Bug 793)

  STATIC_ROUTES:
    - No significant changes.

  MLD/IGMP:
    - Bug fix when checking the source address of IGMP packet if the
      source address is allowed to be 0.0.0.0.

  MLD/IGMP-Lite:
    - Bug fix when checking the source address of IGMP packet if the
      source address is allowed to be 0.0.0.0.

  PIM-SM:
      Ability to add candidate BSR after inserting Cand-RP with same group
      (Bug 803)

  FIB2MRIB:
    - No significant changes.


  SNMP:
    - 

  VRRP:
    - Initial implementation of VRRP version 2 as described in RFC 3768.

    - Supports running more than one VRRP instances on the same box although
      they need to be on different interfaces and different LANs for correct
      behavior (see ERRATA).

    - The following master failure modes have been tested and are known to work
      (i.e., backup becomes master): bringing the master's interface down,
      rebooting / crashing the master, physically removing the network cable.
      Note that in the latter case the master may fail to resume operations
      when the cable is restored (see ERRATA).

    - Successfully interoperates with vrrpd.


From altaf at carroll.com  Mon Dec 29 06:41:45 2008
From: altaf at carroll.com (Altaf Maniar)
Date: Mon, 29 Dec 2008 09:41:45 -0500
Subject: [Xorp-users] Xorp router on windows 2008
Message-ID: <000a01c969c3$9361a900$ba24fb00$@com>

Hi,

 

As you all may know Microsoft removed OSPF protocol in windows 2008. I am
trying to use XORP router for OSPF  on windows 2008.

 

 It is starting and running fine on windows 2008 without windows firewall
turned on.

 

I am trying to resolve  2 issue. First one Is that I need xorp to work with
windows firewall on and  I need to make it so it run as a service.

 

 Has anyone been successful in doing this. I am working on it if fix it I
will let everyone know.

 

Thanks,

-----
Altafhusen Maniar |
Carroll-Net, Inc  |  
Ph: (201) 488-1332| Fax: (201) 488-1093
 <http://www.carroll.com> www.carroll.com

 

 

 

 

 





  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20081229/97170c9b/attachment.html 

From bms at incunabulum.net  Mon Dec 29 07:55:24 2008
From: bms at incunabulum.net (Bruce Simpson)
Date: Mon, 29 Dec 2008 15:55:24 +0000
Subject: [Xorp-users] Xorp router on windows 2008
In-Reply-To: <000a01c969c3$9361a900$ba24fb00$@com>
References: <000a01c969c3$9361a900$ba24fb00$@com>
Message-ID: <4958F2EC.6070202@incunabulum.net>

Altaf Maniar wrote:
>
> Hi,
>
>  
>
> As you all may know Microsoft removed OSPF protocol in windows 2008. I 
> am trying to use XORP router for OSPF  on windows 2008.
>

I'm surprised to hear this, to say the least.

>  
>
>  It is starting and running fine on windows 2008 without windows 
> firewall turned on.
>
>  
>
> I am trying to resolve  2 issue. First one Is that I need xorp to work 
> with windows firewall on and  I need to make it so it run as a service.
>

Whilst getting XORP to work as an NT service would be desirable for a 
number of reasons, it isn't technically possible at the moment without a 
high degree of refactoring, and would be unlikely to appear as a feature 
until well into the XORP 2.0 train.
>
>  
>
>  Has anyone been successful in doing this. I am working on it if fix 
> it I will let everyone know.
>

There are ways you can parcel up single commands and run then as NT 
services. I know OpenVPN uses this approach. Unfortunately XORP is a bit 
more complicated than OpenVPN.

thanks
BMS


From bms at incunabulum.net  Mon Dec 29 14:48:35 2008
From: bms at incunabulum.net (Bruce Simpson)
Date: Mon, 29 Dec 2008 22:48:35 +0000
Subject: [Xorp-users] Xorp router on windows 2008
In-Reply-To: <002701c969ce$8d2a9f50$a77fddf0$@com>
References: <000a01c969c3$9361a900$ba24fb00$@com>
	<4958F2EC.6070202@incunabulum.net>
	<002701c969ce$8d2a9f50$a77fddf0$@com>
Message-ID: <495953C3.9050205@incunabulum.net>

Altaf Maniar wrote:
> Bruce,
>
> Thanks for replaying. How about the windows firewall issue? Anything on
> that.
>   

What we did, when demonstrating the prototype, was to just knock holes 
through for the appropriate ports. Unfortunately, if memory serves me 
correctly, you can't do that for OSPF because it needs to use its own 
specific IP protocol number.

Whilst with time we could probably augment the existing Windows FEA 
support to use the Windows Firewall APIs to open the appropriate hole in 
the firewall configs automatically, this is unlikely to appear as a 
feature until the XORP 2.0 train.

thanks,
BMS


From bms at incunabulum.net  Tue Dec 30 08:29:39 2008
From: bms at incunabulum.net (Bruce M Simpson)
Date: Tue, 30 Dec 2008 16:29:39 +0000
Subject: [Xorp-users] Xorp router on windows 2008
In-Reply-To: <495953C3.9050205@incunabulum.net>
References: <000a01c969c3$9361a900$ba24fb00$@com>	<4958F2EC.6070202@incunabulum.net>	<002701c969ce$8d2a9f50$a77fddf0$@com>
	<495953C3.9050205@incunabulum.net>
Message-ID: <495A4C73.4080701@incunabulum.net>

Bruce Simpson wrote:
> ...
> What we did, when demonstrating the prototype, was to just knock holes 
> through for the appropriate ports. Unfortunately, if memory serves me 
> correctly, you can't do that for OSPF because it needs to use its own 
> specific IP protocol number.
>   

P.S.
I think this should work fine if you add the xorp_fea.exe process to the 
Windows Firewall application list.  You may have to do this anyway for 
raw sockets to work properly.

thanks,
BMS


From altaf at carroll.com  Tue Dec 30 08:41:52 2008
From: altaf at carroll.com (Altaf Maniar)
Date: Tue, 30 Dec 2008 11:41:52 -0500
Subject: [Xorp-users] Xorp router on windows 2008
In-Reply-To: <495A4C73.4080701@incunabulum.net>
References: <000a01c969c3$9361a900$ba24fb00$@com>	<4958F2EC.6070202@incunabulum.net>	<002701c969ce$8d2a9f50$a77fddf0$@com>
	<495953C3.9050205@incunabulum.net>
	<495A4C73.4080701@incunabulum.net>
Message-ID: <005801c96a9d$84857bc0$8d907340$@com>

Bruce,

I did add all exe related to xorp it still does not work. By the way when do
you thin version 2 will come in play.

 
 
 
Thanks,

-----
Altafhusen Maniar |
Carroll-Net, Inc  |  
Ph: (201) 488-1332| Fax: (201) 488-1093
www.carroll.com
 
 
 
 
 




  
-----Original Message-----
From: Bruce M Simpson [mailto:bms at incunabulum.net] 
Sent: Tuesday, December 30, 2008 11:30 AM
To: Altaf Maniar
Cc: xorp-users at xorp.org
Subject: Re: [Xorp-users] Xorp router on windows 2008

Bruce Simpson wrote:
> ...
> What we did, when demonstrating the prototype, was to just knock holes 
> through for the appropriate ports. Unfortunately, if memory serves me 
> correctly, you can't do that for OSPF because it needs to use its own 
> specific IP protocol number.
>   

P.S.
I think this should work fine if you add the xorp_fea.exe process to the 
Windows Firewall application list.  You may have to do this anyway for 
raw sockets to work properly.

thanks,
BMS