Dialin Server - Connects but no net activity. Any pointers?

Hi all,
I'm trying to setup a dialin server on a redhat 7.3 box that sits
on our network. The machine gets internet connection by a defaultroute
on a gateway machine that NATs the machines on the 192.168.0.x LAN.
The dialin server has one NIC that is connected to the lan/accesses
the net. Basically, I have set it up so I should be able to dial in
and use the net/LAN using a windows machine + dial up modem. I can
connect to the machine, auth username/password but when I connect, no
internet activity happens nor can I ping anywhere (net or lan or
dialup server IPS) from the windows machine. The relative info is:

The IP of eth0 on dialin is 192.168.0.75
THE IP I have assigned for ppp0 is 192.168.0.76

the IP of the gateway/NAT machine is 192.168.0.1

echo 1 > /proc/sys/net/ipv4/ip_forward
echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp



/usr/local/etc/mgetty+sendfax/login.config

/AutoPPP/ - @ /usr/sbin/pppd file /etc/ppp/options.server
* - - /bin/login @
---------------

/etc/ppp/options.server

# -detach <- I commented it out since it seemed I was getting d/c
with it left in
asyncmap 0
modem
crtscts
lock
nodefaultroute
proxyarp
login
debug
ms-dns 203.8.183.1 <- the DNS we use from our upstream provider

---------------
/etc/ppp/options.ttyS0

192.168.0.75:192.168.0.76
netmask 255.255.255.0

The modem connected to the dialin server was found on ttyS0 by wvdial

---------------
/etc/inittab

S0:2345:respawn:/usr/local/sbin/mgetty -x 5 ttyS0
---------------



Output from log files

/var/log/mgetty.ttyS0

10/06 14:54:57 yS0 match: user='/AutoPPP/', key=''
10/06 14:54:57 yS0 match: user='/AutoPPP/', key=''
10/06 14:54:57 yS0 match: user='/AutoPPP/', key='/AutoPPP/'*** hit!
10/06 14:54:57 yS0 login: utmp entry: /AutoPPP/
10/06 14:54:57 yS0 utmp + wtmp entry made
10/06 14:54:57 yS0 calling login: cmd='/usr/sbin/pppd', argv[]='pppd
file /etc/ppp/options.server'
10/06 14:54:57 yS0 setenv: 'CALLER_ID=none'
10/06 14:54:57 yS0 setenv: 'CONNECT=33600'
10/06 14:54:57 yS0 setenv: 'DEVICE=ttyS0'
10/06 14:54:57 ##### data dev=ttyS0, pid=1599, caller='none',
conn='33600', name='', cmd='/usr/sbin/pppd', user='/AutoPPP/'

-----------------

/var/log/daemon

Oct 6 14:39:47 access pppd[1383]: pppd 2.4.1 started by /AutoPPP/,
uid 0
Oct 6 14:39:47 access pppd[1383]: using channel 1
Oct 6 14:39:48 access pppd[1383]: Using interface ppp0
Oct 6 14:39:48 access pppd[1383]: Connect: ppp0 <--> /dev/ttyS0
*heap of LCP lines removed*
Oct 6 14:39:54 access pppd[1383]: found interface eth0 for proxy arp
Oct 6 14:39:54 access pppd[1383]: local IP address 192.168.0.75
Oct 6 14:39:54 access pppd[1383]: remote IP address 192.168.0.76
Oct 6 14:39:54 access pppd[1383]: Script /etc/ppp/ip-up started (pid
1418)
Oct 6 14:39:54 access pppd[1383]: Script /etc/ppp/ip-up finished (pid
1418), status = 0x0


Routing:

Before connecting:
]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref
Use Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0
0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0
0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0
0 lo
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0
0 eth0

after connecting:
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref
Use Iface
192.168.0.76 0.0.0.0 255.255.255.255 UH 0 0
0 ppp0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0
0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0
0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0
0 lo
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0
0 eth0



