From illidan at lineway.net  Mon Mar  2 06:16:25 2009
From: illidan at lineway.net (illidan)
Date: Mon, 02 Mar 2009 15:16:25 +0100
Subject: [Xorp-hackers] Check a connection
Message-ID: <49ABEA39.60909@lineway.net>

Hello,

I am using socket4 library and I am trying to check if a neighbor A is 
reachable.
I did something like :

void
SocketClient::connect() {

        XorpCallback2<void, const XrlError&, const string*>::RefPtr cb;
        cb = callback(this,&SocketClient::connect_cb);
        
send_tcp_open_bind_connect("fea",_rtr.instance_name(),_localIP,_localPort,_remoteIP,_remotePort,cb);
}

void
SocketClient::connect_cb(const XrlError& e,const string* socket_id) {
    if (e != XrlError::OKAY()) {
        XLOG_ERROR("%s\n", "Error");
    } else {
        _socket_id = *socket_id;
        _connected = true;
    }
}

SocketClient::send_data(vector<uint8_t> data) {
    if(connected()) {
        XLOG_INFO("%s\n", "Try to send data...");
        XorpCallback1<void, const XrlError&>::RefPtr cb;
        cb = callback(this,&SocketClient::send_data_cb);
        send_send("fea",_socket_id,data,cb);
        //send_send_to("fea",_socket_id,_remoteIP,_remotePort,data,cb);
    }
}

void
SocketClient::send_data_cb(const XrlError& e) {
    if(e!=XrlError::OKAY()) {
       XLOG_ERROR("%s %s\n", "ERROR :",e.str().c_str());
    } else {
        XLOG_INFO("%s\n", "Packet send");
    }
    _is_waiting = false;
}

I was supposing that if the neighbor doesn't exist, socket4 will return 
an error on connect_cb function, but apparently it doesnt.

When I run this code with a remote neighbor which doesn't exist, I got 
an error :

[ 2009/03/02 14:59:23 INFO xorp_consensus CONSENSUS ] Try to send data...
[ 2009/03/02 14:59:23  ERROR xorp_fea:3591 LIBXORP +811 asyncio.cc start 
] AsyncFileWriter: Failed to add I/O event callback.
[ 2009/03/02 14:59:23 INFO xorp_consensus CONSENSUS ] Packet send

So I don't really know how to check if a neighbor is reachable or not.
Can you help me???

Thank you!

Michael


From pavlin at ICSI.Berkeley.EDU  Mon Mar  2 10:33:29 2009
From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov)
Date: Mon, 02 Mar 2009 10:33:29 -0800
Subject: [Xorp-hackers] Check a connection
In-Reply-To: <49ABEA39.60909@lineway.net> 
References: <49ABEA39.60909@lineway.net>
Message-ID: <200903021833.n22IXUiK012184@fruitcake.ICSI.Berkeley.EDU>

You need to consider the
inbound_connect_event/outgoing_connect_event/error_event/disconnect_event
XRL upcalls (from the xrl/interfaces/socket4_user.xif API) to track
the connection status of the sockets.
The TCP sockets through the FEA are non-blocking hence we can't use
the tcp_open_bind_connect return status to indicate whether the
connect request has successfully completed.

Regards,
Pavlin

illidan <illidan at lineway.net> wrote:

> Hello,
> 
> I am using socket4 library and I am trying to check if a neighbor A is 
> reachable.
> I did something like :
> 
> void
> SocketClient::connect() {
> 
>         XorpCallback2<void, const XrlError&, const string*>::RefPtr cb;
>         cb = callback(this,&SocketClient::connect_cb);
>         
> send_tcp_open_bind_connect("fea",_rtr.instance_name(),_localIP,_localPort,_remoteIP,_remotePort,cb);
> }
> 
> void
> SocketClient::connect_cb(const XrlError& e,const string* socket_id) {
>     if (e != XrlError::OKAY()) {
>         XLOG_ERROR("%s\n", "Error");
>     } else {
>         _socket_id = *socket_id;
>         _connected = true;
>     }
> }
> 
> SocketClient::send_data(vector<uint8_t> data) {
>     if(connected()) {
>         XLOG_INFO("%s\n", "Try to send data...");
>         XorpCallback1<void, const XrlError&>::RefPtr cb;
>         cb = callback(this,&SocketClient::send_data_cb);
>         send_send("fea",_socket_id,data,cb);
>         //send_send_to("fea",_socket_id,_remoteIP,_remotePort,data,cb);
>     }
> }
> 
> void
> SocketClient::send_data_cb(const XrlError& e) {
>     if(e!=XrlError::OKAY()) {
>        XLOG_ERROR("%s %s\n", "ERROR :",e.str().c_str());
>     } else {
>         XLOG_INFO("%s\n", "Packet send");
>     }
>     _is_waiting = false;
> }
> 
> I was supposing that if the neighbor doesn't exist, socket4 will return 
> an error on connect_cb function, but apparently it doesnt.
> 
> When I run this code with a remote neighbor which doesn't exist, I got 
> an error :
> 
> [ 2009/03/02 14:59:23 INFO xorp_consensus CONSENSUS ] Try to send data...
> [ 2009/03/02 14:59:23  ERROR xorp_fea:3591 LIBXORP +811 asyncio.cc start 
> ] AsyncFileWriter: Failed to add I/O event callback.
> [ 2009/03/02 14:59:23 INFO xorp_consensus CONSENSUS ] Packet send
> 
> So I don't really know how to check if a neighbor is reachable or not.
> Can you help me???
> 
> Thank you!
> 
> Michael
> 
> _______________________________________________
> Xorp-hackers mailing list
> Xorp-hackers at icir.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers


From illidan at lineway.net  Tue Mar  3 03:42:10 2009
From: illidan at lineway.net (illidan)
Date: Tue, 03 Mar 2009 12:42:10 +0100
Subject: [Xorp-hackers] Check a connection
In-Reply-To: <200903021833.n22IXUiK012184@fruitcake.ICSI.Berkeley.EDU>
References: <49ABEA39.60909@lineway.net>
	<200903021833.n22IXUiK012184@fruitcake.ICSI.Berkeley.EDU>
Message-ID: <49AD1792.8080005@lineway.net>

