Re: suggestion for the installer
On 10/29/20 3:38 PM, Nick Holland wrote:
On 2020-10-29 08:00, Harald Dunkel wrote:
Hi folks,
do you think it would be possible for the installer to show
an eye-catching warning, if "ifconfig" reports "no carrier"
for the network port to configure?
Just a suggestion, of course
Harri
Why?
Because accidents happen. You plugin a cable in the left
socket and em0 turns out to be the right one. Imagine a
network appliance with ports labeled eth{1..8} instead
of eth{0..7}.
Sorry for asking
Harri
Re: suggestion for the installer
it possibly an inline indicator on wired on question which interface do you want to configure em0, em1 (down), em2down) [em0] : but wireless interfaces will always be down before you associate with the AP... that said if using DHCP it is pretty obvious when a link is down... and on a static ip you know how to set it so you know how to run ifconfig to diagnose it... I dont feel that strongly about it ... but i can see it would help in some situation ... so if there is an existing network status line in the installer perhaps appending a lnk down message there would be helpful without impacting someone's terminal (as highlighted by Theo and Nick) All the best, Tom Smyth On Thu, 29 Oct 2020 at 16:10, Theo de Raadt wrote: > > Nick Holland wrote: > > > On 2020-10-29 08:00, Harald Dunkel wrote: > > > Hi folks, > > > > > > do you think it would be possible for the installer to show > > > an eye-catching warning, if "ifconfig" reports "no carrier" > > > for the network port to configure? > > > > > > Just a suggestion, of course > > > Harri > > > > Why? > > What problem are you trying to solve, and how many are you > > planning on making for me in the process? > > > > I often end up setting up OpenBSD systems with no network > > attached. Nothing to warn me about. > > > > I very often install OpenBSD configuring several NICs when > > only one has a network currently. Again, PLEASE don't give > > me three, five or ten bogus warning messages. > > Precisely. vertical screen real-estate is valuable. People > often look up higher at what they've already done, and a warning > would consume 1 line per interface, and reduce the visible context > for a person performing an multi-network install manually, thereby > increasing potential error. > -- Kindest regards, Tom Smyth.
Re: suggestion for the installer
Nick Holland wrote: > On 2020-10-29 08:00, Harald Dunkel wrote: > > Hi folks, > > > > do you think it would be possible for the installer to show > > an eye-catching warning, if "ifconfig" reports "no carrier" > > for the network port to configure? > > > > Just a suggestion, of course > > Harri > > Why? > What problem are you trying to solve, and how many are you > planning on making for me in the process? > > I often end up setting up OpenBSD systems with no network > attached. Nothing to warn me about. > > I very often install OpenBSD configuring several NICs when > only one has a network currently. Again, PLEASE don't give > me three, five or ten bogus warning messages. Precisely. vertical screen real-estate is valuable. People often look up higher at what they've already done, and a warning would consume 1 line per interface, and reduce the visible context for a person performing an multi-network install manually, thereby increasing potential error.
Re: suggestion for the installer
Hi Harald, If im not mistaken when the installer is running when you configure dhcp on the interface t will warn you that it is not receiving any leases. I can see your concerns about the static ip configuration at a guess I think the issue is there is no config on the interfaces so they havent yet been instructed to start or put a config on them... as a workaround when you start up the installer you can select shell or hit c to exit the installer back to a shell and you can can do ifconfig interface name or ifconfig interface_name up and when you are done checking you can run the install to restart the install process I hope this helps a little On Thu, 29 Oct 2020 at 12:06, Harald Dunkel wrote: > > Hi folks, > > do you think it would be possible for the installer to show > an eye-catching warning, if "ifconfig" reports "no carrier" > for the network port to configure? > > Just a suggestion, of course > Harri > -- Kindest regards, Tom Smyth.
Re: suggestion for the installer
On 2020-10-29 08:00, Harald Dunkel wrote: > Hi folks, > > do you think it would be possible for the installer to show > an eye-catching warning, if "ifconfig" reports "no carrier" > for the network port to configure? > > Just a suggestion, of course > Harri Why? What problem are you trying to solve, and how many are you planning on making for me in the process? I often end up setting up OpenBSD systems with no network attached. Nothing to warn me about. I very often install OpenBSD configuring several NICs when only one has a network currently. Again, PLEASE don't give me three, five or ten bogus warning messages. Usually if I'm doing an install, I look to see if the link light on the NIC and the switch port is lit. If I'm using DHCP, I'll quickly know if there's a network problem. Come to think of it, if I'm NOT using DHCP, I'll quickly know, too. If I'm installing to an unknown system, I almost always first drop to (s)hell from the installer, look at my dmesg, look at the network port options and see if I'm plugged into the NIC port I think I am (ifconfig), look at my disks to see if they are recognized as I expect and see if I'm about to clobber something I might consider important. So...I think what you are trying to accomplish can be done as things are without adding to the wonderfully simple OpenBSD installer. Nick.
suggestion for the installer
Hi folks, do you think it would be possible for the installer to show an eye-catching warning, if "ifconfig" reports "no carrier" for the network port to configure? Just a suggestion, of course Harri
