We haven't forgotten that, but we're also aware that non-IT people can't run NAT either. They can plug in a box that already has NAT configured though, and if they can manage that then they can also plug in a box that already has a firewall configured.
VMs work fine without NAT too -- DHCPv6-PD lets the VM software automatically request a routed prefix.
but for that to work, you need to attach an antenna, no? and where do i get such an FM transmitter? AND android does not support it in the software level, and there's no protocol for the waves?
To have an FM receiver work on a phone, you do need an antenna, the wired headphones serve that purpose perfectly. An FM transmitter is easy to find; you can use the simple 'Jack-to-FM' adapters designed for car radios, or much better, a USB SDR (which can range from a few kHz to GHz).
Regarding the 'protocol for the waves,' you'll need to play with modulation. That’s the fun part. In technical literature, there are many well-defined modulations (like AFSK or FSK) with clear suggested applications for low-SNR environments.
As for Android support, I have no idea. I understand that in this thread, 'free' sounds like 'freedom,' but freedom has a cost. The freedom of communication requires investment: in hardware, software, and the time to learn the physics of the environment.
It depends on which step of the staircase, from pure hardware to pure software, you want to position yourself. Some projects require staying closer to the metal, while others can be purely software. I move up and down this staircase depending on the specific requirements.
If the requirement is to communicate where consumer standards like Bluetooth fail, like in a ship, you have to choose the system for the environment. I evaluate these choices like an architect building a robust system, rather than just using what is available at the nearby shop.
is there an actual real good comparison of bitchat vs. briar from all sides? protocols, cryptography, supplychain, which software stack, usability and so on?
yes, but question can be done in different ways. and tilo jung always at least, not cared, if his questions are offensive... or trying to up the interviewed person
a group of people seems to think, that journalists should trip up people, like in interrogations, instead of being hard in the topic but nice in the tone.
Yeah, that sentiment surely exist that PR and journalism is not the same. Some would even argue that journalism should try to find facts and that being particularly pleasant and nice with doing so is secondary to the goal of fact finding, it’s not PR after all. One could even go as far as to speculate that a journalist being “nice” is not genuine but just a method to gain information. I know I am biased here as this is how I want it to be.
The case if Tilo is quite specific, his interview style uses methods that are effective and uncommon and in part extremely unpleasant, but super effective in making people a accidentally confess to him whilst forgetting all their media training.
Yes on the same computer. Pretty much every multicast-capable host has a unicast address and has multicast groups that they join when they get an IP address. [0] Edge routers almost always have -at minimum- a global address and a "site-local" address. Any host that has multiple active interfaces can have multiple "categories" of addresses assigned to it.
You might also be unaware of the fact that network interfaces can usually be assigned multiple IPv4 addresses, just like they can be assigned multiple IPv6 addresses.
> ...the application does not have to figure out which one it has to use.
You might be surprised to learn that that's the job of the routing table on the system. Applications can influence the choices made by the system by binding to a specific source address, but the default behavior used by nearly everything is to let the system handle all that for you.
[0] You appear to be unaware that multicast addresses aren't assigned to a host. I suspect you're unaware that IPv6 removed the special-case "broadcast" address. It's now treated as what it actually is; the "all hosts" multicast address.
* (S|D)NAT are not first class citizen in IPV6 Standards and Implementation
* there's no mapping of the IPv4 Adresspace into the v6 space, so people can reroute stuff which is needed.
because only then, we can
a) migrate
b) rebuild the same structures.
> as long as [...] (S|D)NAT are not first class citizen in IPV6 Standards and Implementation
Yeah, I mostly agree... IMO, a ULA (equivalent to RFC1918, so 192.168.x.x and so forth) is the only sane way to set up your IPv6 network at home, unless you're one of the wizards who owns their own prefix. Dynamic prefix delegation just breaks too many things when the prefix changes, and I really wish NPTv6 was more supported and ubiquitous, because it solves the problem in the most elegant way IMO.
> there's no mapping of the IPv4 Adresspace into the v6 space
You don't need NPTv6 to use ULA. Just use both ULA and the dynamic prefix from your ISP. The latter is handled automatically by DHCPv6-PD, and if you're only using it for outbound connections then it changing isn't going to break anything.
I'd say this is actually elegant, compared to NPTv6 which is a kludge and will break things (and isn't well-supported anyway).
I definitely do both ULA and GUA at home, but this only really works well to the degree that the OS will prefer the ULA when connecting to things. Like if I want to put hostnames in netgroups, I need reverse DNS to work (which only works if the client is using the ULA address I expect.) In fact the whole idea of reverse lookups working and having expected hostnames show up where you want them to (logs, etc) really depends on not only using ULA for connections, but using the stable address and not the privacy address, which can also cause issues.
For the most part it works today, if I stick to using ULA’s only in my zone file, and configure hosts to prefer the DHCPv6-provided ULA for connections in the ULA subnet, it’s fine. But suddenly if you connect to somehost.local instead of somehost.fqdn, the machine picks a GUA source address and you’re back to being unpredictable.
So although I say I want to use NPTv6 and be ULA-only, I don’t actually do that today, so I’m not super familiar with the downsides to the approach. But it does sound a lot cleaner to me in theory.
> if you're only using it for outbound connections then it changing isn't going to break anything.
A prefix change absolutely does break things in a lot of setups though. It happens something like:
- Your router reboots unexpectedly (no time to rescind the RA)
- Router comes up and gets a new prefix, starts advertising it
- Clients are brain dead and continue using the old prefix when making outbound connections.
I’ve had this happen and both Apple devices and Linux devices (I had no Windows machines) kept using the old prefix until I went around and rebooted them. So connecting to any IPv6 WAN address would fail, and only IPv4 was saving me from my internet being down until I went and manually rebooted everything.
There have since been RFC’s that come up with recommendations for routers to keep a stateful log of old prefixes, so that they can rescind them (advertise a zero TTL) when a new prefix arrives… but afaict none of them actually do this.
NAT (in all its forms) is just a very convenient technology for many people and niche situations.
And adoption of IPv6 will be hindered as long as NAT is not a first class citizen.
And of course, mostly NAT should not be used as "firewall replacement". But what many firewall proponents forget here:
NON-IT People at home cannot run and manage a firewall (and proxies). For them, NAT is a convenient and mostly okayish replacements.
Another niche would be IP Packet Handling of VMs.
reply