From: Blaisorblade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Steve Schmidtke <steve_schmidtke@hotmail.com>,
mcr@marajade.sandelman.ottawa.on.ca, kraxel@bytesex.org,
uml@uxu.ch, jdike@addtoit.com
Subject: Re: [uml-devel] Re: What to do with uml_switch?
Date: Mon, 6 Dec 2004 21:16:42 +0100 [thread overview]
Message-ID: <200412062116.43380.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <BAY24-F43C12817C138B110B213583B30@phx.gbl>
On Sunday 05 December 2004 21:20, Steve Schmidtke wrote:
> Michael Richardson wrote:
> > uml_netjig is a tool which does the following:
> > 1) moves packets using "daemon" mode a la uml_switch.
> > 2) has an expect-friendly command line interface 3) can create
> >*multiple* switches and keep them seperate
> If they are separate, why not just run multiple uml_switches?
Probably easier to manage... simplicity is good, but not as important, or
important in the same way, for userspace problems. Don't apply on uml_switch
the same inclusion criteria you use for the kernel.
> > 4) can record all packets to a .pcap file
> > 5) can play packets from a .pcap file at a given rate (or under
> >command line interface control)
> > 6) can optionally answer ARP queries for imaginary nodes.
> I like these 3, but could you not just connect another UML guest to the
> switch and run arp -s pub and tcpdump to accomplish the same thing?
Needing another UML guest to do something which can be accomplished in a
simpler way (supposing it's not too badly coded / heavy / intrusive in the
patch) could even be reported as a bug, on the reverse!
Another problem: it's doable even without support for "pcap transport" in UML
(which is currently broken in 2.6)? I know what to do to fix that (build
problem only), only it's a bit ugly to fix - or requires pcap maintainers to
fix up some screwage:
a symbol which *should* be static is global, in the static libraries it gets
obviously exported, it's called vmap, conflicts with the kernel functions
with the same name, and since it's also a common symbol (i.e. it can share
the space of the function, see LD manual) it crashes UML silently, by trying
to overwrite the vmap() code when you use it - funny breakage, isn't it?
Would you imagine somebody to be able to screw up things so much? And is
there a polite way to get it fixed? Yes, but needs time to settle down
I've recently learned to fix that with objcopy --keep-global, just haven't
done it yet).
> > 7) can talk to tuntap device(s) as uml_switch could.
> >
> > My patches refactor uml_switch to get uml_netjig + uml_switch'
> I am still not clear if uml_netjig is a separate program running on top of
> uml_switch or inside it, but (and I apologize for being dense if this is
> what you are doing) I think the proper way to accomplish what you want is
> to create a "-monitor <socket>" option to uml switch to filter all network
> traffic through. Then create a monitor program that can attach/detach from
> a uml_switch at will through the monitor socket. A hook to filter packets
> entering uml_switch and a new function to inject packets (with/without
> updating MAC tables) might be all that's necessary. All your traffic
> management and expect code could reside in the external monitor program.
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-12-06 20:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-05 20:20 [uml-devel] Re: What to do with uml_switch? Steve Schmidtke
2004-12-06 1:23 ` mcr
2004-12-07 16:06 ` Steve Schmidtke
2004-12-08 17:11 ` Michael Richardson
2004-12-08 19:49 ` Steve Schmidtke
2004-12-08 21:41 ` Michael Richardson
2004-12-14 0:36 ` Werner Almesberger
2004-12-10 18:36 ` Blaisorblade
2004-12-12 0:11 ` Michael Richardson
2004-12-12 19:11 ` Steve Schmidtke
2004-12-12 20:50 ` Michael Richardson
2004-12-16 18:20 ` Blaisorblade
2004-12-06 20:16 ` Blaisorblade [this message]
2004-12-08 16:42 ` Michael Richardson
-- strict thread matches above, loose matches on Subject: below --
2004-12-04 3:52 [uml-devel] " Blaisorblade
2004-12-05 3:42 ` [uml-devel] " Michael Richardson
2004-12-06 19:25 ` Gerd Knorr
2004-12-07 16:21 ` Steve Schmidtke
2004-12-08 16:51 ` Michael Richardson
2004-12-08 19:33 ` Gerd Knorr
2004-12-09 3:22 ` Michael Richardson
2004-12-08 19:36 ` Steve Schmidtke
2004-12-08 21:37 ` Michael Richardson
2004-12-09 0:28 ` Steve Schmidtke
2004-12-09 0:53 ` Michael Richardson
2004-12-05 20:00 ` [uml-devel] " Steve Schmidtke
2004-12-06 18:30 ` [uml-devel] " Gerd Knorr
2004-12-06 19:35 ` [uml-devel] " Blaisorblade
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200412062116.43380.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=jdike@addtoit.com \
--cc=kraxel@bytesex.org \
--cc=mcr@marajade.sandelman.ottawa.on.ca \
--cc=steve_schmidtke@hotmail.com \
--cc=uml@uxu.ch \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox