- CheckMates
- :
- Products
- :
- Quantum
- :
- Security Gateways
- :
- Weird Networking configuration Question
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Weird Networking configuration Question
Hi,
it might be dummy question, just thinking out loud, maybe someone knows a way of making this work.
I have a FW with Lan interface (let's say eth0) with address: 192.168.1.254/16 (note the subnet)
this network includes servers, PCs, Printers etc.. now i'm required to do segmentation inside this network.
i want to keep this address range (not use 172.16./10.x.x.x.).
i thought of how can i accomplish this step at a time, without taking down the whole network to maintanance.
my quesion is as follows:
if i will create new interface (eth2) with address 192.168.2.254/24 and i will move some servers to this network.
1. is it supported to create interface with address that included/conflicted with other interface?
2.i need that the PCs and other Servers/devices still located on 192.168.0.0/16 network to keep communicating with the servers moved to 192.168.2.0/24 network. so i think how it might work is that FW should know to reply to arp request to servers on 192.168.2.0, and to respond on behalf (proxy arp) and then move the packet to 192.168.2.0 int, and packets to 192.168.0.0 expect from 192.168.2.0 will go to the 192.168.0.0/16 int. and also on the opposite direction that arp request to 192.168.3.0 for example from within 192.168.2.0 will respond by the fw and let the communication occur.
is anyone knows a way to make this happen ?
thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ok i can see that gaia not allow to configure this right on the interface config. it says that the address conflicts with destination network of interface (the original class b int)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
the only way to do these type of things is by using a layer 3 device in between the GW and the new network, so on eth2 you use a network 100.64.64.0/29 and connect that interface to a router/layer-3 switch.
Then you story remains the same, create proxy arps for each used IP in the 192.168.2/24 on eth0.
It also depends on the part on the /16 really being used, if only the bottom half of the /16 is used you can change the eth0 interface to a /17 and then add a new range in the top half. If 3/4 of the /16 is used you set a primary IP of 192.168.0.0/17 and add an alias for 192.168.128.0/18, then you have the top quarter available.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yeah, those are the conclusions i also came up with yesterday.
Thank you!
