nemesis-users — General discussion about Nemesis

[nemesis-users] Nemesis the Resurrection

[Joachim N. <tro...@gm...>]

Hi list,

my name is Joachim Nilsson and I've recently picked up maintenance of
Nemesis at GitHub¹.  Yeah, I'm a bit late to the party ... :-)

So far I've:

- merged the libnet1 CVS branch, builds fine on Debian/Ubuntu
- fixed a few issues with that port,
- merged Debian patches to man pages,
- merged the IGMP general query fix from this list by Randy Robertson
- fixed the long-standing issue with the non-functioning OSPF
- ...

More details in the ChangeLog².  A v1.5 release will be out in a few
weeks time, unless there's a sudden influx of bug reports and/or pull
requests (patches to this list are also fine :) 

To test the latest GIT master, remember to run ./autogen.sh first to
create the configure script.


Cheers
 /Joachim 

___
¹) https://github.com/troglobit/nemesis
²) https://github.com/troglobit/nemesis/blob/master/ChangeLog.md

[nemesis-users] Linux bridge don't see nemesis injected packages to eth0 or eth1

[Kfir L. <lav...@gm...>]

Hi,
I want to use nemesis for testing my ebtables, iptables behavior,
injecting packages via a script and check the results.
Apparently br0 don't see locally injected packages to eth0 or eth1.
My setup is a simple bridge br0 that have eth0 and eth1.
Using this two lines inside a script, I'm creating arp request in eth0
and arp reply in eth1.
nemesis arp -v -d eth0 -S $SRC -D $DST -h $SRC_MAC
nemesis arp -v -r -d eth1 -S $DST -D $SRC -h $DST_MAC -m $SRC_MAC

If I run those commands in the bridge locally, I will see each packet
(tcpdump -i ethX) in the interface ethX, but not on the bridge br0.
If I run this command from another computer in the lan, I do see this
2 arp packets at br0 and eth0 and eth1.
So the bridge do forward the arp packets, but just if they are created
outside of the bridge machine.

Is it possible to generate traffic inside the bridge that br0  could see?

Regards,
Kfir

[nemesis-users] ICMP - Redirect - Bad CheckSum

[kecajkecaj <kec...@tl...>]

Hi. 
I'm tring to send a icmp redirect packet as follows:
nemesis icmp -v -d eth0 -i 5 -c 1 -G 192.168.1.20 -qR -S 192.168.1.1 -D 192.168.1.10 -H 00:50:DA:3A:2D:B3  -M 00:07:95:07:DC:ED

packet is injected but in wireshark i can see that a checksum of icmp field is incorrect. I have no idea why it's happening.
Can somebody gives me a clue ?
thx

[nemesis-users] OSPF

[Charis <cyc...@ya...>]

Is nemesis supporting OSPF?

[nemesis-users] Broken link (need a patch) - Nemesis for libnet 1.1

[William V. <bi...@bi...>]