Pavlin Radoslavov wrote:
> You need to consider the
> inbound_connect_event/outgoing_connect_event/error_event/disconnect_event
> XRL upcalls (from the xrl/interfaces/socket4_user.xif API) to track
> the connection status of the sockets.
> The TCP sockets through the FEA are non-blocking hence we can't use
> the tcp_open_bind_connect return status to indicate whether the
> connect request has successfully completed.
>
> Regards,
> Pavlin
>
> illidan <illidan at lineway.net> wrote:
>
>   
>> Hello,
>>
>> I am using socket4 library and I am trying to check if a neighbor A is 
>> reachable.
>> I did something like :
>>
>> void
>> SocketClient::connect() {
>>
>>         XorpCallback2<void, const XrlError&, const string*>::RefPtr cb;
>>         cb = callback(this,&SocketClient::connect_cb);
>>         
>> send_tcp_open_bind_connect("fea",_rtr.instance_name(),_localIP,_localPort,_remoteIP,_remotePort,cb);
>> }
>>
>> void
>> SocketClient::connect_cb(const XrlError& e,const string* socket_id) {
>>     if (e != XrlError::OKAY()) {
>>         XLOG_ERROR("%s\n", "Error");
>>     } else {
>>         _socket_id = *socket_id;
>>         _connected = true;
>>     }
>> }
>>
>> SocketClient::send_data(vector<uint8_t> data) {
>>     if(connected()) {
>>         XLOG_INFO("%s\n", "Try to send data...");
>>         XorpCallback1<void, const XrlError&>::RefPtr cb;
>>         cb = callback(this,&SocketClient::send_data_cb);
>>         send_send("fea",_socket_id,data,cb);
>>         //send_send_to("fea",_socket_id,_remoteIP,_remotePort,data,cb);
>>     }
>> }
>>
>> void
>> SocketClient::send_data_cb(const XrlError& e) {
>>     if(e!=XrlError::OKAY()) {
>>        XLOG_ERROR("%s %s\n", "ERROR :",e.str().c_str());
>>     } else {
>>         XLOG_INFO("%s\n", "Packet send");
>>     }
>>     _is_waiting = false;
>> }
>>
>> I was supposing that if the neighbor doesn't exist, socket4 will return 
>> an error on connect_cb function, but apparently it doesnt.
>>
>> When I run this code with a remote neighbor which doesn't exist, I got 
>> an error :
>>
>> [ 2009/03/02 14:59:23 INFO xorp_consensus CONSENSUS ] Try to send data...
>> [ 2009/03/02 14:59:23  ERROR xorp_fea:3591 LIBXORP +811 asyncio.cc start 
>> ] AsyncFileWriter: Failed to add I/O event callback.
>> [ 2009/03/02 14:59:23 INFO xorp_consensus CONSENSUS ] Packet send
>>
>> So I don't really know how to check if a neighbor is reachable or not.
>> Can you help me???
>>
>> Thank you!
>>
>> Michael
>>
>> _______________________________________________
>> Xorp-hackers mailing list
>> Xorp-hackers at icir.org
>> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers
>>     
It works!
Thanks.

Michael


From arjun at ceeyes.com  Mon Mar  9 04:05:33 2009
From: arjun at ceeyes.com (Arjun Prasad)
Date: Mon, 9 Mar 2009 16:35:33 +0530
Subject: [Xorp-hackers] bgp message(keepalive) sending and receiving
Message-ID: <000a01c9a0a6$f9a70e20$1a83a8c0@ceeyes.com>

Hi all,

I have written a piece of code (implementing finite sate machine of bgp(rfc 1771)).
I tried it for interoprablity test with xorp BGP.

I successfully sent and received the OPEN meaasage from XORP(BGP).
Then i sent keepalive message successfully but i did'nt  get  keepalive from XORP(BGP).

What can be the problem?
Please help...

  *************************************************
THANKS & REGARDS,
Arjun Prasad,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-hackers/attachments/20090309/ce78465d/attachment.html 
-------------- next part --------------
************************* www.ceeyes.com **************************************
CONFIDENTIALITY AND DISCLAIMER NOTICE
Please note that this message may contain confidential information. If you have received this message by mistake, please inform the sender of the mistake by e-mailing info at ceeyes.com, then delete the message from your system without making, distributing or retaining any copies of it. Any views or opinions presented are solely those of the sender and do not necessarily represent those of Ceeyes unless otherwise specifically stated. Although we believe that the message and any attachments are free from viruses and other errors that might affect the computer or IT system where it is received and read, the recipient opens the message at his or her own risk. We assume no responsibility for any loss or damage arising from the receipt or use of this message.

From rays at maine.edu  Tue Mar 10 08:41:43 2009
From: rays at maine.edu (Soucy, Ray)
Date: Tue, 10 Mar 2009 11:41:43 -0400
Subject: [Xorp-hackers] RIPng not Accepting routes from Cisco box.
Message-ID: <36243D984F88BA4ABD1E0EFC1E61B989652C22@fudd.ad.maine.edu>

I've been trying to get RIPng working on a XORP 1.6 box.

>From what I can see the XORP box is rejecting routes received by a Cisco
box running RIPng.

I verified that the Cisco router is announcing IPv6 routes through
RIPng, but on the XORP side when I do a trace I get:

[ 2009/03/10 11:16:17 TRACE xorp_ripng RIP ] Packet on
00000000-49b67bfe-000cb2c3-42150000 from interface eth0 vif eth0
fe80::219:7ff:fea8:4280/521 604 bytes
[ 2009/03/10 11:16:17 TRACE xorp_ripng RIP ] Discarding packet
fe80::219:7ff:fea8:4280/521 604 bytes

I'm not sure why it would be discarding the packet, can anyone shed some
light on what would cause a RIPng packet to be discarded?

Also, on the Cisco side, I can get the route advertisements from XORP,
so routing is working in one direction (by the way, routes were going
out with a metic of 0 so they were being rejected by default, until I
set a policy to bump the metric to 1).

Here is debugging from the Cisco side:

