From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] nfs mounting
Date: Thu, 31 Oct 2024 15:09:50 +0000 [thread overview]
Message-ID: <3330731.44csPzL39Z@cube> (raw)
In-Reply-To: <2020013.8hb0ThOEGa@rogueboard>
On Thursday 31 October 2024 14:21:27 GMT Michael wrote:
> On Thursday 31 October 2024 11:07:13 GMT Peter Humphrey wrote:
> > I've always used static addresses. The exception is the wireless network,
> > on which things come and go. I'm confident in dnsmasq on the wired LAN -
> > it's been running for years.
>
> Is dnsmasq also used by the wireless network successfully, or is the router
> running its own DHCP/DNS show?
I meant to say: dnsmasq serves the wired network; the router serves DHCP to
the wireless one, since it's directly upstream of them and dnsmasq isn't.
--->8
> > The router is a Fritz!Box, and it's a bit of a beast to understand. (Is
> > there a characteristic German approach to user interface design? I begin
> > to wonder, what with this and my boiler...)
>
> Fritz!Box is one of the better provisioned domestic routers.
That'll be why Zen Internet uses it then. That's my ISP, as you can tell from
my address.
> I've only used it once and mostly over wired Ethernet, but was impressed by
> its functions and features compared to other rubbish on the market. I can't
> recall its firewall options menu - I would think there would be no
> restrictions across LAN devices, bar Wireless Client Isolation. Different
> VLANs would either way isolate wireless devices to their own broadcast
> domain. For a quick test you can disable wireless client isolation and see
> if things start working as expected.
I've just tried to find its firewall setup, and failed. Searching for 'firewall'
in the manual finds nothing. I'll keep looking.
--
Regards,
Peter.
next prev parent reply other threads:[~2024-10-31 15:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 15:00 [gentoo-user] nfs mounting Peter Humphrey
2024-10-30 23:24 ` Peter Humphrey
2024-10-31 9:52 ` Michael
2024-10-31 11:07 ` Peter Humphrey
2024-10-31 14:21 ` Michael
2024-10-31 15:09 ` Peter Humphrey [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-18 13:41 [gentoo-user] NFS mounting Peter Humphrey
2024-10-18 14:55 ` Michael
2024-10-21 2:12 ` Peter Humphrey
2024-10-21 5:47 ` William Kenworthy
2024-10-21 8:22 ` Michael
2024-10-22 1:10 ` Peter Humphrey
2024-10-22 9:14 ` Michael
2024-10-22 12:00 ` Peter Humphrey
2024-10-22 13:36 ` Michael
2024-10-22 17:01 ` Matt Jolly
2024-10-22 19:29 ` Michael
2024-10-22 21:07 ` Peter Humphrey
2024-10-23 10:56 ` Peter Humphrey
2024-10-23 11:36 ` Arve Barsnes
2024-10-23 12:17 ` Peter Humphrey
2024-10-18 15:40 ` Jack Ostroff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3330731.44csPzL39Z@cube \
--to=peter@prh.myzen.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox