[Xorp-users] Re: help establishing OSPF adjacencies

[Pavlin Radoslavov]

> Hi Pavlin,
> 
> On Mon, Oct 17, 2005 at 02:28:01PM -0700, Pavlin Radoslavov wrote:
> > A quick suggestion. Please use the full path name to the click
> > binary instead of using "~". Previously the click binary and its
> > arguments were executed via "sh -c" (and execve()).
> > Now it is executed directly via execve() without "sh -c" and the "~"
> > in the path name is not expanded.
> 
> I spoke a little too soon, perhaps.  It's true now that I don't have
> errors on click startup, and the click control socket appears to be
> running, but it's not reading the configuration correctly, I don't
> think.  So, ps shows me this:
> 
> click -f /dev/null -p 13000 -R
> 
> and the control socket shows me this (no configuration...huh?):
> 
> % telnet planetlab4.csail.mit.edu 13000
> Trying 128.31.1.14...
> Connected to planetlab4.csail.mit.edu (128.31.1.14).
> Escape character is '^]'.
> Click::ControlSocket/1.1
> read config
> 200 Read handler 'config' OK
> DATA 0

Did you apply the fix in the CVS?
That fix eventually should take care of the above problem.

Pavlin

> 
> 
> For reference, here's the fea/click config I'm running:
> 
> fea {
>     unicast-forwarding4 {
>         disable: true
>     }
> 
>     click {
>         disable: false
> 
>         user-click {
>             disable: false
>             command-file: "/home/mit_rcp/demo/click"
>             command-extra-arguments: "-R"
>             command-execute-on-startup: true
>             control-address: 127.0.0.1
>             control-socket-port: 13000
>             startup-config-file: "/dev/null"
>             user-click-config-generator-file: "/home/mit_rcp/demo/static_config"
>         }
>     }
> }
> 
> -Nick
> _______________________________________________
> Xorp-users mailing list
> Xorp-users@xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users