Re: [...] "How does the new naming scheme look like, precisely?"

[poma]

On 13.03.2017 21:37, Stephen Morris wrote:
[...]
> In fact, for me, Fedora's naming convention raises more questions than 
> it answers. Without knowing anything about the internal hardware design 
> of a motherboard, how is a usb port on a pci bus, I would expect pci 
> ports to be on a pci bus and usb ports to be on a usb bus, and relative 
> to usb ports I would expect there to be a separate bus for usb 2 and usb 
> 3 ports.
[...]

Hello Zbigniew,
would you mind to further explain the naming scheme?

I show an example;

dmesg -t | grep wl -m1
r92su 1-3:1.0 wlp0s2f1u3: renamed from wlan0

wlp0s2f1u3
wl   p0   s2f1u3
wl-wlan  p-bus=0  s-slot=2  f-function=1  u-port=3

lsusb
Bus 001 Device 003: ...

lsusb -t
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
|__ Port 3: Dev 3, If 0, Class=Vendor Specific Class, Driver=r92su, 480M

ls /sys/devices/pci:00/:00:02.1/usb1/1-3/1-3:1.0/net/
wlp0s2f1u3

lspci -d ::0c03
00:02.1 USB controller: ...
 0002   1
:.

udevadm info -q env /sys/class/net/wlp0s2f1u3 | grep PATH
DEVPATH=/devices/pci:00/:00:02.1/usb1/1-3/1-3:1.0/net/wlp0s2f1u3
ID_NET_NAME_PATH=wlp0s2f1u3
ID_PATH=pci-:00:02.1-usb-0:3:1.0
ID_PATH_TAG=pci-_00_02_1-usb-0_3_1_0

udevadm info -a -p /sys/class/net/wlp0s2f1u3 | grep looking -A 3
  looking at device 
'/devices/pci:00/:00:02.1/usb1/1-3/1-3:1.0/net/wlp0s2f1u3':
KERNEL=="wlp0s2f1u3"
SUBSYSTEM=="net"
DRIVER==""
--
  looking at parent device '/devices/pci:00/:00:02.1/usb1/1-3/1-3:1.0':
KERNELS=="1-3:1.0"
SUBSYSTEMS=="usb"
DRIVERS=="r92su"
--
  looking at parent device '/devices/pci:00/:00:02.1/usb1/1-3':
KERNELS=="1-3"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
--
  looking at parent device '/devices/pci:00/:00:02.1/usb1':
KERNELS=="usb1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
--
  looking at parent device '/devices/pci:00/:00:02.1':
KERNELS==":00:02.1"
SUBSYSTEMS=="pci"
DRIVERS=="ehci-pci"
--
  looking at parent device '/devices/pci:00':
KERNELS=="pci:00"
SUBSYSTEMS==""
DRIVERS==""

Ref.
https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames
https://github.com/systemd/systemd/blob/master/src/udev/udev-builtin-net_id.c#L46
 *   [P]ps[f][u][..][c][i]
 * — USB port number chain
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: virt-manager thinks an ISO file is a directory

[Ed Greshko]

On 03/14/17 08:10, Ed Greshko wrote:
> I have a "shadier" version of a Win10 DVD that I installed in VirtualBox
> last year.  I'll give it a try later today.


Later today came earlier than expected.

I am now in the process of installing Win10 under virt-manager.  The ISO
file was recognized just fine. 

-- 
Fedora Users List - The place to go to get others to do the work for you
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: virt-manager thinks an ISO file is a directory

[Ed Greshko]

On 03/14/17 08:01, Patrick O'Callaghan wrote:
>> A Windows 10 ISO downloaded from Microsoft (i.e. legit) plus some
>> shadier versions as a test. None of them worked.
> To clarify: none of them worked today. Last time I tried this was
> several months ago and they did work, so something has changed in the
> meantime. Currently using virt-manager-1.4.0-5.fc25.noarch


OK, thanks.

I have a "shadier" version of a Win10 DVD that I installed in VirtualBox
last year.  I'll give it a try later today.

-- 
Fedora Users List - The place to go to get others to do the work for you
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: virt-manager thinks an ISO file is a directory

