From: Gerd K. <kr...@by...> - 2004-12-08 20:00:43
|
> Gerd> Hmm, not sure I like that idea. Is this with vlan tagging > Gerd> support? How can this be configured? Is the command mode the > Gerd> only way, or can you also use some config file or command line > Gerd> switches for that? > > No VLANs. Would be cool I think, so you could debug vlan code in the kernel using uml for example. > It creates multiple sockets, and you tell the UML(s) about the multiple > interfaces. That is clear. How to you tell uml_switch which sockets it should create? > Please read the mentione paper. I've looked at it, it doesn't answer the configuration question through. Your openswan test setup seems to use command mode. It's not clear whenever that is the only way to do it. It shouldn't, for running tests that likely is perfect, but for other applications I just want a static configuration and uml_switch shouldn't wait for commands on stdin/out. > Secondly, I do not put these things into uml_switch. > Rather, I *refactor* things so that uml_switch and uml_netjig share > back end code. uml_switch has none of the above things, only the same > port.c code. Oh, so for uml_netjig you just link in some more some object files which do the arp answering, packet injection and so on? That wasn't clear to me. This makes much more sense ... Gerd -- #define printk(args...) fprintf(stderr, ## args) |