Radule; for the system that is behind the let's call it NAT box or Router, just put as the default route of client box = ip of NAT box. I again am not familiar with the dial package......but would image that when that NAT box which has the dial-up, gets "interesting packets" (Cisco term for packets destined for external Nets) it should dial-up. Some others here on the list should be able to help you with parameters for Wvdial or whichever package you need for that, but routing between the boxes is quite easy. BTW, if you are using DHCP on NAT box for the clients add a switch in dhcp.conf like this: option routers x.x.x.x The ip to use would be the internal NIC IP as the clients will use that as their route and the NAT box will translate the IP into the external for packets that are destined for the external nets. Regards, Jon On Fri, 20 Apr 2001, Radule Soskic wrote:
Hi, Jon. Thanx for quick answer! I know for dialup and for DHCP... But, what to do in order to share the connection to Internet between A and B? And, how to initiate dialing on comp. A sitting at B? Also I need details how to put all this together...I think comp. A should become a kind of router, or what? By the way, when I put DHCPd in order, I enabled pinging between A and B, but my dialup stop working. Exactly, dialing itself still works, but after I get connected, I don't ping outside network anymore.. IP on eth0 (A) 172.16.1.1 IP on eth0 (B) 172.16.1.2-5 IP on ppp (A) 192.168.1.xxx
Regards,
rms
marsaro@interearth.com wrote:
Radule;
I have not used a dial-up modem in quite some time, but there is a package in SuSE that does this......wvdial I think.
For the NAT, use SuSEfirrewall
DHCP.....DHCPd
Regards,
Jon
On Fri, 20 Apr 2001, Radule Soskic wrote:
Hello all!
I have two computers (call them A and B) in my network. Comp. B is DHCP client to A. Comp. A also dials out to my ISP, being DHCP client to ISP server. (I can order dialing both from A and B) Both computers share the dialed-out Internet connection. My internal IP addresses set on NICs A and B are "invisible" from the outside network (NAT is in place)...
All this was easily set up in Windows, using program WinRoute. What to do to match this functionality in SuSE 7.0 or 6.4 ?
Best regards,
rms
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com