| 25 Jun 2025 |
 hexa (clat on linux when) | not super motivated, given that I don't have people with apple hardware in my close vicinity | 13:45:59 |
| hexa (clat on linux when) | * not super motivated to retry that, given that I don't have people with apple hardware in my close vicinity | 13:46:06 |
 emily | macOS has native CLAT support and should auto-detect the relevant flags and do the right thing | 13:47:09 |
| emily | I think the only desktop OS where it reportedly "just works" | 13:47:28 |
| hexa (clat on linux when) | that is what I thought | 13:47:30 |
| emily | (Windows still gates its support for WWAN only…) | 13:47:34 |
 Sandro 🐧 | it fixed some olde androids for us | 13:50:37 |
| Sandro 🐧 | iPhones also work fine | 13:50:50 |
| hexa (clat on linux when) | if it doesn't fix sip that is not helping | 13:58:44 |
| hexa (clat on linux when) | I mean, part of the issue was that the access concentrator was on IPv4 only | 13:59:08 |
| Sandro 🐧 | probably not | 14:55:54 |
| Sandro 🐧 | could be that it is similar to what breaks kde connect | 14:56:01 |
| Sandro 🐧 | it partically works but as soon as you want to send a file and it tries to do ssh for that it breaks | 14:56:25 |
| Sandro 🐧 | as for that it uses ipv4 and the eg. laptop does not accept the IP from the proxy | 14:56:39 |
| hexa (clat on linux when) | we only provided 464xlat and not for linux | 14:57:04 |
| hexa (clat on linux when) | nothing sets up a clat on linux automatically | 14:57:11 |
 Tom | At least on Apples Mobile Systems (iOS/iPadOS) they aren't doing proper source address selection for the CLAT.
They'll happily use a seemingly random one of the configured ones. Even deprecated or ULA doesn't seem to bother them. :/ | 15:13:12 |
| emily | fun | 15:14:30 |
|  @freexploit:trafkin.com joined the room. | 16:28:16 |
 matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | In what way is a bridge different from a macvtap? | 16:44:43 |
 adamcstephens | a macvtap is for creating a new interface attached to another individual interface. A bridge can link, or "bridge", multiple interfaces together | 16:46:02 |
| matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | I'm trying to make a nixos module for this https://github.com/lampmerchant/tashrouter?tab=readme-ov-file#creating-a-macvtap-device | 16:48:24 |
| matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | They recommend something like this: | 16:48:32 |
| matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | * They recommend something like this:
# ip link add link eth0 name macvtap0 type macvtap
# ip link set dev macvtap0 promisc on
# ip link set dev macvtap0 up
| 16:48:35 |
| matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | But then in https://68kmla.org/bb/index.php?threads/tashrouter-an-appletalk-router.46047/page-5#post-518796
Someone says:
I experimented with the recommended macvtap interface but found it to be somewhat poorly documented.
In theory it's supposed to function like a bridge+tap, but I could not get that to work properly.
| 16:48:54 |
| matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | For whatever reason his code only supports running on a tap/macvtap
router = Router('router', ports=(
LtoudpPort(seed_network=1, seed_zone_name=b'LToUDP Network'),
TashTalkPort(serial_port='/dev/ttyAMA0', seed_network=2, seed_zone_name=b'TashTalk Network'),
MacvtapPort(macvtap_name='macvtap0', seed_network_min=3, seed_network_max=5, seed_zone_names=[b'EtherTalk Network']),
))
| 16:49:54 |
| matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | Wondering why that could be.. | 16:50:04 |
| matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | When you make a macvtap, is it not bridged to the interface it's part of automatically? | 16:52:47 |
| matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | Does macvtap work on wifi? | 17:09:58 |
| matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) | maybe that is my issue | 17:10:19 |
