From: Stian Sletner <stian@sletner.com>
To: Stas Sergeev <stssppnn@yahoo.com>
Cc: linux-msdos@vger.kernel.org
Subject: Re: DOSEMU does not pick up all packets
Date: Fri, 29 Nov 2002 21:48:53 +0100 [thread overview]
Message-ID: <20021129204853.GD1154@sletner.com> (raw)
In-Reply-To: <3DE7CDC4.6010601@yahoo.com>
* At 2002-11-29T23:27+0300, Stas Sergeev wrote:
:
| >I thought I had a clever idea, ifconfig'd up a virtual interface eth0:0
| >and set $_netdev = "eth0:0", but that made dosemu crash so it probably
| How exactly the crash looks like?
stian:~$ nice -20 dos -D+P -o dos.debug >dos.out 2>&1
dos.debug:
debug flags: -a
debug flags: +P
========Sending packet======
packet to send: :
Dest.=ff:ff:ff:ff:ff:ff: Source=0:40:95:0:3c:31: Type= 3781
PD ERR: AX=0481 BX=03bc CX=003c DX=0c08 FLAGS=00033017
SI=163c DI=164a BP=ff7c SP=ff6e CS=f000 DS=0f90 ES=0f90 SS=17f1
SIGILL while in vm86()
ERROR: unexpected CPU exception 0x06 err=0x00000000 cr2=00000000 while in vm86 (DOS)
leavedos(4|0x4) called - shutting down
dos.out:
Linux kernel 2.4.18; CPU speed is 300676000 Hz
Dosemu-1.1.3.7 Running on CPU=586, FPU=1
^[[?25h^[[0m^[[H^[[2JERROR: unexpected CPU exception 0x06 err=0x00000000 cr2=00000000 while in vm86 (DOS)
Program=sigsegv.c, Line=162
EIP: 8b2e:00003669 ESP: 17f1:0000ff70 VFLAGS(b): 00000 00110000 00000110
EAX: 00007ff9 EBX: 0000000e ECX: 0000003d EDX: 00000733 VFLAGS(h): 00003006
ESI: 0000163c EDI: 0000164a EBP: 0000ff7c DS: 0f90 ES: 0f90 FS: 0000 GS: 0000
FLAGS: PF IF RF VM IOPL: 3
STACK: 35 02 e6 19 00 b8 92 ff 15 07 -> 13 00 27 13 08 16 90 0f 82 03
OPS : 00 00 00 00 00 40 6a 13 33 01 -> ff ff ff ff ff ff 02 00 00 00
ffff 8b2e:3669 ??? di
| >I'm having problems compiling the dosnet module in RH8.
| It was already reported that there
| are problems compiling dosnet under
| RH8. The fix is to get the fresh
| kernel sources and make a proper
| symlinks for /usr/include/linux and
| /usr/include/asm
Ah.
| Why are you limited with bridging between only 2 interfaces?
Well, it only listens on one interface, and packs up the packets in IP
and sends them off in UDP through normal networking means. And listens
for UDP (IPADDR_ANY) and unpacks and puts them out on the interface.
What I'm currently using is "SIB", btw. (It's on freshmeat somewhere if
you want to look.)
--
Stian Sletner
next prev parent reply other threads:[~2002-11-29 20:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-29 20:27 DOSEMU does not pick up all packets Stas Sergeev
2002-11-29 20:48 ` Stian Sletner [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-29 0:40 Stas Sergeev
2002-11-29 19:26 ` Stian Sletner
2002-11-28 21:06 Stas Sergeev
2002-11-28 21:59 ` Stian Sletner
2002-11-26 20:57 Stas Sergeev
2002-11-26 22:02 ` Stian Sletner
2002-11-28 5:26 ` Stian Sletner
2002-11-26 19:01 Stian Sletner
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=20021129204853.GD1154@sletner.com \
--to=stian@sletner.com \
--cc=linux-msdos@vger.kernel.org \
--cc=stssppnn@yahoo.com \
/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