Mar 10 11:06:12: RIPng: Sending multicast update on GigabitEthernet3/12
for v6rip
Mar 10 11:06:12:        src=FE80::219:7FF:FEA8:4280
Mar 10 11:06:12:        dst=FF02::9 (GigabitEthernet3/12)
Mar 10 11:06:12:        sport=521, dport=521, length=612
Mar 10 11:06:12:        command=2, version=1, mbz=0, #rte=30
Mar 10 11:06:12:        tag=0, metric=1, prefix=2610:48::28/126
Mar 10 11:06:12:        tag=0, metric=1, prefix=2610:48:402::8/126
Mar 10 11:06:12:        tag=0, metric=1, prefix=2610:48:402::4/126
Mar 10 11:06:12:        tag=0, metric=2, prefix=2610:48::24/126
Mar 10 11:06:12:        tag=0, metric=2, prefix=2610:48::2C/126
Mar 10 11:06:12:        tag=0, metric=2, prefix=2610:48:0:800::1/128
Mar 10 11:06:12:        tag=0, metric=3, prefix=2610:48:100:800::/54
Mar 10 11:06:12:        tag=0, metric=3, prefix=2610:48::34/126
Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48:200:800::/64
Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48:200:801::/64
Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48:200:802::/64
Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48:200:803::/64
Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48:200:804::/64
Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48:200:805::/64
Mar 10 11:06:12:        tag=0, metric=2, prefix=2610:48::C/126
Mar 10 11:06:12:        tag=0, metric=3, prefix=2610:48::30/126
Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48:0:1000::1/128
Mar 10 11:06:12:        tag=0, metric=3, prefix=2610:48::10/126
Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48::8/126
Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48::18/126
Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48:100:1C00::/54
Mar 10 11:06:12:        tag=120, metric=4, prefix=2610:48::14/126
Mar 10 11:06:12:        tag=120, metric=4, prefix=2610:48:0:C00::1/128
Mar 10 11:06:12:        tag=120, metric=4, prefix=2610:48:0:400::1/128
Mar 10 11:06:12:        tag=120, metric=4, prefix=2610:48::4/126
Mar 10 11:06:12:        tag=120, metric=4, prefix=2610:48::20/126
Mar 10 11:06:12:        tag=120, metric=4, prefix=2610:48:1::4/126
Mar 10 11:06:12:        tag=120, metric=4, prefix=2610:48:100:400::/54
Mar 10 11:06:12:        tag=120, metric=4, prefix=::/0
Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48::38/126

I have no import policy set (only export).  Essentially the
configuration is identical to a working RIP configuration.

RIPng configuration:

    interface eth0 {
        vif eth0 {
            address 2610:48:402::6 {
                advertise-default-route: false
            }
        }
    }
    export: "RIPng-export"

RIPng-export policy:

    term 100 {
        from {
            protocol: "connected"
            network6-list: "RIPng-export"
        }
        then {
            metric: 1
        }
    }

RIPng-export list:

    network 2610:48:402:1::/64

Interface eth0:

    description: "WAN"
    vif eth0 {
        address 169.244.10.50 {
            prefix-length: 30
        }
        address 2610:48:402::6 {
            prefix-length: 126
        }
    }

Interface eth1:

    description: "LAN"
    vif eth1 {
        address 169.244.81.225 {
            prefix-length: 27
        }
        address 2610:48:402:1::1 {
            prefix-length: 64
        }
    }

Do I need an import policy for RIPng?

Ray Soucy
Communications Specialist

+1 (207) 561-3526

Communications and Network Services

University of Maine System
http://www.maine.edu/




From michael_anonyme at hotmail.com  Wed Mar 11 00:05:35 2009
From: michael_anonyme at hotmail.com (michael anonyme)
Date: Wed, 11 Mar 2009 07:05:35 +0000
Subject: [Xorp-hackers] Timer Event
Message-ID: <SNT107-W35D8823B5E7AC6027386A9889E0@phx.gbl>


Hello,

I'm trying to add an event to the EventLoop : 

_timeOutVal(TimeVal(10,0)) is initialized in constructor.

I would like that after 10 seconds, Xorp run test_cb method, but it doesn't seems to work.

XorpTimer t = _eventloop.new_oneoff_after(_timeOutVal,callback(this,&ConsensusMain::test_cb));

void ConsensusMain::test_cb() {
       XLOG_INFO("RUN TEST CALLBACK!!!!!\n");
}

What did I do wrong??

Thanks!

Best regards, 
Michael

_________________________________________________________________
Rejoignez la nouvelle famille de Windows Live Messenger
http://download.live.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-hackers/attachments/20090311/512f5535/attachment.html 

From pavlin at ICSI.Berkeley.EDU  Wed Mar 11 02:07:08 2009
From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov)
Date: Wed, 11 Mar 2009 02:07:08 -0700
Subject: [Xorp-hackers] Timer Event
In-Reply-To: <SNT107-W35D8823B5E7AC6027386A9889E0@phx.gbl> 
References: <SNT107-W35D8823B5E7AC6027386A9889E0@phx.gbl>
Message-ID: <200903110907.n2B978LO026235@fruitcake.ICSI.Berkeley.EDU>

michael anonyme <michael_anonyme at hotmail.com> wrote:

> 
> Hello,
> 
> I'm trying to add an event to the EventLoop : 
> 
> _timeOutVal(TimeVal(10,0)) is initialized in constructor.
> 
> I would like that after 10 seconds, Xorp run test_cb method, but it doesn't seems to work.
> 
> XorpTimer t = _eventloop.new_oneoff_after(_timeOutVal,callback(this,&ConsensusMain::test_cb));
> 
> void ConsensusMain::test_cb() {
>        XLOG_INFO("RUN TEST CALLBACK!!!!!\n");
> }
> 
> What did I do wrong??

If the "XorpTime t" object is destroyed (e.g., if it goes out of
scope), then the timer itself on the eventloop is also destroyed.
You need to save it somewhere (e.g., as a private field in the
ConsensusMain class).

Hope that helps,
Pavlin


From michael_anonyme at hotmail.com  Wed Mar 11 03:11:45 2009
From: michael_anonyme at hotmail.com (michael anonyme)
Date: Wed, 11 Mar 2009 10:11:45 +0000
Subject: [Xorp-hackers] Timer Event
In-Reply-To: <200903110907.n2B978LO026235@fruitcake.ICSI.Berkeley.EDU>
References: <SNT107-W35D8823B5E7AC6027386A9889E0@phx.gbl>
	<200903110907.n2B978LO026235@fruitcake.ICSI.Berkeley.EDU>
Message-ID: <SNT107-W73AFFD7FEC539B1933B5A3889E0@phx.gbl>




> To: michael_anonyme at hotmail.com
> CC: xorp-hackers at icir.org
> Subject: Re: [Xorp-hackers] Timer Event 
> Date: Wed, 11 Mar 2009 02:07:08 -0700
> From: pavlin at ICSI.Berkeley.EDU
> 
> michael anonyme <michael_anonyme at hotmail.com> wrote:
> 
> > 
> > Hello,
> > 
> > I'm trying to add an event to the EventLoop : 
> > 
> > _timeOutVal(TimeVal(10,0)) is initialized in constructor.
> > 
> > I would like that after 10 seconds, Xorp run test_cb method, but it doesn't seems to work.
> > 
> > XorpTimer t = _eventloop.new_oneoff_after(_timeOutVal,callback(this,&ConsensusMain::test_cb));
> > 
> > void ConsensusMain::test_cb() {
> >        XLOG_INFO("RUN TEST CALLBACK!!!!!\n");
> > }
> > 
> > What did I do wrong??
> 
> If the "XorpTime t" object is destroyed (e.g., if it goes out of
> scope), then the timer itself on the eventloop is also destroyed.
> You need to save it somewhere (e.g., as a private field in the
> ConsensusMain class).
> 
> Hope that helps,
> Pavlin

