[S.u.S.E. Linux] Repost: ipfwadm ? (no response the 1st time)
Hey guys, I know this has probably been asked before, but I have been unable to find the threads on this particular question. Where is the best location, SuSE 5.2, to place my rules for masq., so it will be done automatically at boot time? At the moment, I am having to do it manually. Thanks, Danny kepe@home.com -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
How about creating a file in rc#.d called S99local and put your statements in there. This file will be the last file executed on boot up. rc#.d is either rc2.d or rc3.d . Later Lach On Tue, 26 May 1998, Danny Kephart wrote:
Hey guys, I know this has probably been asked before, but I have been unable to find the threads on this particular question.
Where is the best location, SuSE 5.2, to place my rules for masq., so it will be done automatically at boot time? At the moment, I am having to do it manually.
Thanks, Danny kepe@home.com -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
On Tue, 26 May 1998, Danny Kephart wrote:
Where is the best location, SuSE 5.2, to place my rules for masq., so it will be done automatically at boot time? At the moment, I am having to do it manually.
In /etc/rc.config, configure the 'MSQ' variables. Here's mine: MSQ_START="yes" MSQ_NETWORKS="192.168.1.0/24" MSQ_DEV="ppp0" #dial-up modem Internet connection MSQ_MODULES="ip_masq_ftp ip_masq_irc" Masquerading is then initiated in the script: /sbin/init.d/ipfwadm. You can customize it with additional rules. Dwight -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Dwight Johnson wrote:
On Tue, 26 May 1998, Danny Kephart wrote:
Where is the best location, SuSE 5.2, to place my rules for masq., so it will be done automatically at boot time? At the moment, I am having to do it manually.
In /etc/rc.config, configure the 'MSQ' variables. Here's mine:
MSQ_START="yes" MSQ_NETWORKS="192.168.1.0/24" MSQ_DEV="ppp0" #dial-up modem Internet connection MSQ_MODULES="ip_masq_ftp ip_masq_irc"
Masquerading is then initiated in the script: /sbin/init.d/ipfwadm. You can customize it with additional rules.
Dwight
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Mine is setup similarly: MSQ_START="yes" MSQ_NETWORKS="192.168.1.0/24" MSQ_DEV="eth0" MSQ_MODULES="ip_masq_cuseeme ip_masq_ftp ip_masq_irc ip_masq_quake ip_masq_raudio ip_masq_vdolive" but until I physically type: ipfwadm -F -p deny ipfwadm -F -a m -S 192.168.1.0/24 -D 0.0.0.0/0 my other machine just sits there. I will try your suggestion of customizing the ipfwadm script. Thanks -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
At 06:37 AM 5/27/98 -0500, you wrote:
Dwight Johnson wrote:
On Tue, 26 May 1998, Danny Kephart wrote:
Where is the best location, SuSE 5.2, to place my rules for masq., so it will be done automatically at boot time? At the moment, I am having to do it manually.
In /etc/rc.config, configure the 'MSQ' variables. Here's mine:
MSQ_START="yes" MSQ_NETWORKS="192.168.1.0/24" MSQ_DEV="ppp0" #dial-up modem Internet connection MSQ_MODULES="ip_masq_ftp ip_masq_irc"
Masquerading is then initiated in the script: /sbin/init.d/ipfwadm. You can customize it with additional rules.
Dwight
Mine is setup similarly:
MSQ_START="yes" MSQ_NETWORKS="192.168.1.0/24" MSQ_DEV="eth0" MSQ_MODULES="ip_masq_cuseeme ip_masq_ftp ip_masq_irc ip_masq_quake ip_masq_raudio ip_masq_vdolive"
but until I physically type:
ipfwadm -F -p deny ipfwadm -F -a m -S 192.168.1.0/24 -D 0.0.0.0/0
my other machine just sits there. I will try your suggestion of customizing the ipfwadm script. Thanks
Have you picked up the script from <A HREF="http://www.suse.de/Support/sdb_e/firewall.html"><A HREF="http://www.suse.de/Support/sdb_e/firewall.html</A">http://www.suse.de/Support/sdb_e/firewall.html. Seems like I was having similar problems until I found this document. -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
On Wed, 27 May 1998, Danny Kephart wrote:
Dwight Johnson wrote:
On Tue, 26 May 1998, Danny Kephart wrote:
Where is the best location, SuSE 5.2, to place my rules for masq., so it will be done automatically at boot time? At the moment, I am having to do it manually.
In /etc/rc.config, configure the 'MSQ' variables. Here's mine:
MSQ_START="yes" MSQ_NETWORKS="192.168.1.0/24" MSQ_DEV="ppp0" #dial-up modem Internet connection MSQ_MODULES="ip_masq_ftp ip_masq_irc"
Masquerading is then initiated in the script: /sbin/init.d/ipfwadm. You can customize it with additional rules.
Mine is setup similarly:
MSQ_START="yes" MSQ_NETWORKS="192.168.1.0/24" MSQ_DEV="eth0" MSQ_MODULES="ip_masq_cuseeme ip_masq_ftp ip_masq_irc ip_masq_quake ip_masq_raudio ip_masq_vdolive"
It seems similar, but your config: MSQ_DEV="eth0" makes it quite different. What is the physical device that is actually connecting you to the Internet? In my case, it is my modem (ppp0). You say you go to the Internet through 'eth0'. I doubt it. Dwight -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
At 08:14 AM 98-05-27 -0700, you wrote:
On Wed, 27 May 1998, Danny Kephart wrote:
... stuff deleted ...
MSQ_DEV="eth0"
makes it quite different. What is the physical device that is actually connecting you to the Internet? In my case, it is my modem (ppp0). You say you go to the Internet through 'eth0'. I doubt it.
eth0 hmmm. Seems like the machine is trying to access the Internet thru some kind of dial up router on the same ethernet (I have a setup with Webramp M3). If that's true then the dial up router needs to do all the masquarading stuff. just a thought. -- Arun Khan -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Arun K. Khan wrote:
At 08:14 AM 98-05-27 -0700, you wrote:
On Wed, 27 May 1998, Danny Kephart wrote:
... stuff deleted ...
MSQ_DEV="eth0"
makes it quite different. What is the physical device that is actually connecting you to the Internet? In my case, it is my modem (ppp0). You say you go to the Internet through 'eth0'. I doubt it.
eth0 hmmm. Seems like the machine is trying to access the Internet thru some kind of dial up router on the same ethernet (I have a setup with Webramp M3). If that's true then the dial up router needs to do all the masquarading stuff. just a thought.
-- Arun Khan -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
I use a cable modem, so I do not have any dial up programs on the system. The cable modem uses a ethernet card (eth0) to access the internet. I also have another card (eth1) which attaches via a hub to a M$ box.The /sbin/init.d/firewall script was the problem (I still don't understand that) but it is functioning properly now. Danny kepe@home.com -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
On Wed, 27 May 1998, Danny Kephart wrote:
Mine is setup similarly:
MSQ_START="yes" MSQ_NETWORKS="192.168.1.0/24" MSQ_DEV="eth0" MSQ_MODULES="ip_masq_cuseeme ip_masq_ftp ip_masq_irc ip_masq_quake ip_masq_raudio ip_masq_vdolive"
It seems similar, but your config:
MSQ_DEV="eth0"
makes it quite different. What is the physical device that is actually connecting you to the Internet? In my case, it is my modem (ppp0). You say you go to the Internet through 'eth0'. I doubt it.
Dwight
Dwight, You are right. I use a cable modem which uses a 3c900 Boomerang card (eth0). On the other side of the network, I have a 3c509 card (eth1,192.168.1.10) which is used for the internal network (consisting of my Linux box and a M$ box. What I meant was that everything was in place to work, it just wasn't happening the way I thought it should. I took Kyles advice, downed the script as suggested, and BINGO---masq. on boot. Thanks to all (Kyle and Dwight) who assisted in the solution. Danny Kephart kepe@home.com -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
On Wed, 27 May 1998, Danny Kephart wrote:
On Wed, 27 May 1998, Danny Kephart wrote:
Mine is setup similarly:
MSQ_START="yes" MSQ_NETWORKS="192.168.1.0/24" MSQ_DEV="eth0" MSQ_MODULES="ip_masq_cuseeme ip_masq_ftp ip_masq_irc ip_masq_quake ip_masq_raudio ip_masq_vdolive"
... I use a cable modem which uses a 3c900 Boomerang card (eth0). On the other side of the network, I have a 3c509 card (eth1,192.168.1.10) which is used for the internal network (consisting of my Linux box and a M$ box. What I meant was that everything was in place to work, it just wasn't happening the way I thought it should.
I took Kyles advice, downed the script as suggested, and BINGO---masq. on boot.
So, why doesn't the original work? The main difference between the scripts is the original has the '-W {$MSQ_DEV}' parameter. Dwight -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Dwight Johnson wrote: <snip>
... I use a cable modem which uses a 3c900 Boomerang card (eth0). On the other side of the network, I have a 3c509 card (eth1,192.168.1.10) which is used for the internal network (consisting of my Linux box and a M$ box. What I meant was that everything was in place to work, it just wasn't happening the way I thought it should.
I took Kyles advice, downed the script as suggested, and BINGO---masq. on boot.
So, why doesn't the original work? The main difference between the scripts is the original has the '-W {$MSQ_DEV}' parameter.
Dwight
I have no idea. All I did was replace the /sbin/init.d/firewall with the one from the website, changed the 192.168.1.0 (IP) to 192.168.1.10 . It fired up right away, with no problems at all. Weird, huh? Danny kepe@home.com -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Danny Kephart wrote: <snip>
I have no idea. All I did was replace the /sbin/init.d/firewall with the one from the website, changed the 192.168.1.0 (IP) to 192.168.1.10 . It fired up right away, with no problems at all. Weird, huh?
Was it you, or someone else on this thread that said they used a WebRamp? I do believe WebRamp uses a default of xxx.xxx.1.0. Or am I off base here. Dana -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Danny Kephart wrote:
I have no idea. All I did was replace the /sbin/init.d/firewall with the one from the website, changed the 192.168.1.0 (IP) to 192.168.1.10 . It fired up right away, with no problems at all. Weird, huh?
If you're ethernet card is standard, the incompatibility must be in your pppd options? Are you using proxyarp? Would that (or any other options) make a difference? Dwight -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
At 09:03 PM 98-05-27 -0500, you wrote:
Danny Kephart wrote:
<snip>
I have no idea. All I did was replace the /sbin/init.d/firewall with the one from the website, changed the 192.168.1.0 (IP) to 192.168.1.10 . It fired up right away, with no problems at all. Weird, huh?
Was it you, or someone else on this thread that said they used a WebRamp? I do believe WebRamp uses a default of xxx.xxx.1.0. Or am I off base here.
Dana
Webramp M3 comes with a default IP (I don't recall the exact IP) but it can be changed to any other legitimate IP number thru a Win95 utility or via telnet into the box itself. HTH Arun Khan -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Dana J. Laude wrote:
Danny Kephart wrote:
<snip>
I have no idea. All I did was replace the /sbin/init.d/firewall with the one from the website, changed the 192.168.1.0 (IP) to 192.168.1.10 . It fired up right away, with no problems at all. Weird, huh?
Was it you, or someone else on this thread that said they used a WebRamp? I do believe WebRamp uses a default of xxx.xxx.1.0. Or am I off base here.
Dana
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
It wasn't me. I do recall something about webramp, but full memory eludes me at the moment. Anyone else remember, fully? Danny kepe@home.com -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Dwight Johnson wrote:
It seems similar, but your config:
MSQ_DEV="eth0"
makes it quite different. What is the physical device that is actually connecting you to the Internet? In my case, it is my modem (ppp0). You say you go to the Internet through 'eth0'. I doubt it.
Excuse me for putting my two cents in, but if you are running with two machines and using one modem, ie using one machine as a proxy, then it is quite possible to access the internet via "etho":-) That's what I'm doing here, but I'm using two different operating systems. I'm using my Linux box as the proxy server to connect to the internet and my win95 machine access the internet over the intranet:-) Now all I need to do is get dial on demand working so that someone doesn't always have to be on the internet in order for Win95 to access the net:-) -- cya l8r Leon McClatchey leonmcclatchey@homemail.com Party on Linux:-) -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
On Wed, 27 May 1998, Leon McClatchey wrote:
Now all I need to do is get dial on demand working so that someone doesn't always have to be on the internet in order for Win95 to access the net:-)
I am using ppp-2.3.3 rather than diald for this and I recommend it. You do have to compile ppp-2.3.3 from the sources and rebuild the kernel. At first this did not work when I first deinstalled 5.2 pppd and then installed ppp-2.3.3 with 'make install'. But then I reinstalled 5.2 pppd and did the 'make install' over the top of 5.2 pppd and it works fine. Here is my dial-on-demand script (uses PAP authentication): ----------- #!/bin/sh # PPP dial-on-demand DEVICE=ttyS1 #com2 or your serial port INTERVAL=$1 #Interval in seconds for 'idle disconnect'. I use 300. LOCAL=192.168.1.1 #This and REMOTE are replaced by your ISP REMOTE=208.200.249.3 # using options 'ipcp-accept-local/remote' USER=username PROVIDER=your_isp.com PROVIDER_NAME=Your ISPs Name PHONE=555-1234 #Your ISPs dial-up number echo Ready for $PROVIDER_NAME...$PHONE # noccp nobsdcomp nodeflate \ /usr/sbin/pppd demand $LOCAL:$REMOTE \ idle $INTERVAL \ ipcp-accept-local ipcp-accept-remote \ debug lock /dev/$DEVICE name $USER \ remotename $PROVIDER modem 38400 crtscts \ defaultroute asyncmap 0 mtu 1500 mru 1500 \ connect "/usr/sbin/chat -v \ TIMEOUT 3 \ ABORT '\nBUSY\r' \ ABORT '\nNO ANSWER\r' \ ABORT '\nRINGING\r\n\r\nRINGING\r' \ '' \rAT \ 'OK-+++\c-OK' ATH0 \ TIMEOUT 30 \ OK ATDT$PHONE \ CONNECT '\~' \ " & leep 5 route -n ------------ Dwight -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
At 08:59 PM 5/27/98 -0700, you wrote:
On Wed, 27 May 1998, Leon McClatchey wrote:
Now all I need to do is get dial on demand working so that someone doesn't always have to be on the internet in order for Win95 to access the net:-)
I am using ppp-2.3.3 rather than diald for this and I recommend it. You do have to compile ppp-2.3.3 from the sources and rebuild the kernel.
At first this did not work when I first deinstalled 5.2 pppd and then installed ppp-2.3.3 with 'make install'. But then I reinstalled 5.2 pppd and did the 'make install' over the top of 5.2 pppd and it works fine.
The diald setup is pretty cool. Just leave it running and whenever you start up netscape or any other tcp program on any computer on the network, it automagically dials up your ISP. It will also shutdown the connection for you after a set period of time or keep the connection alive depending on your preference. Recently, I set up dctrl. It keeps track of all your diald stats like up time, time til timeout, echos the connect script, it even charts how busy your modem is. I had some trouble setting up diald at first also. Be sure to check /usr/doc/packages/diald. There are some sample configuration files there. The man `diald-examples` (I think that was the name, if that isn't it check 'man diald' I know that it was referenced there) was also very useful. The biggest problem I had was with the preconfigured connect script that comes with diald. If I remember correctly, had to comment out a lot of it. If your interested in setting up diald and get hung up on the connect script let me know and I'll look at mine again. -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Kyle Edbauer wrote:
At 08:59 PM 5/27/98 -0700, you wrote:
On Wed, 27 May 1998, Leon McClatchey wrote:
Now all I need to do is get dial on demand working so that someone doesn't always have to be on the internet in order for Win95 to access the net:-)
The diald setup is pretty cool. Just leave it running and whenever you start up netscape or any other tcp program on any computer on the network, it automagically dials up your ISP. It will also shutdown the connection for you after a set period of time or keep the connection alive depending on your preference. Recently, I set up dctrl. It keeps track of all your diald stats like up time, time til timeout, echos the connect script, it even charts how busy your modem is.
That is one of the reasons that I wanted to get diald working, but I'm not real sure where the problem is. Been playing with /etc/diald.conf and trying different things in there, even went so far as to adapt my normal connect script to work with diald by adding a test to see if $PHONE is blank or not, if it is, give it a default number. The CONNECT script that came with it, I glanced at it, and tried to adapt it to handle PAP AUTHENTICATION by stopping the chat script at CONNECT. but from what I could tell (by using lynx or pine to update, and fetchmail) diald doesn't even attempt to make any connection. The local/remote that I am using is the same as in the example (192.168.0.1/192.168.0.2). It does create a /var/run/diald.pid and a /etc/diald/diald.ctl and /var/log/diald.log, but that is all.
I had some trouble setting up diald at first also. Be sure to check /usr/doc/packages/diald. There are some sample configuration files there. The man `diald-examples` (I think that was the name, if that isn't it check 'man diald' I know that it was referenced there) was also very useful.
Yep, there is even a man diald-examples that goes through the different setups, and that is what I'm apparently stuck at, trying to get set up to run on ppp/dynamic:-(
The biggest problem I had was with the preconfigured connect script that comes with diald. If I remember correctly, had to comment out a lot of it. If your interested in setting up diald and get hung up on the connect script let me know and I'll look at mine again.
That is the reason I tried to adapt my normal connect script, but I think I'm going to have to set one up from scratch:-( BTW, part of the reason that I wanted to use diald was so that I could set up fetchmail to run at specific times instead of only when someone is logged on. But to do that, my provider does have a dedicated mail number, which I would also want to set up. Other than that I would want to use the "normal" dialup number for my provider. Is that possible with diald? From what I could tell, the "connect" script would really have to be pretty complex to handle that? -- cya l8r Leon McClatchey leonmcclatchey@homemail.com Party on Linux:-) -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
On Thu, 28 May 1998, Leon McClatchey wrote:
That is one of the reasons that I wanted to get diald working, but I'm not real sure where the problem is. Been playing with /etc/diald.conf and trying
Somewhere (perhaps on colm) I read that the latest pppd (2.3.5?) includes diald functionality, and eliminates the need for diald. It's worth checking out, if true. HTH -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Sitaram Chamarty wrote:
On Thu, 28 May 1998, Leon McClatchey wrote:
That is one of the reasons that I wanted to get diald working, but I'm not real sure where the problem is. Been playing with /etc/diald.conf and trying
Somewhere (perhaps on colm) I read that the latest pppd (2.3.5?) includes diald functionality, and eliminates the need for diald. It's worth checking out, if true.
I just got done doing a quick search for "pppd linux" on cyber 411, but couldn't find it anywhere. I did discover that the version that I have does not support the "demand" option though it does support the other options. So where can I get the latest and greatest? Thanx Loads -- cya l8r Leon McClatchey leonmcclatchey@homemail.com Party on Linux:-) -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
On Fri, 29 May 1998, Leon McClatchey wrote:
I just got done doing a quick search for "pppd linux" on cyber 411, but couldn't find it anywhere. I did discover that the version that I have does not support the "demand" option though it does support the other options. So where can I get the latest and greatest?
<A HREF="ftp://cs.anu.edu.au/pub/software/ppp/"><A HREF="ftp://cs.anu.edu.au/pub/software/ppp/</A">ftp://cs.anu.edu.au/pub/software/ppp/ Dwight -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Dwight Johnson wrote:
On Fri, 29 May 1998, Leon McClatchey wrote:
I just got done doing a quick search for "pppd linux" on cyber 411, but couldn't find it anywhere. I did discover that the version that I have does not support the "demand" option though it does support the other options. So where can I get the latest and greatest?
<A HREF="ftp://cs.anu.edu.au/pub/software/ppp/"><A HREF="ftp://cs.anu.edu.au/pub/software/ppp/</A">ftp://cs.anu.edu.au/pub/software/ppp/
Thanx! As I am writing this little note, I'm getting ppp-2.3.5.tar.gz:-)From what I've seen of the scripts, it should be easier to set up than diald?
Dwight
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
-- cya l8r Leon McClatchey leonmcclatchey@homemail.com Party on Linux:-) -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Dwight Johnson wrote:
On Wed, 27 May 1998, Leon McClatchey wrote:
Now all I need to do is get dial on demand working so that someone doesn't always have to be on the internet in order for Win95 to access the net:-)
I am using ppp-2.3.3 rather than diald for this and I recommend it. You do have to compile ppp-2.3.3 from the sources and rebuild the kernel.
Thanx, I'll give that a shot:-) I got a printout so I can work with it better:-)I'm not sure what version of pppd I have, whatever came with Suse 5.1:-) I do know that it is active in the kernel rather than loaded as a module.
PROVIDER=your_isp.com
I take it the above is the name of my machine/domain? BTW, does it matter that it (my domain name) does not end in one of the standards? I created the domain name before I was aware of the "standards" as far as domains goes:-( Then, once named, not very inclined to change:-(
PROVIDER_NAME=Your ISPs Name PHONE=555-1234 #Your ISPs dial-up number
I almost forgot, does ppp still read /etc/options with this script? my /etc/options is set up to use PAP Authentication via the NAME keyword. -- cya l8r Leon McClatchey leonmcclatchey@homemail.com Party on Linux:-) -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
On Thu, 28 May 1998, Leon McClatchey wrote:
Dwight Johnson wrote:
On Wed, 27 May 1998, Leon McClatchey wrote:
Now all I need to do is get dial on demand working so that someone doesn't always have to be on the internet in order for Win95 to access the net:-)
I am using ppp-2.3.3 rather than diald for this and I recommend it. You do have to compile ppp-2.3.3 from the sources and rebuild the kernel.
Thanx, I'll give that a shot:-) I got a printout so I can work with it better:-)I'm not sure what version of pppd I have, whatever came with Suse 5.1:-) I do know that it is active in the kernel rather than loaded as a module.
The PPP-HOWTO will answer all your questions about writing ppp scripts. Dwight -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Dwight Johnson wrote:
On Thu, 28 May 1998, Leon McClatchey wrote:
I am using ppp-2.3.3 rather than diald for this and I recommend it. You do have to compile ppp-2.3.3 from the sources and rebuild the kernel.
The only problem is that the version that I am running is a bit older:-( And I did a quick search via Cyber 411 and couldn't find where to download 2.3.3 from. The version that I have does not support "demand" though the rest of the parameters did work.
The PPP-HOWTO will answer all your questions about writing ppp scripts.
hehe, that's what I used to put together my original script which would handle two (or more) IP's and 5 users using pap authentication. Though that one did not have the capabilities of handling my intranet connection which from what I understood of your script could possibly handle that? And there were a few of the options that I was not familiar with, but it did look like your script could be run without a /etc/options file since all the options were included within the script itself. That is one thing that I was also a bit concerned with diald about. For a standard connection, I didn't want to keep changing the /etc/options file, but I did wonder, if it was possible to dynamically select which phone number to dial (one for mail and another for "normal" connections?) At any rate, my version of pppd choked on "demand" so I guess I need a newer version or at least a version which includes the source so I can recompile (basicaly like I did with Apache to enable the proxy service). That brings up the question, where? Thanx Loads! -- cya l8r Leon McClatchey leonmcclatchey@homemail.com Party on Linux:-) -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
participants (8)
-
arunkhan＠xnet.com -
dana＠ntd.net -
dwj＠aaronsrod.com -
kepe＠home.com -
kyle＠binary.net -
lach＠lach.net -
leonmcclatchey＠homemail.com -
sitaram＠diac.com