Cannot ping another subnet? (SOLVED)

Derelict · Feb 20, 2016, 4:50 PM

You have a host with an interface configuration of 10.10.2.86/21. Its broadcast address is 10.10.7.255.

you mean 10.10.2.255?

No, I mean 10.10.7.255. That is the IP broadcast address for a host configured with 10.10.2.86/21. Don't believe me, how about my handy calculator?

And it doesn't matter. 10.10.1.255 != 10.10.2.255 either.

Quick question how come its possible with iptables they can ping each other by adding the rules.

Don't know don't care. That design is broken. I don't hassle making broken configs "work". I fix them.

![Screen Shot 2016-02-20 at 8.47.23 AM.png](/public/imported_attachments/1/Screen Shot 2016-02-20 at 8.47.23 AM.png)
![Screen Shot 2016-02-20 at 8.47.23 AM.png_thumb](/public/imported_attachments/1/Screen Shot 2016-02-20 at 8.47.23 AM.png_thumb)

killmasta93 · Feb 21, 2016, 7:53 PM

thanks for the replies,
alright so let me start from scratch

So all the servers will be on the 10.10.1.0/24

pfSense will have an Ip of 10.10.1.218 the gateway

with LAN 10.10.1.218/24

Then the windows server 2012r2 which has an ip of 10.10.1.200
gives out the DHCP of 10.10.2.0/24

So would i need to reconfigure my DHCP scope?

So i setup a separate test environment

internet–----pfSense-------switch-----computer static ip 10.10.2.86/24

I see the arp but when i try to ping nothing :(
Thank you

Derelict · Feb 21, 2016, 9:27 PM

Dude.

Then the windows server 2012r2 which has an ip of 10.10.1.200 gives out the DHCP of 10.10.2.0/24

10.10.1.0/24 and 10.10.2.0/24 need to be different network segments. THEY CANNOT SHARE THE SAME WIRE (aka broadcast domain) if you want the network to behave in a sane fashion.

killmasta93 · Feb 21, 2016, 9:42 PM

Dude.

Im so sorry im not sure why im so confused if its this week..

Alright i got that it has to be a different segment which he has it right now as 10.10.2.86 with subnet of 255.255.248.0

So not sure what I need to change or am i overthinking it?

Thank you and sorry for being so retarded :(

Derelict · Feb 21, 2016, 9:57 PM

Two different segments - two different pfSense interfaces (physical or VLAN). with routing between 10.10.1.0/24 and 10.10.2.0/24.

Like I said that network needs a complete redesign.

killmasta93 · Feb 23, 2016, 2:33 AM

WELLL i feel like an idiot….all i had to do is change pfSense LAN to /21 .....i dont know why i complicated myself something so simple..

Thanks again

Derelict · Feb 23, 2016, 5:54 AM

SMH

killmasta93 · Feb 23, 2016, 6:17 PM

its those days that nothing works out…But now that i told my friend to change the whole network hes going back to 192.168.1.1/24 and putting VLANS so the network does not get congested

Thanks again

Derelict · Feb 23, 2016, 6:23 PM

If you're going to renumber and redesign, take the opportunity to get off 10/8 and 192.168.0.0 and 192.168.1.0/24.

For VPN purposes, it's better to be on networks that do not conflict with a billion or so other networks worldwide.

A couple random choices:

172.28.95.0
192.168.213.0

killmasta93 · Feb 23, 2016, 6:24 PM

Good idea Will take your advice :)