I think I may need to do some forwarding with iptables. I did some
forwarding/nat stuff I found from google but it didn't seem to help.
I'm not too sure if NATing from the dialin server to another NAT
gateway box would be stuffing my connection up at all? Also, no other
firewalls/iptable stuff is on the dialin box.

Any help is appreciated.

Warren Smith schrieb:
> Hi all,
> I'm trying to setup a dialin server on a redhat 7.3 box that sits
> on our network. The machine gets internet connection by a defaultroute
> on a gateway machine that NATs the machines on the 192.168.0.x LAN.
> The dialin server has one NIC that is connected to the lan/accesses
> the net. Basically, I have set it up so I should be able to dial in
> and use the net/LAN using a windows machine + dial up modem. I can
> connect to the machine, auth username/password but when I connect, no
> internet activity happens nor can I ping anywhere (net or lan or
> dialup server IPS) from the windows machine. The relative info is:
>
> The IP of eth0 on dialin is 192.168.0.75
> THE IP I have assigned for ppp0 is 192.168.0.76
>
> the IP of the gateway/NAT machine is 192.168.0.1
>
> echo 1 > /proc/sys/net/ipv4/ip_forward
> echo 1 > /proc/sys/net/ipv4/conf/eth0/proxy_arp
>
>
>
> /usr/local/etc/mgetty+sendfax/login.config
>
> /AutoPPP/ - @ /usr/sbin/pppd file /etc/ppp/options.server
> * - - /bin/login @
> ---------------
>
> /etc/ppp/options.server
>
> # -detach <- I commented it out since it seemed I was getting d/c
> with it left in
> asyncmap 0
> modem
> crtscts
> lock
> nodefaultroute
> proxyarp
> login
> debug
> ms-dns 203.8.183.1 <- the DNS we use from our upstream provider
>
> ---------------
> /etc/ppp/options.ttyS0
>
> 192.168.0.75:192.168.0.76
> netmask 255.255.255.0
>
> The modem connected to the dialin server was found on ttyS0 by wvdial
>
> ---------------
> /etc/inittab
>
> S0:2345:respawn:/usr/local/sbin/mgetty -x 5 ttyS0
> ---------------
>
>
>
> Output from log files
>
> /var/log/mgetty.ttyS0
>
> 10/06 14:54:57 yS0 match: user='/AutoPPP/', key=''
> 10/06 14:54:57 yS0 match: user='/AutoPPP/', key=''
> 10/06 14:54:57 yS0 match: user='/AutoPPP/', key='/AutoPPP/'*** hit!
> 10/06 14:54:57 yS0 login: utmp entry: /AutoPPP/
> 10/06 14:54:57 yS0 utmp + wtmp entry made
> 10/06 14:54:57 yS0 calling login: cmd='/usr/sbin/pppd', argv[]='pppd
> file /etc/ppp/options.server'
> 10/06 14:54:57 yS0 setenv: 'CALLER_ID=none'
> 10/06 14:54:57 yS0 setenv: 'CONNECT=33600'
> 10/06 14:54:57 yS0 setenv: 'DEVICE=ttyS0'
> 10/06 14:54:57 ##### data dev=ttyS0, pid=1599, caller='none',
> conn='33600', name='', cmd='/usr/sbin/pppd', user='/AutoPPP/'
>
> -----------------
>
> /var/log/daemon
>
> Oct 6 14:39:47 access pppd[1383]: pppd 2.4.1 started by /AutoPPP/,
> uid 0
> Oct 6 14:39:47 access pppd[1383]: using channel 1
> Oct 6 14:39:48 access pppd[1383]: Using interface ppp0
> Oct 6 14:39:48 access pppd[1383]: Connect: ppp0 <--> /dev/ttyS0
> *heap of LCP lines removed*
> Oct 6 14:39:54 access pppd[1383]: found interface eth0 for proxy arp
> Oct 6 14:39:54 access pppd[1383]: local IP address 192.168.0.75
> Oct 6 14:39:54 access pppd[1383]: remote IP address 192.168.0.76
> Oct 6 14:39:54 access pppd[1383]: Script /etc/ppp/ip-up started (pid
> 1418)
> Oct 6 14:39:54 access pppd[1383]: Script /etc/ppp/ip-up finished (pid
> 1418), status = 0x0
>
>
> Routing:
>
> Before connecting:
> ]# route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref
> Use Iface
> 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0
> 0 eth0
> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0
> 0 eth0
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0
> 0 lo
> 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0
> 0 eth0
>
> after connecting:
> # route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref
> Use Iface
> 192.168.0.76 0.0.0.0 255.255.255.255 UH 0 0
> 0 ppp0
> 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0
> 0 eth0
> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0
> 0 eth0
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0
> 0 lo
> 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0
> 0 eth0
>
>
>
> I think I may need to do some forwarding with iptables. I did some
> forwarding/nat stuff I found from google but it didn't seem to help.
> I'm not too sure if NATing from the dialin server to another NAT
> gateway box would be stuffing my connection up at all? Also, no other
> firewalls/iptable stuff is on the dialin box.
>
> Any help is appreciated.

