> Well, an ethernet header is 14 bytes, so maybe 2.6 is sticking one of those
> on?
>
> And maybe there was some flag that we missed in 2.6 that says "this is not
> an ethernet device".
ok, i managed to "fix" the problem.
it was exactly what jeff said.
here is a quick and ugly hack, which works
> > so, my question is, why 2.6 sends ~14 bytes more
>
> Well, an ethernet header is 14 bytes, so maybe 2.6 is sticking one of those
> on?
>
> And maybe there was some flag that we missed in 2.6 that says "this is not
> an ethernet device".
this sounds like the problem.
however, the questi
[EMAIL PROTECTED] said:
> so, my question is, why 2.6 sends ~14 bytes more
Well, an ethernet header is 14 bytes, so maybe 2.6 is sticking one of those
on?
And maybe there was some flag that we missed in 2.6 that says "this is not
an ethernet device".
Jeff
ok, i think i have narrowed down the problem:
(this also appears on a post from 4/2004...)
when running slirp in debug mode, and trying to ping the host ip:
in 2.4.27, for each ping about 86 bytes are sent, and are received
correctly.
in 2.6, for each ping about 100 bytes are sent, received, and d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi again
> All I can say is that I just tried slirp in 2.4.27-1um on my system and it
> works for me. Unless you provide details how your system is set up I have
> no idea why it would not work for you.
i tried with 2.4.27, and it works for me too
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi
> Thanks for the feedback. Could you post a problem description? WHAT
> doesn't work: does the interface not come up, does it segfault, does
> everything look fine but network traffic hangs, does it even compile? WHAT
> versions are you usin
hi.
I was using slirp to give network access for students, working on uml.
i did not want to assign any ip addresses to the uml instances, as the
address space is not under my control, and i dont have root access to
the machines student work on.
So, slirp was my default choice. However, i doesn't