Hello there
I'm trying to install nemesis 1.4 with libnet 1.1 without results.
Read in the mail list archive, that there is a new version when the
nemesis is patched (1.5), bute the URL
(http://www.cisco.nctu.edu.tw/nemesis) don't work.
I would appreciate if they provide a valid link or the patch for nemesis 1.4

Best regards

--
William Vera <bi...@bi...>
PGP Key: 1024D/F5CC22A4
Fingerprint: 3E73 FA1F 5C57 6005 0439 4D75 1FD2 BF96 F5CC 22A4



-- 
William Vera <bi...@bi...>
PGP Key: 1024D/F5CC22A4
Fingerprint: 3E73 FA1F 5C57 6005 0439 4D75 1FD2 BF96 F5CC 22A4

[nemesis-users] please help-nemesis --ospf

[zvonimir k. <zvo...@gm...>]

Can anyone tell me is there an older version of nemesis available  the one
that supports OSPF protocol
because in the newest one OSPF is not supported. And if there is such a
version where could I find it.
If there is not such a version does anyone know of a similar program for
freebsd for injecting
packets (specifically OSPF packets).
Will be most grateful for anyone s help.

Zvonimir Krile

[nemesis-users] installation problem

[<pas...@fr...>]

Hy,

i have installed nemesis under XP, but i 've got one problem.

when i want to execute nemesis.exe , le following message appear:

see  word file joigned



thank you for your help.

Bye

Re: [nemesis-users] Windows Installation Problems

[<nnp...@us...>]

Kamran Shafi wrote:
> First of all there is no .exe and .dll file when the nemesis 1.4 zip file is
> unzipped. I found the 1.4 Beta version from
> http://www.packetfactory.net/projects/nemesis/#windows which do have these
> two files and co-located in the same directory as required. However upon
> trying to run the exe I get the following error
> 
> "The procedure entry point PacketGetNetInfor could not be located in the
> dynamic link library packet.dll"

Have you tried the executable included with SourceForge patch 1341100?

Cheers,
nnposter

[nemesis-users] Windows Installation Problems

[Kamran S. <kam...@gm...>]

Hi,

I can't figure out how to install or configure nemesis on windows.

The INSTALL file says
nemesis.exe can be installed anywhere on a Windows system. The caveat is
that LibnetNT.dll must exist either in the same directory as nemesis.exe or
in any of the directories listed in the %PATH% variable. On Windows 2000
this would be %SystemRoot%\System32

Luckily, the nemesis zip file contains LibnetNT.dll inside the 'nemesis'
directory which should allow you to begin using Nemesis immediately.

First of all there is no .exe and .dll file when the nemesis 1.4 zip file is
unzipped. I found the 1.4 Beta version from
http://www.packetfactory.net/projects/nemesis/#windows which do have these
two files and co-located in the same directory as required. However upon
trying to run the exe I get the following error

"The procedure entry point PacketGetNetInfor could not be located in the
dynamic link library packet.dll"

Any help is appreciated!!!

Regards
Kam


-- 
Regards
Kamran Shafi
+61 41 824 9510

[nemesis-users] nemesis installation error

[Bhuvaneswari R. <ram...@ia...>]

Hi,

I'm a newbie to nemesis. I've tried to install nemesis -1.4 (which says
libnet included) in my windows XP as
well as in a cygwin box. I have a successful installtion of WinPcap already
in my system ( I'm guessing so)
But while installing nemesis, I get an error that packet lib is not found. I
tried getting a separate installation
of libnet also and found the same error while installing libnet separately.

what does it mean when "Libnet library not found" is relayed ?

I have searched as many archives as possible and there doesnt seem to be a
definite answer to how we can fix it.

Does anyone have a suggestion ?


Thanks
Bhuvana

[nemesis-users] PATCH -- Fix nemesis-igmp to allow 0.0.0.0 group address.

[Randy R. <rmr...@vm...>]

With IGMP, it should be possible to send a General Query.

http://www.faqs.org/rfcs/rfc2236.html:
   In a Membership Query message, the group address field is set to zero
   when sending a General Query, and set to the group address being
   queried when sending a Group-Specific Query.

Here is a patch to allow this.  The problem was that nemesis_name_resolve returns
-1 when given the IP 0.0.0.0, but in this context, it is valid.  The patch is just 
one workaround, you might want to just change nemesis_name_resolve itself to be 
less picky because it might be useful in other protocols to set an IP field all zeros.

Also, probably you will want to drop the new fprintf.

diff -ur nemesis-1.4beta3-orig/src/nemesis-igmp.c nemesis-1.4beta3/src/nemesis-igmp.c
--- nemesis-1.4beta3-orig/src/nemesis-igmp.c    2003-06-25 20:54:56.000000000 -0700
+++ nemesis-1.4beta3/src/nemesis-igmp.c 2007-10-23 00:31:22.000000000 -0700
@@ -301,9 +301,13 @@
                 if ((nemesis_name_resolve(optarg,
                         (u_int32_t *)&igmphdr.igmp_group.s_addr)) < 0)
                 {
-                    fprintf(stderr, "ERROR: Invalid IGMP group address: \"%s\"."
-                            "\n", optarg);
-                    igmp_exit(1);
+                       if (!strncmp(optarg, "0.0.0.0", 7)) {
+                               fprintf(stderr, "Allowing 0.0.0.0 IGMP group address");
+                       }else {
+                               fprintf(stderr, "ERROR: Invalid IGMP group address: \"%s\"."
+                                       "\n", optarg);
+                               igmp_exit(1);
+                       }
                 }
                 got_group = 1;
                 break;

[nemesis-users] Regarding IP Options

[Kumar Bharath-A. <bha...@mo...>]

Hi all,

I'm using nemesis-1.4beta3.

I'm working on modifying IP header and inject the packet.
Coming to IP Options, nemesis says use -O with IP-option-file or else
use -O -<mention option from stdin>

I'm unable to use both the options.

Here is my query now.
How should the IP-option-file looks like or how we should give the IP
optionf from stdin.

Next query is how to set the IP precedence field in the IP header.
We have IP TOS but not the Precedence.

Please clarify me.

Waiting for your replies.. :-)

Thanks n Rgds,
Bharath A

[nemesis-users] any example of shell-scripts using nemesis??

[Pablo E. <azt...@gm...>]

hi to the list

I want to emulate a ddos attack against one of my apache webservers to test=
=20
the diffence when mod_security is enabled and when mod_security is disabled.

not sure if could be better using a tool as "Apache HTTP server benchmarkin=
g=20
tool" http://httpd.apache.org/docs/2.0/programs/ab.html or nemesis. =BF=BFa=
ny=20
suggestion about this??

I havent found any example of shell script using nemesis on the website. =
=BFcan=20
anyone please post some example in order not to start from cero??

thanks in advance for any help or suggestiong.

[nemesis-users] installing nemesis in fedora core 5

[Premnath M. <pr...@gm...>]

Hi,
      I am trying to install nemesis in fedorea core 5 after first
installing libnet.
./configure worked with no problems
but 'make' showed these errrors:
[root]# make
gcc  -g -O2 -Wall -funroll-loops -pipe   -o nemesis  nemesis-arp.o
nemesis-dns.o nemesis-ethernet.o nemesis-fileio.o nemesis-functions.o
nemesis-icmp.o nemesis-igmp.o nemesis-ip.o nemesis-ospf.o
nemesis-printout.onemesis-proto_arp.o nemesis-proto_dns.o
nemesis-proto_ethernet.o
nemesis-proto_icmp.o nemesis-proto_igmp.o nemesis-proto_ip.o
nemesis-proto_ospf.o nemesis-proto_rip.o nemesis-proto_tcp.o
nemesis-proto_udp.o nemesis-rip.o nemesis-tcp.o nemesis-udp.o
nemesis.oW32_fzs.o
strlcat.o strlcpy.o -lnet -lresolv -lnsl -lm
/usr/lib/gcc/i386-redhat-linux/4.1.0/../../../libnet.a(libnet_build_arp.o):
In function `libnet_do_arp':libnet_build_arp.c:(.text+0x357): undefined
reference to `pcap_open_live'
:libnet_build_arp.c:(.text+0x468): undefined reference to `pcap_next'
collect2: ld returned 1 exit status

If libpcap is needed , I already have that( since ethereal is installed and
working fine)
Files in /usr/include/:
[root]# ls libnet*
libnet.h
libnet:
libnet-asn1.h       libnet-headers.h  libnet-ospf.h
libnet-functions.h  libnet-macros.h   libnet-structures.h

Files in /usr/lib:
[root]# ls libnet*
libnet.a            libnetsnmpagent.so.10        libnetsnmpmibs.so.10.0.0
libnetpbm.a         libnetsnmpagent.so.10.0.0    libnetsnmp.so.10
libnetpbm.so        libnetsnmphelpers.a          libnetsnmp.so.10.0.0
libnetpbm.so.10     libnetsnmphelpers.so.10      libnetsnmptrapd.a
libnetpbm.so.10.31  libnetsnmphelpers.so.10.0.0  libnetsnmptrapd.so.10
libnetsnmp.a        libnetsnmpmibs.a             libnetsnmptrapd.so.10.0.0
libnetsnmpagent.a   libnetsnmpmibs.so.10

Can anyone please help me out with this ?

regards,
Prem

Re: [nemesis-users] Compilation under Windows and Visual C

[Arturo 'B. B. <bu...@bu...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

nnp...@us... wrote:
> I believe that your assumption is not correct. MinGW is also dependent 
> on msvcrt.dll. Furthermore, I have inspected the binary you are 
> referring to and it appears to be compiled with MinGW, not Visual Studio.

Well, that's good, too! - I'll work with mingw then!

Yours,


- --
Arturo "Buanzo" Busleiman - www.buanzo.com.ar
Consultor en Seguridad Informatica / Dominio Digital TV - Da FOSS man!
KTP Consultores - info AT ktpconsultores.com.ar

Romper un sistema de seguridad los acerca tanto a ser hackers como
encender autos puenteando los convierte en ingenieros automotrices.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEAeDmAlpOsGhXcE0RAuTOAJ0eUlHRBLNL8d6ZuTu4cbEpgQHOSQCdErZS
pPmsXYk6M7zcEBJNIPrF+u4=
=UDDq
-----END PGP SIGNATURE-----

RE: [nemesis-users] Compilation under Windows and Visual C

[<nnp...@us...>]

I believe that your assumption is not correct. MinGW is also dependent 
on msvcrt.dll. Furthermore, I have inspected the binary you are 
referring to and it appears to be compiled with MinGW, not Visual Studio.

Cheers,
nnposter


----- Original Message ----- 
From: "Arturo 'Buanzo' Busleiman" <bu...@bu...>
To: <nem...@li...>
Sent: Sunday, February 26, 2006 4:43 AM
Subject: [nemesis-users] Compilation under Windows and Visual C


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi people!
> 
> I'm trying to get Nemesis compiled under Windows.
> 
> The provided .exe file in the Windows package is compiled with visual C (as it includes the
> msvcrt.dll file, which is the Microsoft Visual C Run Time DLL), but the makefile.win that is
> provided is set to gcc.
> 
> Any projects or makefiles I could use? I'm trying to make some windows patches for nemesis, and I
> would like to avoid using gcc for windows (native or under cygwin).
> 
> Sincerely,
> 
> - --
> Arturo "Buanzo" Busleiman - www.buanzo.com.ar
> Consultor en Seguridad Informatica / Dominio Digital TV - Da FOSS man!
> KTP Consultores - info AT ktpconsultores.com.ar
> 
> Romper un sistema de seguridad los acerca tanto a ser hackers como
> encender autos puenteando los convierte en ingenieros automotrices.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2.1 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
> 
> iD8DBQFEAZRHAlpOsGhXcE0RAmAVAJ91oQh+RNQKAuzAr/2MIBj/eyRlxwCfaZyZ
> 0KIrWFC45bkljwMY9eCGbo8=
> =2VDZ
> -----END PGP SIGNATURE-----

[nemesis-users] Compilation under Windows and Visual C

[Arturo 'B. B. <bu...@bu...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi people!

I'm trying to get Nemesis compiled under Windows.

The provided .exe file in the Windows package is compiled with visual C (as it includes the
msvcrt.dll file, which is the Microsoft Visual C Run Time DLL), but the makefile.win that is
provided is set to gcc.

Any projects or makefiles I could use? I'm trying to make some windows patches for nemesis, and I
would like to avoid using gcc for windows (native or under cygwin).

Sincerely,

- --
Arturo "Buanzo" Busleiman - www.buanzo.com.ar
Consultor en Seguridad Informatica / Dominio Digital TV - Da FOSS man!
KTP Consultores - info AT ktpconsultores.com.ar

Romper un sistema de seguridad los acerca tanto a ser hackers como
encender autos puenteando los convierte en ingenieros automotrices.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEAZRHAlpOsGhXcE0RAmAVAJ91oQh+RNQKAuzAr/2MIBj/eyRlxwCfaZyZ
0KIrWFC45bkljwMY9eCGbo8=
=2VDZ
-----END PGP SIGNATURE-----

[nemesis-users] Running nemesis on 64 bit Windows OS

[Mandar K. <mdk...@gm...>]

Hi Guys,
I don't know if anybody of you has tried running nemesis on 64 bit OS.
I was specifically trying the case with Win XP 64 bit and I was unable
to run nemesis.
It gives me error unable to load driver.

Also when I do nemesis.exe arp -Z it shows me 1 as device but no other
information is supplied.
Is this the Libnet.dll problem?

~Mandar

Re: [nemesis-users] Nemesis igmp destination mac

[<nnp...@us...>]

Stefaan Maertens wrote...
> >s.maertens wrote...
> >> I am new to this list / project, so forgive me for any stupid questions.
> >> I have tried to use nemesis to create IGMP packets. I am trying to make an
> >> igmp membership report to group 224.18.32.1 using following syntax
> >> 
> >> Nemesis.exe igmp -D 224.18.32.1 -i 224.18.32.1 -p 22 -S 10.1.0.28
> >> 
> >> When I sniff with ethereal the packet that goes out I see indeed an IGMP V2
> >> membership report going out. The destination mac however is
> >> (78:01:9b:00:0b:00). I think this should be something starting with
> >> 01:00:5E:XX:XX:XX instead.
> >> -M specifies the source Mac so I have changed my syntax to following
> >> Nemesis.exe igmp -D 224.18.32.1 -i 224.18.32.1 -M 01-00-5E-12-20-01 -p 22 -S
> >> 10.1.0.28
> >> Ethereal tells me now the destinatin mac in the packet is 48:05:9B:00:02:00.
> >> 
> >> I am using nemesis 1.4 with Winpcap 3.0 on windows XP SPII
> >> Any ideas ? 
> >
> >Try -d to specify the interface if you have more than one.
> >
> >> Btw : I saw in earlier post reference to "new binaries in the patches
> >> section" I have been unable to find those. Could someone point me to the
> >> right place please.
> >
> >The Patches section on sourceforge. Keep in mind that these are not 
> >officially released builds.
> >
> >Cheers,
> >nnposter
> >
> Hi,
> 
> Thank you for your reply. I have however tried to use the -d option also. It didn't make any difference. I will try this on some other machines to see if it's maybe a machine specific thing.
> 
> Best regards,
> 
> Stefaan Maertens

FWIW, it seems to be working fine on Win2K SP4 and WinPcap 3.1 with the 
patched libnet and nemesis.

Cheers,
nnposter

[nemesis-users] old libnet imported into CVS

[Jeff N. <je...@sn...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've imported the old libnet code into CVS to track changes made by  
nnposter.

Use of this code is temporary though.  Nemesis is being ported to use  
libdnet.

- -Jeff

- --
http://cerberus.sourcefire.com/~jeff       (DSA key id 6923D3FD)
"Great spirits have always encountered violent opposition from
mediocre minds."   - Albert Einstein


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFDbr5OEqr8+Gkj0/0RAjGzAJ96opXOQRcp6B3BaD7rCjsaVPoOTACfW3WK
KTTC786ripl2inFJcwpLB00=
=8FcM
-----END PGP SIGNATURE-----

Re: [nemesis-users] Nemesis igmp destination mac

[<s.m...@te...>]

>s.maertens wrote...
>> I am new to this list / project, so forgive me for any stupid questions.
>> I have tried to use nemesis to create IGMP packets. I am trying to make an
>> igmp membership report to group 224.18.32.1 using following syntax
>> 
>> Nemesis.exe igmp -D 224.18.32.1 -i 224.18.32.1 -p 22 -S 10.1.0.28
>> 
>> When I sniff with ethereal the packet that goes out I see indeed an IGMP V2
>> membership report going out. The destination mac however is
>> (78:01:9b:00:0b:00). I think this should be something starting with
>> 01:00:5E:XX:XX:XX instead.
>> -M specifies the source Mac so I have changed my syntax to following
>> Nemesis.exe igmp -D 224.18.32.1 -i 224.18.32.1 -M 01-00-5E-12-20-01 -p 22 -S
>> 10.1.0.28
>> Ethereal tells me now the destinatin mac in the packet is 48:05:9B:00:02:00.
>> 
>> I am using nemesis 1.4 with Winpcap 3.0 on windows XP SPII
>> Any ideas ? 
>
>Try -d to specify the interface if you have more than one.
>
>> Btw : I saw in earlier post reference to "new binaries in the patches
>> section" I have been unable to find those. Could someone point me to the
>> right place please.
>
>The Patches section on sourceforge. Keep in mind that these are not 
>officially released builds.
>
>Cheers,
>nnposter
>
Hi,

Thank you for your reply. I have however tried to use the -d option also. It didn't make any difference. I will try this on some other machines to see if it's maybe a machine specific thing.

Best regards,

Stefaan Maertens

Re: [nemesis-users] Nemesis igmp destination mac

[<nnp...@us...>]

s.maertens wrote...
> I am new to this list / project, so forgive me for any stupid questions.
> I have tried to use nemesis to create IGMP packets. I am trying to make an
> igmp membership report to group 224.18.32.1 using following syntax
> 
> Nemesis.exe igmp -D 224.18.32.1 -i 224.18.32.1 -p 22 -S 10.1.0.28
> 
> When I sniff with ethereal the packet that goes out I see indeed an IGMP V2
> membership report going out. The destination mac however is
> (78:01:9b:00:0b:00). I think this should be something starting with
> 01:00:5E:XX:XX:XX instead.
> -M specifies the source Mac so I have changed my syntax to following
> Nemesis.exe igmp -D 224.18.32.1 -i 224.18.32.1 -M 01-00-5E-12-20-01 -p 22 -S
> 10.1.0.28
> Ethereal tells me now the destinatin mac in the packet is 48:05:9B:00:02:00.
> 
> I am using nemesis 1.4 with Winpcap 3.0 on windows XP SPII
> Any ideas ? 

Try -d to specify the interface if you have more than one.

> Btw : I saw in earlier post reference to "new binaries in the patches
> section" I have been unable to find those. Could someone point me to the
> right place please.

The Patches section on sourceforge. Keep in mind that these are not 
officially released builds.

Cheers,
nnposter

[nemesis-users] Nemesis igmp destination mac

[s.maertens <s.m...@cr...>]

Hi,

I am new to this list / project, so forgive me for any stupid questions.
I have tried to use nemesis to create IGMP packets. I am trying to make an
igmp membership report to group 224.18.32.1 using following syntax

Nemesis.exe igmp -D 224.18.32.1 -i 224.18.32.1 -p 22 -S 10.1.0.28

When I sniff with ethereal the packet that goes out I see indeed an IGMP V2
membership report going out. The destination mac however is
(78:01:9b:00:0b:00). I think this should be something starting with
01:00:5E:XX:XX:XX instead.
-M specifies the source Mac so I have changed my syntax to following
Nemesis.exe igmp -D 224.18.32.1 -i 224.18.32.1 -M 01-00-5E-12-20-01 -p 22 -S
10.1.0.28
Ethereal tells me now the destinatin mac in the packet is 48:05:9B:00:02:00.

I am using nemesis 1.4 with Winpcap 3.0 on windows XP SPII
Any ideas ? 

Btw : I saw in earlier post reference to "new binaries in the patches
section" I have been unable to find those. Could someone point me to the
right place please.

Best regards

Stefaan Maertens

email: s.m...@cr... 

[nemesis-users] RE: Way to get nemesis1.4beta3 to work with winpcap 3.1?

[<nnp...@us...>]

Small, Jim <jim@ed...> wrote:
> Hi,
> 
> I was wondering if there is a way to get nemesis1.4beta3 to work with
> winpcap version 3.1?  I am using the latest version of windump and it is not
> compatible with winpcap < 3.1b2.
> 
> It appears that winpcap 2.3 is not compatible with XPsp2, and winpcap 3.0 is
> not compatible with a version of windump (or at least not with one I can
> find).
> 
> Please correct me if I"m mistaken.
> 
> Thanks,
>    <> Jim
 
Try the updated binaries I have uploaded today into the "Patches" section.
They should be fully compatible with WinPcap 3.0 and 3.1.

Cheers,
nnposter

[nemesis-users] RE: problem with -d option on WinXP

[<nnp...@us...>]

Stefano Tebaldi <steteb@gm...> wrote:
> i have a problem with Nemesis on Windows XP. Even if Nemesis correctly shows 
> the three network interfaces that i have on my PC with the -Z option, when i 
> try to use for instance the third network interface (-d 3), nemesis uses 
> always the first one (i can see it with ethereal). 
> 
> What could be the problem?
> 
> Ste
 
Try the updated binaries I have uploaded today into the "Patches" section.
There is a possibility that they resove your issue.

Cheers,
nnposter