Re: Firewall blocking my new Debian 11 server ports 80 and 443

On Wed, Jun 1, 2022 at 11:21 john doe wrote: > when does it actually start operating? Does it do so then, or does it take > > a reboot? > Apparently, if you 'enable' 'ufw', it will start and be enabled at boot. Good, thanks. According to (1), ufw should work with nftables, I did not follow

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On 6/1/2022 1:45 PM, Tom Browder wrote: On Mon, May 30, 2022 at 19:46 Edwin Zimmerman wrote: On 5/30/22 09:41, Greg Wooledge wrote: On Mon, May 30, 2022 at 07:13:54AM -0500, Tom Browder wrote: No worries. All those responses about the subject IP now are the norm for a bare-iron server

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On Mon, May 30, 2022 at 19:46 Edwin Zimmerman wrote: > On 5/30/22 09:41, Greg Wooledge wrote: > > On Mon, May 30, 2022 at 07:13:54AM -0500, Tom Browder wrote: > >> No worries. All those responses about the subject IP now are the norm > for a > >> bare-iron server ready for use by a customer,

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On 5/30/22 09:41, Greg Wooledge wrote: > On Mon, May 30, 2022 at 07:13:54AM -0500, Tom Browder wrote: >> No worries. All those responses about the subject IP now are the norm for a >> bare-iron server ready for use by a customer, yours truly. It is the same >> server I messed up the firewall with

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On Mon, May 30, 2022 at 1:24 PM Tom Browder wrote: > On Mon, May 30, 2022 at 09:03 IL Ka wrote: > >> IMHO: It is better to have a firewall and block (policy -- drop) INPUT >> and FORWARD by default. >> And open only ports that must be opened. >> This will hel

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On Mon, May 30, 2022 at 09:03 IL Ka wrote: > IMHO: It is better to have a firewall and block (policy -- drop) INPUT and > FORWARD by default. > And open only ports that must be opened. > This will help if you install some software that listens for 0.0.0.0 by > accident >

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On Mon, May 30, 2022 at 08:42 Greg Wooledge wrote: .. > Unless this machine is more than just a web server...? It does serve other purposes.

Re: Firewall blocking my new Debian 11 server ports 80 and 443

IMHO: It is better to have a firewall and block (policy -- drop) INPUT and FORWARD by default. And open only ports that must be opened. This will help if you install some software that listens for 0.0.0.0 by accident On Mon, May 30, 2022 at 4:42 PM Greg Wooledge wrote: > On Mon, May 30, 2

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On Mon, May 30, 2022 at 07:13:54AM -0500, Tom Browder wrote: > No worries. All those responses about the subject IP now are the norm for a > bare-iron server ready for use by a customer, yours truly. It is the same > server I messed up the firewall with and locked myself out of. The OS has > been

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On Mon, May 30, 2022 at 02:13 john doe wrote: > On 5/30/2022 12:26 AM, Tom Browder wrote: > > On Sun, May 29, 2022 at 15:55 Greg Wooledge wrote: No worries. All those responses about the subject IP now are the norm for a bare-iron server ready for use by a customer, yours truly. It is the

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On 2022-05-29, Greg Wooledge wrote: > > Second, I cannot ping this IP address, nor can I telnet to port 80 of it. > (Nor port 22.) > That's strange; I can ping it (I'm not in Kansas anymore): curty@einstein:~$ ping 69.30.225.10 PING 69.30.225.10 (69.30.225.10) 56(84) bytes of data. 64 bytes

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On 5/30/2022 12:26 AM, Tom Browder wrote: On Sun, May 29, 2022 at 15:55 Greg Wooledge wrote: ... Thanks, Greg. It looks like my server was blocked from ports 80 and 443 upstream from it (as you and others suspected), so I asked my provider to reinstall the OS and ensure it has public access

Re: Firewall blocking my new Debian 11 server ports 80 and 443

