Intel Xeon PHI?

[moebius]

Originally Posted by LaurV

is anybody here still using wep? (or wpa1 btw)
(anybody can hack it in few minutes with aircrack-ng - it takes me 3-5 minutes to hack any wep)

And before that, you bypass the MAC address filter via MAC address spoofing, isn't it true? Because of specialists (secret agents) like you, I prefer to use LAN on my Linux router. I also use only WPA2 with a 63-character password with special characters and numbers for the WLAN and the administrator account .Still a question of time before 007 can log in.

[paulunderwood]

Originally Posted by ewmayer

'nmcli device wifi' comes up empty - that seems to reflect the lack of a wifi entry in the 'ifconfig' output. When I unplug and re-plug the wifi stick, I see the USB connection resetting in the terminal output and finding the device, but the afore-tried command still comes up empty.

Hmm. The installation did not work through this "front" usb socket. Maybe the socket is at fault. Can you try the wifi stick in another socket? Maybe the one in which you did the installation. .

[Mark Rose]

Originally Posted by LaurV

is anybody here still using wep? (or wpa1 btw)
(anybody can hack it in few minutes with aircrack-ng - it takes me 3-5 minutes to hack any wep)

I said, certified geek
Seven days a week
WEP protocol
Make that wifi game weak, woo

[Mark Rose]

Originally Posted by moebius

And before that, you bypass the MAC address filter via MAC address spoofing, isn't it true? Because of specialists (secret agents) like you, I prefer to use LAN on my Linux router. I also use only WPA2 with a 63-character password with special characters and numbers for the WLAN and the administrator account .Still a question of time before 007 can log in.

Turn off WPS, too. WiFi Pathetic Security is susceptible to brute forcing.

[ewmayer]

Originally Posted by paulunderwood

Hmm. The installation did not work through this "front" usb socket. Maybe the socket is at fault. Can you try the wifi stick in another socket? Maybe the one in which you did the installation. .

I've tried the wifi stick in both the usb3 and usb2 sockets, no joy either way.

But note the stackexchange page you referred me to, Connect to Wi-Fi with minimal installation of Centos, is in fact marked as a duplicate, with a link to this page, which says that the solution is to install NetworkManager-wifi, as 'rpm -q NetworkManager-wifi' comes up empty for me.

To install that package of course again needs at least an ethernet connection - rather than run a long cable into the next room to my router, I managed to activate network sharing on my Macbook, running just a short ethernet cable between that and the KNL box. Used nmtui to check "automatically connect" for the Ethernet, now 'ping yahoo.com' finally works.

But 'yum install NetworkManager-wifi' again fails with the same DNS error I got earlier, when I first tried installing the Gnome desktop, before realizing the wifi was borked:

CentOs-8 AppStream
Errors during downloading metadata for repsitory 'AppStream'
- Curl error (6): Couldn't resolve hostname for http://mirrorlist.centos.org/,,, etc.

[kriesel]

Originally Posted by ewmayer

I've tried the wifi stick in both the usb3 and usb2 sockets, no joy either way.
...
CentOs-8 AppStream
Errors during downloading metadata for repsitory 'AppStream'
- Curl error (6): Couldn't resolve hostname for http://mirrorlist.centos.org/,,, etc.

Sheesh, run the long cable, or temporarily relocate the box. There are better uses for your time than battling wifi install on a case with 2 or 3 RJ45s, such as proving out F33 P-1 code or producing Mlucas V20. Or someday resuming Mfactor checkpointing updates for multithreading.

(Aren't you one of the people that were trying to convince me things were so much simpler and easier on Linux? And now it's taking a committee to slowly over weeks get your one xeon phi box operational?)

[ewmayer]

Originally Posted by kriesel

Sheesh, run the long cable, or temporarily relocate the box. There are better uses for your time than battling wifi install on a case with 2 or 3 RJ45s, such as proving out F33 P-1 code or producing Mlucas V20. Or someday resuming Mfactor checkpointing updates for multithreading.

(Aren't you one of the people that were trying to convince me things were so much simpler and easier on Linux? And now it's taking a committee to slowly over weeks get your one xeon phi box operational?)

Long-cable is likely what I'm gonna need to do ... but router is hidden behind a large sofa, with end tables at sides and rug+coffeetable in front, so getting physical access to it will require moving some furniture.

Re. other-work, the hour-per-day-max I've budgeted for this is not eating into my worktime, been sacrificing other internet activities, mainly lightening up my daily newsreading. And what do you think I intend to use the KNL *for*? Lots of cores, not a lot of memory, just the 16GB fast onboard RAM ... how much RAM would a really deep p-1 stage 1 run of F33 need? Mersenne-mod p-1 for v20 of course has first priority, but the front and back ends are more or less the same, just for M(p) one supplements the stage 1 prime-powers product with 2*p, whereas for F(m) one uses 2^(m+2).

Re. your spoiier: been very happy with my Ubuntu installs on other systems. CentOS, alas, seems to have been packaged by sysadmins, for sysadmins - not packaging the GUI and all-the-packages-needed-to-use-wifi with the basic install image, as e.g. Ubuntu does, is unforgivable in user-friendliness terms. But being annoyed at the folks who put together the distro is not helpful from a practical standpoint.

[paulunderwood]

You can ping yahoo.com, but not resolve centos.org -- weird.

May you should download the full 8GB Centos install image and try that.

[PhilF]

If it is anything like Debian/Ubuntu, check the /etc/resolv.conf file. Put your router's IP address there.

For example:

nameserver 192.168.1.1

[ewmayer]

Originally Posted by PhilF

If it is anything like Debian/Ubuntu, check the /etc/resolv.conf file. Put your router's IP address there.

For example:

nameserver 192.168.1.1

It's there, 'nameserver 192.168.2.1' ... per my Mac wifi details, my router is 192.168.0.1, but using the shared connection, from the KNL I was unable to successfully ping ...0.1 and ...1.1, but ping ...2.1 worked.

Gonna move some furniture later tonight - space behind sofa needed vacumming anyway - first try long ethernet cable directly between router and KNL, if still unable to get out that way, will burn the full 8GB CentOs .iso tomorrow and give that a whirl. Gotta run ... Mlucas v20 stage 1 has "first light" in terms of reproducing a known test factor, but the restart-from-savefile control logic needs some fresh air and comeback-to-with-fresh-eyes.

[ewmayer]

Update:
- sofa moved, ethernet cable hooked into router
- on plugging other end ito KNL and activating the connection, /etc/resolv.conf now shows the same nameservers I see on my Mac's airport setup info, 75^4 and 76^4
- able to ping yahoo.com, but that's meaningless - more importantly ping centos.org works
- NetworkManager-wifi installed, did 'systemctl restart NetworkManager', now nmtui->'Activate a connection' shows a bunch of netwworks under 'Wi-Fi' ... not including mine, NETGEAR63.

Worst case I csn use the ethernet cable again tomorrow to DL the Gnome stuff, but that wifi needs to work at some point, jeebus this is annoying. Dinnertime, back tomorrow.
Wait - OMFG, just tried posting the above using my Mac, it no longer sees NETGEAR63 anymore, either. Only ~half the usual # of router status LEDs lit. Unplug ethernet, no joy. Unplug/replug router (reset button is microscopic and recessed), wait 5 mins, LEDs green but again only half the usual. Using the downstairs Whole Foods' wifi to post this. Better stop for tonight or I'm gonna risk getting into breaking-stuff-out-of-frustration mode. Replugging the ethernet cable better at least give me something usable.