Paul Walsh
asked on
One VLAN two IP ranges, how is this possible?
Hi All,
We have two firewall devices with their own sperate internal ip ranges say 192.168.1.0 subnet 255.255.255.0 and 192.168.2.0 subnet 255.255.255.0. Both are set to act as dhcp servers. Both internally are connected to the same VLAN. I am assuming these work as the company that manages them have not reported there are problems and they have been in place this way for a good few years.
If I plug my laptop into a switch port untagged on this vlan I receive an ip address from the first device. I cannot see the other device. If I statically assign a free IP on the other range (device 2) I cannot ping this device (the gateway) or basically do anything.
How is this possible? I am clearly missing something, but I was under the impression that each VLAN only has one IP range and not two.
Sorry if this is a simply answer but I really cant get my head around this.
Kind Regards,
Paul
We have two firewall devices with their own sperate internal ip ranges say 192.168.1.0 subnet 255.255.255.0 and 192.168.2.0 subnet 255.255.255.0. Both are set to act as dhcp servers. Both internally are connected to the same VLAN. I am assuming these work as the company that manages them have not reported there are problems and they have been in place this way for a good few years.
If I plug my laptop into a switch port untagged on this vlan I receive an ip address from the first device. I cannot see the other device. If I statically assign a free IP on the other range (device 2) I cannot ping this device (the gateway) or basically do anything.
How is this possible? I am clearly missing something, but I was under the impression that each VLAN only has one IP range and not two.
Sorry if this is a simply answer but I really cant get my head around this.
Kind Regards,
Paul
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Yes that is probably the best approach.
ASKER
Sorry for the delay in getting back to you. It could very well be meant as a failover, the setup has been in place for ages and the people at the support company who put it in place have since moved on.... I think its time to start a fresh and do it correctly. Thanks for your help.