> Maybe I should remove all firewall progs and start from zero. I would suggest you install Shorewall. it is not the pain in the arse that's been the theme of this thread so far.

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On Sun, May 29, 2022 at 8:13 PM Greg Wooledge wrote: > On Sun, May 29, 2022 at 11:50:44PM +, Lee wrote: > > On 5/29/22, Greg Wooledge wrote: > > > Second, I cannot ping this IP address, nor can I telnet to port 80 of > it. > > > > For whatever it's worth.. > > > > Pinging 69.30.225.10 with

Re: Firewall blocking my new Debian 11 server ports 80 and 443

> > > ssh gives me a login prompt > > Btw, I highly recommend: * Block SSH access from any IP except one you are going to use to manage this server * If you have dynamic IP, you can add all your ISP network, or, at least, your country: (list can be downloaded here

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On Sun, May 29, 2022 at 11:50:44PM +, Lee wrote: > On 5/29/22, Greg Wooledge wrote: > > Second, I cannot ping this IP address, nor can I telnet to port 80 of it. > > For whatever it's worth.. > > Pinging 69.30.225.10 with 32 bytes of data: > Reply from 69.30.225.10: bytes=32 time=43ms

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On 5/29/22, Greg Wooledge wrote: > On Sun, May 29, 2022 at 03:39:05PM -0500, Tom Browder wrote: >> I have not intentionally hidden anything, Greg--I just never saw the need >> for >> mentioning it given the dialogue--x.y.z.w is just shorthand. If you >> must know the exact IP address, it is

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On Sun, May 29, 2022 at 15:55 Greg Wooledge wrote: ... Thanks, Greg. It looks like my server was blocked from ports 80 and 443 upstream from it (as you and others suspected), so I asked my provider to reinstall the OS and ensure it has public access to ports 80 and 443. Best regards, -Tom

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On Sun, May 29, 2022 at 03:39:05PM -0500, Tom Browder wrote: > I have not intentionally hidden anything, Greg--I just never saw the need for > mentioning it given the dialogue--x.y.z.w is just shorthand. If you > must know the exact IP address, it is 69.30.225.10. OK. Now we can actually start

Re: Firewall blocking my new Debian 11 server ports 80 and 443

t know the exact IP address, it is 69.30.225.10. (And you could have asked for it at any time--I don't remember anyone asking for it--but I will do so the next time I ask for this kind of help again.) GIven all the advice, I'm leaning towards the popular hypothesis that my provider has

Re: Firewall blocking my new Debian 11 server ports 80 and 443

> > > btw, are you able to ping server? > > > > Yes. > > It is always better to show the command and the output instead of saying > yes/no! :) Except it should be abundantly clear by now that you're dealing with someone who believes that they must hide every single detail from the ones who

Re: Firewall blocking my new Debian 11 server ports 80 and 443

> > > I must say, I can not realy understand how you can ping and not > telnet/access your web server. > > Some router between OP and his server has something like -I FORWARD -j REJECT --reject-with icmp-host-unreachable

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On 5/29/2022 7:20 PM, Tom Browder wrote: On Sun, May 29, 2022 at 11:39 IL Ka wrote: btw, are you able to ping server? Yes. It is always better to show the command and the output instead of saying yes/no! :) I must say, I can not realy understand how you can ping and not telnet/access

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On Sun, May 29, 2022 at 11:39 IL Ka wrote: > btw, are you able to ping server? > Yes.

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On Sun, May 29, 2022 at 05:41:59AM -0500, Tom Browder wrote: > On Sat, May 28, 2022 at 20:06 IL Ka wrote: > ... > > 3. You should also check that Apache is running and listening to this port, > > use ``ss -lt``. > > For this command you _may_ use sudo to get process names (``sudo ss > > -ltp``).

Re: Firewall blocking my new Debian 11 server ports 80 and 443

btw, are you able to ping server? On Sun, May 29, 2022 at 7:26 PM Tom Browder wrote: > On Sun, May 29, 2022 at 10:33 AM IL Ka wrote: > > > > > >> When running those, I'm told neither the arptablrs nor the ebtables are > registered (not installed). Should I install them? > > > > No. > > > > So,

Re: Firewall blocking my new Debian 11 server ports 80 and 443

