Hello.
jayakumar_i wrote:
> By way of introduction, we are a company that specialises in
> placements in niche technology and non technology related areas.
[snip]
> We have many active compnaies / openings that could be of your
> interest. For enahncement in your career and explore new
> oppurtunities kindly mail me your resume at vishal@...
This is not a mailing list for discussing career opportunities. It is a
mailing list for discussing libsocket and related subjects. Please do not
post job adverts here.
The mailing list's scope is described here:
http://groups.yahoo.com/group/libsocket/
Regards,
--
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]
By way of introduction, we are a company that specialises in
placements in niche technology and non technology related areas.
Because we cater to niche and specialised requirements we have among
our clients some of leading companies in India and abroad.
A number of leading companies like Lehman Brothers (HK/Japan), DSP
Merrill Lynch Ltd., ABN AMRO, Hindustan Lever Ltd., Asian Paints, IBM
Global Services, WebTek, Digital (Europe), Mphasis, I2 Technologies,
Talisma Corporation, Sapient, I-flex, Planetasia (Europe Positions),
Citibank, Cambridge Technology Partners, California Software,
Schlumberger, Hughes tele.com , Reliance have used our services to
fullfill their recruitment needs.
We also have an offline careers desk in Mumbai that works like a
placement agency and uses the site to increase its network.
We have many active compnaies / openings that could be of your
interest. For enahncement in your career and explore new
oppurtunities kindly mail me your resume at vishal@...
In case you know any of your friends who may be interested for the
same please send us their resume .
Looking forward to your email at the earliest.
We thank you for spending the time to go through this mail .
Regards,
Mr. Vishal Arora
Email: vishal@...
**********************************************************************
**************************
NEW POSITIONS CURRENTLY ON :
1. Position of PM (Systems Integration)
Project Managers with 7 -8yrs of experience.
Technical knowledge and hands on experience in handling Large
Networking and system integration, Platform projects .
Exposure to working on Cisco products & Sun platform
Competencies reqd:
* Good project & people management skills
* Good Customer Interaction skills
* Excellent presentation & communication skills .
These postions are based in the all metros & Bangalore. Candidates
should be open to relocate.
======================================================================
===========================
2. Storage Consultants-
Experience- 5-6 yrs
Job Description-
Exposure consultanting / Technical support on practical storage
solutions
in implementation , configuration of Sun, Hitachi, EMC, NetApps,
Good communication & presentation skills must.
======================================================================
===========================
3. EMS Consultants-
Experience-6-8 yrs
Job Description-
Consulting skills in Unicenter ( exposure on Brite Store is a must )
TNG,
HP-OV, Tivoli, Remedy Skills, Micromuse.
======================================================================
===========================
4. Technical support- iPlanet
Experience- 4yrs
Job Description-
-Good hands on exposure on installation/configuration
- Database skills
- Unix Skills
======================================================================
===========================
5 . Principal Consultants
Job Responsibilities :
The company needs Principal Consultants in the areas of Finance-
Banking, Securities & Insurance, Manufacturing-Process & Discrete,
Logistics & Distribution.
Responsibilities:
- Responsible for delivering consulting assignments in a defined
practice framework.
- Prepare consulting practices in specific domain.
- Help in creating, supporting consulting business along with
vertical heads and business sales group in a particular domain(s).
- Independently create consulting opportunities.
- Should act as Principal Consultant for 2-3 consulting assignments
at a time.
Educational Requirements: BE/MBA
Work Experience Desired:
Experience:8+ years of experience
- Should understand the domain business processes very well.
- Analytical skills wrt business process analysis, efficiencies,
enhancements and operational expertise.(Finance-Banking, Securities &
Insurance, Manufacturing-Process & Discrete, logistics &
Distribution)
- Should be expertise in business process re-engineering techniques,
change management techniques and financial modeling.
- Should be focussed on dependency, risk management and quality
drive.
- Should ideally be from a consulting background
Other Skills Desired:
- Excellence in presentation and analysis.
- Good communication skills.
======================================================================
===========================
Best underground information print now !!!
1. Guaranteed Unsecured Credit Cards up to $50,000 Regardless of Bad Credit.
We can show you how and where you can obtain unsecured Gold and Platinum credit
cards with credits limits up to $50,000 per card! Regardless of your past
credit history!
You are guaranteed to receive at least 2 unsecured credit cards of up to $20,000
through
our exclusive list. The secret to getting the credit you deserve is knowing how
and where
to look!
__No credit checks! No employment check!
__No credit turndowns! No credit, Bad credit!
__Some with as low as 0% APR for the life of the card!
__Guaranteed approval!
2. Satellite TV/RCA Dish Descrambler
Complete plans for building home satellite TV descrambler. For access to a clear
reception of pay TV signals on home satellite dish! It does not require any
additional
equipment! Complete PC board template & instructions! This also includes a
manual for
accessing the RCA/DSS satellite dish. All the latest information for doing it
right.
3. Free Long Distance
Learn how some people make long distance calls to other countries at no cost!
The
information in these reports explains everything to call other countries for
free! Country
codes, city codes, overseas sender codes!
4. Underground Guide to Utility Meters
The illustrated guide to gas, water & electric meters! We show you in detail
methods
many people use to stop, slow down, even reverse all three types! This
underground
manual is one of our most popular items! Complete illustrated techniques and
easy to do.
Shows how to defeat all major brands & models of gas, water & electric meters.
5. X-Ray Envelope Spray
Have you ever wanted to read the contents of an envelope without opening it?
Many
government and other organizations use what is known as X-Ray Envelope Spray to
do
this! An envelope is sprayed with this secret chemical and it becomes
translucent for a
short period of time, which allows the contents to be read without opening.
Private supply
houses sell small cans of this aerosol spray for up to $50 a can! The spray is
actually a
commonly available item found in major grocery and discount stores. No
modification of
the spray is needed, as it is ready to use as X-Ray Envelope Spray and sells for
about
$1.99 in retail stores!
6. How to Find Anyone and Obtain Unlisted Phone Numbers
Tired of getting the wrong number? Stop looking! We can help! We'll show you how
to
get the unlisted phone number of anyone. No one can hide now! Simple. Skip
tracers use
these tricks. We also include everything you need to know about finding missing
people
or loved ones from the comfort of your home. Why pay money when you can do it
yourself?
7. Radar Zapper
This simply technique converts existing radar detectors into a device that will
jam police
radar. This device sends false readings back to the police radar! Works on
virtually all
detectors and easy to use!
8. Untraceable E-Mail
How to send totally anonymous and untraceable E-mail. We're not talking about
those
generic Yahoo! Accounts -- this is the real McCoy, anonymous email. Everything
explained. Absolutely untraceable.
9. Scan-Tron Genius
Here at last!! This very controversial report describes in detail how any
student can easily
defeat Scan-Tron test readers to pass a test even though he does not know the
answer!
This simple method will fool the scan reader into thinking you answered
correctly! No
tools needed. Completely tested. You won't believe how simple this method is!
10. Bad Credit Cleaning Manual
Simple ways to restore bad credit rating to A++. Many methods presented here -
some
legal & some "not so legal".
11. Pass Drug Tests
Don't use drugs! However, many innocent people are victims of drug testing. Some
over
the counter medicine can trigger false results & cost you your job. Proven
methods to
beat drug tests. We show you how to build a simple device that can fool the
best! Protect
yourself & your job, even if you don't use drugs.
12.Cable TV Decoders
How some people get cable TV and turn their converter box into "full service"
mode.
This is the latest information. Also, how to build your own "snooper stopper"
for pennies.
Prevents cable companies from spying on you.
13. Outsmart Lie Detector Tests
Hundreds of thousands of people in this country are wrongfully fired or not
hired simply
because they did not pass the lie detector test even though they've done nothing
wrong!
Read drugless methods to help pass whether you are lying or not! A valuable tool
for any
job seeker. Don't be harassed by your employer ever again. Tested and proven.
14. Lock-picks & Lock-picking.
Why buy expensive lock-picks we'll show you how to make your own professional
lock-
picks. Exact detailed drawings & construction techniques! This is perhaps the
easiest to
understand course ever published. You won't believe how easy it is to make these
tools!
We also show you how a basic lock works & how they are picked. This publication
is
complete with detailed drawings & illustrations.
ORDER NOW!!!
That's 14 products, all for just $19.95. CA residents please add sales Tax
We accept: Visa, MasterCard, American Express, Cash, Personal Checks, Money
Orders
and Cashiers Checks.
Print the following form and fax it to: 1 323 436 6271
Or mail it to:
Info 4 Edu Only
1300 N. Cahuenga Blvd # 362
Los Angeles, CA 90028
You must include a Primary and secondary E-mail address, as we will be emailing
you all
the reports as soon as we receive your payment.
Please Print Clearly
Primary Email Address: ___________________________________
Secondary Email Address: _________________________________
Credit Card Information:
*Card Type: [ ] Visa [ ] MasterCard [ ] Amex
*Credit Card Number: ______________________________________
*Expiration Date: ____________
Name : _________________________________________________
Address: ________________________________________________
State/Province & Postal Code : ______________________________
If you are paying by check or money order make it payable to: Info 4 Edu Only
DISCLAIMER: Please note that this information is being provided for educational
purposes only. The information itself is legal, while the usage of such
information may be
illegal. We do not advocate unauthorized use or theft of any services. If in
doubt, check
your local laws and act accordingly.
NOTE: All of the publications are Copyright 2001 by Info 4 Edu Only. We
aggressively
protect our copyrights and will seek prosecution of any website, web-master, web
hosting
service or anyone else that is in violation of US & International Copyright
Laws.
To be opt out please email optout1234@...
4eb22be7279a5e6788c47cf6da72b832c535ef9
Hello.
rubikz@... wrote:
> I create a socket and put it into non blocking mode, then
> call connect(). The connect fails with this error message
> : <Operation not supported on endpoint EOPNOTSUPP>.
libsocket does not support non-blocking connect calls.
You must use blocking connect calls. You can switch the socket
into non-blocking mode, once you are connected.
Bye, Rich =]
Hi,
I create a socket and put it into non blocking mode, then
call connect().
The connect fails with this error message : <Operation
not supported on endpoint EOPNOTSUPP>.
After, i use select() to find when it is ready
(connected). But the socket will not select() as writable.
The program runs under Dos.
I succeed to connect to the server only with a socket
into blocking mode. Thus, the timeout is longer (1 or 2
minutes).
How can i do ?
Thanks
This is a short of my program :
int skan(rmt_host)
char rmt_host[100];
{
int r, err, retval;
fd_set a_tester;
struct timeval tv; /* valeur du time out */
int on=1, off=0, end=0;
s = socket(AF_INET, SOCK_STREAM, IPPROTO_TCP);
if (s < 0) {
printf("ERROR: socket() failed\n");
exit(0);
}
/*on= operation non bloquante */
err=ioctl(s,FIONBIO,&on);
if (err < 0) {
printf("ERROR\n");
exit(0);
}
addr.sin_family = AF_INET;
addr.sin_port = htons(PORT);
addr.sin_addr.s_addr = inet_addr(rmt_host);
r = connect(s,(struct sockaddr *) &addr, sizeof
(addr));
if (r==-1) {
perror("Socket en ecoute mais connection
impossible\n");
}
end=6;
while (end)
{
end--;
FD_ZERO (&a_tester);
FD_SET (s, &a_tester);
/* Attente de 2 secondes. */
tv.tv_sec =30;
tv.tv_usec = 100;
retval= select (s,NULL , &a_tester, NULL, &tv);
if (retval == 1)
printf("Socket prete en ecriture\n");
else {
printf("Limite temporelle atteinte\n");
end=0;
}
} /* fin while */
close(s);
if (r==-1) {
return (1 == 0);
}
return (1 == 1);
}
-------------------
L'e-mail gratuit pas comme les autres.
Pour créer votre adresse : http://www.nomade.fr/courrier/ouvrir.asp
NOMADE.FR, pourquoi chercher ailleurs ?
Bonjour!
"rubikz@..." wrote:
> The programm run ( OS windows 98) correctly on a
> computer with Djgpp installed.
> When i try to run it on a computer with no Djgpp
> installed, this message appears :
>
> Protocol not supported < EPROTONOSUPPORT >
Have you installed the socket extension on the computer that does not have
DJGPP? You need to run this program, to install it:
contrib/ls080/redist/sockvxd.exe
If you want to distribute your libsocket program, you will have to
distribute sockvxd.exe with it.
Hope that helps, bye,
--
Richard Dawe
http://www.phekda.freeserve.co.uk/richdawe/
Hi, i'm french so sorry for my english !
I created a server program and i compiled it with Djgpp
(gcc server.c -o server.exe -lsocket).
I use ls080.
The programm run ( OS windows 98) correctly on a
computer with Djgpp installed.
When i try to run it on a computer with no Djgpp
installed, this message appears :
Protocol not supported < EPROTONOSUPPORT >
int
main (void)
{
struct sockaddr_in sin;
struct sockaddr_in remote;
int sockfd, newfd;
size_t len;
int pl_len;
int ret;
memset ( &sin, 0, sizeof ( struct sockaddr_in ) );
sockfd = socket ( AF_INET, SOCK_STREAM, 0 );
sin.sin_family = AF_INET;
sin.sin_addr.s_addr = NULL;
sin.sin_port = htons ( PORT );
/* création de la socket sockfd */
if((sockfd=socket(AF_INET, SOCK_STREAM, 0)) == -1) {
lsck_perror("socket");
exit(1);
}
...
Do you have an idea ?
Please contact me rubikz@...
Thanks
-------------------
L'e-mail gratuit pas comme les autres.
Pour créer votre adresse : http://www.nomade.fr/courrier/ouvrir.asp
NOMADE.FR, pourquoi chercher ailleurs ?
Hi, i'm french so sorry for my english !
I created a server program and i compiled it with Djgpp
(gcc server.c -o server.exe -lsocket).
I use ls080.
The programm run ( OS windows 98) correctly on a
computer with Djgpp installed.
When i try to run it on a computer with no Djgpp
installed, this message appears :
Protocol not supported < EPROTONOSUPPORT >
int
main (void)
{
struct sockaddr_in sin;
struct sockaddr_in remote;
int sockfd, newfd;
size_t len;
int pl_len;
int ret;
memset ( &sin, 0, sizeof ( struct sockaddr_in ) );
sockfd = socket ( AF_INET, SOCK_STREAM, 0 );
sin.sin_family = AF_INET;
sin.sin_addr.s_addr = NULL;
sin.sin_port = htons ( PORT );
/* création de la socket sockfd */
if((sockfd=socket(AF_INET, SOCK_STREAM, 0)) == -1) {
lsck_perror("socket");
exit(1);
}
...
Do you have an idea ?
Please contact me rubikz@...
Thanks
-------------------
L'e-mail gratuit pas comme les autres.
Pour créer votre adresse : http://www.nomade.fr/courrier/ouvrir.asp
NOMADE.FR, pourquoi chercher ailleurs ?
Hello.
mahmoud abotaleb wrote:
> if you have a client and server that they use HTTP1.1 protocol
> i read HTTP1.1 and knew its rules BUT i need some implementation of
> that using programming language C++ or VC++
Hmmm, it sounds like you have some homework to do. Anyway, you can find
lots of source code for these things on the web. You may to look at some
web server sources - e.g. Apache, Boa - and some web client sources - e.g.
Lynx or links.
Bye,
--
Richard Dawe
http://www.phekda.freeserve.co.uk/richdawe/
hi...
if you have a client and server that they use HTTP1.1 protocol
i read HTTP1.1 and knew its rules BUT i need some implementation of
that using programming language C++ or VC++
first (BY using C++ or VC++)
how can i know the header section of the message
and the body section of the same message..
second(using C++ or VC++)
how can you make the parser (( i.e knowing header parameters
such as media type , content encoding, transefer coding
,...etc))
third (using C++or VC++)
HOW CAN I MANIPULATE THE BODY ALONE WITHOUT CHANGING
THE HEADER SECTION ...
i.e cut the message into tow new sections first section is the header
the second is the body then i can manipulate body alone
forth (using C++ or VC++)
how can reassemble the body and the header again...
PLZZZZZZ
if any one can help me
give me a sample cde to do that...
MANY THANKS.....
(-: :-)
____________________________________________________
Cannot read this message in arabic?
Join the EGYPTIAN mail community @ http://www.masrawy.com
Hello.
libsocket appears to work with SOCK.VXD on Windows ME. There appears to be
a bug in the host name parsing though. Perhaps I fixed this in the copy of
my CVS on the development page - I can't remember.
Attached is the output from 'diag'. I changed the domain name to
'domain.name'. Notice that the host name appears as '.domain.name'.
Bye, Rich =]
Damian Yerrick wrote:
> Here's diag > diag.txt:
>
> libsocket Diagnostic Program
>
> Copyright (C) 1997, 1998 by Indrek Mandre, 1997-2000 by Richard Dawe
> libsocket version 0.8.0
>
> Host name: '.domain.name'
> Domain name: 'domain.name'
> Configuration directory: '(null)'
>
> DNS servers: 137.112.5.28 137.112.4.197 137.112.4.196
>
> Interface Coda SOCK.VXD
> Address 127.0.0.1 netmask 255.0.0.0
> ---
> Address 137.112.207.28 netmask 255.255.255.0 gateway 137.112.207.50
> DNS 1 137.112.5.28
> DNS 2 137.112.4.197
> DNS 3 137.112.4.196
> Host name '.domain.name'
> Domain name '.domain.name'
> ---
>
> Interface Unix->mailslot
>
> Testing Internet domain (AF_INET) sockets...
> + SUPPORTED: stream type socket with default (0) protocol
> + SUPPORTED: stream type socket with TCP protocol
> + SUPPORTED: datagram type socket with default (0) protocol
> + SUPPORTED: datagram type socket with UDP protocol
> . Unsupported: everything else
>
> Testing Unix domain (AF_UNIX) sockets...
> + SUPPORTED: stream type socket with default (0) protocol
> + SUPPORTED: datagram type socket with default (0) protocol
> . Unsupported: everything else
>
> These should be meaningful error messages:
> strerror(): Address family not supported (EAFNOSUPPORT)
>
> > httpget retrieves a web page, given a URL, e.g.:
> >
> > httpget http://www.yahoo.com/
>
> httpget http://www.yahoo.com/
> displays some HTML and then freezes in the middle of the page,
> and Ctrl+C or Ctrl+Break does nothing.
--
Richard Dawe <richdawe@...> http://www.bigfoot.com/~richdawe/
"The soul is the mirror of an indestructible universe."
--- Gottfried W. Leibniz
>Has anyone had any experience with sock.vxd to share?
...
>sock.vxd part of the libsocket library. I would be interested if anyone else
>has been dong anything with sock.vxd. so that we could collaborate
>I'm not fond of the wsock2.vxd approach and the discussion of 'patching' the
>binary file ... well I cannot afford this
Don't know if it helps or not but at
http://www.sysinternals.com/
there are some VxD debugging programs you can download.
--
For information on any of the following check out my WEB site at:
http://www.csonline.net/bpaddock/
Chronic Pain Relief, Philadelphia Experiment, better Spelling via UNIFON
http://www.chipcenter.com/circuitcellar/crparciv.htmhttp://www.uCOS-II.com
Hello.
Wojciech Ga³±zka wrote:
> Has anyone had any experience with sock.vxd to share?
> I checked the sources and the buglist and I'm going to take care of the
> coda sock.vxd part of the libsocket library. I would be interested if
> anyone else has been dong anything with sock.vxd. so that we could
> collaborate
Most of my knowledge is contained in the Coda SOCK.VXD
Pseudo-documentation:
http://www.phekda.freeserve.co.uk/richdawe/dl/csockvxd.htm
and the libsocket source code.
I did upload some modified SOCK.VXD sources to the dossock site. I tried
to fix a few of the problems, but did not have much success. I made some
modifications to the code to allow the same headers to be used in the VxD
or software using the VxD. Anyhow the dossock site is here, with a link to
the modified SOCK.VXD sources:
http://www.phekda.freeserve.co.uk/richdawe/dossock/
If you have any specific questions about SOCK.VXD, I can try to answer
them.
> I'm not fond of the wsock2.vxd approach and the discussion of 'patching'
> the binary file ... well I cannot afford this
Yes, I agree, this does not seem like a very user-friendly solution.
Distributing a modified version of WSOCK2.VXD is probably illegal.
Bye, Rich =]
--
Richard Dawe <richdawe@...> http://www.bigfoot.com/~richdawe/
"The soul is the mirror of an indestructible universe."
--- Gottfried W. Leibniz
Hi,
Has anyone had any experience with sock.vxd to share?
I checked the sources and the buglist and I'm going to take care of the coda
sock.vxd part of the libsocket library. I would be interested if anyone else
has been dong anything with sock.vxd. so that we could collaborate
I'm not fond of the wsock2.vxd approach and the discussion of 'patching' the
binary file ... well I cannot afford this
Wojciech Ga³±zka
MCSE, MCDBA
> ----------
> Od: Richard Dawe[SMTP:rich@...]
> Wys³ano: 10 lutego 2001 18:14
> Do: libsocket Mailing List
> DW: DJGPP newsgroup; dossock Mailing List
> Temat: CVS snapshot (2001-02-10) of libsocket uploaded
>
> Hello.
>
> I've just uploaded a snapshot of libsocket's CVS to the libsocket
> development page:
>
> http://www.phekda.freeserve.co.uk/richdawe/lsck/lsck_dev.htm#snapshots
>
> There's an announcement here:
>
> http://www.phekda.freeserve.co.uk/richdawe/lsck/lsck_new.htm
>
> This is aimed at the people who are interested in developing libsocket
> further. It has basic Winsock 2 support (send(), recv() don't work), which
> is need a lot of work. It's a bit of a hack right now.
>
> There is _no support_ for this version. It's a development release. If you
> want a stable release, please get libsocket 0.8.0 from the DJGPP archive -
> there are links here:
>
> http://www.phekda.freeserve.co.uk/richdawe/lsck/lsck_dl.htm
>
> Anyway, have fun, bye, Rich =]
>
> --
> Richard Dawe <richdawe@...> http://www.bigfoot.com/~richdawe/
>
> "The soul is the mirror of an indestructible universe."
> --- Gottfried W. Leibniz
>
Hello.
Alain wrote:
> I am comming to you to ask some advice. I need to have TCP
> just for sending messages between programs but in different
> platforms:
> - DOS (MS/DR/Free/...)
> - Dos-Box under Windows as long as this continues to exist
> - Windows native programs (using somthing like Delphi)
> - Linux native programs, using whatever becomes availabe
> Can someone please send me advice as to what should I turn
> my attentions to?
I'd recommend you read a book called "Unix Network Programming: Volume
One" by W. Richard Stevens. It's a classic book and it will help you a
lot. You could also start by reading Beej's tutorial - see
http://www.phekda.freeserve.co.uk/richdawe/lsck/lsck_lnk.htm for a link.
For working under DOS, you can use Watt-32 with DJGPP - see
http://www.bgnett.no/~giva/ . It also works with some other compilers.
Watt-32, libsocket and Linux have the BSD sockets API - socket(),
connect(), bind(), accept(), etc. Windows has Winsock, which has mostly
the same interface as BSD sockets, but there are some big differences. It
shouldn't be too hard to make in C a simple TCP/IP application build & run
on DOS, Windows and Linux with some #ifdef's and some portable
programming.
In fact, libraries exist for portable socket programming. I cannot think
of any right now, but there must be some on Freshmeat -
http://www.freshmeat.net/ .
I hope that answers your question. If not, please ask again.
Bye, Rich =]
--
Richard Dawe <richdawe@...> http://www.bigfoot.com/~richdawe/
"The soul is the mirror of an indestructible universe."
--- Gottfried W. Leibniz
Hi all,
I have just started studying TCP/IP for a project about one year fom now.
It makes me very sad the perspective of libsocket endig :((
I am comming to you to ask some advice. I need to have TCP
just for sending messages between programs but in different
platforms:
- DOS (MS/DR/Free/...)
- Dos-Box under Windows as long as this continues to exist
- Windows native programs (using somthing like Delphi)
- Linux native programs, using whatever becomes availabe
Can someone please send me advice as to what should I turn
my attentions to?
thanks
Alain M.
Hello.
Wojciech Galazka wrote:
> Ok, I got the idea. What is needed is a socket library that provides
> * TCP
> * UDP
> for socket() call
> that 's working under Win 9x/ME (= under Winsock 2.0)
Yes, exactly. AFAIK Windows ME implements its networking drivers as DLLs
rather VxDs. I suspect that libsocket will not work it.
Damian Yerrick, did you test libsocket with Windows ME? I sent you test
programs a while back, but got no response. Did you receive my test
programs?
> Ideally this library should rely on services provided by MS TCP/IP stack
> that comes with Windows
> so it implies either
> * wsock2.vxd
> * TDI API (coda.vxd)
> and IPv6 if Windows 9x/ME provides its own IPv6 stack
IPv6 is not available for Windows '9x. Microsoft is unlikely to do IPv6,
from what I've heard. An experimental IPv6 stack is available for Windows
NT, maybe Windows 2000 too (see http://www.research.microsoft.com/ and
follow links).
I think IPv6 can wait. It's not widely used (yet). Also, if we support
IPv6, then the DNS code will need a lot of work, since it does not support
IPv6-extensions to DNS.
> Direct access to lower levels of OSI layers (IP,ICMP,raw sockets) is not
> as much relevant at this moment
> How about select() and poll() ?
select() is already supported, but may be a bit buggy. I've never had
problems, but other people may have had problems with select() and dial-up
connections.
> I'll check the latest version of libsocket sources and the bug report to
> see if we can stay with wsock2.vxd and/or benefit from using coda.vxd
I'm not sure what you mean here. libsocket already uses Coda's SOCK.VXD to
work with Winsock 2. I have some work done for WSOCK2.VXD support in my
local CVS, but it needs work.
> The case with Windows NT is much clearer, once the CygWin team gets its
> version of Unix sockets to work we can make a simple stub library tthat
> calls that implementation.
How are they implementing Unix domain sockets? libsocket has a basic
implementation. It would be good if DJGPP & Cygwin could interoperate.
Bye,
--
Richard Dawe <richdawe@...> http://www.bigfoot.com/~richdawe/
"The soul is the mirror of an indestructible universe."
--- Gottfried W. Leibniz
Wojciech Galazka wrote:
>
> Eli Zaretskii wrote in a message
> <9791-Tue06Feb2001104746+0200-eliz@...>...
> >
> >I'd say that it needs to support Windows 9X and ME as its primary
> >target. Plain DOS already has a solution, and I'm guiessing that
> >making libsocket work on NT and W2K is an entirely different ball
> >game.
>
> Ok, I got the idea. What is needed is a socket library that provides
> * TCP
> * UDP
> for socket() call
> that 's working under Win 9x/ME (= under Winsock 2.0)
>
> Ideally this library should rely on services provided by MS TCP/IP stack
> that comes with Windows
> so it implies either
> * wsock2.vxd
> * TDI API (coda.vxd)
> and IPv6 if Windows 9x/ME provides its own IPv6 stack
> Direct access to lower levels of OSI layers (IP,ICMP,raw sockets) is not as
> much relevant at this moment
> How about select() and poll() ?
>
> I'll check the latest version of libsocket sources and the bug report to see
> if we can stay with wsock2.vxd
> and/or benefit from using coda.vxd
>
> The case with Windows NT is much clearer, once the CygWin team gets its
> version of Unix sockets to work
> we can make a simple stub library tthat calls that implementation.
--
Richard Dawe <richdawe@...> http://www.bigfoot.com/~richdawe/
"The soul is the mirror of an indestructible universe."
--- Gottfried W. Leibniz
Hello.
Matt Lewandowsky wrote:
[snip]
> However, a few of them will be relying on libsocket (or something
> similar including offspring...)
[snip]
> It'd be even better for someone like me who dual-boots and wants to run
> the same programs in both environments. Of course, I *could* compile in
> both environments, however, only having one binary is a huge plus in
> trying to distribute it.
[snip]
Yes, I agree. I tried to integrate with Watt-32, but gave up due to time
constraints. It seemed like it could work. One big problem would be
maintainance - feeding later Watt-32 changes into the modified version -
because there were a lot of changes (~5% of every file?).
> Is Wojciech Galazka offering to take over maintainership? I hope someone
> will, because I would like to see this project continue, and I
> unfortunately do not have the time or knowledge to properly maintain it
> myself.
I'm not sure who will maintain it yet.
> Richard, if someone else takes over maintainership, will you still
> be active in assisting development? You have put a lot of (excellent)
> work into this project, and it would be a grave loss if you left it
> behind completely.
I don't intend to leave libsocket behind completely. I just don't have
time to spend on it right now. Rather than let it wither and die due to
lack of attention, I'd like to hand it over to someone else. I'm trying to
concentrate on getting zippo, a package manager for DJGPP, ready for
release right now. I think this will be of benefit to DJGPP users.
I expect to be around giving advice, testing, contributing patches for as
long as libsocket exists. I'm happy to do this.
I just don't have time to do *all* libsocket research & development. I
estimate that 50% of my libsocket time was spent looking for hacks to get
libsocket to work _at all_. The other 50% was spent coding, writing
documentation, answering mail, etc. Not enough was spent testing.
Ideally several people would become involved in maintaining libsocket,
because doing all the work I mentioned is pretty demanding.
BTW thanks for the compliments. 8)
> Also, if no maintainer is found, it may be worth considering a second
> person holding a copy of your CVS repository, just in case something
> bizarre happens. Like, say you go on a year long trip around the world
> in a few years and someone decides to revive the project and can't reach
> you.
I'm trying to get all my current changes committed to my CVS. This will
have preliminary (read: hack-hack-hack!) Winsock 2 support and some
documentation fixes. Then I will upload a copy of the latest sources to
the libsocket development page. Hopefully that will be sometime this
weekend.
By "CVS repository" do you actually mean the libsocket part of my CVS
repository? Is it simple to extract that? Do I just tar/zip up the lsck
module subdirectory in my CVS root?
Thanks, bye,
--
Richard Dawe <richdawe@...> http://www.bigfoot.com/~richdawe/
"The soul is the mirror of an indestructible universe."
--- Gottfried W. Leibniz
OK, here are my thoughts:
I really find it sad that you're ending development of libsocket. I've been
quite busy since early December and am just finding time for my projects
again. However, a few of them will be relying on libsocket (or something
similar including offspring...) to allow TCP/IP from both DOS and Windows.
(I had mentioned trying to revive the WATTCP code in libsocket at one
point.) For example I have an IRC client in the works, but I need to do a
*lot* of screen handling stuff before I worry about actually trying to
connect to an IRC network... I think this is why there are so few good IRC
clients, let alone in DOS... ;) It'd be even better for someone like me who
dual-boots and wants to run the same programs in both environments. Of
course, I *could* compile in both environments, however, only having one
binary is a huge plus in trying to distribute it. (Kinda like the early
days of Win 95 when all 32 bit apps [pretty much] worked with Win 32S...)
Is Wojciech Galazka offering to take over maintainership? I hope someone
will, because I would like to see this project continue, and I
unfortunately do not have the time or knowledge to properly maintain it
myself. Richard, if someone else takes over maintainership, will you still
be active in assisting development? You have put a lot of (excellent) work
into this project, and it would be a grave loss if you left it behind
completely.
If libsocket is doomed to die a death of lack of maintainence, can anyone
suggest a replacement which would be suitable? Also, if no maintainer is
found, it may be worth considering a second person holding a copy of your
CVS repository, just in case something bizarre happens. Like, say you go on
a year long trip around the world in a few years and someone decides to
revive the project and can't reach you.
I agree that there's plenty of work to be done on libsocket, but it is well
worth doing.
--Matt
--
Matt Lewandowsky matt.l@... 877-225-7490
PGP Key ID: 0x1D3A6BA7 URL: http://www.greenviolet.net
(Web page only up when I'm online)
"... one of the main causes of the fall of the Roman Empire was that,
lacking zero, they had no way to indicate successful termination of
their C programs."
-- Robert Firth
Hello.
I'm CC'ing the libsocket list on my reply, since it's relevant.
Wojciech Galazka wrote:
[snip]
> Since the mission is to develop a BSD compliant networking library then
> I'd consider a entry level library that supports:
> * data link level
> * ARP / RARP
> * IP + fragmentation (both IPv4 & INv6)
> * ICMP
> * UDP
> * no TCP at the moment
> * limited ioctls
> * no selec()t, pool() (oh no , perhaps could anyone suggest select()
> under DOS ?)
> * no async i/o
I would suggest that support of the Unix98 specification's networking is
about all you need, from an applications point of view. TCP support is
IMHO required, if the library is to be any use. This is much more vital
than RARP/BOOTP/DHCP support for getting addressses.
ioctl support could just be FIONBIO, for flipping into non-blocking mode,
since not much else is used. select() is probably also a requirement.
DJGPP doesn't support multithreading, so select() is the only the real way
of supporting multiple connections in a server.
IPv6 support is probably an ambitious aim, since it's still changing. BTW
I don't think the concept of fragmentation exists in IPv6 as it does in
IPv4. I think path MTU discovery is always used. All network types have to
support minimum MTU packets (1280 bytes, if memory servers), so senders
can always fall back to that packet size.
> Dave took the top-down approach, that is with wsock.vxd he got TCP and
> UDP protocols and tried to go down to IP which is almost impossible
> under Windows as most of the stack inrternals are undocumented
> I'd opt for quite the opposite direction
Dave is my brother. ;) I think you mean "Dawe", my last name. 8)
Going down to IP has never been an option. ICMP echo ("ping") would be
possible, by writing a helper application that uses the ping DLL. It never
seemed that important, though.
Writing it from the bottom only makes sense on DOS, where you have direct
hardware access. I remember you suggested porting the BSD stack a while
ago. That would give you a TCP/IP stack more advanced than Watt-32,
because FreeBSD's stack currently has support for IPv4, IPv6, IPSec (AH
and ESP). I'm not sure how simple it would be to port the IPSec facilities
though.
> PS Could anyone, please, forward this to the dossock list, I can post at
> the usenet only now
Yes, done. I sent it to the libsocket list too, so that this reply makes
sense.
Bye,
--
Richard Dawe <richdawe@...> http://www.bigfoot.com/~richdawe/
"The soul is the mirror of an indestructible universe."
--- Gottfried W. Leibniz
Wojciech Galazka wrote:
>
> Richard Dawe nwrote in a message
> <3A745502.497CA8DF@...>...
> >Hello.
> >
> >As the title suggests, I am ending development of libsocket. I no longer
> >have the time, energy or interest to keep on developing libsocket to a
> >good standard. It's a bit sad, because I've learnt a lot since I took over
> >maintainership from Indrek Mandre.
> >
> Hi,
>
> I'd like to hear how libsocket users would like this library to be targeted
> at? Which operating system
> * Windows NT DOS-box - Cygwin is perhaps a better approach?
> * Windows 9x/ME - ?
> * plain DOS ?
>
> Unless I'd grab more information
> *where is one willing to use libsocket
> * what are the 'must have' features of this library and which ones are only
> 'nice to have'?
> it's very difficult to make this library 'well and alive'. This is because
> one needs to develop a reasonable plan first.
> For what seemed to me as a simple task - to provide long file name API to
> DJGPP under Windows NT - took me
> almost a year. most of that time spent on testing and making the piece of
> code 'compatible' with Microsoft's
> So I assume it may take at least a year as well to come up with something
> robust enough to make it useful
> when it comes to libsocket
>
> Since the mission is to develop a BSD compliant networking library then I'd
> consider a entry level library that
> supports:
> * data link level
> * ARP / RARP
> * IP + fragmentation (both IPv4 & INv6)
> * ICMP
> * UDP
> * no TCP at the moment
> * limited ioctls
> * no selec()t, pool() (oh no , perhaps could anyone suggest select() under
> DOS ?)
> * no async i/o
>
> Dave took the top-down approach, that is with wsock.vxd he got TCP and UDP
> protocols and tried to go down to IP which is almost impossible under
> Windows as most of the stack inrternals are undocumented
> I'd opt for quite the opposite direction
>
> PS
> Could anyone, please, forward this to the dossock list, I can post at the
> usenet only now
--
Richard Dawe <richdawe@...> http://www.bigfoot.com/~richdawe/
"The soul is the mirror of an indestructible universe."
--- Gottfried W. Leibniz
Hello.
As the title suggests, I am ending development of libsocket. I no longer
have the time, energy or interest to keep on developing libsocket to a
good standard. It's a bit sad, because I've learnt a lot since I took over
maintainership from Indrek Mandre.
I did make a little progress towards proper Winsock 2 support (using
WSOCK2.VXD) at the end of December. If anyone would like to take over
maintainership, please mail me and I'd be happy to discuss it and send you
my current source tree from my personal CVS.
Anyway, thanks for the help & usage of libsocket over the years. I'm sorry
to end development, but libsocket's just too broken.
Bye,
--
Richard Dawe <richdawe@...> http://www.bigfoot.com/~richdawe/
"The soul is the mirror of an indestructible universe."
--- Gottfried W. Leibniz
Hello.
Tim Van Holder wrote:
> ZoneAlarm can't filter packets that are sent low-level through
> WinSock, as done by the CODA sock.vxd.
> I contacted them about this, and they said it was unlikely
> this behaviour would change anytime soon.
> I'm hoping that as soon as libsocket itself talks to wsock2.vxd,
> this problem will go away.
Well, I'm working on Winsock 2 support at the moment. Currently it can
create/destroy/connect, but send() and recv() don't work, because...wait
for it...there's a bug in wsock2.vxd! There is a fix for it - patching
wsock2.vxd - but I'm hoping there's a less drastic work around. I don't
fancy writing end-user install instructions for that.
As soon as I have a library with functional Winsock 2 support, I'll do an
alpha of 0.9.0. It'll need tidying up for release, since it's just a
hacked copy of the Winsock 1.x source currently. The wsock2.vxd interface
appears to be only a little different from the wsock.vxd one.
> bpaddock wrote:
> > I still don't understand why this behavior is inconsistent.
> > What would be different where all other programs cause the
> > box to pop up, but the mailfilter/libsocket based one
> > doesn't?
This might be to do with the layer that libsocket interfaces to Windows's
networking. It depends where the ZoneAlarm hooks are in the networking
layers.
> Probably a limitation of Win32's NDIS filters (might be limited
> to Win9x as well, haven't tried it on NT, Win2K or WinMe yet).
Windows '9x VxDs don't work on NT or Windows 2000, so libsocket does not
work /at all/ there. I've heard that Windows ME uses PE-format drivers for
networking, rather VxDs - a shift towards the Windows Driver Model (WDM),
I guess. So I'm doubtful that libsocket works on ME.
Bye, Rich =]
--
Richard Dawe
[ mailto:richdawe@... | http://www.bigfoot.com/~richdawe/ ]
> ZL normally pops up with a box and says "Is it all right to
> allow this program Internet access?". However with
> mailfilter that box never pops up.
ZoneAlarm can't filter packets that are sent low-level through
WinSock, as done by the CODA sock.vxd.
I contacted them about this, and they said it was unlikely
this behaviour would change anytime soon.
I'm hoping that as soon as libsocket itself talks to wsock2.vxd,
this problem will go away.
> I still don't understand why this behavior is inconsistent.
> What would be different where all other programs cause the
> box to pop up, but the mailfilter/libsocket based one
> doesn't?
Probably a limitation of Win32's NDIS filters (might be limited
to Win9x as well, haven't tried it on NT, Win2K or WinMe yet).
> I'm going to see if I can convince ZL to allow mailfilter
> manually some how.
Good luck! I'm afraid this might be a Win32 limitation, so
ZoneLabs can't do much about it.
I know ZoneLabs was mentioned in the libsocket docs, but I
didn't make the connection because mailfilter ran all but
the first time.
I might have stumbled into a clue why my 'mailfilter'
program doesn't work the first time I use it, this popped up
this morning:
"The firewall has blocked Internet access to xxx.xxx.xxx.xxx
(POP3) from your computer [TCP Flags: S].
Time: 12/28/00 6:22:36"
The instructions from ZoneLabs is to permit zonelabs to
access the internet.
ZL normally pops up with a box and says "Is it all right to
allow this program Internet access?". However with
mailfilter that box never pops up.
I still don't understand why this behavior is inconsistent.
What would be different where all other programs cause the
box to pop up, but the mailfilter/libsocket based one
doesn't?
I'm going to see if I can convince ZL to allow mailfilter
manually some how.
>If you could send an excerpt of the socket-creating part of that source
>file to the list, then I could take a look at it. I don't have much time
>right now to do CVS checkouts, etc. as I'm trying to concentrate on fixing
>libsocket's Winsock 2 support.
/* PopAccount.cc - source file for the mailfilter program
* Copyright (c) 2000 Andreas Bauer <baueran@...>
[Lots of BIG snips to post to list here...]
*/
...
int PopAccount::check() {
char cmd[CMD_LENGTH];
string result;
int messages = 0, size = 0, connectError = 0, loginError = 0;
// Establish server connection and login
if ( ((connectError = connectSocket()) == 0) && ((loginError = login()) ==
0) ) {
// Store message headers
try {
if (sendCommand("STAT\r\n") <= 0) {
logout();
disconnectSocket();
return(CMD_STAT_FAILED);
}
else {
result = receiveResult();
...
// Logout and clean up connections
try {
logout();
disconnectSocket();
return 0;
}
catch(...) {
disconnectSocket();
throw;
}
}
...
// Creates a sockets and creates connection to the server
// Returns 0 on success, or DNS_LOOKUP_FAILURE and SOCKET_CONNECTION_FAILURE
on error
int PopAccount::connectSocket() {
struct sockaddr_in socketAddress;
struct hostent *myHost;
// Create socket and try to connect
if ( (mySocket = socket(PF_INET, SOCK_STREAM, 0)) < 0)
return(SOCKET_CONNECTION_FAILURE);
else {
myHost = gethostbyname(server.c_str());
if (!myHost)
return(DNS_LOOKUP_FAILURE);
else {
memset( (char*)&socketAddress, 0, sizeof(struct sockaddr_in) );
socketAddress.sin_family = AF_INET;
memcpy( &(socketAddress.sin_addr.s_addr), myHost->h_addr, myHost->h_length);
socketAddress.sin_port=htons(port);
if (connect(mySocket, (struct sockaddr*)&socketAddress, sizeof(struct
sockaddr)) < 0)
return(SOCKET_CONNECTION_FAILURE);
}
}
return 0;
}
// Closes the socket
int PopAccount::disconnectSocket() {
return (close(mySocket));
}
// Disconnects from the server
// Returns 0 on success, -1 otherwise
int PopAccount::logout() {
try {
if ( (sendCommand("QUIT\r\n") > 0) && (serverResult(receiveResult()) ==
TRUE) )
return 0;
else
return -1;
}
catch(...) {
throw;
}
}
// Sends a command to the socket (server)
// Returns bytes written on success, -1 otherwise
int PopAccount::sendCommand(string command) {
int error = 0;
if ( (error = write(mySocket, command.c_str(), strlen(command.c_str()))) ==
-1 )
return -1;
else
return error;
}
Hello.
bpaddock@... wrote:
> Richard Dawe wrote:
> > Perhaps you could debug the program and see exactly where the
> > problem occurs. A snippet of the code from the program would also
> > help, so that I can get some context on the problem. If there's lots
> > of code, maybe it would be better to send it as a private mail.
>
> If your referring to mailfilter you can check it out of CVS.
[snip]
> The relevant section of code is in popaccount.cc . However
> I can tell you this code works fine under Linux, BSD,
> Cygwin, and I've never changed the related code in any way
> for use with DJGPP/Libsocket (perhaps I need to tho?).
If you could send an excerpt of the socket-creating part of that source
file to the list, then I could take a look at it. I don't have much time
right now to do CVS checkouts, etc. as I'm trying to concentrate on fixing
libsocket's Winsock 2 support.
> It comes when you install Dial Up Networking 1.3 update from
> Microsoft.
Ah yes, thanks, I'll add that to the FAQ.
> >Thanks for the 'diag' output. It looks OK to me.
>
> Thats to bad, I think.
No, it's good, trust me. ;)
Bye, Rich =]
--
Richard Dawe
[ mailto:richdawe@... | http://www.bigfoot.com/~richdawe/ ]
>> 8.0 (What is on Simtel right now.)
>I think you mean 0.8.0.
Yes.
>> the first time after a reboot, and I've not gotten mail yet
>> (don't usually web surf before mail so don't know if that
>> would have same effect?).
>
>Perhaps you could debug the program and see exactly where the problem
>occurs. A snippet of the code from the program would also help, so that I
>can get some context on the problem. If there's lots of code, maybe it
>would be better to send it as a private mail.
If your referring to mailfilter you can check it out of CVS.
cvs -d:pserver:anonymous@...:/cvsroot/mailfilter
login
cvs -z3 -d:pserver:anonymous@...:/cvsroot/mailfilter
co mailfilter
The password is a carriage return.
The relevant section of code is in popaccount.cc . However
I can tell you this code works fine under Linux, BSD,
Cygwin, and I've never changed the related code in any way
for use with DJGPP/Libsocket (perhaps I need to tho?).
>> >5. Have you run sockvxd.exe to install the Winsock helper VxD?
>>
>> Yes I did. Would it have worked at all if I didn't?
>
>I thought Windows 95 OSR2 came with Winsock 1.1, not Winsock 2. My old
>computer had Windows 95 OSR2 on and I could use libsocket without the
>helper. It's likely that you've installed some software that included
>Winsock 2.
It comes when you install Dial Up Networking 1.3 update from
Microsoft.
>Thanks for the 'diag' output. It looks OK to me.
Thats to bad, I think.
>Bye, Rich =]
Happy Holidays.
--
For information on any of the following check out my WEB site at:
http://www.csonline.net/bpaddock/
Chronic Pain Relief, Philadelphia Experiment, better Spelling via UNIFON
http://www.chipcenter.com/circuitcellar/crparciv.htmhttp://www.uCOS-II.com