Hi Warren,

should work if you change your addresses in options.ttyS0 so they are
not part of your LAN, for example 192.168.1.100:192.168.1.101

At least that´s how it works now on my net with ISDN, i encountered the
same problem before.

HTH

Stephan Reihle

Stephan Reihle <(E-Mail Removed)> wrote in message news:<blrvdu$bu8$04
> Hi Warren,
>
> should work if you change your addresses in options.ttyS0 so they are
> not part of your LAN, for example 192.168.1.100:192.168.1.101
>
> At least that´s how it works now on my net with ISDN, i encountered the
> same problem before.
>
> HTH
>
> Stephan Reihle



Thanks for your reply Stephan,
seems it didn't work though. I tried putting 192.168.1.x IPs
in the options.ttyS0 file (i.e 192.168.1.100:192.168.1.101) and also
the local IP of the dialin server (192.168.0.75:192.168.1.101) but
both times the following error showed up in logs:
Cannot determine ethernet address for proxy ARP


And I still don't have network activity but it seems I am sending a
lot of packets but none are being returned. I guess it's a case of
forwarding/routing but not exactly sure how to fix this. Hopefully
someone has come across this before and knows how to fix it as nothing
in logs etc gives me a 'real clue' on how to fix it.

Warren

(E-Mail Removed) (Warren Smith) wrote in
news:(E-Mail Removed) om:

> Hi all,
> I'm trying to setup a dialin server on a redhat 7.3 box that sits
> on our network. The machine gets internet connection by a defaultroute
> on a gateway machine that NATs the machines on the 192.168.0.x LAN.
> The dialin server has one NIC that is connected to the lan/accesses
> the net. Basically, I have set it up so I should be able to dial in
> and use the net/LAN using a windows machine + dial up modem. I can
> connect to the machine, auth username/password but when I connect, no
> internet activity happens nor can I ping anywhere (net or lan or
> dialup server IPS) from the windows machine. The relative info is:
>
> The IP of eth0 on dialin is 192.168.0.75
> THE IP I have assigned for ppp0 is 192.168.0.76
>

> ---------------
> /etc/ppp/options.ttyS0
>
> 192.168.0.75:192.168.0.76
> netmask 255.255.255.0
>
<snip>

> Any help is appreciated.
>

Your options.ttyS0 file is the file that assigns the IP 192.168.0.75 or
192.168.0.76 to your connecting computer. However, 192.168.0.75 is ALREADY
ASSIGNED to the dialin server. Remove it from the options.ttyS0 file and
leave the .76 ip there. See if that works.

Just how did you assign 192.168.0.76 to ppp0? That should be done in the
options.ttyS0 file.



M