Thanks it works great!!

_________________________________________________________________
D?couvrez la nouvelle g?n?ration des servives de Windows Live
http://download.live.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-hackers/attachments/20090311/71507487/attachment.html 

From arjun at ceeyes.com  Wed Mar 11 21:22:57 2009
From: arjun at ceeyes.com (Arjun Prasad)
Date: Thu, 12 Mar 2009 09:52:57 +0530
Subject: [Xorp-hackers] BGP
Message-ID: <002901c9a2ca$39e544f0$1a83a8c0@ceeyes.com>

Hi all,

I have written a piece of code (implementing finite sate machine of bgp(rfc 1771)).
I tried it for interoprablity test with xorp BGP.

I successfully sent and received the OPEN meaasage from XORP(BGP).
Then i sent keepalive message successfully but i did'nt  get  keepalive from XORP(BGP).

What can be the problem?
Please help...

  *************************************************
THANKS & REGARDS,
Arjun Prasad,

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-hackers/attachments/20090312/e10ee38f/attachment.html 

From pavlin at ICSI.Berkeley.EDU  Sun Mar 15 00:22:35 2009
From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov)
Date: Sun, 15 Mar 2009 00:22:35 -0700
Subject: [Xorp-hackers] RIPng not Accepting routes from Cisco box.
In-Reply-To: <36243D984F88BA4ABD1E0EFC1E61B989652C22@fudd.ad.maine.edu> 
References: <36243D984F88BA4ABD1E0EFC1E61B989652C22@fudd.ad.maine.edu>
Message-ID: <200903150722.n2F7MZkD014576@fruitcake.ICSI.Berkeley.EDU>

[A copy of an reply I just sent to xorp-users]

I am not sure this will solve the problem, but you might try to
explictly add the link-local address to the corresponding
ripng/interface/vif and interfaces/interface/vif blocks.

Pavlin

Soucy, Ray <rays at maine.edu> wrote:

> I've been trying to get RIPng working on a XORP 1.6 box.
> 
> From what I can see the XORP box is rejecting routes received by a Cisco
> box running RIPng.
> 
> I verified that the Cisco router is announcing IPv6 routes through
> RIPng, but on the XORP side when I do a trace I get:
> 
> [ 2009/03/10 11:16:17 TRACE xorp_ripng RIP ] Packet on
> 00000000-49b67bfe-000cb2c3-42150000 from interface eth0 vif eth0
> fe80::219:7ff:fea8:4280/521 604 bytes
> [ 2009/03/10 11:16:17 TRACE xorp_ripng RIP ] Discarding packet
> fe80::219:7ff:fea8:4280/521 604 bytes
> 
> I'm not sure why it would be discarding the packet, can anyone shed some
> light on what would cause a RIPng packet to be discarded?
> 
> Also, on the Cisco side, I can get the route advertisements from XORP,
> so routing is working in one direction (by the way, routes were going
> out with a metic of 0 so they were being rejected by default, until I
> set a policy to bump the metric to 1).
> 
> Here is debugging from the Cisco side:
> 
> Mar 10 11:06:12: RIPng: Sending multicast update on GigabitEthernet3/12
> for v6rip
> Mar 10 11:06:12:        src=FE80::219:7FF:FEA8:4280
> Mar 10 11:06:12:        dst=FF02::9 (GigabitEthernet3/12)
> Mar 10 11:06:12:        sport=521, dport=521, length=612
> Mar 10 11:06:12:        command=2, version=1, mbz=0, #rte=30
> Mar 10 11:06:12:        tag=0, metric=1, prefix=2610:48::28/126
> Mar 10 11:06:12:        tag=0, metric=1, prefix=2610:48:402::8/126
> Mar 10 11:06:12:        tag=0, metric=1, prefix=2610:48:402::4/126
> Mar 10 11:06:12:        tag=0, metric=2, prefix=2610:48::24/126
> Mar 10 11:06:12:        tag=0, metric=2, prefix=2610:48::2C/126
> Mar 10 11:06:12:        tag=0, metric=2, prefix=2610:48:0:800::1/128
> Mar 10 11:06:12:        tag=0, metric=3, prefix=2610:48:100:800::/54
> Mar 10 11:06:12:        tag=0, metric=3, prefix=2610:48::34/126
> Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48:200:800::/64
> Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48:200:801::/64
> Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48:200:802::/64
> Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48:200:803::/64
> Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48:200:804::/64
> Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48:200:805::/64
> Mar 10 11:06:12:        tag=0, metric=2, prefix=2610:48::C/126
> Mar 10 11:06:12:        tag=0, metric=3, prefix=2610:48::30/126
> Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48:0:1000::1/128
> Mar 10 11:06:12:        tag=0, metric=3, prefix=2610:48::10/126
> Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48::8/126
> Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48::18/126
> Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48:100:1C00::/54
> Mar 10 11:06:12:        tag=120, metric=4, prefix=2610:48::14/126
> Mar 10 11:06:12:        tag=120, metric=4, prefix=2610:48:0:C00::1/128
> Mar 10 11:06:12:        tag=120, metric=4, prefix=2610:48:0:400::1/128
> Mar 10 11:06:12:        tag=120, metric=4, prefix=2610:48::4/126
> Mar 10 11:06:12:        tag=120, metric=4, prefix=2610:48::20/126
> Mar 10 11:06:12:        tag=120, metric=4, prefix=2610:48:1::4/126
> Mar 10 11:06:12:        tag=120, metric=4, prefix=2610:48:100:400::/54
> Mar 10 11:06:12:        tag=120, metric=4, prefix=::/0
> Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48::38/126
> 
> I have no import policy set (only export).  Essentially the
> configuration is identical to a working RIP configuration.
> 
> RIPng configuration:
> 
>     interface eth0 {
>         vif eth0 {
>             address 2610:48:402::6 {
>                 advertise-default-route: false
>             }
>         }
>     }
>     export: "RIPng-export"
> 
> RIPng-export policy:
> 
>     term 100 {
>         from {
>             protocol: "connected"
>             network6-list: "RIPng-export"
>         }
>         then {
>             metric: 1
>         }
>     }
> 
> RIPng-export list:
> 
>     network 2610:48:402:1::/64
> 
> Interface eth0:
> 
>     description: "WAN"
>     vif eth0 {
>         address 169.244.10.50 {
>             prefix-length: 30
>         }
>         address 2610:48:402::6 {
>             prefix-length: 126
>         }
>     }
> 
> Interface eth1:
> 
>     description: "LAN"
>     vif eth1 {
>         address 169.244.81.225 {
>             prefix-length: 27
>         }
>         address 2610:48:402:1::1 {
>             prefix-length: 64
>         }
>     }
> 
> Do I need an import policy for RIPng?
> 
> Ray Soucy
> Communications Specialist
> 
> +1 (207) 561-3526
> 
> Communications and Network Services
> 
> University of Maine System
> http://www.maine.edu/
> 
> 
> 
> _______________________________________________
> Xorp-hackers mailing list
> Xorp-hackers at icir.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers


