Did not work as expected
Simon Hobson
simon at thehobsons.co.uk
Mon Jun 29 21:05:46 UTC 2015
Leandro <ingrogger at gmail.com> wrote:
> shared-network Public {
> What is wrong ?
What you have drawn is ***NOT*** a shared network.
It seems you did not digest that from the previous discussion regarding your network architecture.
To recap, a shared network is where there are two (or more) subnets ON THE SAME BIT OF WIRE (or more technically, on the same broadcast domain).
So, looking at your diagram, in Cisco speak you have something like :
interface Fastethernet0/1
ip address 192.168.88.1 255.255.255.128
interface Fastethernet0/2
ip address 192.168.88.129 255.255.255.128
Or in Linux speak :
ip addr add 192.168.88.1/25 dev eth1
ip addr add 192.168.88.129/25 dev eth2
Two separate networks, separate broadcast domains, separate IP subnets.
For it to be a shared network, both subnets would need to be defined on the **SAME** interface of your router :
interface Fastethernet0/1
ip address 192.168.88.1 255.255.255.128
ip address 192.168.88.129 255.255.255.128 secondary
Or :
ip addr add 192.168.88.1/25 dev eth1
ip addr add 192.168.88.129/25 dev eth1 <- note same device
I'll reiterate, you REALLY REALLY must get these very basic IP networking concepts sorted - if you don't then you WILL struggle to build a working and reliable network.
Once you have the network and IP topology sorted, then you must accurately describe that to the DHCP server - that means NOT declaring a shared network where you do not have one.
More information about the dhcp-users
mailing list