Networking Forums

Networking Forums > Computer Networking > Linux Networking > Dialup via PPP/mgetty works, but can't get to anything beyond server

Reply
Thread Tools Display Modes

Dialup via PPP/mgetty works, but can't get to anything beyond server

 
 
Alex
Guest
Posts: n/a

 
      08-18-2003, 01:51 PM
Hello,

I've setup PPP dialup on RH 8 per Red Hat's instructions, but I'm
unable to get outside the box I'm dialed into. I can ping it, but
nothing else. Here's what I followed:
http://www.redhat.com/support/resour...er_tips-1.html

Modem is on ttyS0 (com1) and here's my set-up files:
/etc/inittab entry -
S0 :2345 :respawn:/sbin/mgetty -D ttyS0

/etc/ppp/pap-secrets -
# Secrets for authentication using PAP
# client server secret IP addresses
* * "" *

/etc/ppp/options -
lock
-detach
modem
crtscts
proxyarp
asyncmap 0

/etc/ppp/options.ttyS0
192.168.10.23:192.168.10.200
(the server I'm dialing into is 192.168.10.23 on my LAN and I want to
give the dialed in system 192.168.10.200)

The only entries I added outside of the howto follow:
/etc/mgetty+sendfax/mgetty.config -
rings 3
post-init-chat "" AT#CID=1 OK
(Added these for Caller ID to work - which it does great)

/etc/mgetty+sendfax/dialin.config -
all
(added this to allow all numbers to connect, but I'll restrict it
later)

When connected, here's what /var/log/messages shows:


Aug 18 08:24:47 icebox mgetty[908]: data dev=ttyS0, pid=908,
caller='--removed--', conn='16800/ARQ/V34/LAPM/V42BIS',
name='--removed--', cmd='/usr/sbin/pppd', user='/AutoPPP/'
Aug 18 08:24:48 icebox kernel: CSLIP: code copyright 1989 Regents of
the University of California
Aug 18 08:24:48 icebox kernel: PPP generic driver version 2.4.2
Aug 18 08:24:48 icebox pppd[908]: pppd 2.4.1 started by a_ppp, uid 0
Aug 18 08:24:48 icebox pppd[908]: Using interface ppp0
Aug 18 08:24:48 icebox pppd[908]: Connect: ppp0 <--> /dev/ttyS0
Aug 18 08:24:49 icebox /etc/hotplug/net.agent: assuming ppp0 is
already up
Aug 18 08:24:50 icebox ppp(pam_unix)[908]: session opened for user
alex by a_ppp(uid=0)
Aug 18 08:24:50 icebox pppd[908]: user alex logged in
Aug 18 08:24:51 icebox modprobe: modprobe: Can't locate module
ppp-compress-21
Aug 18 08:24:51 icebox kernel: PPP Deflate Compression module
registered
Aug 18 08:24:51 icebox modprobe: modprobe: Can't locate module
ppp-compress-21
Aug 18 08:24:51 icebox pppd[908]: found interface eth0 for proxy arp
Aug 18 08:24:51 icebox pppd[908]: local IP address 192.168.10.23
Aug 18 08:24:51 icebox pppd[908]: remote IP address 192.168.10.200
Aug 18 08:28:30 icebox iptables: succeeded

First thought was IPTABLES might be limiting me, but I have no rules
setup (installed with no firewall settings):
service iptables status
Table: filter
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

On my LAN, the dialup server is 192.168.10.23 with gateway to Internet
being 192.168.10.1. But that's it. After all changes, I submitted
'kill -HUP 1', but I've rebooted since then.

I'm dialing in with Windows 2000 Pro, and it has the following when
ipconfig is entered:
Connection-specific DNS Suffix . :
IP Address.......................:192.168.10.200
Subnet Mask......................:255.255.255.255
Default Gateway..................:192.168.10.200

I'm assuming this is fine for dialup, but most systems on my LAN have
255.255.255.0 for subnet and 192.168.10.1 for gateway. If this needs
to change, where do I do it in PPP? This is a clean install of Red
Hat with all updates.

Thanks for any suggestions or help. I'm almost there

Alex.
 
Reply With Quote
 
 
 
 
Clifford Kite
Guest
Posts: n/a

 
      08-18-2003, 04:02 PM
Alex <(E-Mail Removed)> wrote:

> I've setup PPP dialup on RH 8 per Red Hat's instructions, but I'm
> unable to get outside the box I'm dialed into. I can ping it, but
> nothing else. Here's what I followed:
> http://www.redhat.com/support/resour...er_tips-1.html


....

