Hi Steve,

I have a few comments:

1) have you enabled ip forwarding on the linux machine?  Among other,
better ways, you can use this crude method;

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

2) on point to point connections you don't really have a gateway as
all packets are going to the other end of the wire.

I think that should be enought,

soyeb


> Hi all!  I know there is a lot in this e-mail, but please read through the whole 
> thing.  Here, I need to give some background, then describe the problem and list 
> out some configuration data...
> 
> I've been using Miami v3.0 for a while (yes, I'm registered) to connect to my 
> dial-up ISP.
> 
> I want to do something different now with Miami, and most of it is working, but 
> part is not.
> 
> I now have a new ISP, a cable modem service.  Attached to my cable modem is a 
> cable router (linksys). Attached to the cable router are 2 of my PCs, one is a 
> Win98 box, the other Linux.  These systems work great to connect to each other 
> and the internet using the cable router as their gateway.
> 
> Anyway, my amiga, I decided, I would like to have disconnected from my old 
> dial-up ISP and instead, be hosted by my linux box (which now has it's own 
> internet connection through the cable router).  (i.e., not connecting the Amiga 
> to the cable router directly, but using PPP to connect the Amiga to the Linux 
> box which would run a PPP server.
> 
> So, now, I have a PPP server running on my linux box.  I have the linux box 
> connected to my Amiga (Amiga 2000 '040 with O.S. 3.9, Miami V 3.0) box via 
> serial ports (no modems).  One side has a null modem, the other side does not, 
> and communication is done with 4-wire telephone wire (pins 2, 3, 7, and 20).
> 
> Anyway, I was very successful in this endeavor.  :)  Using Miami, I am able to 
> connect my Amiga via PPP to my PPP server, the linux box!  It really worked.
> 
> They can now ping each other.  They can communicate with each other, transfer 
> files, etc.
> 
> [ I am *not* using DHCP on the Linux server to serve IPs.  Nor is the Amiga 
> using DHCP to get the IP. ]
> 
> [ I've assigned the Amiga the IP address (192.168.1.4) that the linux box 
> (192.168.1.2) wants the amiga to have  --set through the linux  PPP server's 
> options file as you'll see below--, and have given the amiga a hostname (not 
> fully qualified).  Miami seems to get and set the Amiga's IP properly. ]
> 
> Things look good so far... but...
> 
> I can communicate fully between the linux box and the amiga, however, the amiga 
> cannot see *past* thelinux box.  The linux box uses the IP address(192.168.1.1) 
> of the Cable Router box as it's gateway tothe Internet and the other machine on 
> my local lan.
> 
> I need to somehow inform Miami what to use as it's gateway.  In other TCP/IP 
> implementations, there's usually a section for entering a gateway or router IP.  
> But for serial PPP in Miami, I have not found a way to enter the gateway.  Any 
> thoughts?  Below is some more information and some things I tried.
> 
> (** Note that When I would connect my Amiga to my old *dial-up* ISP, the gateway 
> is set automatically from the ISP.  I did not have to set anything on my Amiga 
> directly in Miami.  Miami got it somehow from the ISP. **   Not so in the case 
> described here...)
> 
> 
> My Linux box's IP is 192.168.1.2 (behind the cable router)
> My Amiga box's IP is 192.168.1.4
> My cable router box's IP is 192.168.1.1
> 
> On the Amiga side, here is the output from ifconfig:
> 
> lo0: flags=8009<up.loopback,multicast>mtu=2108
>       inet 127.0.0.1 netmask FF000000
>       HW Type:  Loopback
>       
> mi0: flags=8011<up,pointtopoint, multicast>mtu=296
>       inet 192.168.1.4 --> 192.168.1.2  netmask FFFFFF00
>       HW Type: other
> 
> The Linux box's PPP serving options are:
> 
> 
> asyncmap 0
> local
> xonxoff
> lock
> +pap
> -chap
> 38400
> 192.168.1.2:192.168.1.4    # sets the gateway and ip address for dial-in
>       
> 
> Using the above, I can communicate back and forth between my linux box and the 
> amiga, no problem, but my amiga cannot see outside the linux box (i.e., it 
> cannot see the cable router or anything else on the local lan.)
> 
> Now, if I change the last line in the linux box's PPP options to:
> 
> 192.168.1.1:192.168.1.4    # sets the gateway and ip address for dial-in      
> 
> Where now the gateway for PPP is set to the cable router IP, and restart the PPP 
> server on the linux box, the amiga can still communicate with the linux box (as 
> before), but can *NOW* also ping the cable router!  That's a slight improvement.
> 
> However, the amiga can not ping anything else on my local lan, nor can it see 
> the Internet... It can only see it's PPP server host (the linux box) and the 
> cable router.
> 
> So, doing as above, and now seeing the cable router, still does not seem to 
> configure the Amiga (through Miami) to use the cable router as a gateway.
> 
> Here is the linux box's PPP server log file when I have the linux box as the 
> gateway and have the Amiga connect to it:
> 
>   Using 192.168.1.2:192.168.1.4 in PPP's options file (PPP server -- LINUX)
>       192.168.1.4 is the amiga box connecting in.  This works, but
>         no gateway.
> 
> May 21 23:16:23 linux1 pppd[6578]: pppd 2.3.11 started by root, uid 0
> May 21 23:16:23 linux1 pppd[6578]: Using interface ppp0
> May 21 23:16:23 linux1 pppd[6578]: Connect: ppp0 <--> /dev/ttyS1
> May 21 23:16:41 linux1 pppd[6578]: local  IP address 192.168.1.2
> May 21 23:16:41 linux1 pppd[6578]: remote IP address 192.168.1.4
> May 21 23:30:15 linux1 pppd[6578]: local  IP address 192.168.1.2
> May 21 23:30:15 linux1 pppd[6578]: remote IP address 192.168.1.4
> May 21 23:39:52 linux1 pppd[6578]: local  IP address 192.168.1.2
> May 21 23:39:52 linux1 pppd[6578]: remote IP address 192.168.1.4
> 
> 
> 
> Here is the linux box's PPP server log file when I have the cable rotuer as the 
> gateway and have the Amiga connect to it:
> 
>   Using 192.168.1.1:192.168.1.4 in PPP's options file (PPP server -- LINUX)
>       but setting the cable router to be the gateway for ppp.
>       192.168.1.4 is the amiga box connecting in.  This works, but
>       again, no gateway
>       
>       
> 
> May 22 00:14:10 linux1 pppd[7235]: Connect: ppp0 <--> /dev/ttyS1
> May 22 00:14:24 linux1 pppd[7235]: local  IP address 192.168.1.1
> May 22 00:14:24 linux1 pppd[7235]: remote IP address 192.168.1.4
> May 22 00:23:07 linux1 su: (to root) steve on /dev/pts/4
> May 22 00:29:38 linux1 pppd[7235]: Terminating on signal 2.
> May 22 00:29:38 linux1 pppd[7235]: Connection terminated.
> May 22 00:29:38 linux1 pppd[7235]: Connect time 15.5 minutes.
> May 22 00:29:38 linux1 pppd[7235]: Sent 2196 bytes, received 5611 bytes.
> May 22 00:29:38 linux1 pppd[7235]: Exit.
> 
> Note that all the machines on the current lan including the cable router can see 
> each other just fine, and all the machines on the current lan use the cable 
> router as the gateway to the Internet.
> 
> It's just the Amiga that cannot see past what I've described above.
> 
> Thanks so much for any sugggestions any of you can offer.  Again, I think it's 
> mainly being able to set the gateway through Miami that's holding this up from 
> working.
> 
> Oh, and does Miami 3.2b add the gateway setting option?
> 
> Steve Rifkin - JHU CS Dept Sr. Unix Systems Administrator
>                Technical Director
> [EMAIL PROTECTED]
> 
> -- 
> 
> To unsubscribe send "unsubscribe miami-talk-ml" to
> "[EMAIL PROTECTED]". For help on list commands send "help" to
> "[EMAIL PROTECTED]".
> 
> 
> 

-- 
email: [EMAIL PROTECTED]
www: http://www.soyeb.homeip.net
work: http://www.tertio.com
-- 

To unsubscribe send "unsubscribe miami-talk-ml" to
"[EMAIL PROTECTED]". For help on list commands send "help" to
"[EMAIL PROTECTED]".


Reply via email to