Any good Discussion forums?

I have years experience and training in networking / routing / voip and all the things. Im looking for discusions on all things network related from layer 1 - 7.. lets say a guy finds a bgp bug, and discusses it with others, or maybe someone created a new sub protocol for tcp that works better eith current standard wireless.. if you understand what i mean?

I want to stick with your top post. If you want to start a new topic on layer 1 - 7 then you do that.

This is how most forums work. It's frowned on to go too far from the opening topic. And I'm one of those that won't diverge from the opening questions.

So again, why do you think setting the correct IP range is not useful?

Setting the correct IP range to devices is common knowledge. This will in some cases help solve a problem, but only by bypassing it. It does not resolve the problem.

And thanks

I've been using IP networking for decades and you claim setting the correct IP range is a bypass to a problem.

That's news to me. As well as resetting devices. Very odd view you have there. How long have you been setting up IP networks? Me? Decades.

There are 2 clients in different ranges, and they wish to communicate with each other.

In my opinion, telling the client to change his address would solve the problem yes, but it would imply he has no services bound to that specific range and has no problem with downtime.

A proper solution to this would be either to masquerade the destination and source addresses on the router, or to create a bridge with multiple addresses. (bridging it will cause downtime though, but it saves you a frustrating conversation )

I have been setting up networks for about 4 years.

It's fairly advanced and you are straying from your opening topic.

Why is a bridge causing downtime?

And how did the IT setup such a mess?

The bridge would cause downtime depending on how fast you can set it up for you will have to disable the 10 range gateway and apply it onto the bridge, causing connections to drop of the connection table. same goes to the other range.

And about the IT haha ... almost every other guy with a piece of grey matter in their heads can plug in a switch (sometimes they even can't )

A routing option would also be viable, but only if there was another router / gateway device on either side.

But regarding that statement "almost had a suggestion" any link to a forum popped up maybe?

It's accepted to reboot things after changes to be sure of the setup. It's going to reboot someday and if the changes don't survive a boot then you would get a call back.

Your view of no reboot is going to get you burned over time. That is, you strike me as not new but not seasoned enough. Time will help you there.

Yes a device will have to reboot at some point in its lifetime. I'm with you on that point.

Then on the other hand, keeping a connection from dropping whilst changing settings on the device, and knowing there will be no downtime.. Those are the forums I'm looking for. People talking about how they did it and others discussing how they would have and sharing their personal experience around the topic.

But not seasoned.

"keeping a connection from dropping whilst changing settings on the device, and knowing there will be no downtime.."

If you manage to do that, you are now a magician.

I'm only an electronics designer, coder, and have written router code long ago so while I can discuss IP networking your goals sound wishful. As in "I wish it would not drop after or during network changes."

Of course I use Linux, but in that I can create extra "bookmarks" in my file manager which are multiple network connections and not be limited to just one route. In windows I would think making a second network connection describing the IP route and workgroup name should be sufficient.

Such as windows wanting to use 10.0.0.0 range but the router and other computers all lined up on 192.168.0.0 range? what would you tell the window user to do for finding the others and the work group they were on?