[Xorp-users] Error writing to routing socket: No such process

Edwin Schokkenbroek edwin at spacebugs.nl
Wed Jul 28 12:23:30 PDT 2010


Hello Garry, 

The goal is to export static routes into OSPF.  I normally work with Juniper routers and in junos policies are used to redistribute routes. So I figured this is the same in Xorp. Or isn't this the way to do it in Xorp ?

Edwin


On Jul 28, 2010, at 9:15 PM, Garry Peirce wrote:

> Not sure I understand your policy statement - I assume you desire to accept
> static routes.
> Do you actually mean the following?
> 
>>  term a {
>>      from {
>>          protocol: "static"
>>      }
>>      then {
>>          accept {
>>          }
>>      }
>>  }
>>  then {
>>      reject {
>>      }
>>  }
> 
> 
> 
>> -----Original Message-----
>> From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org]
>> On Behalf Of Edwin Schokkenbroek
>> Sent: Wednesday, July 28, 2010 2:43 PM
>> To: xorp-users at xorp.org
>> Subject: [Xorp-users] Error writing to routing socket: No such process
>> 
>> Hello list.,
>> 
>> Maybe someone here can help me out on the following issue. I'm working
>> on it now for a couple weeks to get this solved, but I can't find a
>> solution.
>> 
>> I'm using xorp version 1.06 on FreeBSD 8.0 (AMD64).
>> xorp is running inside vimages. When I start xorp I receive the
>> following messages:
>> 
>> [ 2010/07/28 20:03:37  ERROR xorp_fea:2207 FEA +527
>> fibconfig_entry_set_routing_socket.cc delete_entry ] Error writing to
>> routing socket: No such process
>> [ 2010/07/28 20:03:37  ERROR xorp_rib:2208 RIB +916 redist_xrl.cc
>> dispatch_complete ] Failed to commit transaction: 102 Command failed
>> DeleteEntry4: net = 0.0.0.0/0 nexthop = 172.19.0.2 ifname = epair4a
>> vifname = epair4a metric = 1 admin_distance = 1 xorp_route = true
>> is_deleted = false is_unresolved = false is_connected_route = false
>> [ 2010/07/28 20:03:37  ERROR xorp_fea:2207 FEA +80
>> fibconfig_transaction.cc operation_result ] FIB transaction commit
>> failed on DeleteEntry4: net = 0.0.0.0/0 nexthop = 172.19.0.2 ifname =
>> epair4a vifname = epair4a metric = 1 admin_distance = 1 xorp_route =
>> true is_deleted = false is_unresolved = false is_connected_route =
>> false
>> [ 2010/07/28 20:03:37 WARNING xorp_fea XrlFeaTarget ] Handling method
>> for redist_transaction4/0.1/commit_transaction failed: XrlCmdError 102
>> Command failed DeleteEntry4: net = 0.0.0.0/0 nexthop = 172.19.0.2
>> ifname = epair4a vifname = epair4a metric = 1 admin_distance = 1
>> xorp_route = true is_deleted = false is_unresolved = false
>> is_connected_route = false
>> 
>> The route table looks like:
>> 
>> beheer at router1> show route table ipv4 unicast final
>> 0.0.0.0/0       [static(1)/1]
>>> to 172.19.0.2 via epair4a/epair4a
>> 10.0.0.0/24     [connected(0)/0]
>>> via epair1a/epair1a
>> 10.1.0.0/24     [connected(0)/0]
>>> via epair3a/epair3a
>> 172.19.0.0/30   [connected(0)/0]
>>> via epair4a/epair4a
>> 
>> Interface information:
>> 
>> beheer at router1> show interfaces
>> epair1a/epair1a: Flags:<ENABLED,BROADCAST,MULTICAST> mtu 1500 speed
>> unknown
>>        inet 10.0.0.1 subnet 10.0.0.0/24 broadcast 10.0.0.255
>>        physical index 2
>>        ether 02:ca:d0:00:05:0a
>> epair3a/epair3a: Flags:<ENABLED,BROADCAST,MULTICAST> mtu 1500 speed
>> unknown
>>        inet 10.1.0.1 subnet 10.1.0.0/24 broadcast 10.1.0.255
>>        physical index 3
>>        ether 02:ca:cb:00:05:0a
>> epair4a/epair4a: Flags:<ENABLED,BROADCAST,MULTICAST> mtu 1500 speed
>> unknown
>>        inet 172.19.0.1 subnet 172.19.0.0/30 broadcast 172.19.0.3
>>        physical index 4
>>        ether 02:ca:d0:00:05:0a
>> 
>> The config file I'm using:
>> 
>> /*XORP Configuration File, v1.0*/
>> protocols {
>>    ospf4 {
>>        router-id: 10.0.0.1
>>        rfc1583-compatibility: false
>>        ip-router-alert: false
>>        area 0.0.0.0 {
>>            area-type: "normal"
>>            interface epair1a {
>>                link-type: "broadcast"
>>                vif epair1a {
>>                    address 10.0.0.1 {
>>                        priority: 128
>>                        hello-interval: 10
>>                        router-dead-interval: 40
>>                        interface-cost: 1
>>                        retransmit-interval: 5
>>                        transit-delay: 1
>>                        disable: false
>>                    }
>>                }
>>            }
>>            interface epair3a {
>>                link-type: "broadcast"
>>                vif epair3a {
>>                    address 10.1.0.1 {
>>                        priority: 128
>>                        hello-interval: 10
>>                        router-dead-interval: 40
>>                        interface-cost: 1
>>                        retransmit-interval: 5
>>                        transit-delay: 1
>>                        disable: false
>>                    }
>>                }
>>            }
>>        }
>>        export: "red-static-rt"
>>    }
>>    static {
>>        disable: false
>>        route 0.0.0.0/0 {
>>            next-hop: 172.19.0.2
>>            metric: 1
>>        }
>>    }
>> }
>> policy {
>>    policy-statement "red-static-rt" {
>>        term a {
>>            from {
>>                protocol: "static"
>>            }
>>            then {
>>                accept {
>>                }
>>                reject {
>>                }
>>            }
>>        }
>>    }
>> }
>> fea {
>>    unicast-forwarding4 {
>>        disable: false
>>    }
>> }
>> interfaces {
>>    restore-original-config-on-shutdown: false
>>    interface epair1a {
>>        description: ""
>>        disable: false
>>        discard: false
>>        unreachable: false
>>        management: false
>>        vif epair1a {
>>            disable: false
>>            address 10.0.0.1 {
>>                prefix-length: 24
>>                broadcast: 10.0.0.255
>>                disable: false
>>            }
>>        }
>>    }
>>    interface epair3a {
>>        description: ""
>>        disable: false
>>        discard: false
>>        unreachable: false
>>        management: false
>>        vif epair3a {
>>            disable: false
>>            address 10.1.0.1 {
>>                prefix-length: 24
>>                disable: false
>>            }
>>        }
>>    }
>>    interface epair4a {
>>        description: ""
>>        disable: false
>>        discard: false
>>        unreachable: false
>>        management: false
>>        vif epair4a {
>>            disable: false
>>            address 172.19.0.1 {
>>                prefix-length: 30
>>                disable: false
>>            }
>>        }
>>    }
>> }
>> rtrmgr {
>>    config-directory: "/root/chaos/vrd/edwin/router1/boot"
>>    load-file-command: "/root/chaos/vrd/edwin/router1/boot/config.boot"
>>    load-file-command-args: "-o"
>>    load-ftp-command: "fetch"
>>    load-ftp-command-args: "-o"
>>    load-http-command: "fetch"
>>    load-http-command-args: "-o"
>>    load-tftp-command: "sh -c 'echo Not implemented 1>&2 && exit 1'"
>>    load-tftp-command-args: ""
>>    save-file-command: "/root/chaos/vrd/edwin/router1/boot/config.boot"
>>    save-file-command-args: ""
>>    save-ftp-command: "sh -c 'echo Not implemented 1>&2 && exit 1'"
>>    save-ftp-command-args: ""
>>    save-http-command: "sh -c 'echo Not implemented 1>&2 && exit 1'"
>>    save-http-command-args: ""
>>    save-tftp-command: "sh -c 'echo Not implemented 1>&2 && exit 1'"
>>    save-tftp-command-args: ""
>> }
>> 
>> 
>> The vimages are started with the following options:
>> 
>> sysctl net.inet.ip.forwarding=1
>> sysctl security.jail.allow_raw_sockets=1
>> 
>> 
>> I seems that the error messages appear when I apply the policy. What
>> can I do to solve the  error messages ?
>> 
>> 
>> 
>> 
>> 
>> Hades
>> 
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> Xorp-users mailing list
>> Xorp-users at xorp.org
>> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
> 


Edwin Schokkenbroek
edwin at spacebugs.nl

Engineers are full of great ideas. Making things better is what we're built to do. However, when it comes to engineers, there seems to be an inverse relationship between great ideas and great communication skills. This is what gets us into trouble.









More information about the Xorp-users mailing list