On Fri, Jan 5, 2024 at 12:18 PM David wrote:
> On Fri, 2024-01-05 at 00:43 -0500, Felix Miata wrote:
> > David composed on 2024-01-04 04:30 (UTC):
> >
> > > With the latest Debian I'm trying to find the file to edit to
> > > change
> > > the IP address of a remote box, can anybody point me in the
On 1/5/24 05:41, David wrote:
On Fri, 2024-01-05 at 00:43 -0500, Felix Miata wrote:
David composed on 2024-01-04 04:30 (UTC):
With the latest Debian I'm trying to find the file to edit to
change
the IP address of a remote box, can anybody point me in the correct
direction please?
I can SSH
Am 05.01.2024 um 10:41:26 Uhr schrieb David:
> But I cannot find the file to edit.
Use the Networkmanager (nmcli, nmtui) to edit it.
nmcli connection show
nmcli connection edit
"print" gives all attributes
set
changes it.
save to write it and then
nmcli connection up to apply it.
On Fri, 2024-01-05 at 00:43 -0500, Felix Miata wrote:
> David composed on 2024-01-04 04:30 (UTC):
>
> > With the latest Debian I'm trying to find the file to edit to
> > change
> > the IP address of a remote box, can anybody point me in the correct
> > direction please?
>
> > I can SSH into this
On Fri, Jan 05, 2024 at 08:15:08PM +1100, Keith Bainbridgge wrote:
> On 5/1/24 15:30, David wrote:
> > Morning Group,
> >
> > With the latest Debian I'm trying to find the file to edit to change
> > the IP address of a remote box, can anybody point me in the correct
> > direction please?
> >
> >
David
I use nmtuI (from a terminal) for jobs like this. I think it is
installed by default.
I'd bet you'll be terminated when the change activates
All the best
Keith Bainbridge
keith.bainbridge.3...@gmail.com
+61 (0)447 667 468
UTC + 10:00
On 5/1/24 15:30, David wrote:
Morning Group,
Am 05.01.2024 um 04:30:44 Uhr schrieb David:
> With the latest Debian I'm trying to find the file to edit to change
> the IP address of a remote box, can anybody point me in the correct
> direction please?
There are various ways to configure it.
Files in /etc/network, systemd-networkd, NetworkMan
David composed on 2024-01-04 04:30 (UTC):
> With the latest Debian I'm trying to find the file to edit to change
> the IP address of a remote box, can anybody point me in the correct
> direction please?
> I can SSH into this box, but cannot find the file to edit.
Traditionally it would be in /et
Morning Group,
With the latest Debian I'm trying to find the file to edit to change
the IP address of a remote box, can anybody point me in the correct
direction please?
I can SSH into this box, but cannot find the file to edit.
Thank you,
David.
On Ma, 31 aug 21, 16:33:49, Reco wrote:
> On Tue, Aug 31, 2021 at 01:32:32PM +0300, Andrei POPESCU wrote:
> >
> > Another completely different approach is to use some other tool to
> > configure your network that can match on MAC address and just ignore the
> > names completely.
>
> Surely you
On Mon, 2021-08-30 at 20:26 -0400, Greg Wooledge wrote:
> On Tue, Aug 31, 2021 at 01:44:09AM +0200, Steve Keller wrote:
[...]
> > Actually, I don't know this. When I wrote unpredictable new naming
> > scheme I meant systemd's enps scheme, since it's
> > unpredictable for me as long as I don't lear
ably use en<0>, since the wiki
> recommends not using eth. I still don't understand, why eth in
> a systemd.link file would be a problem, since in the udev .rules this
> has worked for years.
It's rather futile as the result is two races instead of one. The
kernel
the release notes I wonder what's the best way to avoid the new scheme
> > > of unpredictable network interface names.
> >
> > You say "server", so I'm guessing it has more than one NIC. That means
> > the old way (net.ifnames=0) is not viable.
> &g
want to keep
it that way.
The Debian wiki on this shows several ways involving kernel cmdline,
udev, and systemd. I've read it, I've also read some of the sparse
and incomplete systemd documentation for almost an hour. Still I
don't know when and what software component (kernel,
On Tue, Aug 31, 2021 at 01:32:32PM +0300, Andrei POPESCU wrote:
> Another completely different approach is to use some other tool to
> configure your network that can match on MAC address and just ignore the
> names completely.
>
> For systemd-networkd
>
> /etc/systemd/network/my.network
>
> [
; of unpredictable network interface names.
>
> You say "server", so I'm guessing it has more than one NIC. That means
> the old way (net.ifnames=0) is not viable.
>
> Your best strategy is to create systemd.link(5) files, and give the NICs
> the names you want t
On Ma, 31 aug 21, 01:11:33, Steve Keller wrote:
>
> I still don't understand, why eth in
> a systemd.link file would be a problem, since in the udev .rules this
> has worked for years.
Greg already explained what problems might show up if you try to use
eth.
The ud
On Tue, Aug 31, 2021 at 01:11:33AM +0200, Steve Keller wrote:
[...]
> OK, several people suggested the kernel command-line option
> net.ifnames=0. Since I almost never change hardware configurations
> this is probably OK even with my two NICs, one on the mainboard, the
> second is a PCI card. I
> the eth. Does udevd run first, does systemd call udev, does
> systemd do the renaming itself or is it done by "net_setup_link udev
> builtin" as systemd.link(5) states?
I don't pretend to know every permutation. On my system, which is a
desktop PC with a builtin NIC con
Roberto C. Sánchez writes:
> Since nobody else has mentioned this link, here is where I recommend you
> start: https://wiki.debian.org/NetworkInterfaceNames
Oh, that's what I meant by "wiki" in my posts. Sorry, I should have
given the URL. It's linked from the buster release-notes in section
5
Greg Wooledge writes:
> On Tue, Aug 31, 2021 at 12:27:57AM +0300, IL Ka wrote:
> > >
> > > This gives unpredictable results if the system has more than one
> > > ethernet interface, or more than one wireless interface.
> > >
> > > It's fine on systems that have 0-1 ethernet and 0-1 wireless NICs.
Greg Wooledge writes:
> On Mon, Aug 30, 2021 at 04:41:55PM -0400, Dan Ritter wrote:
> > Steve Keller wrote:
> > > I plan to upgrade a server from Debian stretch to buster. Having read
> > > the release notes I wonder what's the best way to avoid the new scheme
> > > of unpredictable network in
emd documentation for almost an hour. Still I
> don't know when and what software component (kernel, udev, systemd)
> decides the NIC names and whether and in which way these conflict each
> other. [1]
>
> Also, after reading the wiki it's still unclear to me, which of
IL Ka schrieb:
> > It's fine on systems that have 0-1 ethernet and 0-1 wireless NICs.
>
> Isn't that what the topic starter asked about?:)
I don't think so:
| I simply have eth0 for the internal network and eth1 for
| my external network to the DSL router.
That looks like two ethernet NICs.
On Tue, Aug 31, 2021 at 12:27:57AM +0300, IL Ka wrote:
> >
> > This gives unpredictable results if the system has more than one
> > ethernet interface, or more than one wireless interface.
> >
> > It's fine on systems that have 0-1 ethernet and 0-1 wireless NICs.
> >
>
> Isn't that what the topic
>
> This gives unpredictable results if the system has more than one
> ethernet interface, or more than one wireless interface.
>
> It's fine on systems that have 0-1 ethernet and 0-1 wireless NICs.
>
Isn't that what the topic starter asked about?:)
To make names predictable one can either leave
b, assuming that you are booting with grub,
>
> GRUB_CMDLINE_LINUX_DEFAULT="quiet net.ifnames=0"
>
> The "quiet" is not necessary and is a different feature.
The success of this method on my 5-nic router may be related to
not using systemd.
Also, an update-grub will be necessary.
-dsr-
On Mon, Aug 30, 2021 at 11:36 PM Steve Keller wrote:
> So I'm still confused what to do after the upgrade to buster to keep
> my network names.
>
>
>
in /etc/default/grub add
"net.ifnames=0"
to GRUB_CMDLINE_LINUX
and execute "update-grub"
This service:
https://www.freedesktop.org/software/system
On Mon, Aug 30, 2021 at 04:41:55PM -0400, Dan Ritter wrote:
> Steve Keller wrote:
> > I plan to upgrade a server from Debian stretch to buster. Having read
> > the release notes I wonder what's the best way to avoid the new scheme
> > of unpredictable network interface names.
>
> In /etc/def
Steve Keller wrote:
> I plan to upgrade a server from Debian stretch to buster. Having read
> the release notes I wonder what's the best way to avoid the new scheme
> of unpredictable network interface names.
In /etc/default/grub, assuming that you are booting with grub,
GRUB_CMDLINE_LIN
uot;, so I'm guessing it has more than one NIC. That means
the old way (net.ifnames=0) is not viable.
Your best strategy is to create systemd.link(5) files, and give the NICs
the names you want them to have, based on their MAC addresses.
For example:
unicorn:~$ cat /etc/systemd/network/10-lan
s shows several ways involving kernel cmdline,
udev, and systemd. I've read it, I've also read some of the sparse
and incomplete systemd documentation for almost an hour. Still I
don't know when and what software component (kernel, udev, systemd)
decides the NIC names and whether a
Jaikumar Sharma wrote:
> For my tests on Cisco switch at office (without any changes on
> switch) and using bonding in "active-backup" mode, I can ping the
> active interface using bond0 IP after plugging out the network cable
> of the cable of active interface.
> Only catch was all interfaces m
Hello,
On Sun, Aug 23, 2020 at 09:16:48PM +0200, deloptes wrote:
> Dan Ritter wrote:
> > This really sounds like you're trying to test out a scenario in
> > a situation where it can't possibly work.
> >
>
> But this is exactly what he has to do - connect two wired network interfaces
> to a manag
On Sat, Aug 22, 2020 at 9:36 PM Dan Ritter wrote:
> This really sounds like you're trying to test out a scenario in
> a situation where it can't possibly work.
>
> Don't do that. Test it in as close a simulation to reality as
> possible.
Thanks Dan for insights, it worked - I humbly appreciate you
On Mon, Aug 24, 2020 at 12:47 AM deloptes wrote:
> But this is exactly what he has to do - connect two wired network interfaces
> to a managed switch. Then configure LAGG (LACP) on the switch for the two
> ports and LAGG (LACP) on the PC/server.
Right :)
For my tests on Cisco switch at office (wi
Dan Ritter wrote:
>> Have to test it with two wired connections connected to Cisco managed
>> switch.
>
> This really sounds like you're trying to test out a scenario in
> a situation where it can't possibly work.
>
But this is exactly what he has to do - connect two wired network interfaces
to
Jaikumar Sharma wrote:
> On Sat, Aug 22, 2020 at 5:10 PM Dan Ritter wrote:
> > You still want bridging, not bonding.
> Preferred is bonding, if it works :)
> Have to test it with two wired connections connected to Cisco managed switch.
This really sounds like you're trying to test out a scenar
> hrmm... I just went back to the original post; I missed this bit the
> first time around:
> > In this setup i'm using a D-Link 8 port switch to connect eth0 using
> > ethernet cable and eth1 is connected on wireless adapter of my laptop.
>
> eth0 and eth1 are probably on two different networks (s
On Sat, Aug 22, 2020 at 5:10 PM Dan Ritter wrote:
> You still want bridging, not bonding.
Preferred is bonding, if it works :)
> WiFi doesn't have a cable, so it can't tell you when the
> connection goes away, and it can't decide by itself to bring up
> a connection. You need a management program
only thing that 'ip route'
>> shows is wls1.
>> Yay! automatic failover + automatic selection of the faster interface
>> when it's up :-)
>
> This will generally work, but it does have a drawback: you have
> two different IPs, so when a change happens, all
automatic selection of the faster interface
> when it's up :-)
This will generally work, but it does have a drawback: you have
two different IPs, so when a change happens, all your existing
connections will drop and new inbound connections will only work
on the NIC that's up.
You'll also need to replicate firewall rules on each NIC.
-dsr-
On 8/22/20, Dan Ritter wrote:
> Jaikumar Sharma wrote:
>> On Fri, Aug 21, 2020 at 9:30 PM Dan Ritter wrote:
>> > You don't want a bond, you want a bridge.
>> >
>> > Bonding takes two interfaces that talk to the same switch on the
>> > othe
Jaikumar Sharma wrote:
> On Fri, Aug 21, 2020 at 9:30 PM Dan Ritter wrote:
> > You don't want a bond, you want a bridge.
> >
> > Bonding takes two interfaces that talk to the same switch on the
> > other side, and makes them into one bond nic. You need support
On Fri, Aug 21, 2020 at 9:30 PM Dan Ritter wrote:
> You don't want a bond, you want a bridge.
>
> Bonding takes two interfaces that talk to the same switch on the
> other side, and makes them into one bond nic. You need support
> on the switch, too, which is unlikely in a
Jaikumar Sharma wrote:
> Thank you for pointers, this is a test switch at home but of course
> we have bigger Cisco switches at office which have management interface.
> It look like LACP needs to be checked/enabled on ports which needs to
> be used in network bonding.
Note that LACP is not "acti
On Fri, Aug 21, 2020 at 9:30 PM Dan Ritter wrote:
>
> You don't want a bond, you want a bridge.
>
> Bonding takes two interfaces that talk to the same switch on the
> other side, and makes them into one bond nic. You need support
> on the switch, too, which is unlikely in
Dan Ritter wrote:
> You don't want a bond, you want a bridge.
>
> Bonding takes two interfaces that talk to the same switch on the
> other side, and makes them into one bond nic. You need support
> on the switch, too, which is unlikely in a D-Link 8-port unless
> it has
1 is connected on wireless adapter of my laptop.
You don't want a bond, you want a bridge.
Bonding takes two interfaces that talk to the same switch on the
other side, and makes them into one bond nic. You need support
on the switch, too, which is unlikely in a D-Link 8-port unless
it has a ma
Hi folks,
I'm using Debian 10 (point release 5) and i've set up the bonding for
eth0 and eth1 in 'active-backup' mode, i'm using virtualbox VM for
testing it, if i disconnect cable (virtually from first ethernet -
eth0) ping to bond0 IP stops and if i disconnect it from eth1 and
reconnect on eth0
Hi there,
On Mon, 30 Mar 2020, David Wright wrote:
On Sun 29 Mar 2020 at 13:46:05 (+0100), G.W. Haywood wrote:
> On Sat, 28 Mar 2020, Alan Tu wrote:
>
> > ... "Debian testing" system ... network-manager 1.22.8-1. ...
> > # systemctl restart network-manager
> > After one to four times of this,
On Sun 29 Mar 2020 at 13:46:05 (+0100), G.W. Haywood wrote:
> On Sat, 28 Mar 2020, Alan Tu wrote:
>
> > ... "Debian testing" system ... network-manager 1.22.8-1. ...
> > # systemctl restart network-manager
> > After one to four times of this, eventually network-manager
> > establishes the network
Andrei POPESCU wrote:
> It's very convenient on a laptop switching between various wireless
> networks and has been quite reliable for me in the past years (don't
> even remember how many).
+1
On Du, 29 mar 20, 13:46:05, G.W. Haywood wrote:
> Hi there,
>
> On Sat, 28 Mar 2020, Alan Tu wrote:
>
> > ... "Debian testing" system ... network-manager 1.22.8-1. ...
> > # systemctl restart network-manager
> > After one to four times of this, eventually network-manager
> > establishes the netwo
Hi there,
On Sat, 28 Mar 2020, Alan Tu wrote:
... "Debian testing" system ... network-manager 1.22.8-1. ...
# systemctl restart network-manager
After one to four times of this, eventually network-manager
establishes the network connection.
It seems to me that network-manager is only really us
Alan Tu wrote:
> Thanks for the tip about systemctl -l status network-manager. There is a
> difference.
perhaps you inspect the full log for details. It could be you have a problem
with the driver or with how the device is handled (detected, initialized
etc.), could be also even a kernel bug some
I do not have any other interfaces in /etc/network/interfaces, besides lo.
Thanks for the tip about systemctl -l status network-manager. There is a
difference.
I ran systemctl -l status network-manager on two boots. In both cases, the USB
dongle was already plugged in and was not touched. The f
On Sat 28 Mar 2020 at 20:28:15 +0100, deloptes wrote:
> Alan Tu wrote:
>
> > The network was and is configured in network-manager. I should add that
> > one out of six or seven times, the connection is established automatically
> > at boot. Alan
>
> Do you have anything in /etc/network/interface
Alan Tu wrote:
> The network was and is configured in network-manager. I should add that
> one out of six or seven times, the connection is established automatically
> at boot. Alan
Do you have anything in /etc/network/interfaces except lo?
There should not be anything
furthermore NetworkManage
The network was and is configured in network-manager. I should add that one out
of six or seven times, the connection is established automatically at boot.
Alan
Sent from my iPhone
> On Mar 28, 2020, at 12:02, deloptes wrote:
>
> Alan Tu wrote:
>
>> After trial and error, the best fix is fo
Alan Tu wrote:
> After trial and error, the best fix is for me to get into a terminal
> and restart network-manager:
> # systemctl restart network-manager
>
> After one to four times of this, eventually network-manager
> establishes the network connection.
Have you configured the network-card/co
Hello, I have a "Debian testing" system installed with Mate. It has
network-manager 1.22.8-1.
My network adapter is an Asus USB dongle based on rtl8814au, I
compiled and installed a kernel module for it and the network works
great, once it gets going.
My problem is, when I boot the system and it
:
[4.873221] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready
[7.699434] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex,
Flow Control: Rx/Tx
[7.699478] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s31f6: link becomes ready
[ 10.237498] e1000e :00:1f.6 enp0s31f6: Detected Hardware Unit Hang
basti wrote:
> On 27.05.19 17:32, Sven Hartge wrote:
>> basti wrote:
>>
>>> also on a network card with 2 NIC's
>>
>>> srv-a nic ens2f0 ens2f0 srv-b
>>> ens2f1 ens2f1
>>
>>> Can I use a switch that only
On 27.05.19 17:32, Sven Hartge wrote:
> basti wrote:
>
>> also on a network card with 2 NIC's
>
>> srv-a nic ens2f0 ens2f0 srv-b
>> ens2f1 ens2f1
>
>> Can I use a switch that only supoort static LAC to speedup my
>> connect
Sven Hartge wrote:
>> also on a network card with 2 NIC's
>
>> srv-a nic ens2f0 ens2f0 srv-b
>> ens2f1 ens2f1
>
>> Can I use a switch that only supoort static LAC to speedup my
>> connection? For example tp-link TL-SG108E ? Or must it support
basti wrote:
> I want to speedup my network connection beween srv-a and srv-b. There is
> only a 1:1 connection.
> I have try to use balance-alb and copy some files from a to b with only
> 112 MB/s with dd and netcat.
In the RHEL Network Guide [1] it says that LACP is supported only with
switch
basti wrote:
> also on a network card with 2 NIC's
> srv-a nic ens2f0 ens2f0 srv-b
> ens2f1 ens2f1
> Can I use a switch that only supoort static LAC to speedup my
> connection? For example tp-link TL-SG108E ? Or must it support LACP?
For this direct c
Reco wrote:
> On Mon, May 27, 2019 at 01:48:39PM +0200, basti wrote:
>> Can this mode be used in this setup?
> AFAIK standard linux bonding can only use Passive LACP in 802.3ad.
No, it does active LACP.
>> How must I configure the other side?
> That's means you have to use openvswitch on eith
also on a network card with 2 NIC's
srv-a nic ens2f0 ens2f0 srv-b
ens2f1 ens2f1
Can I use a switch that only supoort static LAC to speedup my
connection? For example tp-link TL-SG108E ? Or must it support LACP?
On 27.05.19 15:49, Reco wrote:
> Hi.
>
>
Hi.
On Mon, May 27, 2019 at 04:36:10PM +0200, basti wrote:
> also on a network card with 2 NIC's
>
> srv-a nic ens2f0 ens2f0 srv-b
> ens2f1 ens2f1
>
> Can I use a switch that only supoort static LAC to speedup my
> connection? For example
also on a network card with 2 NIC's
srv-a nic ens2f0 ens2f0 srv-b
ens2f1 ens2f1
Can I use a switch that only supoort static LAC to speedup my
connection? For example tp-link TL-SG108E ? Or must it support LACP?
On 27.05.19 15:49, Reco wrote:
> Hi.
>
>
Hi.
On Mon, May 27, 2019 at 03:36:38PM +0200, basti wrote:
> Hello sven,
> hello reco,
>
> I want to speedup my network connection beween srv-a and srv-b. There is
> only a 1:1 connection.
Any bonding mode will utilize a single link in such case.
The 'catch 22' for active-active bonding
Hello sven,
hello reco,
I want to speedup my network connection beween srv-a and srv-b. There is
only a 1:1 connection.
I have try to use balance-alb and copy some files from a to b with only
112 MB/s with dd and netcat.
So Im not shure if balance-alb use both interfaces.
On 27.05.19 15:09, Reco
Hi.
On Mon, May 27, 2019 at 01:48:39PM +0200, basti wrote:
> Can this mode be used in this setup?
AFAIK standard linux bonding can only use Passive LACP in 802.3ad.
> How must I configure the other side?
That's means you have to use openvswitch on either side as it can be
configured to
basti wrote:
> I have 2 Servers both of them has an dual port nic, I want to bond this
> and try to configure this in 802.3ad mode. There are no switch beween,
> and there is no crossover cable installed.
"and there is no crossover cable installed"?
Beside the point that Gi
Hello,
I have 2 Servers both of them has an dual port nic, I want to bond this
and try to configure this in 802.3ad mode. There are no switch beween,
and there is no crossover cable installed.
Can this mode be used in this setup?
How must I configure the other side? (I have use this howto,
https
On Mon, Jul 31, 2017 at 11:18 Curt wrote:
...
> Are you not confounding the de and dk domain suffixes, because I believe
> Sven is 'de' (Germany).
You are certainly correct and I should have caught my error before
sending. My apologies for any offended sensibilities.
50th wedding anniversary.
On Mon, Jul 31, 2017 at 04:17:24PM +, Curt wrote:
>
> Never heard of Arhus.
Aarhus is the main town of Jutland, Danmark.
--
"Certitude is not the test of certainty."
--Oliver Wendell Holmes, Jr.
&
"Education is a man's going
from cocksure ignorance
to thoughtful uncertainty."
On 2017-07-26, Tom Browder wrote:
>
> Thanks so much Sven.
>
> Best regards,
>
> -Tom
>
> BTW, my wife and I and two friends had a very nice time visiting
> Denmark in May while on a cruise in the Baltic celebrating our 50th
> wedding anniversary. Our ship, Holland-America's ms Rotterdam,
> visit
On Wed, Jul 26, 2017 at 5:42 PM, Tom Browder wrote:
> On Wed, Jul 26, 2017 at 3:43 PM, Sven Hartge wrote:
...
>> ,
>> | auto eth0
>> | iface eth0 inet static
>> | address 142.54.186.2/29
>> | gateway 142.54.186.1
>> | dns-nameservers 192.187.107.16 69.30.209.16
>>
On Wed, Jul 26, 2017 at 3:43 PM, Sven Hartge wrote:
> Tom Browder wrote:
>> On Wed, Jul 26, 2017 at 2:11 PM, Sven Hartge wrote:
>
>> So can the above be simplified by leaving out the repeated info like
>> dns-nameservers, gateway, and netmask to give something like:
>
>> #===
Tom Browder wrote:
> On Wed, Jul 26, 2017 at 2:11 PM, Sven Hartge wrote:
> So can the above be simplified by leaving out the repeated info like
> dns-nameservers, gateway, and netmask to give something like:
> #=
> iface eth0 inet static
> address 142
On Wed, Jul 26, 2017 at 2:11 PM, Sven Hartge wrote:
> Georgi Naplatanov wrote:
>> On 07/26/2017 09:22 PM, Sven Hartge wrote:
>>> Tom Browder wrote:
>>> You don't need those up/down parts, you can add additional blocks for
>>> eth0:
>>>
>>> auto eth0
>>> iface eth0 inet static
>>> address
Georgi Naplatanov wrote:
> On 07/26/2017 09:22 PM, Sven Hartge wrote:
>> Tom Browder wrote:
>>
>>> The proposed /etc/network/interfaces file:
>>> # begin =
>>> iface eth0 inet static
>>> address 142.54.186.2
>>> netmask 255.255.255.248
>>> gate
On 07/26/2017 09:22 PM, Sven Hartge wrote:
> Tom Browder wrote:
>
>> The proposed /etc/network/interfaces file:
>> # begin =
>> iface eth0 inet static
>> address 142.54.186.2
>> netmask 255.255.255.248
>> gateway 142.54.186.1
>> dns-name
Tom Browder wrote:
> The proposed /etc/network/interfaces file:
> # begin =
> iface eth0 inet static
> address 142.54.186.2
> netmask 255.255.255.248
> gateway 142.54.186.1
> dns-nameservers 192.187.107.16 69.30.209.16
> # add n
Last year I successfully modified /etc/network/interfaces on my remote
debian 8 server to handle multiple IPv4 addresses on a single NIC, and
now I want to add its IPv6 capability.
But, before I do, I would like to show you my proposed new interfaces
file for comment and to make sure I don&#
Dan Ritter wrote:
> Case 2: a system gains redundancy and capacity.
> Each NIC attaches to the same switch. The switch has to be
> configurable to do Link Aggregation Protocol -- not all can.
> You configure the system NICs to become a bond device, using
> 80
Dennis Wicks wrote:
> I find myself with several unused NICs (network interface
> cards) and some empty ports on my switches.
>
> Would it be beneficial to have more than one network
> connection on a system?
As with many things, "it depends". What's the box in question do?
--
|_|O|_| Regist
o with it, and how would I set it up? Pointers to
> tutorials and how-to's would be nice!
Case 1: A system becomes a router.
Each NIC attaches to a different IP network. Turn on IP
Forwarding. Now it's a router.
Run iptables, and it's a firewall, too.
Case 2: a system gai
I find myself with several unused NICs (network interface
cards) and some empty ports on my switches.
Would it be beneficial to have more than one network
connection on a system?
If so, what would I do with it, and how would I set it up?
Pointers to tutorials and how-to's would be nice!
Ma
Le 27/11/2015 08:16, Leslie Rhorer a écrit :
[...]
> Upon detecting this card, Debian Jessie uses the rfkill API to soft
> block the wireless adapter, assuming this to be a laptop who should
> not have WiFi enabled unless the user specifically enables it
> manually. Of course, if there were a moni
I've seen lots of posts concerning turning off WiFi on a laptop or using a
button on the laptop to turn on wireless, but nothing that covers this
situation. There are a number of bookshelf PCs, including the Intel NUC line
of computers that use the same mini PCI cards as laptop computers such a
Hello,
you can find a lot of useful info on: http://www.aboutdebian.com/network.htm
2015-06-01 16:22 GMT+02:00 Darac Marjal :
> On Mon, Jun 01, 2015 at 03:48:51PM +0200, notoneofmy wrote:
> > Hallo,
> >
> > Would some please say, how to configure the wifi card and the Ethernet
> > port on my lap
On Mon, Jun 01, 2015 at 03:48:51PM +0200, notoneofmy wrote:
> Hallo,
>
> Would some please say, how to configure the wifi card and the Ethernet
> port on my laptop, so that one can go online and the other can only
> access the local network. And in such a way that connection from one
> network, lo
Hallo,
Would some please say, how to configure the wifi card and the Ethernet
port on my laptop, so that one can go online and the other can only
access the local network. And in such a way that connection from one
network, local, cannot be used to access another network, internet.
Thanks a lot i
On Wednesday, February 18, 2015 09:32:42 PM Dan Purgert wrote:
> On Wed, 18 Feb 2015 20:46:20 -0500, Gene Heskett wrote:
> > On Wednesday, February 18, 2015 07:01:19 PM BUCH wrote:
> >> [...]
> >
> > ...sure learned a lot about installing the plugs on a piece of cat5.
> >
> > Cheers, Gene Heskett
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/18/2015 08:06 PM, Richard Hector wrote:
> On 19/02/15 15:32, Dan Purgert wrote:
>> Point of contention -- if the BUCH is only using cat5 in his
>> install, the fact he's getting gbit for any time at all is a
>> miracle. Min requirement for gig
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19/02/15 15:32, Dan Purgert wrote:
> Point of contention -- if the BUCH is only using cat5 in his
> install, the fact he's getting gbit for any time at all is a
> miracle. Min requirement for gig over copper is 5e (with cat6
> being preferred).
My
1 - 100 of 1553 matches
Mail list logo