> > > > and ``iptables -S`` ? > > -P INPUT ACCEPT > -P FORWARD ACCEPT > -P OUTPUT ACCEPT > -N f2b-sshd > -A INPUT -p tcp -m multiport --dports 22 -j f2b-sshd > -A f2b-sshd -s 61.177.173.50/32 -j REJECT --reject-with > icmp-port-unreachable > -A f2b-sshd -s 61.177.173.7/32 -j REJECT --reject-with >

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On Sun, May 29, 2022 at 10:33 AM IL Ka wrote: > > >> When running those, I'm told neither the arptablrs nor the ebtables are >> registered (not installed). Should I install them? > > No. > > So, you now have legacy (classic) iptables, right? Yes. > What is the output of ``iptables -L -v -n``

Re: Firewall blocking my new Debian 11 server ports 80 and 443

> When running those, I'm told neither the arptablrs nor the ebtables are > registered (not installed). Should I install them? > No. So, you now have legacy (classic) iptables, right? What is the output of ``iptables -L -v -n`` and ``iptables -S`` ?

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On Sun, May 29, 2022 at 09:51 IL Ka wrote: > >>> Do I have to switch all four *legacy *tables? >> > > yes > When running those, I'm told neither the arptablrs nor the ebtables are registered (not installed). Should I install them? >

Re: Firewall blocking my new Debian 11 server ports 80 and 443

> > >> Do I have to switch all four *legacy *tables? > yes

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On Sat, May 28, 2022 at 17:24 IL Ka wrote: > ... I am not familiar with nft, bit you can switch to iptables using >> ``update-alternatives`` >> > > # update-alternatives --set iptables /usr/sbin/iptables-legacy > # update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy > #

Re: Firewall blocking my new Debian 11 server ports 80 and 443

different systems will lead to inconsistency and erratic behiaviour. First thing is to identify what is putting the rules you showed us. (rules that do not block ports 80 and 443)

Re: Firewall blocking my new Debian 11 server ports 80 and 443

> > > > Good to know. But does fail2ban require ipset? > No, but having several thousand rules is not convenient, so I prefer ipset > They never have before in over 15 years, and, before I got this server > started, its mate was serving fine. But if the ufw doesn't work, I'll ask > them. > I'd

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On Sun, May 29, 2022 at 07:06 IL Ka wrote: > Does anyone have a good reason for me to NOT install and enable UFW? >> > > ufw can't be used with ipset AFAIK, and I use ipset for many reasons > (fail2ban, block access outside of my country etc). > But If you only SSH your host from one static IP,

Re: Firewall blocking my new Debian 11 server ports 80 and 443

> > > > Does anyone have a good reason for me to NOT install and enable UFW? > > ufw can't be used with ipset AFAIK, and I use ipset for many reasons (fail2ban, block access outside of my country etc). But If you only SSH your host from one static IP, you probably do not need fail2ban at all.

Re: Firewall blocking my new Debian 11 server ports 80 and 443

> > $ telnet x.y.z.w 80 > Trying x.y.z.w... > telnet: Unable to connect to remote host: No route to host > But you can ssh to this host, right? Well, that means the firewall blocks your request and sends the ICMP message "no route to host". Switch to the legacy iptables using

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On Sun, May 29, 2022 at 05:41 Tom Browder wrote: Does anyone have a good reason for me to NOT install and enable UFW? -Tom

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On Sat, May 28, 2022 at 20:06 IL Ka wrote: ... 3. You should also check that Apache is running and listening to this port, > use ``ss -lt``. > For this command you _may_ use sudo to get process names (``sudo ss > -ltp``). Read ``ss --help`` > > If you were able to connect on this host, then try

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On Sat, May 28, 2022 at 20:06 IL Ka wrote: > >> $ sudo su >> # telnet 80 >> Trying 0.0.0.80... >> > > 1. You are using telnet wrong: it should be "telnet [host] [port]". Please > read "man telnet". > 2. You do not need sudo to use telnet, do not do that > 3. You should also check

Re: Firewall blocking my new Debian 11 server ports 80 and 443

