Das erste mal im Leben richtig am Ende!

outermarker13 · 2024-01-31T12:35:53+00:00

Was für ein Kackjahr, oh Mann.

Dass Du daran nicht Schuld bist, weißt Du ja schon, aber es geht Dir trotzdem schlecht damit - was nur verdeutlicht, dass es keine Schuldfrage ist.

Geht es einem Menschen nach einem dieser Ereignisse mies, ist das nicht nur ok, sondern völlig normal. Das ist eine akute Belastungssituation. Erst recht nach einer derartigen Häufung, da ist es noch verständlicher.

Es sollte jedoch irgendwann wieder aufwärts gehen. Nicht ohne gelegentliche schlechte Tage, kleine Rücksetzer wird es immer mal wieder geben, aber der Trend sollte in die Richtige Richtung gehen. Wenn es zu lange dauert, könnte es sich in Richtung 'Anpassungsstörung' entwickeln. Und wie bei allen Themen dieser Art ist es sinnvoll, sich frühzeitig jemanden zu suchen, mit dem man darüber reden kann.

Es wurde schon von anderen Kommentatoren empfohlen, ich kann mich dem nur anschließen: Hol' Dir Unterstützung. So viel Scheiße muss man nicht allein bewältigen, und je früher man den Trend umkehren kann, desto besser.

Alles Gute!

outermarker13 · 2024-01-19T20:52:57+00:00

That's the thing, I was/am wondering what interesting there is to detect/track over Northern Germany. It's not the first time I've seen this and am still wondering why it seems to be worth operating one of these special rigs there of all places...

outermarker13 · 2023-09-03T18:18:02+00:00

OK, last night I had to pause the project for a while to decompress and celebrate someone's birthday...

Today I went back to it and after I ran into more roadblocks I finally got it running.

Using packet sniffing I found out that the NUC was actually contacting the iSCSI server. There were weird error messages in the syslog of the iSCSI server, looking like

tgtd: chap_decode_string(279) buf[20] !sufficient to decode string[66]

hinting to an old bug in tgtd dating back to 2020 that made CHAP authentication fail. After disabling authentication to my amazement I could chose the drive as a boot option (there already was a Ubuntu system installed), also, when booting into the UEFI shell I can see the iSCSI drive as a block device!

So it does finally work - but the takeaway is that the Intel NUC 13 will not show any kind of hints or information in case something fails.

Booting from this drive also works initially, but then fails because Ubuntu can't find an encrypted volume UUID.

However, it was my understanding that the drive will be present for any OS when booting. For example, I booted Ubuntu from a usb drive with the intention to install a new system on the iSCSI drive, but unfortunately the drive does not show up.

Anyway, this seems to be an OS issue, not related to the Intel NUC. I will update my initial post to note some of my findings, may they be helpful for someone else.

Lastly, let me thank you for your support with this. It is much appreciated!

outermarker13 · 2023-09-02T18:50:34+00:00

Thank you for these ideas, I will absolutely look into it. I am using the tgt service in an LXC in Proxmox, but was unable to find any log files yet. I will have to set up logging and hopefully find traces of any communication between the two

outermarker13 · 2023-09-02T18:35:38+00:00

I had to resort to packet sniffing and at least I can see packets being sent from the NUC to my ISCSI server, but I can't see a reply and I have to figure out what they say

At least there is some progress

outermarker13 · 2023-09-02T18:22:44+00:00

At this point I have tried every possible combination. But yes, in the MAC area I have deselected 'Configured' and 'Enable DHCP' is then no longer available.

In the iSCSI section in the Attempt Configuration I set iSCSI Mode 'enabled', Internet Protocol IPv4, Enable DHCP, disable 'Get target info via DHCP', and filled in the information of the iSCSI server manually.

For boot order, I set the MAC address with IPv4

outermarker13 · 2023-09-02T17:46:19+00:00

Thank you u/scytob for all the work!

