Board index Linux Networking

: Setting Up A Dial In Server Using SuSE 7.3 Pro

: Setting Up A Dial In Server Using SuSE 7.3 Pro

Post by In Ye » Wed, 06 Feb 2002 13:22:02



Hi,

I have made the necessary changes to the following files on a
SuSE 7.0 Pro Linux distro to support for a dial-in and it worked:

        /etc/mgetty+sendfax/login.config
        /etc/ppp/options.server
        /etc/ppp/options.ttyS15
        /etc/ppp/pap-secrets

Now that I have upgraded to SuSE 7.3 Pro, the modifications that
I made to the SuSE 7.0 Pro is no longer working.  The
/var/log/messages for the dial-in as shown below:

        Feb  4 23:16:42 linux pppd[7530]: Using interface ppp0
        Feb  4 23:16:42 linux pppd[7530]: Connect: ppp0 <--> /dev/ttyS15
        Feb  4 23:16:49 linux pppd[7530]: user inyen logged in
        Feb  4 23:16:50 linux pppd[7530]: found interface eth0 for
proxy arp
        Feb  4 23:16:50 linux pppd[7530]: local  IP address 192.168.1.2
        Feb  4 23:16:50 linux pppd[7530]: remote IP address 192.168.1.7
        Feb  4 23:17:47 linux pppd[7530]: Hangup (SIGHUP)
        Feb  4 23:17:47 linux pppd[7530]: Modem hangup
        Feb  4 23:17:47 linux pppd[7530]: Connection terminated.
        Feb  4 23:17:47 linux pppd[7530]: Connect time 1.1 minutes.
        Feb  4 23:17:47 linux pppd[7530]: Sent 73 bytes, received 2346
bytes.
        Feb  4 23:17:48 linux pppd[7530]: Exit.

said the dial-in user, inyen, had successfully logged in with an
IP address of 192.168.1.7; however, I could not connect to any
website or even download my e-mail and when I went to other
computer, a win2k (on the same subnet with IP address
192.168.1.8), and did a "ping 192.168.1.7" to no avail.  The
"ping" returned "Request timed out".  This looked like the the
linux machine failed to forward/route the packets from/to my
machine.  Does anyone out here have any idea what I am missing?

TIA.

 
 
 
Top

: Setting Up A Dial In Server Using SuSE 7.3 Pro

Post by Dean Thompso » Thu, 07 Feb 2002 01:03:53


Hi!,

Quote:> I have made the necessary changes to the following files on a
> SuSE 7.0 Pro Linux distro to support for a dial-in and it worked:

>         /etc/mgetty+sendfax/login.config
>         /etc/ppp/options.server
>         /etc/ppp/options.ttyS15
>         /etc/ppp/pap-secrets

> Now that I have upgraded to SuSE 7.3 Pro, the modifications that
> I made to the SuSE 7.0 Pro is no longer working.  The
> /var/log/messages for the dial-in as shown below:

>         Feb  4 23:16:42 linux pppd[7530]: Using interface ppp0
>         Feb  4 23:16:42 linux pppd[7530]: Connect: ppp0 <--> /dev/ttyS15
>         Feb  4 23:16:49 linux pppd[7530]: user inyen logged in
>         Feb  4 23:16:50 linux pppd[7530]: found interface eth0 for
> proxy arp
>         Feb  4 23:16:50 linux pppd[7530]: local  IP address 192.168.1.2
>         Feb  4 23:16:50 linux pppd[7530]: remote IP address 192.168.1.7
>         Feb  4 23:17:47 linux pppd[7530]: Hangup (SIGHUP)
>         Feb  4 23:17:47 linux pppd[7530]: Modem hangup
>         Feb  4 23:17:47 linux pppd[7530]: Connection terminated.
>         Feb  4 23:17:47 linux pppd[7530]: Connect time 1.1 minutes.
>         Feb  4 23:17:47 linux pppd[7530]: Sent 73 bytes, received 2346
> bytes.
>         Feb  4 23:17:48 linux pppd[7530]: Exit.

> said the dial-in user, inyen, had successfully logged in with an
> IP address of 192.168.1.7; however, I could not connect to any
> website or even download my e-mail and when I went to other
> computer, a win2k (on the same subnet with IP address
> 192.168.1.8), and did a "ping 192.168.1.7" to no avail.  The
> "ping" returned "Request timed out".  This looked like the the
> linux machine failed to forward/route the packets from/to my
> machine.  Does anyone out here have any idea what I am missing?

Do you have the "proxyarp" option in your PPP settings.  Also, take a look
through the PocketISP setup HOWTO located at http://www.linuxdoc.org.
Although it isn't suited to SuSE (from memory) you might find a few pointers
in it.

See ya

Dean Thompson

--
+____________________________+____________________________________________+