[Patrick O'Callaghan]

On Mon, 2017-03-13 at 23:56 +, Patrick O'Callaghan wrote:
> On Tue, 2017-03-14 at 07:45 +0800, Ed Greshko wrote:
> > On 03/14/17 00:02, Patrick O'Callaghan wrote:
> > > I have had used virt-manager multiple times with other ISOs, just not
> > > with this one. I've sent the log to Cole (BTW it seems to log to
> > > ~/.cache/virt-manager/virt-manager.log by default, i.e. when run
> > > without options).
> > 
> > 
> > Great.
> > 
> > Looking forward to hearing the results.
> > 
> > BTW, can your reveal what iso you were attempting to use?
> > 
> 
> A Windows 10 ISO downloaded from Microsoft (i.e. legit) plus some
> shadier versions as a test. None of them worked.

To clarify: none of them worked today. Last time I tried this was
several months ago and they did work, so something has changed in the
meantime. Currently using virt-manager-1.4.0-5.fc25.noarch

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: virt-manager thinks an ISO file is a directory

[Patrick O'Callaghan]

On Tue, 2017-03-14 at 07:45 +0800, Ed Greshko wrote:
> On 03/14/17 00:02, Patrick O'Callaghan wrote:
> > I have had used virt-manager multiple times with other ISOs, just not
> > with this one. I've sent the log to Cole (BTW it seems to log to
> > ~/.cache/virt-manager/virt-manager.log by default, i.e. when run
> > without options).
> 
> 
> Great.
> 
> Looking forward to hearing the results.
> 
> BTW, can your reveal what iso you were attempting to use?
> 

A Windows 10 ISO downloaded from Microsoft (i.e. legit) plus some
shadier versions as a test. None of them worked.

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: virt-manager thinks an ISO file is a directory

[Ed Greshko]

On 03/14/17 00:02, Patrick O'Callaghan wrote:
> I have had used virt-manager multiple times with other ISOs, just not
> with this one. I've sent the log to Cole (BTW it seems to log to
> ~/.cache/virt-manager/virt-manager.log by default, i.e. when run
> without options).


Great.

Looking forward to hearing the results.

BTW, can your reveal what iso you were attempting to use?

-- 
Fedora Users List - The place to go to get others to do the work for you
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Networkmanager Refuses to use my Dlink DWA-192 USB Wifi Device in F24 [Resolved]

[Stephen Morris]

On 3/8/17 8:25 AM, Rick Stevens wrote:

On 03/07/2017 01:14 PM, Stephen Morris wrote:

On 3/7/17 3:49 PM, poma wrote:

On 06.03.2017 21:44, Stephen Morris wrote:


It has subsequently turned out that wlp4s6 was an old pci wifi card that
I still had in my machine that I thought was dead. I was not aware of
the naming conventions for the device identifiers, so I was not aware
that wlp4s6 was not my USB wifi adapter. So I have been trying all this
time to get the 5GHz channel working on wlp4s6 because of this
misunderstanding when in reality that device doesn't have a 5 GHz
channel.
The whole reason for my USB wifi adapter not being used was because I
needed to download and compile a driver to be able to use the device as
there is no inbuilt support for it.
I would like to thank everybody who provided support for this issue and
apologize for wasting everyone's time (I had a DWA182 which had to have
a driver compiled to be usable so I should have expected the DWA192 to
be in the same situation).

As a side issue to this, actually getting the USB device working has
highlighted a bug in Fedora that doesn't exist in Ubuntu (Ubuntu has a
different bug that Fedora doesn't have).

Also Fedora and Ubuntu both use the same naming convention for the pci
wifi adapter but they use a different naming convention for the same USB
wifi adapter plugged into the same USB port. Why is this the case, why
isn't there a Linux wide naming standard?


$ man 8 udevadm
...
OPTIONS
...
 udevadm info [options] [devpath|file]
 Queries the udev database for device information stored in the
udev database. It can also query the properties of a device from its
 sysfs representation to help creating udev rules that match
this device.
 ...

Thus, one can do the following,
e.g. for D-Link DWA-192 - if the ifname is "wlp3s0u2":

# udevadm info -a -p /sys/class/net/wlp3s0u2