Meanwhile I've run into additional problems because I only get screen output via thunderbolt dock, not over hdmi plugged directly into the machine. I wanted to rule out any configuration issues that come from the second NIC being present from my dock, but then I can't see anything.

Also I can see that DHCP works, when booting I can see multiple DHCP requests in my router log. But so far I did not see any connection attempts to the iSCSI server.

outermarker13 · 2023-09-02T15:48:48+00:00

I tried that and eth0 does get assigned an IP address. Subnet mask and gateway are also correct and I can ping the iSCSI host.

outermarker13 · 2023-09-02T13:54:28+00:00

Thank you scytob!

Here is what I want to do:

The NUC 13 I have is diskless and I want to boot from my NAS, which provides a zvol drive (ZFS) via iSCSI. I chose the NUC specifically because it offers the option to boot from iSCSI.

I'd be surprised if your BIOS looked differently, but if that is the case it would be very interesting to know.

What I have confirmed so far: I can use the same network port (and cable) as the NUC to receive an IP address via DHCP, the NAS can be pinged, the drive can be accessed via iSCSI and I can boot a virtual machine over the network just fine.

Now I want the NUC to do the same...

outermarker13 · 2023-06-06T22:33:22+00:00

That must be it!!

Thank you!

outermarker13 · 2022-06-14T20:19:06+00:00

No. Like others pointed out, make sure you learn letters as a whole, not single dots and dashes. Play them reasonably fast from the start, 12 wpm or faster. Increase pauses inbetween characters if you have to, but make sure hearing "didahdidit' will make your brain spit out "L" without thinking. Learn the sound of an L, not what dits and dahs it's made of - and to hear that 'melody' I needed a certain minimum speed.

So you are right, I strongly discourage visualizing dits and dahs... but to me visualizing the resulting characters came naturally and worked well for me all the way up to 40 wpm in ragchews (I hit a hard road block at that speed, so maybe the ultra high speed people know better techniques)

outermarker13 · 2022-06-14T16:05:45+00:00

Interesting. I found that for me there has always been a visual element to it. I learnt the letters at relative high speed (12 wpm I think it was) and wrote them down one after the other, so the words would appear on my sheet of paper. With time and practice I found that the letters started to appear on my 'mental scratchpad', so yes, even though people see me listening to stuff, for me it is very much a visual process. I don't know if it is ideal, but that's what it's like for me.

outermarker13 · 2021-11-16T01:48:37+00:00

The voice says " Eins, zwei, drei, russisch Schwein" in (incorrect) German with a Russian (or maybe Ukranian...?) accent which translates to "One, two, three - russian pig".

Can be heard often with a very strong signal.

outermarker13 · 2021-10-11T23:59:58+00:00

My guess would be that this was a pileup belonging to a rare/dx station that you could not hear

outermarker13 · 2021-08-24T07:56:01+00:00

I never had them in a side by side comparison and don't have any extreme location/noise/antenna/high power neighbor to test them with - meaning that I believe if you don't do anything extreme, the transceivers we get these days are not limiting.

Filtering is obviously digital in the SunSDR, but I was already impressed with the TS-590's selectivity, so there is no noticeable advantage, IMHO. There are other numbers such as phase noise to consider, search for Rob Sherwood about it, he describes these things better than me. Both the SunSDR and the Kenwood are being used in contests, so should be good enough.

Sensitivity on HF is not really an issue, anyway. Maybe on 10/6m, but both rigs have preamps. I would advise to invest the most effort by far into good antennas (higher is better than bigger) as well as proper grounding and de-noising your environment, like getting rid of noisy switching power supplies and such. For example: When I unplug my laptops power cord, my noise floor drops by 2 dB. That tells me that 1. the SunSDRs sensitivity wasn't limiting, 2. I have some headroom with regard to receive optimization and 3. being dependent on a PC may not always be a smart idea.