> > > $ sudo su > # telnet 80 > Trying 0.0.0.80... > 1. You are using telnet wrong: it should be "telnet [host] [port]". Please read "man telnet". 2. You do not need sudo to use telnet, do not do that 3. You should also check that Apache is running and listening to this port, use ``ss

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On Sat, May 28, 2022 at 19:10 Timothy M Butterworth < timothy.m.butterwo...@gmail.com> wrote: … On the local host try running `telnet 127.0.0.1 80` > I was able to connect, thanks, Timothy! Now what? I would really like to use ufw. -Tom

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On Sat, May 28, 2022 at 19:01 Greg Wooledge wrote: > On Sat, May 28, 2022 at 05:51:38PM -0500, Tom Browder wrote: > … > > ... wow. Just wow. How can such a short excerpt contain so many failures? Greg, calm down. I get it, but I haven’t unlearned years of muscle memory—sorry. And the

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On Sat, May 28, 2022 at 7:52 PM Tom Browder wrote: > > > On Sat, May 28, 2022 at 17:51 Tom Browder wrote: > >> On Sat, May 28, 2022 at 17:30 IL Ka wrote: >> >>> I am running an Apache server and using Qualys Lab’s server checker. It shows no access to the server. Have you tried

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On Sat, May 28, 2022 at 05:51:38PM -0500, Tom Browder wrote: > $ sudo su > # telnet 80 > Trying 0.0.0.80... ... wow. Just wow. How can such a short excerpt contain so many failures? 1) "sudo su" is stupid. You don't need TWO setuid programs to get a root shell. Either use

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On Sat, May 28, 2022 at 17:51 Tom Browder wrote: > On Sat, May 28, 2022 at 17:30 IL Ka wrote: > >> I am running an Apache server and using Qualys Lab’s server checker. It >>> shows no access to the server. >>> >>> Have you tried to telnet to port 80 from home? Do you see apache >> listening

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On Sat, May 28, 2022 at 17:30 IL Ka wrote: > I am running an Apache server and using Qualys Lab’s server checker. It >> shows no access to the server. >> >> Have you tried to telnet to port 80 from home? Do you see apache > listening this port using ``ss``? > On the new host I did: $ sudo

Re: Firewall blocking my new Debian 11 server ports 80 and 443

> > I am running an Apache server and using Qualys Lab’s server checker. It > shows no access to the server. > > Have you tried to telnet to port 80 from home? Do you see apache listening this port using ``ss``? > > Whatever attempt I make to change the ports disappears wh

Re: Firewall blocking my new Debian 11 server ports 80 and 443

Tom Browder wrote: > On Sat, May 28, 2022 at 14:11 Tom Browder wrote: > > > As the bare-iron server came from my long-time cloud provider (since > > Debian 6), incoming ports 80 and 443 are blocked. > > > A little more digging shows the new server is using fail

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On Sat, May 28, 2022 at 17:08 Dan Ritter wrote: … Therefore, something outside of your machine is blocking the > ports, or you are misreading or misusing the tools that are > telling you the ports are blocked. Tell us how you are checking the ports I am running an Apache server and

Re: Firewall blocking my new Debian 11 server ports 80 and 443

> > > > A little more digging shows the new server is using fail2ban and nft > tables, so I > need help on how to properly allow https and http inbound. > > I am not familiar with nft, bit you can switch to iptables using ``update-alternatives`` # update-alternatives --set iptables

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On Sat, May 28, 2022 at 14:11 Tom Browder wrote: > As the bare-iron server came from my long-time cloud provider (since > Debian 6), incoming ports 80 and 443 are blocked. A little more digging shows the new server is using fail2ban and nft tables, so I need help on how to properly allow

Re: Firewall blocking my new Debian 11 server ports 80 and 443

tore each network as separate rule. On my Debian server I use netfilter-persistent with ipset plugin and fail2ban. Works like charm! https://dhtar.com/make-ipset-and-iptables-configurations-persistent-in-debianubuntu.html <https://dhtar.com/make-ipset-and-iptables-configurations-persistent-in-de

Re: Firewall blocking my new Debian 11 server ports 80 and 443

On 5/28/22 22:11, Tom Browder wrote: > As the bare-iron server came from my long-time cloud provider (since > Debian 6), incoming ports 80 and 443 are blocked. > > I ran my usual iptables command for new servers from them, but this > time the default settings were different so

