Path: csiph.com!weretis.net!feeder6.news.weretis.net!feeder8.news.weretis.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Kyonshi Newsgroups: comp.os.linux.networking Subject: Re: issue with ufw blocking interface Date: Wed, 24 Apr 2024 16:21:09 +0200 Organization: A noiseless patient Spider Lines: 20 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Wed, 24 Apr 2024 16:50:10 +0200 (CEST) Injection-Info: dont-email.me; posting-host="89077c95b12bf61e1322a914cd2b2449"; logging-data="2509106"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/dbjqRkwtB7s9xBkTkXDWT" User-Agent: Betterbird (Windows) Hamster/2.1.0.1548 Cancel-Lock: sha1:fDDvyVsqsn+MS0jbMRmdKzJHhqc= Content-Language: en-US In-Reply-To: Xref: csiph.com comp.os.linux.networking:8480 On 4/24/2024 1:35 PM, Kyonshi wrote: > Ok, here's an issue where I might have some issues with understanding > how this actually works. > I have a machine that has both a public IP on eth0 and a private one on > wlan0. > I tried to block off all inbound traffic on eth0 with >     ufw deny in on eth0 > > Instead I now seem to have blocked all incoming traffic, including the > wlan0 interface (which kicked me out of the ssh session). > What am I doing wrong here? > ah, no, turns out it just blocks everything and I needed to allow port 22 first. yeah, I was thinking the wrong direction. -- microblog: https://dice.camp/@kyonshi macroblog: https://gmkeros.wordpress.com pictures: https://portfolio.pixelfed.de/kyonshi