Franco Martelli wrote:
> On 30/07/24 at 17:29, Tawsif wrote:
> > On Tue, Jul 30, 2024 at 01:08:39PM +0600, Tawsif wrote:
> > I have a very small storage size for my laptop (64gb). So, I installed
> > debian minimal in it.
>
> If you can, reinstalls Debian as usual, my KDE's installation takes abo
Am Wed, 19 Jun 2024 10:14:32 +0800
schrieb Jeff Peng :
> when my server is a vps who has floating IP (that means, the server's
> iP is an internal IP, the public ip is bond on provider's
> router/firewall devices), then my ssh client connecting to the server
> will never disconnect even if I chang
Hi all,
thank you for the fast response. Your answers did help much and made
everything clear.
Have a nice weekend!
Best
Hans
On 05/04/2024 04:29, David Wright wrote:
autoconnect-priorityint32 0 [...]
from
https://developer-old.gnome.org/NetworkManager/stable/settings-connection.html
(I don't know the significance of -old.)
It is documented in nm-settings-nmcli(5)
On Thu 04 Apr 2024 at 19:11:31 (+0200), Hans wrote:
> again an easy thing, I did not understand and where I did not find a clear
> answer in the web.
>
> Question:
>
> In network-manager I find "network-priority" set to "0".
>
> Is zero the highes priority or the lowest?
This might be what y
On 2/4/24 09:03, Marco Moock wrote:
Am 04.02.2024 um 07:12:50 Uhr schrieb Gremlin:
I also slay all the mDNS non sense.
mDNS works fine if the host names are properly set and no other way of
setting the addresses (Unicast DNS, /etc/hosts) is being used.
It is not needed if the network is se
Am 04.02.2024 um 07:12:50 Uhr schrieb Gremlin:
> I also slay all the mDNS non sense.
mDNS works fine if the host names are properly set and no other way of
setting the addresses (Unicast DNS, /etc/hosts) is being used.
--
kind regards
Marco
Spam und Werbung bitte an ichschickerekl...@cartoonie
On 2/4/24 02:39, Marco Moock wrote:
Am 02.02.2024 um 17:12:06 Uhr schrieb Gremlin:
On 2/2/24 16:28, Greg Wooledge wrote:
On Fri, Feb 02, 2024 at 02:03:46PM -0700, Charles Curley wrote:
root@hawk:~# host samba
samba.localdomain is an alias for hawk.localdomain.
hawk.localdomain has address 192
On Fri, 2024-02-02 at 16:47 -0700, Charles Curley wrote:
> On Fri, 2 Feb 2024 15:52:41 -0700
> Charles Curley wrote:
>
> > But I don't think that will solve the routing problem.
>
> Well, I was wrong. That did solve the routing problems.
>
> I moved the apt-proxy line for the VMs' benefit into
Am 02.02.2024 um 17:12:06 Uhr schrieb Gremlin:
> On 2/2/24 16:28, Greg Wooledge wrote:
> > On Fri, Feb 02, 2024 at 02:03:46PM -0700, Charles Curley wrote:
> >> root@hawk:~# host samba
> >> samba.localdomain is an alias for hawk.localdomain.
> >> hawk.localdomain has address 192.168.100.6
> >
On Fri, 2 Feb 2024 15:52:41 -0700
Charles Curley wrote:
> But I don't think that will solve the routing problem.
Well, I was wrong. That did solve the routing problems.
I moved the apt-proxy line for the VMs' benefit into a VM's /etc/hosts
and took it out of hawk's /etc/hosts. samba is now an a
On Fri, 2 Feb 2024 16:52:48 -0500
Greg Wooledge wrote:
> Well, we don't know what's "right" or "wrong" on your networks. These
> are private (non-routable) addresses with no meaning to anyone but you
> and your fellow network denizens.
Agree.
>
> If you need different name resolution dependin
On 2/2/24 16:28, Greg Wooledge wrote:
On Fri, Feb 02, 2024 at 02:03:46PM -0700, Charles Curley wrote:
root@hawk:~# host samba
samba.localdomain is an alias for hawk.localdomain.
hawk.localdomain has address 192.168.100.6
host(1) looks in DNS only. It doesn't do the standard name resolution
th
> > > # For the benefit of virtual machines.
> > > 192.168.100.12 apt-proxy
> > > 192.168.122.1 samba samba.localdomain
> >
> > And that's where it came from (/etc/hosts). If this IP address is
> > wrong, then it shouldn't be in here.
>
> Gnrrr. It's right for the virtual network (192.168.122.
On Fri, 2 Feb 2024 22:10:19 +0100
Marco Moock wrote:
> Sorry for the first post.
> Your problem is located in the name resolution.
>
> Show /etc/nsswitch.conf
I have not touched this.
root@hawk:~# cat /etc/nsswitch.conf
# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch
On Fri, 2 Feb 2024 16:28:06 -0500
Greg Wooledge wrote:
> > However, when I try to ping samba by host name:
> >
> > root@hawk:~# ping samba
> > PING samba (192.168.122.1) 56(84) bytes of data.
>
> Note that this is a *different* IP address.
Good catch, thank you.
>
> > # For the benefit of
On Fri, Feb 02, 2024 at 02:03:46PM -0700, Charles Curley wrote:
> root@hawk:~# host samba
> samba.localdomain is an alias for hawk.localdomain.
> hawk.localdomain has address 192.168.100.6
host(1) looks in DNS only. It doesn't do the standard name resolution
that applications do.
> root@hawk:~#
Am 02.02.2024 um 14:03:46 Uhr schrieb Charles Curley:
> root@hawk:~# host samba
> samba.localdomain is an alias for hawk.localdomain.
> hawk.localdomain has address 192.168.100.6
> root@hawk:~# ping samba
> PING samba (192.168.122.1) 56(84) bytes of data.
Sorry for the first post.
Your problem
Am 02.02.2024 um 14:03:46 Uhr schrieb Charles Curley:
> From apt-proxy (192.168.100.12): icmp_seq=2 Redirect Host(New
> nexthop: hawk.localdomain (192.168.100.6))
Check the routing table on apt-proxy.
ICMP redirect happens if you have 2 routers on the same ethernet link
and the router you try to
On Thu, Nov 09, 2023 at 04:40:22PM -0500, gene heskett wrote:
> On 11/9/23 14:41, to...@tuxteam.de wrote:
[...]
> A possibility I hadn't considered yet, but that might need the CIDR changed
> also.
You don't change CIDR. You change your netmask.
No you don't have to: tcpdump puts your interface
On 11/9/23 14:15, Greg Wooledge wrote:
On Thu, Nov 09, 2023 at 02:05:49PM -0500, gene heskett wrote:
I have plugged in a supplied cat-5 jumper into a port of the local switch
serving that room and now need to find it on my local net IF it has a ping
responder.
So the questions are:
What do I n
On 11/9/23 14:41, to...@tuxteam.de wrote:
On Thu, Nov 09, 2023 at 02:05:49PM -0500, gene heskett wrote:
Greetings all netsperts;
I've purchased a new 3d printer which is factory equipt with klipper.
[...]
So the questions are:
What do I need to change in my network config on this machine s
On Thu, Nov 09, 2023 at 02:05:49PM -0500, gene heskett wrote:
> Greetings all netsperts;
>
> I've purchased a new 3d printer which is factory equipt with klipper.
[...]
> So the questions are:
> What do I need to change in my network config on this machine so I can ping
> all 65536 address of t
On Thu, Nov 09, 2023 at 02:05:49PM -0500, gene heskett wrote:
> I have plugged in a supplied cat-5 jumper into a port of the local switch
> serving that room and now need to find it on my local net IF it has a ping
> responder.
>
> So the questions are:
> What do I need to change in my network co
Henggi writes:
> Oh wow… that’s interesting. I had no idea about „nft“ (I just knew
> „iptables-nft“) which seem to be very different.
> I think I have dig down where those „nft" rules are coming from while
> iptables-nft is completely empty. Thanks, great clue!
Typically you'd have a /etc/nft
> On 24 Oct 2023, at 17:36, Arno Lehmann wrote:
>
> Hello,
Hi Arno,
>
> Am 24.10.2023 um 16:19 schrieb Henggi:
> ...
>> As I mentioned in my 1st email, I think (afaik) that no other netfitler
>> module/service is running.
>
> My anecdote was intended to illustrate that beliefs are not really
> On 24 Oct 2023, at 16:33, Max Nikulin wrote:
>
> On 24/10/2023 19:04, Henggi wrote:
>> - iptables on server are cleared/open (firewalld or other firewall
>> frameworks are not used/installed).
>
> Nowadays nft or iptables is not the only option to drop packets. Another one
> is eBPF used e
> On 24 Oct 2023, at 17:22, Charles Curley
> wrote:
>
> On Tue, 24 Oct 2023 15:30:14 +0200
> Arno Lehmann wrote:
>
>> Recently I encountered something similar, and my usual test for local
>> firewall being active,
>>
>> iptables -L -n
>>
>> came back with policies "accept" all over the p
Hello,
Am 24.10.2023 um 16:19 schrieb Henggi:
...
As I mentioned in my 1st email, I think (afaik) that no other netfitler
module/service is running.
My anecdote was intended to illustrate that beliefs are not really good
tools to diagnose problems ;-)
root@server:~# systemctl status firew
On Tue, 24 Oct 2023 15:30:14 +0200
Arno Lehmann wrote:
> Recently I encountered something similar, and my usual test for local
> firewall being active,
>
> iptables -L -n
>
> came back with policies "accept" all over the place, and no
> particular rules.
>
> Took me a while to understand that
> On 24 Oct 2023, at 15:30, Arno Lehmann wrote:
>
> Hi Henggi, all,
Hi Arno, thanks for your reply!
>
> Am 24.10.2023 um 14:04 schrieb Henggi:
>> Hi list,
>> Completely stuck here, any clue appreciated!
>> Trying to bring up XRDP service on Debian 11-bullsyeye (arm64, incl.
>> backports, full
On 24/10/2023 19:04, Henggi wrote:
- iptables on server are cleared/open (firewalld or other firewall
frameworks are not used/installed).
Nowadays nft or iptables is not the only option to drop packets. Another
one is eBPF used e.g. by systemd.
I have the following link in my notes, but I ha
> On 24 Oct 2023, at 15:14, Dan Ritter wrote:
>
> Henggi wrote:
>>
>>> On 24 Oct 2023, at 14:46, Dan Ritter wrote:
>>>
>> - when using „port=tcp://:3389“ in xrdp.ini:
>> root@server:~# ss -tlnp | grep 3389
>> LISTEN 0 2 0.0.0.0:3389 0.0.0.0:*
>> users:(("xrdp"
Hi Henggi, all,
Am 24.10.2023 um 14:04 schrieb Henggi:
Hi list,
Completely stuck here, any clue appreciated!
Trying to bring up XRDP service on Debian 11-bullsyeye (arm64, incl. backports,
fully up-to-date) which is only listening on „lo“ interface (not eth0) even
netstat indicates otherwise
Henggi wrote:
>
> > On 24 Oct 2023, at 14:46, Dan Ritter wrote:
> >
> - when using „port=tcp://:3389“ in xrdp.ini:
> root@server:~# ss -tlnp | grep 3389
> LISTEN 0 2 0.0.0.0:3389 0.0.0.0:*
> users:(("xrdp",pid=96436,fd=11))
>
> - when using using „port=3389“ in x
> On 24 Oct 2023, at 14:46, Dan Ritter wrote:
>
> Henggi wrote:
>> Hi list,
>>
>> Completely stuck here, any clue appreciated!
>>
>> — by default xrdp.ini listening config is set to "port=3389“ (which is
>> expected to listen on ipv4 && ipv6 in parallel as I understand). However
>> using t
Henggi wrote:
> Hi list,
>
> Completely stuck here, any clue appreciated!
>
> — by default xrdp.ini listening config is set to "port=3389“ (which is
> expected to listen on ipv4 && ipv6 in parallel as I understand). However
> using that seems only to listen on tcp4 according to „netstat“
> — t
On 17/10/2023 02:11, Gary Dale wrote:
On 2023-10-16 18:52, Igor Cicimov wrote:
Hi,
On Tue, Oct 17, 2023, 8:00 AM Gary Dale wrote:
I'm trying to configure network bonding on an AMD64 system running
Debian/Trixie. I've got a wired connection and a wifi connection,
both
of which
On Wed, Oct 18, 2023 at 7:34 AM Darac Marjal
wrote:
> On 16/10/2023 21:59, Gary Dale wrote:
> > I'm trying to configure network bonding on an AMD64 system running
> > Debian/Trixie. I've got a wired connection and a wifi connection, both
> > of which work individually. I'd like them to work toget
On 16/10/2023 21:59, Gary Dale wrote:
I'm trying to configure network bonding on an AMD64 system running
Debian/Trixie. I've got a wired connection and a wifi connection, both
of which work individually. I'd like them to work together to improve
the throughput but for now I'm just trying to get
On 2023-10-16 21:20, Igor Cicimov wrote:
On Tue, Oct 17, 2023 at 12:12 PM Gary Dale wrote:
On 2023-10-16 18:52, Igor Cicimov wrote:
Hi,
On Tue, Oct 17, 2023, 8:00 AM Gary Dale
wrote:
I'm trying to configure network bonding on an AMD64 system
running
On Tue, Oct 17, 2023 at 12:12 PM Gary Dale wrote:
> On 2023-10-16 18:52, Igor Cicimov wrote:
>
> Hi,
>
> On Tue, Oct 17, 2023, 8:00 AM Gary Dale wrote:
>
>> I'm trying to configure network bonding on an AMD64 system running
>> Debian/Trixie. I've got a wired connection and a wifi connection, bot
On 2023-10-16 18:52, Igor Cicimov wrote:
Hi,
On Tue, Oct 17, 2023, 8:00 AM Gary Dale wrote:
I'm trying to configure network bonding on an AMD64 system running
Debian/Trixie. I've got a wired connection and a wifi connection,
both
of which work individually. I'd like them to wor
Hi,
On Tue, Oct 17, 2023, 8:00 AM Gary Dale wrote:
> I'm trying to configure network bonding on an AMD64 system running
> Debian/Trixie. I've got a wired connection and a wifi connection, both
> of which work individually. I'd like them to work together to improve
> the throughput but for now I'
On Mon, Jul 03, 2023 at 05:21:20PM -0500, Michael Jinks wrote:
> I have a Pi 4 machine where I've installed two OS's, the "house supplied",
> and Ubuntu, both worked fine so I'm sure the hardware is good. Now I'd
> like to install Debian.
>
> I've found one very slim image of that, which ran with
On Tue, Jul 04, 2023 at 02:08:58AM -0400, Timothy M Butterworth wrote:
> On Mon, Jul 3, 2023 at 6:22 PM Michael Jinks
> wrote:
>
> > I have a Pi 4 machine where I've installed two OS's, the "house supplied",
> > and Ubuntu, both worked fine so I'm sure the hardware is good. Now I'd
> > like to i
On Mon, Jul 3, 2023 at 6:22 PM Michael Jinks
wrote:
> I have a Pi 4 machine where I've installed two OS's, the "house supplied",
> and Ubuntu, both worked fine so I'm sure the hardware is good. Now I'd
> like to install Debian.
>
> I've found one very slim image of that, which ran without issue,
On Mon, Jul 03, 2023 at 05:21:20PM -0500, Michael Jinks wrote:
> I have a Pi 4 machine where I've installed two OS's, the "house supplied",
> and Ubuntu, both worked fine so I'm sure the hardware is good. Now I'd
> like to install Debian.
>
> I've found one very slim image of that, which ran with
On Wed, Mar 15, 2023 at 03:35:18PM +0100, krys...@ibse.cz wrote:
> Dne středa 15. března 2023 12:55:55 CET, Henning Follmann napsal(a):
> > This is indeed not right.
> > Please try to ping any other host on the 192.168.1.0/24 network from
> > 192.168.0.0/24 network. This might be just the case that
krys...@ibse.cz wrote:
> Dne středa 15. března 2023 12:55:55 CET, Henning Follmann napsal(a):
> > This is indeed not right.
> > Please try to ping any other host on the 192.168.1.0/24 network from
> > 192.168.0.0/24 network. This might be just the case that the host with the
> > two interfaces rep
Dne středa 15. března 2023 12:55:55 CET, Henning Follmann napsal(a):
> This is indeed not right.
> Please try to ping any other host on the 192.168.1.0/24 network from
> 192.168.0.0/24 network. This might be just the case that the host with the
> two interfaces replies on any interface independent
First, Your return key is broken, please fix that ;)
On Tue, Mar 14, 2023 at 07:51:44PM +0100, krys...@ibse.cz wrote:
> Hello everyone,
> I have a question about network stack configuration in Linux. Lets assume a
> Linux host with multiple network interfaces, a different ip address is set on
Hello again,
From: pe...@easthope.ca
Date: Sun, 01 Jan 2023 11:31:38 -0800
> (2) Why is the second inet6 address omitted from the current result?
br0 isn't created properly. Appears to be this problem, not yet
resolved. =8~/
From: Santiago Garcia Mantinan
To: 993...@bugs.debian.org
S
> On Mon, Jan 02, 2023 at 11:30:02AM +, debian-u...@howorth.org.uk
> wrote:
> > > On Sun, Jan 01, 2023 at 11:31:38AM -0800, pe...@easthope.ca wrote:
> > > It's first quad is 9, binary 0110.
> >
> > Eh? 9 is 0101 in binary! 0110 is denary 10.
>
> 5 is 0101
> 6 is 0110
> 9 is 1001
> 10 i
On Mon, Jan 2, 2023 at 8:47 AM Greg Wooledge wrote:
>
> On Mon, Jan 02, 2023 at 11:30:02AM +, debian-u...@howorth.org.uk wrote:
> > > On Sun, Jan 01, 2023 at 11:31:38AM -0800, pe...@easthope.ca wrote:
> > > It's first quad is 9, binary 0110.
> >
> > Eh? 9 is 0101 in binary! 0110 is denary 10.
On 1/2/23 09:12, to...@tuxteam.de wrote:
On Mon, Jan 02, 2023 at 08:46:37AM -0500, Greg Wooledge wrote:
On Mon, Jan 02, 2023 at 11:30:02AM +, debian-u...@howorth.org.uk wrote:
On Sun, Jan 01, 2023 at 11:31:38AM -0800, pe...@easthope.ca wrote:
It's first quad is 9, binary 0110.
Eh? 9 is 01
On Mon, Jan 02, 2023 at 08:46:37AM -0500, Greg Wooledge wrote:
> On Mon, Jan 02, 2023 at 11:30:02AM +, debian-u...@howorth.org.uk wrote:
> > > On Sun, Jan 01, 2023 at 11:31:38AM -0800, pe...@easthope.ca wrote:
> > > It's first quad is 9, binary 0110.
> >
> > Eh? 9 is 0101 in binary! 0110 is de
On Mon, Jan 02, 2023 at 11:30:02AM +, debian-u...@howorth.org.uk wrote:
> > On Sun, Jan 01, 2023 at 11:31:38AM -0800, pe...@easthope.ca wrote:
> > It's first quad is 9, binary 0110.
>
> Eh? 9 is 0101 in binary! 0110 is denary 10.
5 is 0101
6 is 0110
9 is 1001
10 is 1010
On Mon, Jan 02, 2023 at 11:30:02AM +, debian-u...@howorth.org.uk wrote:
> > On Sun, Jan 01, 2023 at 11:31:38AM -0800, pe...@easthope.ca wrote:
> > > Greetings for the New Year to Debian users,
> > >
> > > Verifying and updating instructions here.
> > > https://en.wikibooks.org/wiki/Oberon/ETH_
> > On Sun, Jan 01, 2023 at 11:31:38AM -0800, pe...@easthope.ca wrote:
> > > Greetings for the New Year to Debian users,
> > >
> > > Verifying and updating instructions here.
> > > https://en.wikibooks.org/wiki/Oberon/ETH_Oberon/QEMUinstall#Network_Connection_on_a_Virtual_Machine
> > > Questions
> On Sun, Jan 01, 2023 at 11:31:38AM -0800, pe...@easthope.ca wrote:
> > Greetings for the New Year to Debian users,
> >
> > Verifying and updating instructions here.
> > https://en.wikibooks.org/wiki/Oberon/ETH_Oberon/QEMUinstall#Network_Connection_on_a_Virtual_Machine
> > Questions (1) and (2) f
On Sun, Jan 01, 2023 at 11:31:38AM -0800, pe...@easthope.ca wrote:
> Greetings for the New Year to Debian users,
>
> Verifying and updating instructions here.
> https://en.wikibooks.org/wiki/Oberon/ETH_Oberon/QEMUinstall#Network_Connection_on_a_Virtual_Machine
> Questions (1) and (2) follow.
>
>
On Sun, 4 Sep 2022 08:39:59 +0200
Rand Pritelrohm wrote:
>Hello,
>
>I am not a network specialist and despite a lot of documentation
>readings and searchs on the net I haven't get a simple and clear answer
>to my question.
>
[...]
>
>
>Here is my question:
>For both scenarios, what is the eff
On Sun, Sep 4, 2022 at 4:40 PM Rand Pritelrohm
wrote:
> Hello,
>
> I am not a network specialist and despite a lot of documentation
> readings and searchs on the net I haven't get a simple and clear answer
> to my question.
>
> Consider this simple schematic:
>
>
> | VM | -> | HOST |
On Sun, Sep 04, 2022 at 09:42:34AM +0200, john doe wrote:
> On 9/4/2022 8:39 AM, Rand Pritelrohm wrote:
[...]
> > #Then I have to enable routing
> > echo '1' > /proc/sys/net/ipv4/ip_forward
> > iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
> >
>
> You are answering your ow
On 9/4/2022 8:39 AM, Rand Pritelrohm wrote:
Consider this simple schematic:
| VM | -> | HOST | -> | GW | -> ISP
Lets say the physical interface name on the 'host' is eth0 and the LAN
subnet is 192.168.0.0.
I want to configure the network on the 'host' in order for the VM to
On 4/9/22 2:39 pm, Rand Pritelrohm wrote:
1. Bridge using routed subnet:
ip link add dev br0 type bridge
ip addr add 192.168.222.1/24 dev br0
ip link set dev br0 up
ip tuntap add tap0 mode tap
ip link set dev tap0 up
ip link set dev tap0 master br0
#Then I h
Hmm, there seems to be a difference between networkmanager in KDE and in Gnome:
Situation is, there are two users, A and B.
B defined this VPN connection and wants to start it.
If only B is logged in (directly, not remotely), she can start the VPN in both
KDE and Gnome.
If B is logged in remote
nmcli con up doesn't work either: nothing happens except the three
dots where the VPN icon is shown and after 90 seconds a timeout message
appears in the terminal window; so exactly the same behaviour :-(
Bernd
On Monday, August 8, 2022 3:03:17 PM CEST Harald Dunkel wrote:
> Hi BM
>
> if your V
Hi BM
if your VPN is IPsec, then you might want to examine charon's output via
journalctl. Probably openvpn, wireguard and others can be found there, too.
Another thing to try is to establish the VPN connection using nmcli in a
terminal window, e.g.
nmcli con up "VPN name"
Maybe you ge
Am 16.10.21 um 09:27 schrieb dude:
Hello,
on latest Debian 11 + MATE Desktop (it is software simplicity at it's
best :)
why is it not possible to set primary & secondary dns via
network-manager-gnome? (only "additional dns")
It is possible. Choose
Method: Automatic (DHCP) addresses only
[
On Thu, 7 Oct 2021 at 12:53, Lee wrote:
> On 10/6/21, David wrote:
> > But others here are vastly more knowledgeable than I am about
> > networks, so additions or corrections are welcome, as always :)
> It's Classless Inter-domain Routing (CIDR) now and network masks are
> no longer supported [
On 10/6/21, David wrote:
> On Thu, 7 Oct 2021 at 10:53, wrote:
>> On Wednesday, October 06, 2021 11:15:11 AM Brian wrote:
>> > On Wed 06 Oct 2021 at 14:09:23 +0200, Pierre Frenkiel wrote:
>>
>> > >netmask 255.255.255.0
>> > >gateway 192.168.1.1
>> >
>> > Just in passing: The line with net
On Wed 06 Oct 2021 at 14:09:23 (+0200), Pierre Frenkiel wrote:
> please note that the main problem is
> "why the /etc/network/interfaces" is not used?"
> I have the following problem on my laptop.
> my /etc/network/interfaces file contains:
>auto enp0s1
>iface enp0s1 inet static
>ad
On Thu, 7 Oct 2021 at 10:53, wrote:
> On Wednesday, October 06, 2021 11:15:11 AM Brian wrote:
> > On Wed 06 Oct 2021 at 14:09:23 +0200, Pierre Frenkiel wrote:
>
> > >netmask 255.255.255.0
> > >gateway 192.168.1.1
> >
> > Just in passing: The line with netmask 255.255.255.0 can be deleted.
On Wednesday, October 06, 2021 11:15:11 AM Brian wrote:
> On Wed 06 Oct 2021 at 14:09:23 +0200, Pierre Frenkiel wrote:
> >netmask 255.255.255.0
> >gateway 192.168.1.1
>
> Just in passing: The line with netmask 255.255.255.0 can be deleted.
> It is a deprecated option, as is broadcast. See
On Wed, 6 Oct 2021 at 23:09, Pierre Frenkiel wrote:
>
> please note that the main problem is
>"why the /etc/network/interfaces" is not used?"
Ok. Noted.
Several knowledgeable and helpful people have already
made an effort trying to help you answer exactly this.
You can find those efforts in
On Wed 06 Oct 2021 at 16:40:55 +0100, Thomas Pircher wrote:
> Brian wrote:
> > Just in passing: The line with netmask 255.255.255.0 can be deleted.
> > It is a deprecated option, as is broadcast. See #912220.
>
> Crikey, it is indeed deprecated. Just removing the line will probably
> not be a goo
Brian wrote:
Just in passing: The line with netmask 255.255.255.0 can be deleted.
It is a deprecated option, as is broadcast. See #912220.
Crikey, it is indeed deprecated. Just removing the line will probably
not be a good idea. I guess it can be deleted only when the address line
contains the
On Wed 06 Oct 2021 at 14:09:23 +0200, Pierre Frenkiel wrote:
[...]
> I have the following problem on my laptop.
> my /etc/network/interfaces file contains:
>auto enp0s1
>iface enp0s1 inet static
>address 192.168.1.10
>netmask 255.255.255.0
>gateway 192.168.1.1
Just in passin
On Wed, Oct 06, 2021 at 02:09:23PM +0200, Pierre Frenkiel wrote:
> please note that the main problem is
> "why the /etc/network/interfaces" is not used?"
Please show us the information you've been asked to show, by multiple
people:
ip addr
ip route
Hi.
On Tue, Oct 05, 2021 at 10:00:45PM +0200, Pierre Frenkiel wrote:
> hi,
> I have the following problem on my laptop.
> my /etc/network/interfaces file contains:
>auto enp0s1
>iface enp0s1 inet static
>address 192.168.1.10
>netmask 255.255.255.0
>gateway 192.168.1.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
‐‐‐ Original Message ‐‐‐
On Tuesday, October 5, 2021 2:00 PM, Pierre Frenkiel
wrote:
> hi,
> I have the following problem on my laptop.
> my /etc/network/interfaces file contains:
> auto enp0s1
> iface enp0s1 inet static
> address 192.16
On Tue, Oct 05, 2021 at 10:00:45PM +0200, Pierre Frenkiel wrote:
> hi,
> I have the following problem on my laptop.
> my /etc/network/interfaces file contains:
>auto enp0s1
>iface enp0s1 inet static
>address 192.168.1.10
>netmask 255.255.255.0
>gateway 192.168.1.1
>
>but a
Pierre Frenkiel wrote:
> hi,
> I have the following problem on my laptop.
> my /etc/network/interfaces file contains:
>auto enp0s1
>iface enp0s1 inet static
>address 192.168.1.10
>netmask 255.255.255.0
>gateway 192.168.1.1
>
>but after boot, ifconfig gives
>
>address
On Sat, 28 Aug 2021 10:19:23 -0400 Jude Informed me about Re:
Network down incorrect
> As part of your reinstall process did you delete all partitions then
> run wipefs -af on the disk? Failure to do so may have left old
> artifacts of the previous system on
On Sat, 28 Aug 2021 17:14:29 +0200 Marco Informed me about Re:
Network down incorrect
> On 28.08.21 15:38, Charlie wrote:
> >
> > From my keyboard:
> >
> > Hello all,
> >
> > Since Bullseye went stable, updated on
On Sat, 28 Aug 2021 10:43:07 -0400 Eike Informed me about Re:
Network down incorrect
> On Samstag, 28. August 2021 09:38:44 -04 Charlie wrote:
> > From my keyboard:
> >
> > Hello all,
> >
> > Since Bullseye went stab
On Sat, 28 Aug 2021 11:39:13 -0500 David Informed me about Re:
Network down incorrect
> On Sat 28 Aug 2021 at 23:38:44 (+1000), Charlie wrote:
> > Since Bullseye went stable, updated on my 12 month old HP
> > laptop. When attempting to bring
On Sat 28 Aug 2021 at 23:38:44 (+1000), Charlie wrote:
> Since Bullseye went stable, updated on my 12 month old HP
> laptop. When attempting to bring up the wireless interface with
> ifup.
>
> The message on the screen tells me the "network is down", which is
> incorrect. Because
On 28.08.21 15:38, Charlie wrote:
From my keyboard:
Hello all,
Since Bullseye went stable, updated on my 12 month old HP
laptop. When attempting to bring up the wireless interface with
ifup.
The message on the screen tells me the "network is down", whic
On Samstag, 28. August 2021 09:38:44 -04 Charlie wrote:
> From my keyboard:
>
> Hello all,
>
> Since Bullseye went stable, updated on my 12 month old HP
> laptop. When attempting to bring up the wireless interface with
> ifup.
>
> The message on the screen tells me the
As part of your reinstall process did you delete all partitions then run
wipefs -af on the disk? Failure to do so may have left old artifacts of
the previous system on the drive which may be messing up your current
installation.
On Sat, 28 Aug 2021, Charlie wrote:
>
> From my keyboard:
>
On Mon, Jul 12, 2021 at 02:32:12PM +0200, Michael Lange wrote:
> Hi,
>
> On Mon, 12 Jul 2021 13:16:13 +0200
> wrote:
>
> (...)
> > Your network clearly *thinks* it is up [...]
> well, as you may have guessed I am completely stupid when it comes to
> networking :)
Most of us are. I know I am.
Hi,
On Mon, 12 Jul 2021 13:16:13 +0200
wrote:
(...)
> Your network clearly *thinks* it is up. What makes you think your net
> doesn't work? (not that I'm doubting your perception, but a more precise
> symptom description might shed some light on the problem).
well, as you may have guessed I am
On Mon, Jul 12, 2021 at 01:00:08PM +0200, Michael Lange wrote:
> Does that tell something?
Yep. First, your interface name is "enp2s0" has not changed.
Second, someone (another instance of dhclient probably) have obtained a
lease, as indicated by both tcpdump and "ip a" outputs.
Reco
On Mon, Jul 12, 2021 at 01:00:08PM +0200, Michael Lange wrote:
[...]
> 2: enp2s0: mtu 1500 qdisc pfifo_fast state
> UP group default qlen 1000
> link/ether 50:e5:49:d8:51:94 brd ff:ff:ff:ff:ff:ff
> inet 192.168.178.27/24 brd 192.168.178.255 scope global dynamic enp2s0
>valid_lft
Hi,
On Mon, 12 Jul 2021 13:32:48 +0300
Reco wrote:
(...)
> does not add up.
>
> If, for some reason, an interface name had changed - you won't see
> "enp2s0" in the ifconfig output.
thanks for the clarification.
>
>
> > some sources I found suggest to look at
> > /etc/udev/rules.d/70-persist
Hi.
On Mon, Jul 12, 2021 at 12:16:59PM +0200, Michael Lange wrote:
This:
> With ifconfig the enp2s0 interface appears to be up,
combined with this:
> I suspected udev to have for some reason changed the interface name;
does not add up.
If, for some reason, an interface name had changed
On 7/4/21 1:12 PM, David Wright wrote:
On Sun 04 Jul 2021 at 13:07:08 (+0800), Robbi Nespu wrote:
On 7/4/21 1:02 PM, David Wright wrote:
If you can give correction directly via chmod also good for me :)
$ ls -l /etc/hosts
-rw-r--r-- 1 root root 420524 Feb 6 16:19 /etc/hosts
that mean
sudo
1 - 100 of 2151 matches
Mail list logo