From rays at maine.edu  Sun Mar 15 17:59:04 2009
From: rays at maine.edu (Soucy, Ray)
Date: Sun, 15 Mar 2009 20:59:04 -0400
Subject: [Xorp-hackers] RIPng not Accepting routes from Cisco box.
In-Reply-To: <200903150722.n2F7MZkD014576@fruitcake.ICSI.Berkeley.EDU>
References: <36243D984F88BA4ABD1E0EFC1E61B989652C22@fudd.ad.maine.edu>
	<200903150722.n2F7MZkD014576@fruitcake.ICSI.Berkeley.EDU>
Message-ID: <36243D984F88BA4ABD1E0EFC1E61B989652D2A@fudd.ad.maine.edu>

We first suspected this as well.  We added the Link Local address and
didn't see a change.
We also tried creating an import policy for RIPng, no luck here either.

It's very odd.  What we're doing is very simple...  I was hoping it was
just my ignorance on how to configure XORP.

I don't think it's a v6 multicast issue since XORP is seeing the packets
and announcing routes successfully (though that default metric of 0 is
rather irritating).

Is anyone else successfully talking to a Cisco box using RIPng (or any
other non-XORP box)?

I think the next option is on a source level to perhaps make error
messages more useful than "packet discarded".

Ray

-----Original Message-----
From: Pavlin Radoslavov [mailto:pavlin at ICSI.Berkeley.EDU] 
Sent: Sunday, March 15, 2009 3:23 AM
To: Soucy, Ray
Cc: xorp-hackers at icir.org
Subject: Re: [Xorp-hackers] RIPng not Accepting routes from Cisco box.

[A copy of an reply I just sent to xorp-users]

I am not sure this will solve the problem, but you might try to
explictly add the link-local address to the corresponding
ripng/interface/vif and interfaces/interface/vif blocks.

Pavlin

Soucy, Ray <rays at maine.edu> wrote:

> I've been trying to get RIPng working on a XORP 1.6 box.
> 
> From what I can see the XORP box is rejecting routes received by a
Cisco
> box running RIPng.
> 
> I verified that the Cisco router is announcing IPv6 routes through
> RIPng, but on the XORP side when I do a trace I get:
> 
> [ 2009/03/10 11:16:17 TRACE xorp_ripng RIP ] Packet on
> 00000000-49b67bfe-000cb2c3-42150000 from interface eth0 vif eth0
> fe80::219:7ff:fea8:4280/521 604 bytes
> [ 2009/03/10 11:16:17 TRACE xorp_ripng RIP ] Discarding packet
> fe80::219:7ff:fea8:4280/521 604 bytes
> 
> I'm not sure why it would be discarding the packet, can anyone shed
some
> light on what would cause a RIPng packet to be discarded?
> 
> Also, on the Cisco side, I can get the route advertisements from XORP,
> so routing is working in one direction (by the way, routes were going
> out with a metic of 0 so they were being rejected by default, until I
> set a policy to bump the metric to 1).
> 
> Here is debugging from the Cisco side:
> 
> Mar 10 11:06:12: RIPng: Sending multicast update on
GigabitEthernet3/12
> for v6rip
> Mar 10 11:06:12:        src=FE80::219:7FF:FEA8:4280
> Mar 10 11:06:12:        dst=FF02::9 (GigabitEthernet3/12)
> Mar 10 11:06:12:        sport=521, dport=521, length=612
> Mar 10 11:06:12:        command=2, version=1, mbz=0, #rte=30
> Mar 10 11:06:12:        tag=0, metric=1, prefix=2610:48::28/126
> Mar 10 11:06:12:        tag=0, metric=1, prefix=2610:48:402::8/126
> Mar 10 11:06:12:        tag=0, metric=1, prefix=2610:48:402::4/126
> Mar 10 11:06:12:        tag=0, metric=2, prefix=2610:48::24/126
> Mar 10 11:06:12:        tag=0, metric=2, prefix=2610:48::2C/126
> Mar 10 11:06:12:        tag=0, metric=2, prefix=2610:48:0:800::1/128
> Mar 10 11:06:12:        tag=0, metric=3, prefix=2610:48:100:800::/54
> Mar 10 11:06:12:        tag=0, metric=3, prefix=2610:48::34/126
> Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48:200:800::/64
> Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48:200:801::/64
> Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48:200:802::/64
> Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48:200:803::/64
> Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48:200:804::/64
> Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48:200:805::/64
> Mar 10 11:06:12:        tag=0, metric=2, prefix=2610:48::C/126
> Mar 10 11:06:12:        tag=0, metric=3, prefix=2610:48::30/126
> Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48:0:1000::1/128
> Mar 10 11:06:12:        tag=0, metric=3, prefix=2610:48::10/126
> Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48::8/126
> Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48::18/126
> Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48:100:1C00::/54
> Mar 10 11:06:12:        tag=120, metric=4, prefix=2610:48::14/126
> Mar 10 11:06:12:        tag=120, metric=4, prefix=2610:48:0:C00::1/128
> Mar 10 11:06:12:        tag=120, metric=4, prefix=2610:48:0:400::1/128
> Mar 10 11:06:12:        tag=120, metric=4, prefix=2610:48::4/126
> Mar 10 11:06:12:        tag=120, metric=4, prefix=2610:48::20/126
> Mar 10 11:06:12:        tag=120, metric=4, prefix=2610:48:1::4/126
> Mar 10 11:06:12:        tag=120, metric=4, prefix=2610:48:100:400::/54
> Mar 10 11:06:12:        tag=120, metric=4, prefix=::/0
> Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48::38/126
> 
> I have no import policy set (only export).  Essentially the
> configuration is identical to a working RIP configuration.
> 
> RIPng configuration:
> 
>     interface eth0 {
>         vif eth0 {
>             address 2610:48:402::6 {
>                 advertise-default-route: false
>             }
>         }
>     }
>     export: "RIPng-export"
> 
> RIPng-export policy:
> 
>     term 100 {
>         from {
>             protocol: "connected"
>             network6-list: "RIPng-export"
>         }
>         then {
>             metric: 1
>         }
>     }
> 
> RIPng-export list:
> 
>     network 2610:48:402:1::/64
> 
> Interface eth0:
> 
>     description: "WAN"
>     vif eth0 {
>         address 169.244.10.50 {
>             prefix-length: 30
>         }
>         address 2610:48:402::6 {
>             prefix-length: 126
>         }
>     }
> 
> Interface eth1:
> 
>     description: "LAN"
>     vif eth1 {
>         address 169.244.81.225 {
>             prefix-length: 27
>         }
>         address 2610:48:402:1::1 {
>             prefix-length: 64
>         }
>     }
> 
> Do I need an import policy for RIPng?
> 
> Ray Soucy
> Communications Specialist
> 
> +1 (207) 561-3526
> 
> Communications and Network Services
> 
> University of Maine System
> http://www.maine.edu/
> 
> 
> 
> _______________________________________________
> Xorp-hackers mailing list
> Xorp-hackers at icir.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers


From syed.khalid at xorp.net  Mon Mar 16 07:27:43 2009
From: syed.khalid at xorp.net (Syed Khalid)
Date: Mon, 16 Mar 2009 07:27:43 -0700
Subject: [Xorp-hackers] RIPng not Accepting routes from Cisco box.
In-Reply-To: <36243D984F88BA4ABD1E0EFC1E61B989652D2A@fudd.ad.maine.edu>
References: <36243D984F88BA4ABD1E0EFC1E61B989652C22@fudd.ad.maine.edu>
	<200903150722.n2F7MZkD014576@fruitcake.ICSI.Berkeley.EDU>
	<36243D984F88BA4ABD1E0EFC1E61B989652D2A@fudd.ad.maine.edu>
Message-ID: <c48427780903160727y6e2909b7x2b6d67ea85204da8@mail.gmail.com>

Hi Ray
We can try it in the lab here as we have a Cisco 7200 here Could you open a
bug so we can track it? Please include Xorp and Cisco configurations,  CLI
commands and logs and versions etc

 We have peered with Cisco using RIP in the lab.

Syed

On Sun, Mar 15, 2009 at 5:59 PM, Soucy, Ray <rays at maine.edu> wrote:

> We first suspected this as well.  We added the Link Local address and
> didn't see a change.
> We also tried creating an import policy for RIPng, no luck here either.
>
> It's very odd.  What we're doing is very simple...  I was hoping it was
> just my ignorance on how to configure XORP.
>
> I don't think it's a v6 multicast issue since XORP is seeing the packets
> and announcing routes successfully (though that default metric of 0 is
> rather irritating).
>
> Is anyone else successfully talking to a Cisco box using RIPng (or any
> other non-XORP box)?
>
> I think the next option is on a source level to perhaps make error
> messages more useful than "packet discarded".
>
> Ray
>
> -----Original Message-----
> From: Pavlin Radoslavov [mailto:pavlin at ICSI.Berkeley.EDU]
> Sent: Sunday, March 15, 2009 3:23 AM
> To: Soucy, Ray
> Cc: xorp-hackers at icir.org
> Subject: Re: [Xorp-hackers] RIPng not Accepting routes from Cisco box.
>
> [A copy of an reply I just sent to xorp-users]
>
> I am not sure this will solve the problem, but you might try to
> explictly add the link-local address to the corresponding
> ripng/interface/vif and interfaces/interface/vif blocks.
>
> Pavlin
>
> Soucy, Ray <rays at maine.edu> wrote:
>
> > I've been trying to get RIPng working on a XORP 1.6 box.
> >
> > From what I can see the XORP box is rejecting routes received by a
> Cisco
> > box running RIPng.
> >
> > I verified that the Cisco router is announcing IPv6 routes through
> > RIPng, but on the XORP side when I do a trace I get:
> >
> > [ 2009/03/10 11:16:17 TRACE xorp_ripng RIP ] Packet on
> > 00000000-49b67bfe-000cb2c3-42150000 from interface eth0 vif eth0
> > fe80::219:7ff:fea8:4280/521 604 bytes
> > [ 2009/03/10 11:16:17 TRACE xorp_ripng RIP ] Discarding packet
> > fe80::219:7ff:fea8:4280/521 604 bytes
> >
> > I'm not sure why it would be discarding the packet, can anyone shed
> some
> > light on what would cause a RIPng packet to be discarded?
> >
> > Also, on the Cisco side, I can get the route advertisements from XORP,
> > so routing is working in one direction (by the way, routes were going
> > out with a metic of 0 so they were being rejected by default, until I
> > set a policy to bump the metric to 1).
> >
> > Here is debugging from the Cisco side:
> >
> > Mar 10 11:06:12: RIPng: Sending multicast update on
> GigabitEthernet3/12
> > for v6rip
> > Mar 10 11:06:12:        src=FE80::219:7FF:FEA8:4280
> > Mar 10 11:06:12:        dst=FF02::9 (GigabitEthernet3/12)
> > Mar 10 11:06:12:        sport=521, dport=521, length=612
> > Mar 10 11:06:12:        command=2, version=1, mbz=0, #rte=30
> > Mar 10 11:06:12:        tag=0, metric=1, prefix=2610:48::28/126
> > Mar 10 11:06:12:        tag=0, metric=1, prefix=2610:48:402::8/126
> > Mar 10 11:06:12:        tag=0, metric=1, prefix=2610:48:402::4/126
> > Mar 10 11:06:12:        tag=0, metric=2, prefix=2610:48::24/126
> > Mar 10 11:06:12:        tag=0, metric=2, prefix=2610:48::2C/126
> > Mar 10 11:06:12:        tag=0, metric=2, prefix=2610:48:0:800::1/128
> > Mar 10 11:06:12:        tag=0, metric=3, prefix=2610:48:100:800::/54
> > Mar 10 11:06:12:        tag=0, metric=3, prefix=2610:48::34/126
> > Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48:200:800::/64
> > Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48:200:801::/64
> > Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48:200:802::/64
> > Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48:200:803::/64
> > Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48:200:804::/64
> > Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48:200:805::/64
> > Mar 10 11:06:12:        tag=0, metric=2, prefix=2610:48::C/126
> > Mar 10 11:06:12:        tag=0, metric=3, prefix=2610:48::30/126
> > Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48:0:1000::1/128
> > Mar 10 11:06:12:        tag=0, metric=3, prefix=2610:48::10/126
> > Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48::8/126
> > Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48::18/126
> > Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48:100:1C00::/54
> > Mar 10 11:06:12:        tag=120, metric=4, prefix=2610:48::14/126
> > Mar 10 11:06:12:        tag=120, metric=4, prefix=2610:48:0:C00::1/128
> > Mar 10 11:06:12:        tag=120, metric=4, prefix=2610:48:0:400::1/128
> > Mar 10 11:06:12:        tag=120, metric=4, prefix=2610:48::4/126
> > Mar 10 11:06:12:        tag=120, metric=4, prefix=2610:48::20/126
> > Mar 10 11:06:12:        tag=120, metric=4, prefix=2610:48:1::4/126
> > Mar 10 11:06:12:        tag=120, metric=4, prefix=2610:48:100:400::/54
> > Mar 10 11:06:12:        tag=120, metric=4, prefix=::/0
> > Mar 10 11:06:12:        tag=0, metric=4, prefix=2610:48::38/126
> >
> > I have no import policy set (only export).  Essentially the
> > configuration is identical to a working RIP configuration.
> >
> > RIPng configuration:
> >
> >     interface eth0 {
> >         vif eth0 {
> >             address 2610:48:402::6 {
> >                 advertise-default-route: false
> >             }
> >         }
> >     }
> >     export: "RIPng-export"
> >
> > RIPng-export policy:
> >
> >     term 100 {
> >         from {
> >             protocol: "connected"
> >             network6-list: "RIPng-export"
> >         }
> >         then {
> >             metric: 1
> >         }
> >     }
> >
> > RIPng-export list:
> >
> >     network 2610:48:402:1::/64
> >
> > Interface eth0:
> >
> >     description: "WAN"
> >     vif eth0 {
> >         address 169.244.10.50 {
> >             prefix-length: 30
> >         }
> >         address 2610:48:402::6 {
> >             prefix-length: 126
> >         }
> >     }
> >
> > Interface eth1:
> >
> >     description: "LAN"
> >     vif eth1 {
> >         address 169.244.81.225 {
> >             prefix-length: 27
> >         }
> >         address 2610:48:402:1::1 {
> >             prefix-length: 64
> >         }
> >     }
> >
> > Do I need an import policy for RIPng?
> >
> > Ray Soucy
> > Communications Specialist
> >
> > +1 (207) 561-3526
> >
> > Communications and Network Services
> >
> > University of Maine System
> > http://www.maine.edu/
> >
> >
> >
> > _______________________________________________
> > Xorp-hackers mailing list
> > Xorp-hackers at icir.org
> > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers<http://mailman.icsi.berkeley.edu/mailman/listinfo/xorp-hackers>
>
> _______________________________________________
> Xorp-hackers mailing list
> Xorp-hackers at icir.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers<http://mailman.icsi.berkeley.edu/mailman/listinfo/xorp-hackers>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-hackers/attachments/20090316/9818d70a/attachment.html 

