Anyone else running udpecho with winXP?

[jaredb0t]

I'm trying to get udpecho to work with winXP to no avail. I've tried several things, including upgrading to the newest version of WinPcap (2.3). I have used the windump tool found on the WinPcap site, and have discovered that winpcap IS working on my system, as it displays a list of adapters and will listen to an adapter of my choice.

However when trying to run udpecho v0.2, it does not detect any of my adapters =X.

I can get udpecho to work on my system when running Windows ME, but not XP.

Anyone else having this problem?

Anyone have udpecho working on their XP box?

Thanks.

[Sparkz]

i have tried to use this with WinblowsME but all i seem to get is a quick flash of a DOS window then nothing else, so i'm no help
;)

[jaredb0t]

to answer your problem... you need to run the program from the dos-prompt.. not just double click the EXE file in windows... if you run the program without supplying the parameters it will just tell you which adapters you have installed.

so get to ms-prompt, and type udpecho, and it will spit out your adapters.. if your connected by a modem the IN should be something like PPPMAC, and your network card should be something .. else.. depending on the driver i believe, i use a 3com card and my network adapter is named FA311

so then i run udpecho PPPMAC FA311.. works great (only in winME that is =x

the newest version of WinPcap (the only one that supports Win XP) i believe came out a few days after winseq updated udpecho to version 0.2.

[S_B_R]

Originally posted by jaredb0t
I have used the windump tool found on the WinPcap site, and have discovered that winpcap IS working on my system, as it displays a list of adapters and will listen to an adapter of my choice. Since you have a list of adapter names from windump, have you tried using those names with udpecho???

[jaredb0t]

Originally posted by S_B_R
Since you have a list of adapter names from windump, have you tried using those names with udpecho???

Yes, I did fool around with that. However using the windump utility:

windump -D

spits out the adapter name something like this
1.) \device\some\directory\here\{324323-1232154-1231234-123123} (3COM FA311 Fast Ethernet Adapter)
2.) \device\similar\directory\here\{12312123-1234-12312354} (4811/Miniport)

(I just made the stuff up.. but thats the format.)

so i tried running udpecho with the full directory like this
udpecho \device\....\{12321...123} \device\..etc

and then just the numbers with the braces

udpecho {23123....12312} {324etc}

and then the numbers with out the braces
udpecho 2313-1423-1232 324123-2341-123etc

and then i tried using the actual names.. but that did work because it has spaces... so then i tried using names similar to those I find in WinME.. no go.

[high_jeeves]

The full directory names are the names of the adapters in 2K and XP (and probably NT, but dont quote me on that). Try surrounding them in double quotes on the command line, or perhaps try doubling all the slashes..

ex:

udpecho "\device\{242141234}"

or

udpecho "\\device\\{23412314234}"

--Jeeves

[jaredb0t]

just tried the quotes and the double slashes... didn't work,

I think i'm just sol unless winseq comes out with a new version that supports XP.

[S_B_R]

Originally posted by jaredb0t
just tried the quotes and the double slashes... didn't work,

I think i'm just sol unless winseq comes out with a new version that supports XP.
Or you could setup your linux box as a router using IPTables and you would be good to go.

[jaredb0t]

well the whole deal is merely convienience. I've got my winbox dual booting XP and ME so i can easily just switch over to ME when i want to use SEQ, but my hardware works much better with win XP than it does with ME, so i prefer to use XP.

I don't always like to have my linux box running.. and wouldn't want it running all the while i want to be on the internet, its old and loud.