X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
From: "Gerrit van Niekerk" <gerritvn AT gpvno DOT co DOT za>
Organization: GPvNO
To: djgpp AT delorie DOT com
Date: Mon, 15 May 2006 16:22:01 +0200
MIME-Version: 1.0
Subject: Re: SwsVpkt
Message-ID: <4468AAA9.29630.ECAC73@gerritvn.gpvno.co.za>
In-reply-to: <44688943$0$21272$8fcfb975@news.wanadoo.fr>
X-mailer: Pegasus Mail for Windows (4.31)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On 15 May 2006 at 15:59, Lawrence Rust wrote:

> "Gerrit van Niekerk" <gerritvn AT gpvno DOT co DOT za> wrote in message
> news:446886C4 DOT 29888 DOT 607887 AT gerritvn DOT gpvno DOT co DOT za...
> >
> >
> > On 15 May 2006 at 10:35, Lawrence Rust wrote:
> >
> > > I wrote SwsVpkt, a free virtual packet driver for Windows
> NT/2k/XP/2k3.
> It's available here
> > > www.softsystem.co.uk/page7.html.  I believe Gisle has tested it
> with
> Watt-32 and it's also
> > > extensively used by radio amateurs for their JNOS project
> www.langelaar.net/projects/jnos2.  It
> > > also provides significantly better performance than NDIS3PKT and is
> a
> lot less hassle and overhead
> > > than WinPcap.
> > >
> > I've been using NDIS3PKT for years and more recently on WinXP SP2
> without
> problems, but not the
> > greatest of performances. With the above promise in mind, I
> downloaded
> SwsVpkt 1.0.0.4, uninstalled
> > NDIS3PKT and installed SwsVpkt. It sends out packets well enough on
> my
> system using a Realtek
> > RTL8139 Family Fast Ethernet Adapter, but does not receive any packets
> -
> not even broadcasts. Any
> > tips on what could be wrong?
> 
> What app(s) are you using to test with?  It may be that your DOS
> TCP/IP
> configuration needs a small tweak.
> 
> I would guess that since only packet reception is affected then the
> problem
> lies with interrupts.  The swsvpkt real mode stub uses irq 7 to
> communicate
> with the win32 code.  You could try using a different irq, maybe 5.  To
> do
> this enter "swsvpkt -i5", then run your app.
> 
> If you still have problems, then it would be useful to know if any
> packets
> are shown with my standalone packet dumper app.  You can download this
> from
> here: www.softsystem.co.uk/SwsSockSDKbin1004.zip - it comes with
> several
> utilities, you'll just need to unzip \djgpp\pktdump.exe.  The source
> is
> available from here: www.softsystem.co.uk/SwsSockSDKdemo1004.zip in
> \apps\pktdump.
> 
> Run pktdump from a DOS box that has successfully executed SwsVpkt.exe. 
> Then
> start some network activity, e.g. web browsing, and you should see a
> trace
> of all packets in & out.  The app puts the NIC into promiscuous mode, so
> you
> see all traffic on the local net if you use a hub.
> 
> If pktdump works OK then the problem is likely to be your DOS TCP/IP
> stack
> configuration.  If pktdump fails then it's likely to be some problem
> with
> SwsVpkt or the installation.  I'll advise further in this case.
> 
> - Lawrence Rust, Software Systems, www.softsystem.co.uk

Thanks Lawrence, changing the hardware interrupt to 9 fixed the problem. 
For clarification: Interrupt 9 is the real h/w interrupt used by my NIC. Should 
one always specify that correctly for SwsVpkt? Isn't the interrupt just a way 
for the realmode stub to communicate with the win32 driver?

Gerrit