February 2019 - WLUG - wlug.mailman3.com

Reminder: NO MEETING TODAY!

by Tim Keller

Just a reminder, the meeting has been moved to Feb. 21st. Thanks, Tim. -- I am leery of the allegiances of any politician who refers to their constituents as "consumers".

Feb. 14, 2019

How do I get on daily emails only??

by John Spencer

I keep getting individual emails. I have tried to change the setting so I only get emails daily not every time someone posts. Can you please make this change for me. Thanks Regards, John Spencer Connected Systems Partners Office: (978) 455-5550 x208 Cell: (978) 621-9743 jspencer(a)connectedsp.com<mailto:jspencer@connectedsp.com> www.connectedsp.com<http://www.connectedsp.com/> GET CONNECTED! All information in this email, unless indicated otherwise in the body of the email, is considered confidential and intended for the view and use of the recipient(s) only.

Feb. 13, 2019

Re: charter.net is blocking all Digital Ocean droplet email

by Kevin Stratton

I am not sure if this is off topic, but there were quite a few pay email services a while ago. I use https:/www.fastmail.com for the freedoom to switch ISPs without affecting email. They do support Thunderbird if you use an application specific password. Depending on your bandwith/storage usage, this might be an acceptable solution. On 2/13/19 1:19 PM, Steven Greenberg via WLUG wrote: > For at least a dozen years I have had my own website on GoDaddy. > I also use my GoDaddy email as my main email route. (Although > Thunderbird is getting ungodly slow of late as an email client.) > > I never want to be dependent on "free" email services like gmail. > > I am willing to pay a service like GoDaddy, so that places like > Google and Facebook can't dictate what I can do just because they > provide their services for "free". > > Charter did not start out to be a computer service provider. That's > probably why I don't want to depend on Charter for computer > services more than I have to. At the moment, Charter is the only > reasonable service of internet connection to my house. > > /Steve > > On 2/12/2019 9:24 PM, John Stoffel via WLUG wrote: >> >> I need to vent here. Charter.net which provides my internet, sucks. >> They are now refusing to accept email from *any* IP blocks owned by >> Digital Ocean, even though I've got a good mail setup on a droplet >> there, with proper DNS entries, SPF, etc. >> >> So I'm looking to spin up a new instance on some other provider, or >> I'm going to try and route the email via my @charter.net account that >> I have since I'm a customer. >> >> And I have opened a ticket with them. No answer. Jerks. >> >> What do people think of Vultr.com? Seems pretty comparable... I just >> wonder when Charter will block their IP blocks... >> >> Jerks. >> >> I think it's too expensive to buy an IPv4 address for more permanent >> use, since it's too easy for that block of 256 to be blanket banned by >> some jerks. >> >> Grr!!!!! >> >> John >> _______________________________________________ >> WLUG mailing list -- wlug(a)lists.wlug.org >> To unsubscribe send an email to wlug-leave(a)lists.wlug.org >> >> > >

Feb. 13, 2019

Re: charter.net is blocking all Digital Ocean droplet email

by Steven Greenberg

For at least a dozen years I have had my own website on GoDaddy. I also use my GoDaddy email as my main email route. (Although Thunderbird is getting ungodly slow of late as an email client.) I never want to be dependent on "free" email services like gmail. I am willing to pay a service like GoDaddy, so that places like Google and Facebook can't dictate what I can do just because they provide their services for "free". Charter did not start out to be a computer service provider. That's probably why I don't want to depend on Charter for computer services more than I have to. At the moment, Charter is the only reasonable service of internet connection to my house. /Steve On 2/12/2019 9:24 PM, John Stoffel via WLUG wrote: > > I need to vent here. Charter.net which provides my internet, sucks. > They are now refusing to accept email from *any* IP blocks owned by > Digital Ocean, even though I've got a good mail setup on a droplet > there, with proper DNS entries, SPF, etc. > > So I'm looking to spin up a new instance on some other provider, or > I'm going to try and route the email via my @charter.net account that > I have since I'm a customer. > > And I have opened a ticket with them. No answer. Jerks. > > What do people think of Vultr.com? Seems pretty comparable... I just > wonder when Charter will block their IP blocks... > > Jerks. > > I think it's too expensive to buy an IPv4 address for more permanent > use, since it's too easy for that block of 256 to be blanket banned by > some jerks. > > Grr!!!!! > > John > _______________________________________________ > WLUG mailing list -- wlug(a)lists.wlug.org > To unsubscribe send an email to wlug-leave(a)lists.wlug.org > > -- Steven Greenberg Email: steve(a)ssgreenberg.name 251 Holland Rd. Phone: (774)241-0095 Fiskdale, Massachusetts 01518-1231 Web: www.ssgreenberg.name Other Email: s.greenberg(a)ieee.org ssg(a)alum.mit.edu

