qman | foo: ufw is one of the go-to solutions specifically for ubuntu, personally I just write my own iptables rules, I find the layers on top more complicated | 01:29 |
---|---|---|
=== chris14_ is now known as chris14 | ||
=== router is now known as Guest6420 | ||
=== Guest6420 is now known as PEAKTOP | ||
=== leazhi1 is now known as leazhi | ||
ghavil | Is there perhaps someone here that's familiar with how the AWS EC2 AMI's are built and published. It looks like at least in us1-east-1, the "ubuntu-minimal/images/hvm-ssd/ubuntu-jammy-22.04-amd64-minimal-20240723" AMI changed 'ImdsSupport' to 'v2.0'. I'm trying to find where these are actually built now days as I believe that's a drastic change from 'ubuntu-minimal/images/hvm-ssd/ubuntu-jammy-22.04-amd64-minimal-20240701" which did not have this | 17:54 |
ghavil | option configured. | 17:54 |
a7x | hi, I noticed something odd after upgrading to 24.04, both machines have issues contacting dns servers, nslookup google.com Server: 8.8.8.8 …. ;; Got bad packet: unexpected end of input | 20:32 |
a7x | similar issue with dig ;; Warning: Message parser reports malformed message packet. | 20:32 |
sarnold | a7x: are there any messages in dmesg that look related? does ip -h -iec -s l | 20:43 |
sarnold | .. show a high error count? | 20:43 |
sarnold | ghavil: I suggest asking in #ubuntu-cloud | 20:44 |
ghavil | sarnold: Thanks, I have gotten help over there | 20:44 |
sarnold | oh yay :) | 20:45 |
a7x | sarnold, no high error count (interesting amount of "dropped") | 20:51 |
a7x | after a third restart (on both machines) it seems to be working, still need to check dmesg | 20:51 |
sarnold | a7x: heh yeah I've got a high 'dropped' on my system, i'm not entirely sure what those are, but I think it's along the lines of multicast packets that it doesn't care about or something similar | 20:52 |
sarnold | weird | 20:52 |
a7x | ah, one thing, I disabled docker | 20:52 |
a7x | I ended up disabling it since it was spamming dmesg with connection issues | 20:53 |
a7x | (maybe I should say that I tried disabling docker with "sudo systemctl disable docker | 20:55 |
a7x | " but after a reboot it's still up) | 20:55 |
a7x | thanks for now, I will report back when it happens again | 20:57 |
sarnold | I *think* if another service depends upon docker, systemd will still start it despite being disabled | 20:57 |
sarnold | I think that's the problem that caused the 'masking' method to be introduced | 20:57 |
a7x | that might be related to "status" showing that preset is enabled | 21:01 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!