Re: Firewall blocking my new Debian 11 server ports 80 and 443

Tom Browder wrote: > As the bare-iron server came from my long-time cloud provider (since > Debian 6), incoming ports 80 and 443 are blocked. > > I ran my usual iptables command for new servers from them, but this > time the default settings were different so it didn't work. &

Firewall blocking my new Debian 11 server ports 80 and 443

As the bare-iron server came from my long-time cloud provider (since Debian 6), incoming ports 80 and 443 are blocked. I ran my usual iptables command for new servers from them, but this time the default settings were different so it didn't work. Output from "sudo iptables -S" before

Re: Fwd: blocking storage media usb ports under linux with dev

- De : *Frédérique Françoise Enama Binong* <mailto:enamabin...@gmail.com>> Date: jeu. 3 mars 2022 à 12:02 Subject: blocking storage media usb ports under linux with dev To: mailto:florian.ber...@free.fr>> hello, My name is Frédérique, I am a computer science student and I

Fwd: blocking storage media usb ports under linux with dev

-- Forwarded message - De : Frédérique Françoise Enama Binong Date: jeu. 3 mars 2022 à 12:02 Subject: blocking storage media usb ports under linux with dev To: hello, My name is Frédérique, I am a computer science student and I have a problem. I would like to have an udev

Ports stop working on Thunderbolt Docking Station

Hi. I have Thunderbolt docking station and ports including USBs and HDMIs stop working intermittently. Is there any way to find out if the issue is Thunderbolt connection related or if its the Docking shutting down the ports? Thanks Jiri

Re: ssh access with all ports close.

On 12/10/2020 6:40 AM, latin...@vcn.bc.ca wrote: latincom writes: I am not able to access my server at home using ssh, but i can see in logs, that someone can access my home server! What, exactly, are you seeing? Copy and paste examples. -- John Hasler jhas...@newsguy.com Elmwood, WI USA

Re: ssh access with all ports close.

> latincom writes: >> I am not able to access my server at home using ssh, but i can see in >> logs, that someone can access my home server! > > What, exactly, are you seeing? Copy and paste examples. > -- > John Hasler > jhas...@newsguy.com > Elmwood, WI USA > Dec 9 20:48:58 xxx sshd[4945]:

Re: ssh access with all ports close.

On 2020-12-09 16:33, latin...@vcn.bc.ca wrote: I had a Buster server at home, but the owner of the house close all ports in the router, i can not access it anymore; i rented a server without root access, and transfer the server. There are many vendors who can rent a Debian virtual private

Re: ssh access with all ports close.

latincom writes: > I am not able to access my server at home using ssh, but i can see in > logs, that someone can access my home server! What, exactly, are you seeing? Copy and paste examples. -- John Hasler jhas...@newsguy.com Elmwood, WI USA

ssh access with all ports close.

I had a Buster server at home, but the owner of the house close all ports in the router, i can not access it anymore; i rented a server without root access, and transfer the server. I am not able to access my server at home using ssh, but i can see in logs, that someone can access my home server

Problème ports USB

Bonjour Problème ports USB suite à un crash. Plus de clavier, ni de souris... Habituellement du Logitech sans fil. J'ai branché un clavier filaire et après maints essais j'ai trouvé un seul port Usb fonctionnel. Ce qui m'a permis de pouvoir accéder à l'uefi. Tous les ports reconnus et

Re: Speed of USB ports on Inspiron 1501

On Monday, March 23, 2020 02:20:19 PM David Christensen wrote: > The first link is: > > https://downloads.dell.com/manuals/all-products/esuprt_laptop/esuprt_inspir > on_laptop/inspiron-1501_owner%27s%20manual_en-us.pdf Thanks, that worked. > Was your laptop originally sold in Finland? Not as

Re: Speed of USB ports on Inspiron 1501

On 2020-03-23 03:43, rhkra...@gmail.com wrote: On Monday, March 23, 2020 01:42:40 AM David Christensen wrote: If I am reading the user manual for my E1505 and the Intel ICH7 datasheet correctly, the ExpressCard port in my laptop should be PCIe 1x at 2.5 Gbps. I would expect your E1501 to be

