[LARTC] Dynamic nat with iproute2 and kernel 2.4.18

Linux Advanced Routing and Traffic Control

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I have one issue that I am hoping you can help me with. After thoroughly researching this issue I can't seem to find any solution to the following situation in our school lab setup:

The server is Gateway/Firewall/DHCP server
IPTables ver: 1.2.6a
Kernel: 2.4.18 (Red Hat)
Cable Modem (with DHCP for external address)
Internal network: 192.168.1.0/24
Internal interface: eth0
External interface: eth1
Internally we use DHCP service to allocate ips to the student PCs. (192.168.1.0/24) mask (255.255.255.0)

Internal Clients: Student laptops


Classroom lab purpose: We have a lab setup for students to use their laptops. The students bring their laptops to the lab and connect to the network to download their homework and study material, or to take exams/quizes.

Classroom lab setup: The lab is using the network layout described above with the Linux server as the Gateway, Firewall, and DHCP server; and the internal network is configure to use the 192.168.1.0/24 network. We have students who bring their own laptops from home; some laptops are DHCP enabled and others are using static configuration per their home network. Things work great for students with their the laptops enabled with DHCP. We run into problems where the laptops are not using DHCP, they have trouble talking on the network to the servers.

Goal of what I am trying to do: I would like to use iproute2 and iptables to dynamically nat any ip that is not using an ip in the 192.168.1.0/24 network; so that any non 192.168.1.0/24 ip gets natted by iproute2 or iptables to 192.168.1.0/24 network and hence can talk on that network to other machines and use the Linux Gateway (192.168.1.1) to access the internet to do research while in class. I've heard that expensive Cisco routers are able to do this and so am hoping Linux is able to do this as well since our budget is tight and can't afford the expensive hardware.

The key here is to basically nat any ip that is not using the 192.168.1.0/24 range so that we can allow them to talk on the 192.168.1.0/24 network transparently.

Any help is greatly appreciated.

Thanks in advance


-- 
_______________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup



[Index of Archives]     [LARTC Home Page]     [Netfilter]     [Netfilter Development]     [Network Development]     [Bugtraq]     [GCC Help]     [Yosemite News]     [Linux Kernel]     [Fedora Users]
  Powered by Linux