In accordance with the properties listed, udev rule can be made,
a rule to rename the ifname:

e.g.
/etc/udev/rules.d/60-persistent-wifi-names.rules:
ACTION=="add", ATTRS{idVendor}=="2001", ATTRS{idProduct}=="331a",
NAME="dwa192"
ACTION=="add", ATTRS{idVendor}=="2001", ATTRS{idProduct}=="3315",
NAME="dwa182"

Re-plug USB device, observe dmesg output.


Sorry, what I was getting at with my question was:
 Under Fedora I issue iwconfig and it tells me the name of my USB
wifi adapter is wlp3s0u2,
 Under Ubuntu I issue iwconfig and it tells me the name of my USB
wifi adapter is wlx6c722000acc4.

 Why is there not a core Linux standard that specifies what the name
of the device must be so that it is the same across all Linux
Distributions (as in my view it should be). Along those lines, why even
change the name from wlan0, sure that doesn't indicate what type of
device it is, but who cares, the driver is written for the chipset in
the device and will work irrespective of whether the device with that
chipset is USB or PCI.

Fedora and Ubuntu use different udev naming rules. Under Fedora, the
device name "wlp3s0u2" means "wireless" (the "wl"), on PCI bus 3
("p3"), subdevice 0 ("s0"), unit 2 ("u2"). Typically, if you see a
"unit" part in a device name, it's probably a USB device. It makes
perfect sense based on Fedora's udev rules. A wired, PCI-based NIC
might be "enp4s0" (ethernet NIC, PCI bus 4, subdevice 0).

Ubuntu uses a similar prefix ("wl" for wireless), but they have
different udev naming rules. Based on what you've given above, it looks
like just put in an "x" followed by the MAC address of the NIC in hex.
That also makes sense and may be easier to chase than Fedora's in some
cases.
It hadn't registered to me that Ubuntu's convention was the mac address, 
but given that it is, and how the mac address is represented, the "x" 
preceding the mac address makes perfect sense.


I'm not saying the either naming convention is right or wrong, what I'm 
objecting to is the fact that they are different. In my view it doesn't 
matter how the device name is derived as long as whatever derivation a 
distribution uses equates to the same name result across all 
distributions. In fact as far as I am concerned it serves no sensible 
purpose, in this case, to rename wlan0 to wlp3s0u2. After all the device 
driver for my device is written specifically for the chipset in the 
device, not the device, all the driver is doing is generating the 
channel program to tell the chipset what to do for the function being 
requested, and whether the device is usb, pci or ethernet is irrelevant 
to the driver, all it is doing is sending the the channel program 
commands to the device named on the network interface and it is up to 
the network interface to take care of how that "data" gets to the device 
based on what type of device it is and where it is.


In fact, for me, Fedora's naming convention raises more questions than 
it answers. Without knowing anything about the internal hardware design 
of a motherboard, how is a usb port on a pci bus, I would expect pci 

Re: Dual head - Dual console?

[stan]

On Mon, 13 Mar 2017 13:53:55 +0100
poma  wrote:

> That "sophisticated" software "that runs the virtual consoles" with
> multiple outputs is called X Window System, be it X11 or Wayland. So
> if you ask the Linux kernel console to be the X Window System, well,
> it is, already! Do you follow? :)

I think you are thinking of xterms, that run under X.  But the virtual
consoles are started by agetty at startup, and when I look in man
agetty, I don't see any way to tell agetty which hardware to use.
Systemd might be able to somehow do that when it starts the consoles.
Maybe some can be set to permanently use a different video output
device.  I didn't look into it deeply enough to find how the output
device is set.

I see that only in kernel 4.11 has the framebuffer code been
enhanced to allow for separate buffers for each virtual console, and I
think that would be essential for using separate screens, though I
haven't got it working. Because they share a scrollback buffer, if I log
into two virtual consoles and do output in both, I lose the ability to
scroll backward in a virtual console if I switch to another virtual
console and back because of this.  Using screen in a virtual console
already has this capability, but that is because screen provides it.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: virt-manager thinks an ISO file is a directory