Re: Speed of USB ports on Inspiron 1501

On Monday, March 23, 2020 01:42:40 AM David Christensen wrote: > If I am reading the user manual for my E1505 and the Intel ICH7 > datasheet correctly, the ExpressCard port in my laptop should be PCIe 1x > at 2.5 Gbps. I would expect your E1501 to be equivalent (?). I bought it used, don't have

Re: Speed of USB ports on Inspiron 1501

On 2020-03-22 17:30, rhkra...@gmail.com wrote: Thanks to all who replied, to either this thread or my other related one, "OT: Questions about (buying and) using a laptop docking station". On Sunday, March 22, 2020 03:37:57 PM David Christensen wrote: ... So, ~$110 for better wired network

Re: Speed of USB ports on Inspiron 1501

Thanks to all who replied, to either this thread or my other related one, "OT: Questions about (buying and) using a laptop docking station". On Sunday, March 22, 2020 03:37:57 PM David Christensen wrote: ... > So, ~$110 for better wired network performance and the convenience of > one cable

Re: Speed of USB ports on Inspiron 1501

On 2020-03-22 10:10, rhkramer wrote: Background: I'm now thinking about buying a Wavlink USB 3.0 Display Universal Docking Station Dual Video HDMI/DVI/VGA, USB 3.0 & USB 2.0, Gigabit Ethernet Ports, Earphone & Mic in/out, Plug and Play For Windows Mac & Android 5.x Above - B

Re: Speed of USB ports on Inspiron 1501

rhkramer wrote: > I don't know if maybe one of them (usb1) is 480 Mbps and the others are 12 > Mbps, or maybe the 480 Mbps is either an internal port (with no physical > port) or maybe something like a bus speed for the combination of all 6 USB > ports. > check if you have loade

Speed of USB ports on Inspiron 1501

Background: I'm now thinking about buying a Wavlink USB 3.0 Display Universal Docking Station Dual Video HDMI/DVI/VGA, USB 3.0 & USB 2.0, Gigabit Ethernet Ports, Earphone & Mic in/out, Plug and Play For Windows Mac & Android 5.x Above - Black to use as a docking station for my I

Re: Looking for FOSS supported PCIe x4 SATA 6 Gb/s HBA with 4 or 8 ports

On Mi, 12 feb 20, 23:39:20, deloptes wrote: > Andrei POPESCU wrote: > > > Could you please elaborate or provide a reference for this? > > > > While my 3TB WD Red doesn't appear to have problems with my current > > usage, I'd like to be prepared. > > Google "western digital wd red 4tb issues" or

Re: Looking for FOSS supported PCIe x4 SATA 6 Gb/s HBA with 4 or 8 ports

David Christensen wrote: > Lately, I have been buying 3 TB Seagate Constellation ES.2.  One pair > has close to 1 year of 24x7 use.  No problems thus far. 1y is not a measure. What counts is 4+ at least.

Re: Looking for FOSS supported PCIe x4 SATA 6 Gb/s HBA with 4 or 8 ports

Andrei POPESCU wrote: > Could you please elaborate or provide a reference for this? > > While my 3TB WD Red doesn't appear to have problems with my current > usage, I'd like to be prepared. Google "western digital wd red 4tb issues" or "western digital wd red 3tb issues" As drives were getting

Re: Looking for FOSS supported PCIe x4 SATA 6 Gb/s HBA with 4 or 8 ports

On 2020-02-11 14:04, deloptes wrote: I stick to 2TB, because the WG RED >2TB are having issues. Lately, I have been buying 3 TB Seagate Constellation ES.2. One pair has close to 1 year of 24x7 use. No problems thus far. David

Re: Looking for FOSS supported PCIe x4 SATA 6 Gb/s HBA with 4 or 8 ports

on supported disk sizes, to 2T IIRC - I bought one from ebay and it was no use at all. Thanks for the warning. My own choice for more SATA/SAS ports is a Highpoint RocketRAID 2720 - 8 ports on a PCIe 2.0 x8 connector. Supported out of the box using the mvsas mainline driver. Okay. David

