Broken network scenario is broken
-
a town has 2 streets with the exactly same name & numbering scheme.
it is impossible for guy/girl from the post office to deliver letters/packages to either of the 2 streets, because the addresses are identical.
-
When you come up with a network "design" such as the one mentioned in the OP, the real question here is "should I really maintain my firewall?!"
-
agreed, a reasonable amount of networking/subnet understanding is important. Maybe do some testing/learning first…
a friend test this same scenario but with Microsoft TMG, and it's worked fine !
micro$oft for a firewall lol, as if that's going to end well…
-
On product that support ended back in april to boot..
I don't know what your buddy was/is doing.. But you can not put the same network on 2 sides of a "router/firewall" and expect it to work… This is just networking 101..
-
Indeed what you're describing isn't valid with any router or firewall. It won't work reliably with TMG or any other device on Earth either, you can't have conflicting networks and have things work correctly. Subject corrected accordingly. :)
-
If your pfsense wan is 192.168.1.0/24 then make your lan 192.168.2.0/24 and you will be fine.. .
-
If your pfsense wan is 192.168.1.0/24 then make your lan 192.168.2.0/24 and you will be fine.. .
Yeah …. but this will be a thought one for Mgd_Elislam. cmb just told him that doing so will force him to change planets.
So, your advise will come in very hard ;Dedit: btw: love the new subject line !
-
Well, there's something on the Mars rover running OpenBSD I've been told, and it can't do it either. So won't even work on Mars! :D
It's a location-independent reality of networking. Yeah, use a diff subnet on LAN.
-
edit: btw: love the new subject line !
Noticed that right off and thought: That must mean all is OK, so this thread is not particularly useful - oh wait….... :o
-
How to make your own default gateway out of nothing?
Say, you have a gateway that isn't default. Of course, you can use the checkbox in the gateway settings to set it as default, but that's too easy.
In the 'System: Static Routes' add the following:
Destination network Gateway 0.0.0.0/1 your_gateway 128.0.0.0/1 your_gatewayNow 'your_gateway' is default, no matter what you see in the 'Diagnostics: Routing tables'. Ugly enough? Yes, but this technique is used by "AVAST SecureLine VPN" client, for example, and has stone-hard theoretical grounds.
"The Longest Prefix Always Wins", so, back to the topic, dear Mgd_Elislam, set your WAN IP to 192.168.1.2/30. Set your LAN IP to 192.168.1.4/24, newer use 192.168.1.3. Nowhere! Probably your friend used alike settings in TMG.
-
And that is still a broke setup using /30 on wan and /24 on lan since they STILL Overlap!!!
