Qubes networking asssistance

Hi folks,

I’m having an issue that I just don’t know how to resolve.

I want to get Qubes Networking Guest to set up and allow for the connections of other guests, but not have any of the Qubes Scripts initiate the connections between things with the forwarding and all.

Is anyone able to assist me in getting this set up please?
I just don’t know what files I need to be looking at.
I have removed, altered and broken files many times.

Would appreciate some help.
If need be, can set up for screen sharing and converse if needed.

I understand the first part of this, but not the second.
Have you read this?

Is anyone able to assist me in getting this set up please?
I just don’t know what files I need to be looking at.
I have removed, altered and broken files many times.
When you are working on a file, take a backup first. That way, you can
quickly revert to the state before your changes. Make this second nature.

Happy to help, but it would help us if you detailed what you have done and
with what result.

I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.

I want to not have all the rulesets there, and want to disable it from starting.
Used to be that the proxy script would be what does it all, so I have tried removing content, deleting files completely, and writing other startup scripts to clear and nullify things to do with the IPs and all.

And no, I have not read that as that is related to NFT’s. I don’t have any NFTs.

I’ve done so many things just trying to get things to work.
To say what I have done I would have to go back and try to do it all again with the same results to tell you. I have no idea of EVERYTHING I have done.

Just knowing what to try and how to do it may actually tell me, if it works, I may have done something the wrong way…

That is why I generally, ,when asking for help, don’t give specifics on what I have done as people will think “Oh, he’s already tried that.” and no think about that method, as I may have just done one thing out of order or incorrectly in accordance with the way Qubes needs things to be done. For example, a while ago the altered sudo and su applications that TITL have created for Qubes I was trying to fix things in relation to that application and many things in Qubes broke immediately due to the fact that it didn’t return any data immediately. So many many things just didn’t want to work as it didn’t wait for a command to finish executing before it continued and read the result of the application output.
Just bad programming in that regard. Probably just something unforseen and not thought about for security. Still trying to work that one out though, and resolve it so that it can work properly and efficiently without causing that break.

I do not understand you. What does mean “I don’t have any NFTs”?
I suggest that you do read it as it explains how to allow traffic
between qubes, which is what you say you want to do.

I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.

I mean I have no NFTs anywhere. I just have IPTABLES.

I have read it, and I do allow traffic between all things using it, and I use it to allow and disallow things on my networking machines.

So I want to get it all disabled so things will work properly, efficiently, and use less resources than these NFTs

What are these templates you are using that dont use nftables?

I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.

Debian primarily, or else Devuan or other fast systems

There is a lot of crap that I remove from the templates to speed them up to be NetVMs.

The light weight templates just miss a tonne of things that are needed to even make them work properly.
The heavy templates are just way too heavy that I have to remove a tonne of stuff, often reducing it by 3-4 GB in size allowing it to be a basic NetVM.

I mean NFT is just an interface for IPT, so I remove NFT as it isn’t needed and I just directly access and use IPT.

Just makes things easier to remove layers that aren’t required.