> Aug 18 08:24:51 icebox pppd[908]: found interface eth0 for proxy arp
> Aug 18 08:24:51 icebox pppd[908]: local IP address 192.168.10.23
> Aug 18 08:24:51 icebox pppd[908]: remote IP address 192.168.10.200


....

> I'm dialing in with Windows 2000 Pro, and it has the following when
> ipconfig is entered:
> Connection-specific DNS Suffix . :
> IP Address.......................:192.168.10.200
> Subnet Mask......................:255.255.255.255
> Default Gateway..................:192.168.10.200


> I'm assuming this is fine for dialup, but most systems on my LAN have
> 255.255.255.0 for subnet and 192.168.10.1 for gateway. If this needs
> to change, where do I do it in PPP? This is a clean install of Red
> Hat with all updates.


It's not fine for dialup. The default gateway for the PPP connection on
the windoze host should be the remote host's IP address, 192.168.10.23
here. I don't do windoze and so can't say how to make it so.

-- Clifford Kite Email: "echo xvgr_yvahk-(E-Mail Removed)|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/
/* ... packets usually cross many administrative boundaries on their way
from a source to a destination and often the only point of agreement
between those separate administrations is that all problems are someone
else's fault. --Van Jacobson, abstract of April 97 MSRI talk */
 
Reply With Quote
 
Clifford Kite
Guest
Posts: n/a

 
      08-18-2003, 06:57 PM
Alex <(E-Mail Removed)> wrote:

> I added some lines to the /etc/ppp/options, so here it is now:
> lock
> -detach
> modem
> crtscts
> proxyarp
> asyncmap 0
> defaultroute


You don't want to set a default route through the PPP interface on the
host connected to the Internet (but pppd won't replace an existing default
route even with this option).

> usepeerdns


You are asking the peer to supply DNS server IP addresses. You don't
want that.

> ms-dns 24.26.193.64
> ms-dns 24.26.193.65
> netmask 255.255.255.0


Setting a netmask is futile. Pppd won't pay any attention to it but
instead use 255.255.255.255.

> Also, here's what ipconfig /all shows on the Windows 2000 box:
> PPP adapter Home:
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
> Physical Address. . . . . . . . . : 00-53-45-00-00-00
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.10.200
> Subnet Mask . . . . . . . . . . . : 255.255.255.255
> Default Gateway . . . . . . . . . : 192.168.10.200


The problem is still the same, the wrong IP address is set as the default
gateway on the PPP interface of the windoze host.

--
Clifford Kite Email: "echo xvgr_yvahk-(E-Mail Removed)|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/
/* Emacs vs vi:
Sort of like a Swiss Army knife versus a rapier. */
 
Reply With Quote
 
CL [dnoyeB] Gilbert
Guest
Posts: n/a

 
      08-18-2003, 09:30 PM
On Mon, 18 Aug 2003 14:08:07 -0700, Alex wrote:

> Clifford Kite <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>...
>
>> > I'm dialing in with Windows 2000 Pro, and it has the following when
>> > ipconfig is entered:
>> > Connection-specific DNS Suffix . :
>> > IP Address.......................:192.168.10.200
>> > Subnet Mask......................:255.255.255.255
>> > Default Gateway..................:192.168.10.200

>>
>> > I'm assuming this is fine for dialup, but most systems on my LAN have
>> > 255.255.255.0 for subnet and 192.168.10.1 for gateway. If this needs
>> > to change, where do I do it in PPP? This is a clean install of Red
>> > Hat with all updates.

>>
>> It's not fine for dialup. The default gateway for the PPP connection on
>> the windoze host should be the remote host's IP address, 192.168.10.23
>> here. I don't do windoze and so can't say how to make it so.

>
> Hi Clifford,
>
> I'm not sure how to change this, but I'm back to the many pages of


Stop right there. He has already indicated your problem. The next
question for you should be how to solve it, not about another side issue
of getting RH9 to work. Get windows working before you move further.

Is your windows box configured to get its address from DHCP?

CL

 
Reply With Quote
 
David Efflandt
Guest
Posts: n/a

 
      08-19-2003, 01:35 AM
On Mon, 18 Aug 2003 13:57:22 -0500, Clifford Kite <(E-Mail Removed)> wrote:
> Alex <(E-Mail Removed)> wrote:
>
>> I added some lines to the /etc/ppp/options, so here it is now:
>> lock
>> -detach
>> modem
>> crtscts
>> proxyarp
>> asyncmap 0
>> defaultroute

>
> You don't want to set a default route through the PPP interface on the
> host connected to the Internet (but pppd won't replace an existing default
> route even with this option).


And you definitely do NOT want replacedefaultroute for pppd either,
because your internet access is in a different direction (ethernet).