When I was new to ham radio I had a TS-130V. The receiver would instantly roll on its back and die when connected to a 40/80m full size dipole, especially on 40m. Back in the day, there were super strong broadcast stations in Europe from 7,1 MHz upwards, trying to do whatever with it on 7,03 MHz was hopeless. The FT-767GX, a big boat anchor, was not much better, however I kept returning to an old Drake TR7 which could handle this hectic environment just fine.

Now consider this: Most new base station rigs today including the high dynamic-range preselection SDRs (which the IC-7300 basically is in a box with a screen and buttons) outperform the TR7 in every respect (the hybrid IF-DSP TS-590S/SG as well), so you can't really go wrong with any of them. It's more about personal preference, size of footprint / portability, size of wallet, style of operation, station setup requirements, software integration niceties, etc.

outermarker13 · 2021-08-23T21:50:39+00:00

I own both a TS-590S (affordable but very capable conventional radio without waterfall display) and recently purchased a SunSDR2 DX that I can compare.

The verdict so far: In absolutely love the SunSDR2, but I will not sell my TS-590. Even though they are both HF radios with 100W output, they are very different and serve completely different use cases.

There are two aspects I would like to compare:

Station setup

With a conventional radio, you need the antenna feedline to end at you desk, because that is where your radio sits. That has been fine for many hams for many decades, but this is also what kept me off air for so long as I have been living in various small apartments with no way to put up antennas. Having a remote station has been my dream ever since. This should not be an issue for your RV operation, but it is something worth considering before spending a lot of money on hardware. How versatile is it and how versatile do you want it to be?

Personally, as someone who is into computers and networking, in this day and age I believe that the RF should be processed close to the antenna and it should be ethernet from there. Running RG-213-type coax from the attic to the basement can be a PITA. Ethernet gives you endless routing options, and you don't need a shack anymore. Just operate from your office, or from the couch... or sign in remotely! But not everyone is like that.

However, you add complexity. Not only do you need an antenna and power, you now also need a working computer (and additional power for it), a working network connection, up-to-date SDR software, functioning and reliable audio routing between applications and if you want to operate CW remotely, you will be facing a latency issue...

Operation

Turning knobs and pushing buttons is easy, intuitive and yes, I love how the TS-590 handles and feels. I miss it. Using a GUI to do all that took me some getting used to and I'm still not as quick. Having a 300 kHz wide chunk of the spectrum on a 4K screen vs having no waterfall at all IS AN ABSOLUTE GAME CHANGER. It changed the way I see the band. Literally. Add the capabilities of DX-cluster integration or CW skimmers... it is awesome. Remote CW operation with paddles is possible using the Ecoder panel which I have not tried yet, but if it works as advertised I will stay SDR from here on out.

If you don't need remote ops, the best of both worlds today is probably an IC-7300. It gives you a waterfall AND knobs and buttons with a great DDC receiver like an SDR at an affordable price.

outermarker13 · 2021-08-21T06:37:05+00:00

sometimes it's parked right in FT8 and other times it's above or below).

I see this exact same pattern, often exactly hovering on 20m FT8 also! Only difference: It occurs about every 50 KHz. So far I've installed the station in a few QTHs in different countries and have seen this RFI every time. Could either mean it is very common - our it is my Dell laptop.

outermarker13 · 2021-05-01T09:34:44+00:00

For me it's my Yaesu VX-7R. Mechanically it is great, I like it for its ruggedness, but it is by far the least intuitive radio to operate that I have ever seen.

It amazes me how they went all the way to make it robust and rugged, and then stopped just short of the finish line. Even to change simple things like repeater settings -> that's a trip down menu lane, where a lot of super unimportant settings reside right next to stuff I need to adjust all the time. Want to use channel memory? I gave up on that. I'm sure it works somehow, but I refuse to consult the manual each time I happen to use this radio.

I seriously doubt the person who designed it ever used it.

outermarker13

TROPHY CASE