| Bach. Computing (Hons)     | ICQ     - 45191180                         |
| PhD Student                | Office  - <Off-Campus>                     |
| School Comp.Sci & Soft.Eng | Phone   - +61 3 9903 2787 (Gen. Office)    |
| MONASH (Caulfield Campus)  | Fax     - +61 3 9903 1077                  |
| Melbourne, Australia       |                                            |
+----------------------------+--------------------------------------------+

 
 
 
Top

: Setting Up A Dial In Server Using SuSE 7.3 Pro

Post by Clifford Kit » Thu, 07 Feb 2002 01:20:27



> "ping" returned "Request timed out".  This looked like the the
> linux machine failed to forward/route the packets from/to my
> machine.  Does anyone out here have any idea what I am missing?

Perhaps a SuSE setup configuration option turning on IP forwarding?

echo -n 1 > /proc/sys/net/ipv4/ip_forward

--

PPP-Q&A links, downloads:    http://users3.ev1.net/~ckite/public_html/
/* I hear and I forget.  I see and I remember.  I do and I understand.
                               --Confucius, 551-479 BC */

 
 
 
Top

: Setting Up A Dial In Server Using SuSE 7.3 Pro

Post by James Knot » Thu, 07 Feb 2002 02:33:11



> said the dial-in user, inyen, had successfully logged in with an
> IP address of 192.168.1.7; however, I could not connect to any
> website or even download my e-mail and when I went to other
> computer, a win2k (on the same subnet with IP address
> 192.168.1.8), and did a "ping 192.168.1.7" to no avail.  The
> "ping" returned "Request timed out".  This looked like the the
> linux machine failed to forward/route the packets from/to my
> machine.  Does anyone out here have any idea what I am missing?

> TIA.

Check "Pocket" ISP based on Redhat Linux HOWTO
http://www.linuxdoc.org/HOWTO/ISP-Setup-RedHat-HOWTO.html

--


james.knott.

 
 
 
Top

: Setting Up A Dial In Server Using SuSE 7.3 Pro

Post by In Ye » Thu, 07 Feb 2002 05:17:35


On Tuesday 05 February 2002 11:20, `Clifford Kite' of



>> "ping" returned "Request timed out".  This looked like the the
>> linux machine failed to forward/route the packets from/to my
>> machine.  Does anyone out here have any idea what I am
>> missing?

> Perhaps a SuSE setup configuration option turning on IP
> forwarding?

> echo -n 1 > /proc/sys/net/ipv4/ip_forward

You reminded me of the IP_FORWARD switch under /etc/rc.config
file.  I changed that to "yes" and now the dial-in works just
fine as before!  Thank Clifford!
 
 
 
Top

1. Printing problems from clients to server using Samba on SuSE 7.3 Pro

Hello  All,

First let me thank Shaun Marolf and Robert for getting me to where I
am to date.  

I don't know if this is a Samba problem or a SuSE problem, therefore I
am posting in both groups.

When attempting to print from any of my clients I get the following
messages:  I have reduced the output to what I think is the pertinent
info.           1st message = apsfilter:  unable to print job
smbprn.wOY0Oo

2nd message = printer hpphoto job cfA084rogers.mallard failed and
could not be retried.  
IF filter 'y2prn_hpphoto.upp--auto-hpphoto' filter msg - 'a2ps:
'Text" is a binary file, printing aborted
IF filter (same as above) filter msg - '%%[ Error: typecheck;
OffendingCommand:  closefile ]%%
IF filter (same as above) filter msg - 'GNU Ghostscript 6.51:
Unrecoverable error, exit code 1'
exit status 'JABORT'

I can print from the server no problem.  Have never been able to print
from clients.

I think the problem is the "binary" file-----why would this happen?

Same setup in Redhat 7.2 professional and I have no problems printing
from server and clients.

This message is the same every time I try to print from my clients.  

Where should I look to try and solve this problem....have perused SuSE
and Samba support database with no help.

Any help would be appreciated.  I will provide any other info that
would be deemed helpful.

Testparm and all other network configs are okay.......From the client
I can access my home directories and write to or delete from same.  I
can capture the printer port.  On the client I can see the printer job
spooling and then it disappears.

Thanks,

Roger

______________________________________________________________________
Posted Via Uncensored-News.Com - Still Only $9.95 - http://www.uncensored-news.com
      <><><><><><><>   The Worlds Uncensored News Source   <><><><><><><><>

2. External SCSI Drive Installation

3. SuSE 7.3 Pro CDs

4. kbdrate after reboot

5. SuSE 7.3 Pro Linux v.s Lexmark E210 Printer on W2K

6. Rsh usage

7. SuSE 7.3 Pro crashes

8. 1.2.13 install with Slackware 3.0 & AHA2940 & 3c590

9. Autoconf vs. SuSE 7.3 Pro

10. SuSE 7.3 Pro vs. 3DFX Voodo 3500 TV AGP Card

11. Suse 7.3 Pro networking

12. Spalsh Screen In Booting On SuSE 7.3 Pro

13. Suse 7.3 Pro and Apm


All times are UTC
Board index