On Tue, 2002-10-29 at 15:01, dan wrote: > Hi Chris, > > Thanks for the reply. Yes there is a firewall on both the box I am dialing > in from (SuSE personal firewall) and the box I am dialing into. I have had > this working before so I am really unsure it is the firewall causing the > problem (much more likely to be something I have done). > > So stuff I have done on the dial-in server is: > > in inittab: mo:235:respawn:/usr/sbin/mgetty -D ttyS0 > > /etc/mgetty+sendfax/mgetty.config > port ttyS0 > > /etc/mgetty+sendfax/login.config > /AutoPPP/ - a_ppp /usr/sbin/pppd auth login -chap +pap > * - - /bin/login @
I'm assuming you have added credentials in /etc/ppp/pap-secrets so that pppd can authenticate the remote user connecting. > > /etc/ppp/options.ttyS0 file: > > myservers IP address:192.168.23.2 > debug > lock > ms-dns primary DNS ip address > ms-dns secondary DNS ip address > > Does this look correct? I dont see a problem with that...but I used to add "asyncmap 0", "crtscts", "defaultroute" and "modem" to /etc/ppp/options.ttyS0...although I dont know what the impact of those are. Oh wait a second! where is the configuration to tell pppd what ip to use and what ip to send the remote host? I cant remember which file but there is usually a file which would have a pool of ip address which pppd could send to the remote host... try using this syntax in your options.ttyS0 file: local address:remote address local address being the address of the dial-in server. set this address to be something different to any other interface addresses...e.g. dont use the same ip or subnet as the address your ethernet interface is using, make up a new subnet (this might require a slight reconfig of your firewall). remote address being the address you want the connecting machine to use. again done use the same subnet as any other interfaces on your dial-in server or the connecting machine. Example: 10.3.2.1:10.3.2.2 this means that once the connection has been established and authenticated the dial-in server will create a ppp interface with the address 10.3.2.1 and then it will send the address 10.3.2.2 to the connecting machine. let me know how you go. > > Cheers > > Dan > > ----- Original Message ----- > From: "Chris Barnes" <[EMAIL PROTECTED]> > To: "SLUG" <[EMAIL PROTECTED]> > Sent: Wednesday, October 30, 2002 2:15 PM > Subject: Re: [SLUG] Problems with wvdial/PPP - URGENT > > > > I could be going down the wrong path all together here but on the remote > > machine it says "No response to 4 echo-requests"..i have no idea but > > could a firewall be causing this problem? do you have a firewall running > > which could be dumping incoming icmp packets on the dial-up interface? > > > > I really don't know...that was just a guess...all the dial-up servers > > I've configured seem to work relatively fine first go for me. > > > > how about you give us a snippet of your config for the dial-up server. > > > > > > On Tue, 2002-10-29 at 12:45, dan wrote: > > > Hi, > > > > > > I am having some real problems with wvdial on SuSE 7.2. I am dialing > into > > > my own Dial-in server and the line is being dropped immediately by the > > > modem. > > > > > > I am trying to work out why this is happening. From the linux box I am > > > dialing in from here are some messages from /var/log/message: > > > > > > Script /etc/ppp/ip-up finished (pid 1993), status = 0x0 > > > Oct 29 12:49:04 linux pppd[1991]: rcvd [LCP EchoReq id=0x1 > magic=0x698b01dd] > > > Oct 29 12:49:04 linux pppd[1991]: sent [LCP EchoRep id=0x1 > magic=0x6df45bfd] > > > Oct 29 12:51:18 linux pppd[1991]: rcvd [LCP EchoReq id=0x2 > magic=0x698b01dd] > > > Oct 29 12:51:18 linux pppd[1991]: sent [LCP EchoRep id=0x2 > magic=0x6df45bfd] > > > Oct 29 12:51:37 linux pppd[1991]: Hangup (SIGHUP) > > > Oct 29 12:51:37 linux pppd[1991]: Modem hangup > > > > > > And from the remote machine I am trying to connect to: > > > > > > ct 29 12:32:03 www pppd[22175]: No response to 4 echo-requests > > > Oct 29 12:32:03 www pppd[22175]: Serial link appears to be disconnected. > > > Oct 29 12:32:07 www pppd[22175]: Connection terminated. > > > Oct 29 12:32:07 www pppd[22175]: Connect time 3.1 minutes. > > > > > > As far as i can see the modem and the dial-in server are setup correctly > so > > > does anyone have any ideas why the modem is hanging up straight away? > > > > > > Should I be looking in any other logs files for clues? > > > > > > Thanks > > > > > > Dan > > > > > > -- > > > SLUG - Sydney Linux User's Group - http://slug.org.au/ > > > More Info: http://lists.slug.org.au/listinfo/slug > > > > > > -- > > SLUG - Sydney Linux User's Group - http://slug.org.au/ > > More Info: http://lists.slug.org.au/listinfo/slug > > > > -- > SLUG - Sydney Linux User's Group - http://slug.org.au/ > More Info: http://lists.slug.org.au/listinfo/slug -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
