Jacob --
Good to hear from you again. I don't know what the proxy ARP problem is (or
even if it is a problem), but the ping problem is a simple one. For the
client, you are using a subnet-10 address; these are addresses that cannot
be sent directly to the Internet (192.168 addresses are similar Class C
addresses, and there's also a Class B block that I can never remember).
You need to run such addresses through a host that will intermediate between
these addresses and "real" IP addresses. On Linux, the relevant feature is
called IP Masquerading. There's a HowTo on it, I believe, and while I have
no personal experience running this package, the many who do usually say it
is fairly straightforward to implement.
On the other hand, if all you are trying to do is to get e-mail relayed,
where the client will be using POP3 or IMAP to access the Linux server, none
of this matters. In this limited case, the client doesn't need to access
hosts beyond your PPP server. You need to address this only if you want to
use Internet services like telnet, http, and ftp directly from the client to
other Internet hosts.
AsS to your mgetty problem, see comments below, interspersed with the
escerpts of your posting.
At 09:38 PM 5/15/99 +0600, IBRIC - International Buddhist Research & Info.
Center wrote [brief excerpts only]:
>May 14 17:58:46 Col7 pppd[668]: Cannot determine ethernet address for proxy ARP
>
>>May 14 17:58:46 Col7 pppd[668]: Cannot determine ethernet address for
proxy ARP
>
>I have an ethernet card in the Client which is not yet connected to anything,
>perhaps the above message is about this card.
Very possibly.
>May 14 11:58:10 dhamma pppd[1505]: Connect: ppp0 <--> /dev/ttyS1
>May 14 11:58:13 dhamma pppd[1505]: local IP address 172.16.1.10
>May 14 11:58:13 dhamma pppd[1505]: remote IP address 10.1.1.1
>May 14 11:58:13 dhamma pppd[1505]: ppp not replacing existing default route
>to eth0[204.143.107.33]
This is the use of the subnet-10 address. The message about not replacing
the default route is okay -- you don't want to change that.
>
>after the PPP is up,
>I can ping host IP address 172.16.1.10
>I can ping host 204.143.107.46
>
>but I cannot ping 204.143.107.33 the gateway of the Host at my ISP.
>and I cannot ping out into the net.
This is the subnet-10 problem showing itself.
>I have read in the /usr/info/mgetty.info1
>that mgetty should be able to stay resident without interupting outgoing calls
>
>I will have to have mgetty up on the client
>as you might remember the client is also a "mail-server"
>to "Win95 persons" who will log in to get their mail.
>
>You are quite right in suggesting that mgetty is locking the modem.
>below are some files at a time when I have mgetty up on the Client side.
As I read the logs below, mgetty is NOT initializing the modem. Instead, it
is FAILING to initialize the modem (the last 3 strings sent return ERROR,
not OK). This may affect its willingness to release the lock. Does it say
what it is waiting for in the last message -- the one you posted only part of?
This is only a guess, though -- as I've said before, I'm no mgetty expert --
I used agetty, which watches the DCD line instead of waiting for a text
string and doesn't try to do any locking while watching for an incoming call.
>/var/log/log_mg.modem
>
>05/14 18:16:09 dem waiting for ``RING''
>05/14 18:16:19 dem timeout in chat script, waiting for `RING'
>05/14 18:16:19 dem huh? Junk on the line?
>--
>05/14 18:16:19 dem mgetty: experimental test release 1.1.5-Apr16
>05/14 18:16:19 dem check for lockfiles
>05/14 18:16:19 dem locking the line
>05/14 18:16:19 dem lowering DTR to reset Modem
>05/14 18:16:20 dem send: \dATQ0V1H0[0d]
>05/14 18:16:20 dem waiting for ``OK'' ** found **
>05/14 18:16:20 dem send: ATS0=0Q0&D3&C1[0d]
>05/14 18:16:20 dem waiting for ``OK'' ** found **
>05/14 18:16:21 dem mdm_send: 'ATI'
>05/14 18:16:21 dem Generic Rockwell modem (33600) -> OK
>05/14 18:16:21 dem mdm_send: 'AT+FCLASS=2' -> ERROR
>05/14 18:16:21 dem mdm_send: 'AT+FCLASS=2.0' -> ERROR
>05/14 18:16:21 dem mdm_send: 'AT+FCLASS=2' -> ERROR
>05/14 18:16:21 dem waiting...
># mgetty has obviously not removed its lock file
>05/14 18:17:26 dem lock not made: lock file exists (pid=729)
>--
>05/14 18:18:11 dem mgetty: experimental test release 1.1.5-Apr16
>05/14 18:18:11 dem check for lockfiles
>05/14 18:18:11 dem locking the line
>05/14 18:18:12 dem lowering DTR to reset Modem
>05/14 18:18:12 dem send: \dATQ0V1H0[0d]
>05/14 18:18:13 dem waiting for ``OK'' ** found **
>05/14 18:18:13 dem send: ATS0=0Q0&D3&C1[0d]
>05/14 18:18:13 dem waiting for ``OK'' ** found **
>05/14 18:18:13 dem mdm_send: 'ATI'
>05/14 18:18:13 dem Generic Rockwell modem (33600) -> OK
>05/14 18:18:13 dem mdm_send: 'AT+FCLASS=2' -> ERROR
>05/14 18:18:13 dem mdm_send: 'AT+FCLASS=2.0' -> ERROR
>05/14 18:18:13 dem mdm_send: 'AT+FCLASS=2' -> ERROR
>05/14 18:18:13 dem waiting...
># mgetty has obviously not removed its lock file
>05/14 18:25:27 dem lock not made: lock file exists (pid=996)
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
762 Garland Drive
Palo Alto, CA 94303-3603
650.328.4219 voice [EMAIL PROTECTED]
----------------------------------------------------------------
