Is your friend masquerading the internal network? If he is not, then there is no way a private IP can be routed to the outside world. Avi --On Monday, September 24, 2001 08:49:30 PM +0100 Richard Ibbotson wrote:

Problem comes when I want to do routing between the internal LAN and the net. The range of the internal LAN is 192.168.1.1 to 192.168.1.10. The connection by DHCP from www.blueyonder.co.uk is something like 62.31.22.0. So, it's a bit obvious that routing may not be possible. Tried to play about with this but it doesn't want to know. -- Avi Schwartz avi@CFFtechnologies.com

"I have to share the credit. I invented it, but Bill made it famous." - IBM engineer Dave Bradley describing the control-alt-delete reboot sequence

on the machine connected to dsl do echo "1" > /proc/sys/net/ipv4/ip_forward ipchains -F ipchains -P forward DENY ipchains -A forward -s 192.168.1.0/24 -j MASQ that should do it if you are using a 2.4 kernel on the box, add the following command modprobe ipchains note, this is not a real firewall, but rather just a way to share the internet connection with the lan. you can add other rules as needed. On Mon, 24 Sep 2001, Richard Ibbotson wrote:

Dear All

Had a phone call from a friend today. He was asking me about configuring a gateway box to connect his LAN to the net with ADSL. He couldn't get it to work so I went round there and had a look. Confused me completely.

I'm going over to ADSL eventually at home so I thought it might be a good idea to get involved with this so that I can understand what to do with my own network.

He's got two 100Mb network cards in the machine. eth1 is the card that goes up to his ISP. The connection is configured at boot time with DHCP. This would seem to be working fine. I can ping www.suse.de and any other address out there on the net. eth0 is the internal card and I can ping any machine internally with another computer.

Problem comes when I want to do routing between the internal LAN and the net. The range of the internal LAN is 192.168.1.1 to 192.168.1.10. The connection by DHCP from www.blueyonder.co.uk is something like 62.31.22.0. So, it's a bit obvious that routing may not be possible. Tried to play about with this but it doesn't want to know.

How do I get round this ? Bootp or something else ? I had thought about running a DHCP server on the same box but this isn't really possible on a firewall machine.

Configuration for eth0 and eth1 can be seen below.......

ifconfig eth0

eth0 Link encap:Ethernet HWaddr 00:10:A7:09:BB:1C inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::210:a7ff:fe09:bb1c/10 Scope:Link inet6 addr: fe80::10:a709:fe09:bb1c/10 Scope:Link UP BROADCASTING RUNNING MULTICAST MTU:1500 METRIC:1 RX packets:2284 errors:0 dropped:0 overruns:0 frame:0 TX packets: 341 errors:0 dropped:0 overruns:0 carrier:0 collisions:1 txqueuelen:100 RX bytes:478325 (467.1 Kb) TX bytes:52076 (50.8 Kb) Interrupt:11 Base address:0xbf00

ifconfig eth1

eth1 Link encap:Ethernet HWaddr 00:10:A7:09:B2:83 inet addr:62.31.22.85 Bcast:255.255.255.255 Mask:255.255.255.0 inet6 addr: fe80::10:a709:b283/10 Scope:Link inet6 addr: fe80::210:a7ff:fe09:b283/10 Scope:Link UP BROADCASTING RUNNING MULTICAST MTU:1500 METRIC:1 RX packets:2707 errors:0 dropped:0 overruns:0 frame:0 TX packets: 587 errors:0 dropped:0 overruns:0 carrier:0 collisions:1 txqueuelen:100 RX bytes:200794 (196.1 Kb) TX bytes:82298 (80.3 Kb) Interrupt:9 Base address:0xde00

netstat -rn

Kernel IP routing table

Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 40 0 0 eth0 62.31.22.0 0.0.0.0 255.255.255.0 U 40 0 0 eth1 0.0.0.0 62.31.22.1 0.0.0.0 UG 40 0 0 eth1

-- Richard

-- 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