Feb. 13, 2019

charter.net is blocking all Digital Ocean droplet email

by John Stoffel

I need to vent here. Charter.net which provides my internet, sucks. They are now refusing to accept email from *any* IP blocks owned by Digital Ocean, even though I've got a good mail setup on a droplet there, with proper DNS entries, SPF, etc. So I'm looking to spin up a new instance on some other provider, or I'm going to try and route the email via my @charter.net account that I have since I'm a customer. And I have opened a ticket with them. No answer. Jerks. What do people think of Vultr.com? Seems pretty comparable... I just wonder when Charter will block their IP blocks... Jerks. I think it's too expensive to buy an IPv4 address for more permanent use, since it's too easy for that block of 256 to be blanket banned by some jerks. Grr!!!!! John

Feb. 13, 2019

Re: Openvpn and Network mapping

by Higgins, Benjamin J

Nick: Reminder... just because you *can* doesn't mean you *should*. That is all. --ben From: Krichevsky, Nicholas Jacob via WLUG <wlug(a)lists.wlug.org> Sent: Sunday, February 3, 2019 11:26 AM To: Worcester Linux Users' Group General Discussion <wlug(a)lists.wlug.org>; Levasseur, Kenneth <klevasseur(a)wpi.edu> Cc: Krichevsky, Nicholas Jacob <njkrichevsky(a)wpi.edu> Subject: [WLUG] Re: Openvpn and Network mapping The goal was to expose the LAN, mostly for fun, but what you're describing is certainly the more practical way of solving the port forwarding problem directly. If I can't solve the routing problem, this might just end up being my fallback. Get Outlook for Android<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2Fg…> ________________________________ From: Levasseur, Kenneth Sent: Sunday, February 3, 2019 8:52:38 AM To: Worcester Linux Users' Group General Discussion Cc: Krichevsky, Nicholas Jacob Subject: Re: Openvpn and Network mapping I hit some keys and it sent the message early. Not sure what happened there. Do you need to route the entire network, or just access the NAS and other hosts? I think you could do something with SSH reverse tunneling, given you have a VPS. On the NAS: ssh -R <desired_port>:localhost:22 user@<vps_address> Then, once you've ssh'd into the VPS from anywhere else: ssh localhost -p <desired_port> Now you're ssh'd into the NAS. The desired port could be anything but it needs to be the same on both ends. This also assumes your VPS has a static IP/dynamic dns, and you may need some way to keep the connection alive if it's going to be up for a long time. ________________________________ From: Levasseur, Kenneth via WLUG <wlug(a)lists.wlug.org<mailto:wlug@lists.wlug.org>> Sent: Sunday, February 3, 2019 8:48:34 AM To: Worcester Linux Users' Group General Discussion Cc: Krichevsky, Nicholas Jacob; Levasseur, Kenneth Subject: [WLUG] Re: Openvpn and Network mapping Do you need to route the entire network, or just access the NAS and other hosts? I think you could do something with SSH reverse tunneling, given you have a VPS. On the NAS: ssh -R <desired_port>:localhost:22 user@<vps_address> Then, once you've ssh'd into the VPS from anywhere else: ________________________________ From: Krichevsky, Nicholas Jacob via WLUG <wlug(a)lists.wlug.org<mailto:wlug@lists.wlug.org>> Sent: Sunday, February 3, 2019 1:42:35 AM To: Worcester Linux Users' Group General Discussion Cc: Krichevsky, Nicholas Jacob Subject: [WLUG] Openvpn and Network mapping So I've found myself in an unfortunate situation where I cannot port forward on my router. My solution to this was to setup an openvpn tunnel on my VPS that would allow me to access my LAN via a NAS that I keep online in my apartment. (In other words, my laptop would connect to my VPS, which would route to my apartment via my NAS, and thus expose the LAN). The big problem is that the network uses 192.168.1.0/24, and given that I cannot edit any router settings, I cannot change this. If I were to simply expose this subnet via openvpn, I wouldn't be able to access any other 192.168.1.0/24 address if I were connect to the VPN. My plan was to try and use some iptables magic to map 10.24.0.0/24 to 192.168.1.0. Luckily, this works, thanks to the NETMAP extension (iptables -A PREROUTING -t nat -d 10.24.0.0/24 -j NETMAP --to 192.168.1.0/24, for the curious). However, the only way I can make this work is if I add the NAS as a gateway on all of the machines I want to connect to on my LAN, which is a bit sad (ip route add 192.168.255.0/24 via 192.168.1.69) . Is there some way I can make this a bit more seamless? This isn't my least favorite solution, as I don't need to run the openvpn client on every host, but it isn't much better...

