On Wed, 26 Nov 1997, Alex Yukhimets wrote: > > OK. Now that I know that this is the Debian way, I am happy to do it this > > way. > > I tried this, and it was a beautiful thing to hear the modem > > connecting...but > > it didn't work. I'm going to include my /etc/ppp.options_out, > > /etc/ppp.chatscript, and the final "plog". > > > > /etc/ppp.options_out > > ------------------------------------- > > defaultroute /dev/ttyS1 57600 persist > > user Larry.Gariepy > > ------------------------------------- > > Hi. > > I would recommend putting all options of the above file in one line. > (If you examine pon script you will see why. It is not strictly necessary > though.) >
And, since you seem to do login below in the chatscript, the "user" option probably isn't necessary. > > > > > /etc/ppp.chatscript > > ------------------------------------- > > ABORT BUSY > > ABORT "NO CARRIER" > > ABORT VOICE > > ABORT "NO DIALTONE" > > "" ATDT16036430102 > > name Larry.Gariepy > > word \qboffo17\q > > ready ppp > > ------------------------------------- > > > > "plog" output: > > ------------------------------------- > > Nov 26 03:03:54 gariepy pppd[440]: Serial connection established. > > Nov 26 03:03:55 gariepy pppd[440]: Using interface ppp0 > > Nov 26 03:03:55 gariepy pppd[440]: Connect: ppp0 <--> /dev/modem > > Nov 26 03:04:01 gariepy pppd[440]: local IP address 129.170.40.79 > > Nov 26 03:04:01 gariepy pppd[440]: remote IP address 129.170.40.12 > > Nov 26 03:04:01 gariepy pppd[440]: ppp not replacing existing default route > > to > > eth0[129.170.28.254] > > Nov 26 03:04:01 gariepy pppd[440]: Cannot determine ethernet address for > > proxy > > ARP > > > > ------------------------------------- > > So when I start ppp with pon, it gets this far, and doesn't do anything. > > "ifconfig" seems to think that my connection is working. What is curious is > > that the last two lines of the "plog" output never make it to > > /var/log/messages. > > Great! You *did* get ppp connection! Your problem is that you have to set up > your routing table properly in /etc/ppp/ip-up (on connection) and > /etc/ppp/ip-down (on disconnect) using "route". And remove defaultroute > option > from /etc/ppp.options_out - you already have defaultroute to your eth0 > interface. > Well, here's the question: apparently you have an ethernet card in your machine. Now, how are you going to use it? If you want to use your ethernet card for most outgoing traffic and only use ppp for accessing a given subnet, put something like the following in your /etc/ppp/ip-up: /sbin/route add 137.22.0.0 netmask 255.255.0.0 ppp0 This will route packets headed for 137.22.*.* through your ppp interface. If you wish to use your ppp interface for most packets and your ethernet card for only a few, put something like the following in /etc/ppp/ip-up: /sbin/route del default /sbin/route add default ppp0 /sbin/route add 137.22.96.0 netmask 255.255.240 eth0 (The number after netmask should be the netmask of the subnet you want to use your ethernet card on - this netmask is a peculiar one actually in use at my undergrad. school) If, while ppp is up, you don't want to use your ethernet card at all, then don't put the last 'route add' line in. If you do this, (meaning anything including the 'route del default' line above) you should probably also put the following lines in /etc/ppp/ip-down: /sbin/route del default /sbin/route add default gw 137.22.96.254 eth0 (where for 137.22.96.254 you should put your ethernet gateway) If in fact your ethernet card isn't connected at all, then leave out the 'add default' bit. Actually, if your card isn't connected at all, you could just make certain that 'route del default' was run before pon (say, run it a system startup) and then the 'defaultroute' option in /etc/ppp.options_out will do the trick (i.e. no messing with /etc/ppp/ip-* necessary) -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
