Re: [gentoo-user] Re: Local mail server
On 8/7/20 2:06 PM, james wrote: Here is an short read on the acceptance and usage of IPv6: https://ungleich.ch/u/blog/2020-the-year-of-ipv6/ So, yes I am working on using IPv6, with my RV/mobile-lab. I think that IPv6 is a good thing. But I would be remis to not say that IPv6 is somewhat of a black sheep in the email administrators community. You still effectively must have IPv4 connectivity to your email server, lest a non-trivial percentage of email fail to flow. I also know of a number of email administrators that are specifically dragging their feet regarding IPv6 because there hasn't yet been critical mass use of IPv6 /for/ /email/. In fact, some of the early IPv6 adopters for email are spammers. So some administrators stim this tide by being exclusively IPv4. I think dual stack for email servers is great. (Deal with the spam.) But being exclusively IPv6 on an email server is going to be problematic. I'm focusing on email servers because that's what this thread had largely been about. -- Grant. . . . unix || die
Re: [gentoo-user] Re: Local mail server
On 8/1/20 2:45 PM, Grant Taylor wrote: On 7/31/20 1:54 PM, Grant Edwards wrote: If I had a week with nothing to do, I'd love to try to get something like that working You don't need a week.� You don't even need a day.� You can probably have a test tunnel working (on your computer) in less than an hour. Then maybe a few more hours to get it to work on your existing equipment (router) robustly and automatically on reboot. I encourage you to spend that initial hour.� I think� you will find that will be time well spent. Hurricane Electric does have something else that will take more time, maybe a few minutes a day over a month or so.� Their IPv6 training program (I last looked a number of years ago) is a good introduction to IPv6 in general.� Once you complete it, they'll even send you a shirt as a nice perk. Note:� H.E. IPv6 training is independent and not required for their IPv6-in-IPv4 tunnel service. but, I assume you need a static IPv4 address. Nope.� Not really. You do need a predictable IPv4 address.� I'm using a H.E. tunnel on a sticky IP (DHCP with long lease and renewals) perfectly fine. If your IP does change, you just need to update the tunnel or create a new one to replace the old one.� This is all manged through their web interface. Here is an short read on the acceptance and usage of IPv6: https://ungleich.ch/u/blog/2020-the-year-of-ipv6/ So, yes I am working on using IPv6, with my RV/mobile-lab. hth, Jams
[gentoo-user] which bitcoin app to use?
hi - which btc app to use? one in portage? or one in the overlay `bitcoin'? and why? rgrds, cm.
Re: [gentoo-user] Cant get wpi_cli going on Lenovo T400
On Wednesday, 5 August 2020 21:25:09 BST Walter Dnes wrote: > I want to do this manually, before automating it; "ifconfig -a" shows > eth0, and lo, and... > > wlan0: flags=4098 mtu 1500 > ether 00:26:c6:4a:b4:92 txqueuelen 1000 (Ethernet) > RX packets 0 bytes 0 (0.0 B) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 0 bytes 0 (0.0 B) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > Next steps are to start wpa_supplicant and wpa_cli > > === > > [thimk][root][~] /etc/init.d/wpa_supplicant start > * Starting WPA Supplicant Daemon ... > Successfully initialized wpa_supplicant [ > ok ] > > [thimk][root][~] wpa_cli > wpa_cli v2.9 > Copyright (c) 2004-2019, Jouni Malinen and contributors > > This software may be distributed under the terms of the BSD license. > See README for more details. > > > > Interactive mode > > Could not connect to wpa_supplicant: (nil) - re-trying > > === > > Even specifying "wpa_cli -i wlan0" fails. The config files... > > > # /etc/conf.d/net > = > config_eth0="dhcp" > > modules="wpa_supplicant" > config_wlan0="dhcp" > > # /etc/wpa_supplicant > = > # The below line not be changed otherwise wpa_supplicant refuses to work > ctrl_interface=/var/run/wpa_supplicant > > # Ensure that only root can read the WPA configuration > ctrl_interface_group=0 > > # Let wpa_supplicant take care of scanning and AP selection > ap_scan=1 These settings are the same here, with two exceptions. The config file is: # ls -la /etc/wpa_supplicant/wpa_supplicant.conf -rw--- 1 root root 77640 Jun 18 2019 /etc/wpa_supplicant/ wpa_supplicant.conf and, ctrl_interface_group=wheel The former is relevant because the default openrc script requires '/etc/ wpa_supplicant/wpa_supplicant.conf', unless you have modified it. The latter most likely not relevant - but it allows me to change settings in the wpa_supplicant GUI. signature.asc Description: This is a digitally signed message part.