[Patrick O'Callaghan]

On Mon, 2017-03-13 at 10:24 -0400, Tom Horsley wrote:
> On Mon, 13 Mar 2017 12:42:37 +
> Patrick O'Callaghan wrote:
> 
> > Trying to set up a new VM using virt-manager (KVM/QEMU) , something
> > I've done several times before now. However on specifying an ISO file
> > for installation it's telling me " must be a file or device,
> > not a directory". This is nonsense as the ISO is unquestionably a file.
> > 
> > Is this a new bug?
> 
> Had you used it in virt-manager previously? I'm pretty sure I remember
> hitting a bug where virt-manager would auto generate an entry for
> a storage pool to hold an iso I navigated to with the local filesystem
> browser, and once that pool existed, I could never use that iso again
> till I first deleted the auto generated pool.

I have had used virt-manager multiple times with other ISOs, just not
with this one. I've sent the log to Cole (BTW it seems to log to
~/.cache/virt-manager/virt-manager.log by default, i.e. when run
without options).

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Dual head - Dual console?

[Michael Hennebry]

On Mon, 13 Mar 2017, poma wrote:


On 11.03.2017 23:36, stan wrote:

On Sat, 11 Mar 2017 12:30:22 -0600
Steve Berg  wrote:


Is there anyway to get a dual head system to use the two monitors as
two different consoles?  I got a dual head setup working nicely in
F25 and Gnome, but when I switch to the console the two monitors are
mirrored. Can they be set up to be two different consoles as well as
the virtual consoles on "Alt-F2, Alt-F3" etc?


I don't know, but I suspect that the framebuffer software that runs the
virtual consoles is not sophisticated enough to do what you want.



That "sophisticated" software "that runs the virtual consoles" with multiple 
outputs is called X Window System, be it X11 or Wayland.
So if you ask the Linux kernel console to be the X Window System, well, it is, 
already!
Do you follow? :)


I don't.
My recollection is that with a single keyboard and monitor,
virtual consoles do not require X.
One can even run different instances of X on each virtual console.

--
Michael   henne...@web.cs.ndsu.nodak.edu
"Sorry but your password must contain an uppercase letter, a number,
a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
 --  someeecards
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: headset/headphones popup

[Matt Morgan]

On Mon, Mar 13, 2017 at 10:58 AM, Matt Morgan 
wrote:

> Since upgrading to Fedora 25 (Gnome), when I plug in my headset, my
> computer now
>
> a) properly routes sound to the speakers and sets sound input to the
> headset's microphone (yay)
> b) asks me anyway, in a popup, what kind of thing I just plugged in (why?).
>

Nevermind, it's a problem with some new laptops and competing standards.

http://voices.canonical.com/david.henningsson/2014/03/07/headset-jacks-on-newer-laptops/
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: SSH problem from BasicLinux floppy booted 486 to Fedora 25

[Philip Rhoades]

Jakub,


On 2017-03-13 23:43, users-requ...@lists.fedoraproject.org wrote:

Date: Mon, 13 Mar 2017 09:55:42 +0100
From: Jakub Jelen 
Subject: Re: SSH problem from BasicLinux floppy booted 486 to Fedora
25
To: p...@pricom.com.au, Community support for Fedora users

Message-ID: 
Content-Type: text/plain; charset=utf-8; format=flowed

On 03/13/2017 07:02 AM, Philip Rhoades wrote:

People,

I get an error trying to ssh from a BasicLinux floppy booted 486 (I 
want

to sort out HD problems on the old Adaptec 1542 controlled SCSI drive
that has RH5.2 on it!) when trying to connect to my Fedora 25 x86_64
workstation.  On the F25 machine in /var/log/secure I get lines like:

Mar 13 16:25:47 phil sshd[7562]: Unable to negotiate with 192.168.1.40
port 1034: no matching key exchange method found. Their offer:
diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 
[preauth]


You are connecting from very old OpenSSH client (3.5), which does not
support any of the currently secure cryptography algorithms. You should
really consider updating that BasicLinux.



There will probably be a very infrequent need to boot that computer - 
once I rsync everything off it, the HD will probably only be used for 
odd testing after that.  Also, I am already using 3 floppies to boot the 
machine - an up-to-date BL will be bigger and use more floppies etc etc




Otherwise you can enable the legacy kex and ciphers in the Fedora
OpenSSH server by following these instructions:

http://www.openssh.com/legacy.html



Perfect!  Thanks for that - I can reverse using the legacy stuff after I 
recover the data from the old machine.


Regards,

Phil.
--
Philip Rhoades

PO Box 896
Cowra  NSW  2794
Australia
E-mail:  p...@pricom.com.au
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

headset/headphones popup

[Matt Morgan]

Since upgrading to Fedora 25 (Gnome), when I plug in my headset, my
computer now

a) properly routes sound to the speakers and sets sound input to the
headset's microphone (yay)
b) asks me anyway, in a popup, what kind of thing I just plugged in (why?).

This popup doesn't seem useful, although there may be some benefit I
haven't needed in 25 years and never thought of myself. Can I turn off the
popup?

This seems to happen to some people using Ubuntu, but I don't see answers
online.

Thanks,
Matt
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: virt-manager thinks an ISO file is a directory

[Cole Robinson]

On 03/13/2017 10:24 AM, Tom Horsley wrote:
> On Mon, 13 Mar 2017 12:42:37 +
> Patrick O'Callaghan wrote:
> 
>> Trying to set up a new VM using virt-manager (KVM/QEMU) , something
>> I've done several times before now. However on specifying an ISO file
>> for installation it's telling me " must be a file or device,
>> not a directory". This is nonsense as the ISO is unquestionably a file.
>>
>> Is this a new bug?
> 
> Had you used it in virt-manager previously? I'm pretty sure I remember
> hitting a bug where virt-manager would auto generate an entry for
> a storage pool to hold an iso I navigated to with the local filesystem
> browser, and once that pool existed, I could never use that iso again
> till I first deleted the auto generated pool.

That's news to me. If you can reproduce, please file a bug with virt-manager
--debug output

Thanks,
Cole
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: virt-manager thinks an ISO file is a directory

[Tom Horsley]

On Mon, 13 Mar 2017 12:42:37 +
Patrick O'Callaghan wrote:

> Trying to set up a new VM using virt-manager (KVM/QEMU) , something
> I've done several times before now. However on specifying an ISO file
> for installation it's telling me " must be a file or device,
> not a directory". This is nonsense as the ISO is unquestionably a file.
> 
> Is this a new bug?

Had you used it in virt-manager previously? I'm pretty sure I remember
hitting a bug where virt-manager would auto generate an entry for
a storage pool to hold an iso I navigated to with the local filesystem
browser, and once that pool existed, I could never use that iso again
till I first deleted the auto generated pool.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: virt-manager thinks an ISO file is a directory

[Cole Robinson]

On 03/13/2017 08:42 AM, Patrick O'Callaghan wrote:
> Trying to set up a new VM using virt-manager (KVM/QEMU) , something
> I've done several times before now. However on specifying an ISO file
> for installation it's telling me " must be a file or device,
> not a directory". This is nonsense as the ISO is unquestionably a file.
> 
> Is this a new bug?

Maybe, but tough to say without more info. Please reproduce with virt-manager
--debug and mail me the full output

Thanks,
Cole
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: virt-manager thinks an ISO file is a directory

[Ed Greshko]

On 03/13/17 20:42, Patrick O'Callaghan wrote:
> Trying to set up a new VM using virt-manager (KVM/QEMU) , something
> I've done several times before now. However on specifying an ISO file
> for installation it's telling me " must be a file or device,
> not a directory". This is nonsense as the ISO is unquestionably a file.
>
> Is this a new bug?


I don't use virt-manager all the often.  But I just tried with an
F25Workstation Live DVD and it works just fine.

virt-manager-1.4.0-5.fc25

-- 
Fedora Users List - The place to go to get others to do the work for you
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Dual head - Dual console?

[poma]

On 11.03.2017 23:36, stan wrote:
> On Sat, 11 Mar 2017 12:30:22 -0600
> Steve Berg  wrote:
> 
>> Is there anyway to get a dual head system to use the two monitors as
>> two different consoles?  I got a dual head setup working nicely in
>> F25 and Gnome, but when I switch to the console the two monitors are
>> mirrored. Can they be set up to be two different consoles as well as
>> the virtual consoles on "Alt-F2, Alt-F3" etc?
> 
> I don't know, but I suspect that the framebuffer software that runs the
> virtual consoles is not sophisticated enough to do what you want.
> 

