Cập nhật thị trường tháng 1/2026: Honda Vision vẫn là cái tên "hot" nhờ thiết kế nhỏ gọn, động cơ eSP+ tiết kiệm nhiên liệu và tính thanh khoản cao. Đây vẫn là lựa chọn hàng đầu trong phân khúc xe tay ga.
#HondaVision #XeMay #TayGa #GiaXe
#Honda #Motorcycle #Scooter #Vietnam
https://vtcnews.vn/bang-gia-xe-honda-vision-moi-nhat-thang-1-2026-ar998214.html
5 mẫu xe tay ga bình dân (30‑50 triệu) phù hợp cho phụ nữ: thiết kế thời trang, tiết kiệm nhiên liệu, dễ lái và an toàn. Lựa chọn lý tưởng cho phái đẹp muốn sở hữu phương tiện cá tính mà không quá tốn kém.
#XeMáy #TayGa #PháiĐẹp #Women #Affordable #Scooter #Vietnam #XeDap #Motorbike #Style #BudgetFriendly
https://vietnamnet.vn/5-mau-xe-may-tay-ga-binh-dan-phu-hop-voi-phai-dep-2454410.html
@apalrd Have you been facing issues with #WiFiCalling while running #IPv6mostly in #OPNsense ?
I can't figure out exactly why it breaks in my home network, since there are no misconfigured rules nor anything related - if I disable DHCP option 108 and assign old addresses to each client, it works; when passing through #tayga #nat64, it stops entirely.
All this because the carrier's servers are stuck in the last millenium, of course they are: https://www.netify.ai/resources/mobile-gateways/country/br
I got asked if I could create a #howto for creating a (public) #NAT64 service - just like I did recently for #BoxyBSD. With #DNS64 and #NAT64 you can also reach resource in the legacy internet (#IPv4) on #IPv6 only systems.
While this is based on #unbound and #tayga, there’s also a solution by using the #OpenBSD's native way which is also running on the other gateway. I’ll share a second how to how to do this in OpenBSD and pf.
https://gyptazy.com/howto-create-a-public-dns64-nat64-gateway/
Maybe it *is* about time to go #IPv6only. Currently running my desktop without #IPv4 for testing.
The outside #IPv4 world is reachable with #NAT64 provided by #tayga running on my #FreeBSD router/firewall (with pf for stateful #NAT and actual firewalling), great! That's the most important part, I mean, nothing we can do about stubbornly operated v4-only stuff outside.
Now I identify all the stuff still not offering #IPv6 in my home network. Already fixed parts of my mail system and my irssi-proxy (for IRC). But there's more to check ... none of my VPN tunnels currently transport v6 ... and I'm still a bit unsure about all the devices (e.g. switch and access points in my management segment, or stuff like a vacuum robot or a kitchen radio in my IoT segment ... oh boy 😂🙈)
@goetz Ah wait, maybe first check how #tayga (in userspace) would perform (with classic pf #nat behind)
https://www.freshports.org/net/tayga/
#TIL #TAYGA and in general, #NAT64 concept.
https://thenewstack.io/tayga-bridge-an-ipv6-network-back-to-ipv4-using-nat64/
Pour un TP #IPv6 avec du #NAT64, j'ai utilisé #Tayga et c'est finalement assez simple et ça marche bien donc c'est utilisable pour un TP court.
(Honte : comme le but du TP était IPv6, pas le DNS, on a utilisé le résolveur DNS64 de Google. Je vais donner un million de brouzoufs à Framasoft pour m'excuser.)
