[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [ossig] SUID problems



Sounds pretty screwed up, yes.
wvdial is nice, but screws up the rest. Reliable, though. Which makes it
astonishing it wouldn't work.
First thing next, screwing up much less: minicom
Just issue an ATZ and it must come back with OK.
Try ATI0, ATI1, etc, and the modem identifies itself.
If this works, try ATDT1515 and it should dial to tmnet, asking for a
userid.
If all of this doesn't, the modem needs urgent replacement.
If it does all of this, it's a config problem.

Uwe

On Tue, 2003-06-24 at 09:44, Venantius Kumar wrote:
> I did that last night.  But still problem persists.  I can dial out ok i.e.
> "connect start" works.  But when I do a "connect stop" it just hangs.
> Meaning it is in a state of "hanging up" the connection.  Same thing with
> windows clients.
> 
> Windows clients are a shareware, where not more than 3 copies are allowed to
> be installed.  So a cunning way (suggested by someone -- I can't remember
> who) is to map the network drive where a single copy of wconnect is
> installed and run off it for all the clients!!!
> 
> Well another funny thing...when I "ifup ppp0", I find that the scripts don't
> read /etc/ppp/options file.  I am using wvdial as a chat replacement, which
> I find very easy to configure and maintain (never got the hang of using
> chat!!!).  In an effort to start pppd directly without going through any
> ifup srcipts I found that when wvdial starts (this way its reading off
> options file) it cannot find the device (/dev/modem -->/dev/ttyS0) or the
> init string doesn't go to the device!!!
> 
> Screwed up pretty well I guess!  More likely that its lack of my knowledge!
> 
> 
> regards,
> Venantius.
> 
> 
> ----- Original Message -----
> From: "Ditesh Kumar" <ditesh@ameba6.com>
> To: <ossig@mncc.com.my>
> Sent: Monday, June 23, 2003 5:37 PM
> Subject: Re: [ossig] SUID problems
> 
> 
> > I have used alt-connect before. Since you can't remember what really
> > happened, perhaps you could wipe out /etc/connect and do the make
> > install and run the add-provider script again? I have screwed up before
> > and reinstallation usually solves the problems.
> >
> > PS: (You mean this alt+connect right:
> > http://freespace.virgin.net/fuchsia.groan/software/ ? I believe the
> > windows client is shareware.)
> >
> > On Mon, 2003-06-23 at 17:10, Venantius Kumar wrote:
> > > Actually its more like dial-on-demand kind of feature.  All my users are
> on
> > > Win98 machines.  They can telnet into the Linux server to initiate the
> > > dialing.  So when One person have initiated it, the other can just
> surf --
> > > internet connection sharing.
> > >
> > > I have experimenting with a solution called "alt-connect".  It worked
> pretty
> > > well, until recently I did something (which I can't remember what) that
> > > broke the whole thing pretty bad.  So now one of the us administrators
> have
> > > to "ifup ppp0" and "ifdown ppp0" manually on request!!!
> > >
> > > Since alt-connect is an open source project (including Windows client),
> I
> > > have asked its maintainer Peter Miller for help.  He is now studying the
> log
> > > files for the problem.  so meanwhile I want to have a temp solution.  I
> have
> > > done this before on MDK 8.2 before.
> > >
> > > So thats the story behind all this.  Any help...suggestions?
> >
> >
> > --
> > Ditesh Kumar
> > Ameba6 Solutions Sdn. Bhd.
> >
> > "Anyone who considers arithmetical methods of producing random digits
> > is, of course, in a state of sin." - John Von Neumann
> >
> >
> > ------------------------------------------------------------
> > To unsubscribe: send mail to ossig-request@mncc.com.my
> > with "unsubscribe ossig" in the body of the message
> >
> >
> 
> 
> ------------------------------------------------------------
> To unsubscribe: send mail to ossig-request@mncc.com.my
> with "unsubscribe ossig" in the body of the message



------------------------------------------------------------
To unsubscribe: send mail to ossig-request@mncc.com.my
with "unsubscribe ossig" in the body of the message