That "sophisticated" software "that runs the virtual consoles" with multiple 
outputs is called X Window System, be it X11 or Wayland.
So if you ask the Linux kernel console to be the X Window System, well, it is, 
already!
Do you follow? :)
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

virt-manager thinks an ISO file is a directory

[Patrick O'Callaghan]

Trying to set up a new VM using virt-manager (KVM/QEMU) , something
I've done several times before now. However on specifying an ISO file
for installation it's telling me " must be a file or device,
not a directory". This is nonsense as the ISO is unquestionably a file.

Is this a new bug?

poc
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: SSH problem from BasicLinux floppy booted 486 to Fedora 25

[Jakub Jelen]

On 03/13/2017 07:02 AM, Philip Rhoades wrote:

People,

I get an error trying to ssh from a BasicLinux floppy booted 486 (I want
to sort out HD problems on the old Adaptec 1542 controlled SCSI drive
that has RH5.2 on it!) when trying to connect to my Fedora 25 x86_64
workstation.  On the F25 machine in /var/log/secure I get lines like:

Mar 13 16:25:47 phil sshd[7562]: Unable to negotiate with 192.168.1.40
port 1034: no matching key exchange method found. Their offer:
diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 [preauth]


You are connecting from very old OpenSSH client (3.5), which does not 
support any of the currently secure cryptography algorithms. You should 
really consider updating that BasicLinux.


Otherwise you can enable the legacy kex and ciphers in the Fedora 
OpenSSH server by following these instructions:


http://www.openssh.com/legacy.html

Regards,

--
Jakub Jelen
Software Engineer
Security Technologies
Red Hat
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

SSH problem from BasicLinux floppy booted 486 to Fedora 25

[Philip Rhoades]

People,

I get an error trying to ssh from a BasicLinux floppy booted 486 (I want 
to sort out HD problems on the old Adaptec 1542 controlled SCSI drive 
that has RH5.2 on it!) when trying to connect to my Fedora 25 x86_64 
workstation.  On the F25 machine in /var/log/secure I get lines like:


Mar 13 16:25:47 phil sshd[7562]: Unable to negotiate with 192.168.1.40 
port 1034: no matching key exchange method found. Their offer: 
diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 [preauth]


On the BasLin terminal I get:

OpenSSH_3.5p1, SSH protocols 1.5/2.0, OpenSSL 0x0090607f
debug1: Rhosts Authentication disabled, originating port will not be 
trusted.

debug1: ssh_connect: needpriv 0
debug1: Connecting to 192.168.1.20 [192.168.1.20] port 22.
debug1: Connection established.
debug1: identity file /root/.ssh/identity type -1
debug1: identity file /root/.ssh/id_rsa type -1
debug1: identity file /root/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.3
debug1: match: OpenSSH_7.3 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.5p1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit: 
diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1

debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit: 
aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-...@lysator.liu.se
debug2: kex_parse_kexinit: 
aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-...@lysator.liu.se
debug2: kex_parse_kexinit: 
hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: 
hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1-96,hmac-md5-96

debug2: kex_parse_kexinit: none,zlib
debug2: kex_parse_kexinit: none,zlib
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: kex_parse_kexinit: 
curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha51

2,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1
debug2: kex_parse_kexinit: 
ssh-rsa,rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ssh-ed25519
debug2: kex_parse_kexinit: 
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com
debug2: kex_parse_kexinit: 
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com
debug2: kex_parse_kexinit: 
umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac-64@openssh.

com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: kex_parse_kexinit: 
umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1

debug2: kex_parse_kexinit: none,z...@openssh.com
debug2: kex_parse_kexinit: none,z...@openssh.com
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
no matching cipher found: client 
aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-...@lysator.liu.se 
server 
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com

debug1: Calling cleanup 0x805deb0(0x0)


Any suggestions about how to fix this SSH problem?

Thanks,

Phil.
--
Philip Rhoades

PO Box 896
Cowra  NSW  2794
Australia
E-mail:  p...@pricom.com.au
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org