Re: Looking for FOSS supported PCIe x4 SATA 6 Gb/s HBA with 4 or 8 ports

Looking at Wikipedia, PCI Express link performance table: https://en.wikipedia.org/wiki/PCI_Express#History_and_revisions I believe 2.5 GT/s produces 2.5 Gb/s under PCIe version 1.0. So, the Syba specification is correct in this case. They apparently conflated "GT/sec" and "Gb/sec" (uhh,

Re: Looking for FOSS supported PCIe x4 SATA 6 Gb/s HBA with 4 or 8 ports

On Ma, 11 feb 20, 23:04:47, deloptes wrote: > > I don't know. I stick to 2TB, because the WG RED >2TB are having issues. Could you please elaborate or provide a reference for this? While my 3TB WD Red doesn't appear to have problems with my current usage, I'd like to be prepared. Kind

Re: Looking for FOSS supported PCIe x4 SATA 6 Gb/s HBA with 4 or 8 ports

stick to 2TB, because the WG RED >2TB are having issues. > My own choice for more SATA/SAS ports is a Highpoint RocketRAID 2720 - > 8 ports on a PCIe 2.0 x8 connector. Supported out of the box using the > mvsas mainline driver. I doubt that my demand will reach that point, having 6x2TB +

Re: Looking for FOSS supported PCIe x4 SATA 6 Gb/s HBA with 4 or 8 ports

ell for all those years 24/7. That particular model is limited on supported disk sizes, to 2T IIRC - I bought one from ebay and it was no use at all. My own choice for more SATA/SAS ports is a Highpoint RocketRAID 2720 - 8 ports on a PCIe 2.0 x8 connector. Supported o

Re: Looking for FOSS supported PCIe x4 SATA 6 Gb/s HBA with 4 or 8 ports

On Feb 10, 2020, David Christensen wrote: > On 2020-02-10 13:55, Dan Purgert wrote: >> On Feb 10, 2020, David Christensen wrote: >>> [...] >>> It has the following expansion slots: >>> >>> - One PCI Express 2.0 x16 add-in card connector >>> - One PCI Express 2.0 x4 add-in card connector >>> - One

Re: Looking for FOSS supported PCIe x4 SATA 6 Gb/s HBA with 4 or 8 ports

deloptes wrote: > David Christensen wrote: > > > Thanks for the data point. > > > > > > Did you have to do anything with firmware? > > not at all - driver in the kernel is mature - but again it is 3Gb/s per > port. > > Honestly I must look inside the server as I do not remember how it is >

Re: Looking for FOSS supported PCIe x4 SATA 6 Gb/s HBA with 4 or 8 ports

David Christensen wrote: > Thanks for the data point. > > > Did you have to do anything with firmware? not at all - driver in the kernel is mature - but again it is 3Gb/s per port. Honestly I must look inside the server as I do not remember how it is connected. I have 12 disk bay. It could

Re: Looking for FOSS supported PCIe x4 SATA 6 Gb/s HBA with 4 or 8 ports

David Christensen composed on 2020-02-10 16:41 (UTC-0800): > I am using another Syba SD-SA2PEX-2IR card in one of my computers with a > pair of Seagate ST31500341AS 1.5 TB drives. I used Seagate SeaTools > Bootable to erase both. The erase seemed to proceed okay. One drive > was visibly

Re: Looking for FOSS supported PCIe x4 SATA 6 Gb/s HBA with 4 or 8 ports

On 2020-02-10 14:28, deloptes wrote: I have this one for may be 7y already. 08:00.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1068E PCI-Express Fusion-MPT SAS (rev 08) https://wiki.pdl.cmu.edu/pub/OpenCloud/CloudManuals/SCG_LSISAS1068E_PB_040407.pdf It is 3Gb/s - don't know about

Re: Looking for FOSS supported PCIe x4 SATA 6 Gb/s HBA with 4 or 8 ports

