From: Mark H. <ma...@os...> - 2004-06-10 16:03:18
|
On Wed, 2004-06-09 at 16:29, Jon Maloy wrote: > Hi all, > I have now checked in my new code for dynamic configuration of TIPC. > There are more changes than I really appreciate in one single delivery, > but it seems to work fairly well so far, and I think it was necessary to > have > it done. > > Major changes: > > 1: No module parameters anymore, -everything must be done via > the new user-land tool "tipc-config" that comes with the package. > 2: TIPC can be executed in single-node mode without any initial > configuration at all. It will use the special node address <0.0.0> > for single-node use, but this must be set to a real address before > running in network mode. > 3: A few bugs, primarily related to manager.c, but also to routing > of named messages were fixed. > > tipc-config is far from being perfect yet, and can certainly be improved > both regarding readability and robustness, but it works well for the > basic cases, such as setting own node address and enabling/disabling > interfaces. > Even the other commands have been tested,and work under normal > cirumstances. > Have a look at the command interface, -I have tried to make it as > comprehensible as possible, but I am very open for improvement > suggestions. > > Enjoy(?) /Jon I was able to set the address of my node fairly easily, but when it came to enabling an ethernet interface, I haven't had any luck yet. I have tried: ./tipc-config -be=eth1 But get: Command rejected, check syntax I had assumed that I just use the net device name like with the insmod. Am I doing something obviously wrong? Thanks, Mark. -- Mark Haverkamp <ma...@os...> |