From isaacnskb at gmail.com  Thu Mar 19 02:39:18 2009
From: isaacnskb at gmail.com (Isaac)
Date: Thu, 19 Mar 2009 02:39:18 -0700
Subject: [Xorp-hackers] Callback/Python
Message-ID: <9312bbe60903190239x30915ac8saf3bc79d121201ff@mail.gmail.com>

Hello everyone,

We are currently trying to dial a PPP connection when a router goes down.
We are thinking about developing a callback to accomplish this.  I am new to
XORP development so I would really appreciate if someone can point me in the
right direction.  Here are some of my questions:

1) Can a callback be setup to monitor routes?  Can this be accomplished
through SNMP?  This will allow us to start our PPP script.
2) Our development is mainly done in Python.  If we have to develop a
callback, what would be the best approach to write as much from Python?

Thanks in advanced.

--
Isaac
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-hackers/attachments/20090319/b1feb577/attachment.html 

From illidan at lineway.net  Fri Mar 20 03:59:57 2009
From: illidan at lineway.net (illidan)
Date: Fri, 20 Mar 2009 11:59:57 +0100
Subject: [Xorp-hackers] TCP connection
Message-ID: <49C3772D.8070808@lineway.net>

Hello.

I'm writing a routing protocol in Xorp, and I use socket4 library.

I use tcp connection, so I used "send_tcp_open_bind_connect" function.
But I get a little problem with this function, It ask two local 
arguments : IP and Port.

But in my case, I don't use the local socket which is open with this 
function ( I have already another connection running ).
And my routers in general have more than one interface, which means more 
than one local IP.

Would it be possible to create a TCP connection without create a local 
socket like this?

Thanks for your help.

Best regards,
Michael


From pavlin at ICSI.Berkeley.EDU  Fri Mar 20 10:06:34 2009
From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov)
Date: Fri, 20 Mar 2009 10:06:34 -0700
Subject: [Xorp-hackers] TCP connection
In-Reply-To: <49C3772D.8070808@lineway.net> 
References: <49C3772D.8070808@lineway.net>
Message-ID: <200903201706.n2KH6Yfe001762@fruitcake.ICSI.Berkeley.EDU>

illidan <illidan at lineway.net> wrote:

> Hello.
> 
> I'm writing a routing protocol in Xorp, and I use socket4 library.
> 
> I use tcp connection, so I used "send_tcp_open_bind_connect" function.
> But I get a little problem with this function, It ask two local 
> arguments : IP and Port.
> 
> But in my case, I don't use the local socket which is open with this 
> function ( I have already another connection running ).
> And my routers in general have more than one interface, which means more 
> than one local IP.
> 
> Would it be possible to create a TCP connection without create a local 
> socket like this?

Try setting the local_addr and local_port to zero.

Regards,
Pavlin

> Thanks for your help.
> 
> Best regards,
> Michael
> 
> _______________________________________________
> Xorp-hackers mailing list
> Xorp-hackers at icir.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers


From illidan at lineway.net  Sat Mar 21 08:15:03 2009
From: illidan at lineway.net (illidan)
Date: Sat, 21 Mar 2009 16:15:03 +0100
Subject: [Xorp-hackers] TCP connection
Message-ID: <49C50477.2040309@lineway.net>