> Setting a netmask is futile. Pppd won't pay any attention to it but
> instead use 255.255.255.255.
>
>> Also, here's what ipconfig /all shows on the Windows 2000 box:
>> PPP adapter Home:
>> Connection-specific DNS Suffix . :
>> Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
>> Physical Address. . . . . . . . . : 00-53-45-00-00-00
>> DHCP Enabled. . . . . . . . . . . : No
>> IP Address. . . . . . . . . . . . : 192.168.10.200
>> Subnet Mask . . . . . . . . . . . : 255.255.255.255
>> Default Gateway . . . . . . . . . : 192.168.10.200

>
> The problem is still the same, the wrong IP address is set as the default
> gateway on the PPP interface of the windoze host.


Actually, certain Win versions have no interface names, so the only
reference they have for which direction a default route should go is their
own IP on that interface. My broadband router does this too.

What I have not seen anyone mention is what is the output of:

cat /proc/sys/net/ipv4/ip_forward

That should be 1. If it is 0, then nothing is going to route through the
mgetty box. Your network scripts probably have a setting for ip
forwarding, but you can try it on the fly with:

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

--
David Efflandt - All spam ignored http://www.de-srv.com/
http://www.autox.chicago.il.us/ http://www.berniesfloral.net/
http://cgi-help.virtualave.net/ http://hammer.prohosting.com/~cgi-wiz/
 
Reply With Quote
 
Clifford Kite
Guest
Posts: n/a

 
      08-19-2003, 03:31 PM
Alex <(E-Mail Removed)> wrote:

> I tried to dial-in with a Linux box (RH9) and I'm getting the same
> results. I can connect to the server I'm dialing into, but nothing
> beyond that (LAN or Internet). Here's the ifconfig results:


> ppp0 Link encap:Point-to-Point Protocol
> inet addr:192.168.10.123 P-t-P:192.168.10.23
> Mask:255.255.255.255
> UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
> RX packets:6 errors:2 dropped:0 overruns:0 frame:0
> TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:3
> RX bytes:112 (112.0 b) TX bytes:112 (112.0 b)


I assume this is from the dial-in Linux host. The ifconfig output above
says that the dial-in host has IP address 192.168.10.123 while the mgetty
host has the IP address 192.168.10.23, which is fine.

I think this should work if IP forwarding is compiled into the kernel
of the mgetty host and turned on as suggested by /dev/rob0 and David
Efflandt.

> I'm not sure if this helps. Also, in reading some posts by others, I


It doesn't help without more information about the pppd configuration on
the dialin host and, if appropriate, any changes in the mgetty host setup.

Also, switching horses in mid-stream isn't productive. An obvious problem
with the Windows dial-in is the Windows default routing. The Windows host
is not doing the right thing, which is to set the mgetty PPP IP address
as it's default gateway. Posting on a Windows usenet group as to how
to set up dial-in might be a lot more productive.

> have a question. Do I need to add something in IPTABLES to allow ppp0
> to have access beyond eth0?


No, you said you didn't configure an iptables firewall on the mgetty
host.

--
Clifford Kite Email: "echo xvgr_yvahk-(E-Mail Removed)|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/
 
Reply With Quote
 
Alex
Guest
Posts: n/a

 
      08-19-2003, 07:33 PM
(E-Mail Removed) (David Efflandt) wrote in message news:<(E-Mail Removed)>...
> On Mon, 18 Aug 2003 13:57:22 -0500, Clifford Kite <(E-Mail Removed)> wrote:
> > Alex <(E-Mail Removed)> wrote:
> >
> >> I added some lines to the /etc/ppp/options, so here it is now:
> >> lock
> >> -detach
> >> modem
> >> crtscts
> >> proxyarp
> >> asyncmap 0
> >> defaultroute

> >
> > You don't want to set a default route through the PPP interface on the
> > host connected to the Internet (but pppd won't replace an existing default
> > route even with this option).

>
> And you definitely do NOT want replacedefaultroute for pppd either,
> because your internet access is in a different direction (ethernet).
>
> > Setting a netmask is futile. Pppd won't pay any attention to it but
> > instead use 255.255.255.255.
> >
> >> Also, here's what ipconfig /all shows on the Windows 2000 box:
> >> PPP adapter Home:
> >> Connection-specific DNS Suffix . :
> >> Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
> >> Physical Address. . . . . . . . . : 00-53-45-00-00-00
> >> DHCP Enabled. . . . . . . . . . . : No
> >> IP Address. . . . . . . . . . . . : 192.168.10.200
> >> Subnet Mask . . . . . . . . . . . : 255.255.255.255
> >> Default Gateway . . . . . . . . . : 192.168.10.200