Warren Smith schrieb:
> Stephan Reihle <(E-Mail Removed)> wrote in message news:<blrvdu$bu8$04
>
>>Hi Warren,
>>
>>should work if you change your addresses in options.ttyS0 so they are
>>not part of your LAN, for example 192.168.1.100:192.168.1.101
>>
>>At least that´s how it works now on my net with ISDN, i encountered the
>>same problem before.
>>
>>HTH
>>
>>Stephan Reihle
>
>
>
>
> Thanks for your reply Stephan,
> seems it didn't work though. I tried putting 192.168.1.x IPs
> in the options.ttyS0 file (i.e 192.168.1.100:192.168.1.101) and also
> the local IP of the dialin server (192.168.0.75:192.168.1.101) but
> both times the following error showed up in logs:
> Cannot determine ethernet address for proxy ARP

What i meant is to give different IPs to eth0 and ppp0 of your
dialin-server. If both IFs share the same address the system runs into
problems with resolving them. Besides I don´t think you should give the
ppp0 a fixed address, it will get one according to your options.ttyS0
during connection.

Your log says that your remote-PC gets the address .76, have you checked
if your dialup-connection in Windoze is set to accept DHCP-addresses? If
so you should be able to ping the .75 from Windows.

>
> And I still don't have network activity but it seems I am sending a
> lot of packets but none are being returned. I guess it's a case of
> forwarding/routing but not exactly sure how to fix this. Hopefully
> someone has come across this before and knows how to fix it as nothing
> in logs etc gives me a 'real clue' on how to fix it.
>
> Warren

CU

Stephan Reihle

Warren Smith <(E-Mail Removed)> wrote:

> I'm trying to setup a dialin server on a redhat 7.3 box that sits
> on our network. The machine gets internet connection by a defaultroute
> on a gateway machine that NATs the machines on the 192.168.0.x LAN.
> The dialin server has one NIC that is connected to the lan/accesses
> the net. Basically, I have set it up so I should be able to dial in
> and use the net/LAN using a windows machine + dial up modem. I can
> connect to the machine, auth username/password but when I connect, no
> internet activity happens nor can I ping anywhere (net or lan or
> dialup server IPS) from the windows machine. The relative info is:

I didn't see a thing wrong with anything in your post *except* that you
seem to want to use the mgetty AutoPPP feature but don't require PAP
authentication, and that the use of the pppd option "login" requires
an entry for the call-in username in the system password database (see
"man pppd" - do you really have a username /AutoPPP/ there? as well
as a suitable entry in pap-secrets. The username is obtained from the
"user username" option required by PAP authentication.

Beyond that, posting exact copies of the "heap of LCP lines removed",
including timestamps, might be helpful in determining why it appears
that PPP negotiations successfully complete but the dial-in is unable
to even ping the "server" IP address.

It's okay (and normal) for the server's local IP address for the
PPP interface to be the same as the one for the LAN, but the dial-in
IP address must belong to the subnet for the LAN if you want to get
beyond the server.

-- Clifford Kite Email: "echo xvgr_yvahk-(E-Mail Removed)|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/
/* Editing with vi is a lot better than using a huge swiss army knife.
Use =} to wrap paragraphs in vi. Or put map ^] !}fmt -72^M in
~/.exrc and use ^] to wrap to 72 columns or whatever you choose. */

Warren Smith <(E-Mail Removed)> wrote:

> I'm trying to setup a dialin server on a redhat 7.3 box that sits
> on our network. The machine gets internet connection by a defaultroute
> on a gateway machine that NATs the machines on the 192.168.0.x LAN.

There is one other thing that might be causing a problem, separate
from the previously mentioned PAP authorization. If this is true NAT,
and not SNAT or masquerade, then I suspect you'll have to provide a
"client identifier" for the host dialing in since it doesn't have a MAC
address. This is mentioned in RFC 2131, and further described in RFC
1533. I have no idea whether Linux DHCP supports client-identifiers.

---
Clifford Kite Email: "echo xvgr_yvahk-(E-Mail Removed)|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/
/* The generation of random numbers is too important to be left
to chance. */