Feb. 4, 2019

Re: Openvpn and Network mapping

by Krichevsky, Nicholas Jacob

The goal was to expose the LAN, mostly for fun, but what you're describing is certainly the more practical way of solving the port forwarding problem directly. If I can't solve the routing problem, this might just end up being my fallback. Get Outlook for Android<https://aka.ms/ghei36> ________________________________ From: Levasseur, Kenneth Sent: Sunday, February 3, 2019 8:52:38 AM To: Worcester Linux Users' Group General Discussion Cc: Krichevsky, Nicholas Jacob Subject: Re: Openvpn and Network mapping I hit some keys and it sent the message early. Not sure what happened there. Do you need to route the entire network, or just access the NAS and other hosts? I think you could do something with SSH reverse tunneling, given you have a VPS. On the NAS: ssh -R <desired_port>:localhost:22 user@<vps_address> Then, once you've ssh'd into the VPS from anywhere else: ssh localhost -p <desired_port> Now you're ssh'd into the NAS. The desired port could be anything but it needs to be the same on both ends. This also assumes your VPS has a static IP/dynamic dns, and you may need some way to keep the connection alive if it's going to be up for a long time. ________________________________ From: Levasseur, Kenneth via WLUG <wlug(a)lists.wlug.org> Sent: Sunday, February 3, 2019 8:48:34 AM To: Worcester Linux Users' Group General Discussion Cc: Krichevsky, Nicholas Jacob; Levasseur, Kenneth Subject: [WLUG] Re: Openvpn and Network mapping Do you need to route the entire network, or just access the NAS and other hosts? I think you could do something with SSH reverse tunneling, given you have a VPS. On the NAS: ssh -R <desired_port>:localhost:22 user@<vps_address> Then, once you've ssh'd into the VPS from anywhere else: ________________________________ From: Krichevsky, Nicholas Jacob via WLUG <wlug(a)lists.wlug.org> Sent: Sunday, February 3, 2019 1:42:35 AM To: Worcester Linux Users' Group General Discussion Cc: Krichevsky, Nicholas Jacob Subject: [WLUG] Openvpn and Network mapping So I've found myself in an unfortunate situation where I cannot port forward on my router. My solution to this was to setup an openvpn tunnel on my VPS that would allow me to access my LAN via a NAS that I keep online in my apartment. (In other words, my laptop would connect to my VPS, which would route to my apartment via my NAS, and thus expose the LAN). The big problem is that the network uses 192.168.1.0/24, and given that I cannot edit any router settings, I cannot change this. If I were to simply expose this subnet via openvpn, I wouldn't be able to access any other 192.168.1.0/24 address if I were connect to the VPN. My plan was to try and use some iptables magic to map 10.24.0.0/24 to 192.168.1.0. Luckily, this works, thanks to the NETMAP extension (iptables -A PREROUTING -t nat -d 10.24.0.0/24 -j NETMAP --to 192.168.1.0/24, for the curious). However, the only way I can make this work is if I add the NAS as a gateway on all of the machines I want to connect to on my LAN, which is a bit sad (ip route add 192.168.255.0/24 via 192.168.1.69) . Is there some way I can make this a bit more seamless? This isn't my least favorite solution, as I don't need to run the openvpn client on every host, but it isn't much better...

Feb. 3, 2019

Re: Openvpn and Network mapping

by Levasseur, Kenneth