> >
> > The problem is still the same, the wrong IP address is set as the default
> > gateway on the PPP interface of the windoze host.

>
> Actually, certain Win versions have no interface names, so the only
> reference they have for which direction a default route should go is their
> own IP on that interface. My broadband router does this too.
>
> What I have not seen anyone mention is what is the output of:
>
> cat /proc/sys/net/ipv4/ip_forward
>
> That should be 1. If it is 0, then nothing is going to route through the
> mgetty box. Your network scripts probably have a setting for ip
> forwarding, but you can try it on the fly with:
>
> echo 1 > /proc/sys/net/ipv4/ip_forward


Hi...

That was it. I round a howto that had the echo 1 > ... command, tried
that and all is working fine now. Even on Windows 2000 where the
Gateway and IP address are the same (I've been unable to find where to
change this BTW on Win or Linux). But all is routing properly and
working great.

Thanks for the feedback from everyone...

Alex.
 
Reply With Quote
 
Alex
Guest
Posts: n/a

 
      08-19-2003, 09:35 PM
(E-Mail Removed) (David Efflandt) wrote in message news:<(E-Mail Removed)>...
<< SNIP >>
> >> Also, here's what ipconfig /all shows on the Windows 2000 box:
> >> PPP adapter Home:
> >> Connection-specific DNS Suffix . :
> >> Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
> >> Physical Address. . . . . . . . . : 00-53-45-00-00-00
> >> DHCP Enabled. . . . . . . . . . . : No
> >> IP Address. . . . . . . . . . . . : 192.168.10.200
> >> Subnet Mask . . . . . . . . . . . : 255.255.255.255
> >> Default Gateway . . . . . . . . . : 192.168.10.200

> >
> > The problem is still the same, the wrong IP address is set as the default
> > gateway on the PPP interface of the windoze host.

>
> Actually, certain Win versions have no interface names, so the only
> reference they have for which direction a default route should go is their
> own IP on that interface. My broadband router does this too.
>
> What I have not seen anyone mention is what is the output of:
>
> cat /proc/sys/net/ipv4/ip_forward
>
> That should be 1. If it is 0, then nothing is going to route through the
> mgetty box. Your network scripts probably have a setting for ip
> forwarding, but you can try it on the fly with:
>
> echo 1 > /proc/sys/net/ipv4/ip_forward


That's it... I ran the above echo statement, and that enabled me to
connect to systems beyond the server I was dialing into. Even on
Windows 2000 where the gateway and IP address are the same, it still
worked fine.

I'll go through the other posts with do's and don'ts and see what else
I can tweak, but it works great now.

Thanks everyone for your help and assistance, and take care.

Alex.
 
Reply With Quote
 
Michael Buchenrieder
Guest
Posts: n/a

 
      08-21-2003, 06:59 AM
/dev/rob0 <(E-Mail Removed)> writes:

[...]

>... and he doesn't know either, but you MUST change that. It's somewhere
>in TCP/IP properties for your dial-up connection. Consult Windows help
>or appropriate forums for Windows advice.


[...]

Yes. It's a checkbox under the "advanced options" that you can reach
by right-clicking onto the DUN icon for the RH connection. "Use Gateway
on remote network" or some such".

Michael
--
Michael Buchenrieder * (E-Mail Removed) * http://www.muc.de/~mibu
Lumber Cartel Unit #456 (TINLC) & Official Netscum
Note: If you want me to send you email, don't munge your address.
 
Reply With Quote
 
James Knott
Guest
Posts: n/a

 
      08-21-2003, 10:55 AM
CL [dnoyeB] Gilbert wrote:

> Is your windows box configured to get its address from DHCP?
>


DHCP is not normally used on dial up lines. The address is assigned to the
dial in port and given to the computer calling in. It's an entirely
different process than DHCP.

--

Fundamentalism is fundamentally wrong.

To reply to this message, replace everything to the left of "@" with
james.knott.
 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
RRAS dialup server not routing dialup clients to LAN resources HYGROG Windows Networking 1 04-18-2007 02:43 AM
How To: Dialup ISP server??? Wolfe Linux Networking 3 01-30-2005 10:06 PM
Problems with mgetty/pppd and more than one modem draoi Linux Networking 0 04-02-2004 03:33 PM
dialup to 2k server neil Windows Networking 0 01-22-2004 09:29 AM
PPPD server routing problem? Mandrake/mgetty/pppd/D-link router martin02 Linux Networking 17 10-06-2003 03:06 PM



1 2 3 4 5 6 7 8 9 10 11