On 2020-02-10 13:55, Dan Purgert wrote: On Feb 10, 2020, David Christensen wrote: [...] It has the following expansion slots: - One PCI Express 2.0 x16 add-in card connector - One PCI Express 2.0 x4 add-in card connector - One PCI Express 2.0 x1 add-in card connector a. While migrating

Re: Looking for FOSS supported PCIe x4 SATA 6 Gb/s HBA with 4 or 8 ports

> My research thus far: > > 1. LSI products are popular, but: > > a. Most seem to be PCIe x8. > > b. STFW I see more than a few posts complaining about changing > firmware from RAID to non-RAID, buggy firmware releases, and/or > motherboard BIOS/UEFI incompatibilities with the

Re: Looking for FOSS supported PCIe x4 SATA 6 Gb/s HBA with 4 or 8 ports

David Christensen composed on 2020-02-10 13:23 (UTC-0800): > Comments? Have you considered incorporating newer (nvme) technology? e.g. Whether compatible with the Q67 chipset I don't know, but it

Re: Looking for FOSS supported PCIe x4 SATA 6 Gb/s HBA with 4 or 8 ports

On Feb 10, 2020, David Christensen wrote: > [...] > It has the following expansion slots: > > - One PCI Express 2.0 x16 add-in card connector > - One PCI Express 2.0 x4 add-in card connector > - One PCI Express 2.0 x1 add-in card connector > > a. While migrating backup data, I recently saw

Looking for FOSS supported PCIe x4 SATA 6 Gb/s HBA with 4 or 8 ports

add-in card connector - One PCI Express 2.0 x1 add-in card connector - One Conventional PCI bus connector I need more SATA III 6 Gb/s ports and am looking for a HBA: 1. I would prefer using PCIe x4 slot, but can use the x16 slot. 2. Non-RAID. 3. At least four SATA ports. 4. Can handle

Re: Serial Ports and Perl

Andy Smith writes: > Hi Martin, > > I have been using it successfully for a long time, but all I do is > read whole lines from the serial device like: > > my $dev = '/dev/ttyUSB0'; > my $port = Device::SerialPort->new($dev); > > $port->baudrate(57600); >

Re: Serial Ports and Perl

On 27/10/17 15:38, Martin McCormick wrote: > A perldoc of Device::SerialPort says that lookfor is > supposed to block or hold until a character string emerges from > the port as in /dev/ttyUSB0 or /dev/ttyS1. When I trace the > code, it just loops as fast as it can and never holds to wait

Re: Serial Ports and Perl

Andy Smith writes: > Hi Martin, > I have been using it successfully for a long time, but all I do is > read whole lines from the serial device like: > > my $dev = '/dev/ttyUSB0'; > my $port = Device::SerialPort->new($dev); > > $port->baudrate(57600); >

Re: Serial Ports and Perl

;) || die "something or other:$!\n"; This would open it for writing. You are using "sane" parameters that serial ports default to so you wouldn't need to specify them. Best regards, Fred Boatwright

Re: Serial Ports and Perl

On Thu, Oct 26, 2017 at 07:37:07PM -0500, Martin McCormick wrote: > The perl list I subscribe to seems to be on the fritz or I would > take the question there. I want to write code that receives from > a RS-232 port and I just can't seem to get it to do anything. > > The port I am reading

Re: Serial Ports and Perl

Hi Martin, On Thu, Oct 26, 2017 at 07:37:07PM -0500, Martin McCormick wrote: > If anybody has gotten the perl Device::SerialPort to > work, I am interested to know what I am doing or not doing. I have been using it successfully for a long time, but all I do is read whole lines from the

Serial Ports and Perl

The perl list I subscribe to seems to be on the fritz or I would take the question there. I want to write code that receives from a RS-232 port and I just can't seem to get it to do anything. The port I am reading is connected to a scanner radio and produces generally short lines of text

Re: plusieurs ports d'écoute pour un serveur SSH

> > > > > Je n'ai pas bidouillé le pare-feu, donc par défaut tous les ports > > > sont  > > > accessibles non ? > > > > > > Voici un extrait de la config du pare-feu sur le serveur : > > > # iptables -L > > > Chain INPUT (policy

  1   2   3   4   5   6   7   8   9   10   >