I hit some keys and it sent the message early. Not sure what happened there. Do you need to route the entire network, or just access the NAS and other hosts? I think you could do something with SSH reverse tunneling, given you have a VPS. On the NAS: ssh -R <desired_port>:localhost:22 user@<vps_address> Then, once you've ssh'd into the VPS from anywhere else: ssh localhost -p <desired_port> Now you're ssh'd into the NAS. The desired port could be anything but it needs to be the same on both ends. This also assumes your VPS has a static IP/dynamic dns, and you may need some way to keep the connection alive if it's going to be up for a long time. ________________________________ From: Levasseur, Kenneth via WLUG <wlug(a)lists.wlug.org> Sent: Sunday, February 3, 2019 8:48:34 AM To: Worcester Linux Users' Group General Discussion Cc: Krichevsky, Nicholas Jacob; Levasseur, Kenneth Subject: [WLUG] Re: Openvpn and Network mapping Do you need to route the entire network, or just access the NAS and other hosts? I think you could do something with SSH reverse tunneling, given you have a VPS. On the NAS: ssh -R <desired_port>:localhost:22 user@<vps_address> Then, once you've ssh'd into the VPS from anywhere else: ________________________________ From: Krichevsky, Nicholas Jacob via WLUG <wlug(a)lists.wlug.org> Sent: Sunday, February 3, 2019 1:42:35 AM To: Worcester Linux Users' Group General Discussion Cc: Krichevsky, Nicholas Jacob Subject: [WLUG] Openvpn and Network mapping So I've found myself in an unfortunate situation where I cannot port forward on my router. My solution to this was to setup an openvpn tunnel on my VPS that would allow me to access my LAN via a NAS that I keep online in my apartment. (In other words, my laptop would connect to my VPS, which would route to my apartment via my NAS, and thus expose the LAN). The big problem is that the network uses 192.168.1.0/24, and given that I cannot edit any router settings, I cannot change this. If I were to simply expose this subnet via openvpn, I wouldn't be able to access any other 192.168.1.0/24 address if I were connect to the VPN. My plan was to try and use some iptables magic to map 10.24.0.0/24 to 192.168.1.0. Luckily, this works, thanks to the NETMAP extension (iptables -A PREROUTING -t nat -d 10.24.0.0/24 -j NETMAP --to 192.168.1.0/24, for the curious). However, the only way I can make this work is if I add the NAS as a gateway on all of the machines I want to connect to on my LAN, which is a bit sad (ip route add 192.168.255.0/24 via 192.168.1.69) . Is there some way I can make this a bit more seamless? This isn't my least favorite solution, as I don't need to run the openvpn client on every host, but it isn't much better...

Feb. 3, 2019

Re: Openvpn and Network mapping

by Levasseur, Kenneth

Do you need to route the entire network, or just access the NAS and other hosts? I think you could do something with SSH reverse tunneling, given you have a VPS. On the NAS: ssh -R <desired_port>:localhost:22 user@<vps_address> Then, once you've ssh'd into the VPS from anywhere else: ________________________________ From: Krichevsky, Nicholas Jacob via WLUG <wlug(a)lists.wlug.org> Sent: Sunday, February 3, 2019 1:42:35 AM To: Worcester Linux Users' Group General Discussion Cc: Krichevsky, Nicholas Jacob Subject: [WLUG] Openvpn and Network mapping So I've found myself in an unfortunate situation where I cannot port forward on my router. My solution to this was to setup an openvpn tunnel on my VPS that would allow me to access my LAN via a NAS that I keep online in my apartment. (In other words, my laptop would connect to my VPS, which would route to my apartment via my NAS, and thus expose the LAN). The big problem is that the network uses 192.168.1.0/24, and given that I cannot edit any router settings, I cannot change this. If I were to simply expose this subnet via openvpn, I wouldn't be able to access any other 192.168.1.0/24 address if I were connect to the VPN. My plan was to try and use some iptables magic to map 10.24.0.0/24 to 192.168.1.0. Luckily, this works, thanks to the NETMAP extension (iptables -A PREROUTING -t nat -d 10.24.0.0/24 -j NETMAP --to 192.168.1.0/24, for the curious). However, the only way I can make this work is if I add the NAS as a gateway on all of the machines I want to connect to on my LAN, which is a bit sad (ip route add 192.168.255.0/24 via 192.168.1.69) . Is there some way I can make this a bit more seamless? This isn't my least favorite solution, as I don't need to run the openvpn client on every host, but it isn't much better...

Feb. 3, 2019

Openvpn and Network mapping

by Krichevsky, Nicholas Jacob

So I've found myself in an unfortunate situation where I cannot port forward on my router. My solution to this was to setup an openvpn tunnel on my VPS that would allow me to access my LAN via a NAS that I keep online in my apartment. (In other words, my laptop would connect to my VPS, which would route to my apartment via my NAS, and thus expose the LAN). The big problem is that the network uses 192.168.1.0/24, and given that I cannot edit any router settings, I cannot change this. If I were to simply expose this subnet via openvpn, I wouldn't be able to access any other 192.168.1.0/24 address if I were connect to the VPN. My plan was to try and use some iptables magic to map 10.24.0.0/24 to 192.168.1.0. Luckily, this works, thanks to the NETMAP extension (iptables -A PREROUTING -t nat -d 10.24.0.0/24 -j NETMAP --to 192.168.1.0/24, for the curious). However, the only way I can make this work is if I add the NAS as a gateway on all of the machines I want to connect to on my LAN, which is a bit sad (ip route add 192.168.255.0/24 via 192.168.1.69) . Is there some way I can make this a bit more seamless? This isn't my least favorite solution, as I don't need to run the openvpn client on every host, but it isn't much better...

Feb. 3, 2019