Whoop, you’re right.
My mistake. What was I thinking?
The rest of my reco’s are good, right?
Bill
Sent from my iPhone
> On Mar 18, 2022, at 11:01 AM, Justin Pryzby wrote:
>
> This conversation has gone off into the weeds, but I should point out that:
>
>> Yes, you can use SFTP (aka FTP
as
… “harder to break?”
Because, in time, sooner or later, everything becomes “insecure” or “broken”.
Our job, managing and maintaining servers is … to stay in the “safe zone” where
stuff isn’t “insecure yet”,
Bill
Sent from my iPhone
> On Mar 18, 2022, at 10:38 AM, William Papolis wr
Remember … FTPS or SFTP, whatever u want to call it, is just SSH providing a
“secure tunnel” for your unencrypted FTP traffic.
So … when trying to figure out “if SSH is secure” or any other encrypted
traffic like HTTPS or whatever, you need to look closely at the encryption
protocols you’re
You guys are confusing Ruud.
Bottom line … FTP is not encrypted.
Yes, you can use SFTP (aka FTP over SSH) but then pay attention to what you are
doing … you’re creating access for ONE service, “SFTP”, thru your Firewall.
What about all the other services (WWW? NFS? SAMBA? LDAP? And yes,
Vieri,
Congrats, buddy! You figured it out. Yes, it wasn’t a Shorewall issue, as I
also suspected!
In my experience I always learn a ton troubleshooting issues like this! I’m
sure you know way more now!
Bill
Sent from my iPhone
> On Feb 5, 2022, at 11:55 AM, Vieri Di Paola wrote:
>
Vieri, did u get this figured out yet?
If not, I can provide “step-by-step” instructions. Is that what u want?
Bill
Sent from my iPhone
> On Jan 26, 2022, at 8:09 AM, Vieri Di Paola wrote:
>
> On Tue, Jan 25, 2022 at 2:08 PM William Papolis wrote:
>>
>> I don’t want
don’t know what they are. 路♂️
Bill
Sent from my iPhone
> On Jan 25, 2022, at 7:55 AM, William Papolis wrote:
>
> What device are you using to configure your vLANs?
>
> Likely your switch, right?
>
> Switches can do “bridging” too.
>
> I would “look there”, if
going on. A lot of networks. Try simplifying.
YOU can do this.
Bill
Sent from my iPhone
> On Jan 25, 2022, at 7:43 AM, Vieri Di Paola wrote:
>
> On Tue, Jan 25, 2022 at 1:21 AM William Papolis wrote:
>>
>> This isn't a "Shorewall" issue.
>>
>> It's an
This isn't a "Shorewall" issue.
It's an "IP ROUTING" issue.
Look at my last response.
Bill
On Mon, Jan 24, 2022 at 6:37 PM Vieri Di Paola
wrote:
> In the failing scenario where a host in vlan 1 with IP addr.
> 10.215.111.210 cannot ping a host in vlan 18 with IP addr.
> 10.215.144.251 this
Yep, you're right. You just need to look at your NIC (Network Interface
Card) configuration.
Make sure your Shorewall device has an IP for both "Networks".
# sudo pico /etc/network/interfaces... on DEBIAN to edit
your network config
Then do ...
# sudo route -n
nother. I also have ports "open" for Remote access and I built a VPN using
Wireguard to allow Remote access with Encryption.
Is this good enough? Or do you need something more explicit?
Bill
On Mon, Jan 24, 2022 at 2:42 PM William Papolis wrote:
> When you move across a "Net
When you move across a "Network" to another "Network", you need a "Bridge"
Is your Firewall acting as a Bridge across those two "Networks"?
I'm assuming those IP's are on your "internal" network.
Bill
On Mon, Jan 24, 2022 at 1:55 PM Vieri Di Paola
wrote:
> Hi,
>
> I'm puzzled as to why I
Hey fellas, and girls ...
I have been struggling with this for a few days now and I just can't
seem to figure it out. :-(
I want to be able to SSH from the INTERNET to a SERVER on my LOCAL
LAN, behind a SHOREWALL firewall.
I have MASQ working great and all users can access the internet from
the
13 matches
Mail list logo