Pavlin Radoslavov wrote:
> illidan <illidan at lineway.net> wrote:
>
>  
>> Hello.
>>
>> I'm writing a routing protocol in Xorp, and I use socket4 library.
>>
>> I use tcp connection, so I used "send_tcp_open_bind_connect" function.
>> But I get a little problem with this function, It ask two local 
>> arguments : IP and Port.
>>
>> But in my case, I don't use the local socket which is open with this 
>> function ( I have already another connection running ).
>> And my routers in general have more than one interface, which means 
>> more than one local IP.
>>
>> Would it be possible to create a TCP connection without create a 
>> local socket like this?
>>     
>
> Try setting the local_addr and local_port to zero.
>
> Regards,
> Pavlin
>
>  
>> Thanks for your help.
>>
>> Best regards,
>> Michael
>>
>> _______________________________________________
>> Xorp-hackers mailing list
>> Xorp-hackers at icir.org
>> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers
>>     
Hello,
Thanks for your answer.
I try this :
send_tcp_open_and_bind("fea",_rtr.instance_name(),NULL,NULL,cb)

But I get this error :
InvalidString from line 77 of ipv4.cc -> Null value
terminate called after throwing an instance of 'InvalidString'
[ 2009/03/21 16:11:41  ERROR xorp_rtrmgr:14823 RTRMGR +1405 task.cc 
execute_done ] 210 Transport failed

:(
Best regards,
Michael


From pavlin at ICSI.Berkeley.EDU  Sat Mar 21 13:29:02 2009
From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov)
Date: Sat, 21 Mar 2009 13:29:02 -0700
Subject: [Xorp-hackers] TCP connection
In-Reply-To: <49C50477.2040309@lineway.net> 
References: <49C50477.2040309@lineway.net>
Message-ID: <200903212029.n2LKT2rv023911@fruitcake.ICSI.Berkeley.EDU>

illidan <illidan at lineway.net> wrote:

> Pavlin Radoslavov wrote:
> > illidan <illidan at lineway.net> wrote:
> >
> >  
> >> Hello.
> >>
> >> I'm writing a routing protocol in Xorp, and I use socket4 library.
> >>
> >> I use tcp connection, so I used "send_tcp_open_bind_connect" function.
> >> But I get a little problem with this function, It ask two local 
> >> arguments : IP and Port.
> >>
> >> But in my case, I don't use the local socket which is open with this 
> >> function ( I have already another connection running ).
> >> And my routers in general have more than one interface, which means 
> >> more than one local IP.
> >>
> >> Would it be possible to create a TCP connection without create a 
> >> local socket like this?
> >>     
> >
> > Try setting the local_addr and local_port to zero.
> >
> > Regards,
> > Pavlin
> >
> >  
> >> Thanks for your help.
> >>
> >> Best regards,
> >> Michael
> >>
> >> _______________________________________________
> >> Xorp-hackers mailing list
> >> Xorp-hackers at icir.org
> >> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers
> >>     
> Hello,
> Thanks for your answer.
> I try this :
> send_tcp_open_and_bind("fea",_rtr.instance_name(),NULL,NULL,cb)
> 
> But I get this error :
> InvalidString from line 77 of ipv4.cc -> Null value
> terminate called after throwing an instance of 'InvalidString'
> [ 2009/03/21 16:11:41  ERROR xorp_rtrmgr:14823 RTRMGR +1405 task.cc 
> execute_done ] 210 Transport failed

You should use IPv4::ZERO() and the number 0 for the local_addr and
local_port respectively instead of NULL.

Hope that helps,
Pavlin

> :(
> Best regards,
> Michael
> 
> _______________________________________________
> Xorp-hackers mailing list
> Xorp-hackers at icir.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers


From illidan at lineway.net  Mon Mar 23 06:13:00 2009
From: illidan at lineway.net (illidan)
Date: Mon, 23 Mar 2009 14:13:00 +0100
Subject: [Xorp-hackers] TCP connection
In-Reply-To: <200903212029.n2LKT2rv023911@fruitcake.ICSI.Berkeley.EDU>
References: <49C50477.2040309@lineway.net>
	<200903212029.n2LKT2rv023911@fruitcake.ICSI.Berkeley.EDU>
Message-ID: <49C78ADC.1080008@lineway.net>

Pavlin Radoslavov wrote:
> illidan <illidan at lineway.net> wrote:
>
>   
>> Pavlin Radoslavov wrote:
>>     
>>> illidan <illidan at lineway.net> wrote:
>>>
>>>  
>>>       
>>>> Hello.
>>>>
>>>> I'm writing a routing protocol in Xorp, and I use socket4 library.
>>>>
>>>> I use tcp connection, so I used "send_tcp_open_bind_connect" function.
>>>> But I get a little problem with this function, It ask two local 
>>>> arguments : IP and Port.
>>>>
>>>> But in my case, I don't use the local socket which is open with this 
>>>> function ( I have already another connection running ).
>>>> And my routers in general have more than one interface, which means 
>>>> more than one local IP.
>>>>
>>>> Would it be possible to create a TCP connection without create a 
>>>> local socket like this?
>>>>     
>>>>         
>>> Try setting the local_addr and local_port to zero.
>>>
>>> Regards,
>>> Pavlin
>>>
>>>  
>>>       
>>>> Thanks for your help.
>>>>
>>>> Best regards,
>>>> Michael
>>>>
>>>> _______________________________________________
>>>> Xorp-hackers mailing list
>>>> Xorp-hackers at icir.org
>>>> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers
>>>>     
>>>>         
>> Hello,
>> Thanks for your answer.
>> I try this :
>> send_tcp_open_and_bind("fea",_rtr.instance_name(),NULL,NULL,cb)
>>
>> But I get this error :
>> InvalidString from line 77 of ipv4.cc -> Null value
>> terminate called after throwing an instance of 'InvalidString'
>> [ 2009/03/21 16:11:41  ERROR xorp_rtrmgr:14823 RTRMGR +1405 task.cc 
>> execute_done ] 210 Transport failed
>>     
>
> You should use IPv4::ZERO() and the number 0 for the local_addr and
> local_port respectively instead of NULL.
>
> Hope that helps,
> Pavlin
>
>   
>> :(
>> Best regards,
>> Michael
>>
>> _______________________________________________
>> Xorp-hackers mailing list
>> Xorp-hackers at icir.org
>> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers
>>     

Thanks it works fine!!