On Tuesday 28 March 2006 11:42, Fuchs, Stephan wrote: > Hi List Members ;-) > > Thanks for your support regarding my interface problem. Seems to be solved > now. When changing the /etc/visdn/device-xxx files, it seems to be the case > that a reboot is the best solution
If you remove all the modules there is nothing that requires a reboot to be reset. If you change some configuration *while* the modules are loaded there may be something that doesn't work and I'd be happy to fix that. I just fixed a bug that leaded to non-working netdevs if visdn_configurator had been run twice. > unloading and loading the drivers takes > me in trouble because asterisk does not recognize the visdn interfaces. Uh? How does this issue manifests? > Am I missing a module? Is there a possibility avoiding the reboot after > configuration changes? Yes :) Bye, -- Daniele "Vihai" Orlandi Espia S.r.l. _______________________________________________ Visdn-hackers mailing list [email protected] https://mailman.uli.it/mailman/listinfo/visdn-hackers
