=== tds9 is now known as tds | ||
sarnold | pymagic: what are you seeing? | 03:06 |
---|---|---|
pymagic | sarnold, boot repair gives me this: http://paste.ubuntu.com/p/d6qyFx9mY2/ -- I am trying to boot from nvme0n1p2 | 03:07 |
pymagic | Booting just boots me into bios | 03:07 |
sarnold | bummer :( this probably would have been a few seconds to fix before the reboot but at this point will require booting to rescue media to fix | 03:09 |
amurray | pymagic: I think you need to set the boot order to specify Ubuntu | 03:10 |
pymagic | sarnold, I've rescue media | 03:10 |
pymagic | I booted into kubunt and can mount the drive | 03:10 |
pymagic | I tried boot-repair - no use | 03:10 |
sarnold | pymagic: start with these "physical machine" instructions to get into a rescue environment, chrooted to your install: https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/GRUB2SecureBootBypass#Physical_machine | 03:10 |
pymagic | I can try those commands | 03:11 |
sarnold | pymagic: yeah, I don't think anyone's taught boot-repair how to fix incorrectly configured debconf settings -- once you're in the rescue environment, chroot'ed to your installation, sudo dpkg-reconfigure grub-efi-amd64 | 03:12 |
pymagic | k - trying | 03:12 |
pymagic | booting into kubuntu - will take some time, thanks | 03:12 |
pymagic | sarnold, what will be ROOT_PARTITION value? | 03:13 |
sarnold | pymagic: it'll be the largest partition on your nvme drive; that might be nvme0n1p2 but check gdisk -l /dev/nvme0n1 to double-check | 03:14 |
pymagic | yes, it is that | 03:14 |
pymagic | sarnold, grub-efi-amd64 is not installed | 03:21 |
pymagic | I could do those steps in prepare the chroot | 03:22 |
sarnold | pymagic: are you sure you're inside the chroot? line 12 of your paste: | 03:23 |
sarnold | The default repair of the Boot-Repair utility will reinstall the grub-efi-amd64-signed of | 03:23 |
sarnold | .. so I certainly expected it to be installed :) | 03:23 |
pymagic | The paste I did came out of boot-repair utility - maybe they installed it? uninstalled it? | 03:23 |
pymagic | not sure | 03:23 |
pymagic | All the steps in chroot - went through cleanly for me | 03:23 |
pymagic | last command was mount /boot/efi | 03:24 |
sarnold | try an apt install grub-efi-amd64 perhaps? see what that does? | 03:24 |
pymagic | sarnold, if i do dpkg --list | grep nvidia - I do see driver-440 - which is what was installed on my machine | 03:25 |
pymagic | I also see other packages that I installed that are not on kubuntu | 03:25 |
sarnold | pymagic: aha, good idea | 03:25 |
pymagic | I do have grub-gfxpayload-liss and grub-pc installed | 03:26 |
pymagic | they are going to be removed if i install grub-efi-amd64 - ok | 03:26 |
sarnold | grub-pc? that's for BIOS machines, not EFI machines | 03:26 |
pymagic | I've not clue how it was working so far | 03:26 |
sarnold | me neither | 03:26 |
pymagic | I had selected UEFI in the bios and could boot | 03:27 |
pymagic | it says EFI Variables are not supported on this system.../sys/firmware/efi/efivars not found, aborting | 03:27 |
pymagic | grub-probe : error: cannot find a GRUB drive for /dev/sdc1 - check your device.map | 03:27 |
pymagic | not sure why sdc1 is even a candidate for grub | 03:28 |
sarnold | curious and curiouser.. try getting another terminal, and check the /sys/firmware/efi/efivars directory from outside the chroot | 03:28 |
pymagic | nothing else | 03:29 |
sarnold | man this is confusing | 03:29 |
sarnold | efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime) | 03:29 |
sarnold | that's what I've got on mine.. | 03:29 |
pymagic | I dont | 03:30 |
pymagic | I have /sys/firmware/ -> acpi dmi and memmap | 03:30 |
pymagic | This is a new Ryzen 3900X X570 machine. AORUS bios | 03:30 |
sarnold | maybe try a mount -tefivars efivars /sys/firmware/efi/efivars/ ... I don't know if the --bind means it's got to be done from outside the chroot, or if it can go from inside the chroot .. | 03:30 |
sarnold | and if that works, then apt install -f ? | 03:31 |
pymagic | could it be that i booted using "Legacy" instead of UEFI into kubuntu | 03:31 |
pymagic | could that do it? | 03:31 |
sarnold | yeah, that'll cause chaos :) | 03:31 |
pymagic | reboot and try again? | 03:32 |
sarnold | if you *want* to keep the legacy thing, then reinstall that grub-pc! if you want to switch to uefi, then, yeah, reboot, flip the switch.. | 03:32 |
pymagic | Let me uefi - rebootin | 03:32 |
pymagic | bios is uefi :( csm support = on, storage boot = uefi , other pci device = uefi | 03:33 |
pymagic | In kubuntu, there is an option in grub which says "UEFI firmware settings" - when i clicked it, it took me to bios...where uefi settings were | 03:35 |
sarnold | pymagic: aha, turn off csm and try again :) | 03:38 |
sarnold | csm == legacy | 03:38 |
pymagic | I thought csm = uefi option? | 03:38 |
sarnold | csm is some cursed thing :) | 03:38 |
pymagic | k - disabling it and trying again | 03:38 |
pymagic | sarnold, Intramfs -unpacking failed - decoding...its trying to boot now | 03:46 |
pymagic | sarnold, but /sys/firmware now has efi :) | 03:46 |
pymagic | sarnold, now it says grub-efi-amd64-signed is already newest version | 03:47 |
pymagic | update-grub? | 03:48 |
pymagic | or perhaps update-grub2? not sure | 03:49 |
pymagic | I reinstalled that package using --reinstall | 03:51 |
pymagic | will try to reboot and see if that wrks | 03:51 |
sarnold | pymagic: so, next up is dpkg-reconfigure grub-efi-amd64 and make sure it thinks to install it in the correct place | 03:53 |
pymagic | ah - k - i'll have to get back into chroot again. I rebooted after i --reinstalled it | 03:54 |
pymagic | its now in a black screen - nothing on there | 03:55 |
pymagic | rebooting into kubuntu | 03:56 |
pymagic | sarnold, the reconfigure is askin me for Linux Command Line | 04:01 |
sarnold | pymagic: whatever it's got is probably fine | 04:02 |
pymagic | I think it had a legacy line or it was empty - it did not show me anything | 04:02 |
sarnold | you pastebin shows empty | 04:02 |
pymagic | leave it empty? | 04:02 |
sarnold | yeah | 04:03 |
pymagic | linux default command line: quiet splash -ok | 04:03 |
pymagic | update nvram variables to automatically boot into debian? ! | 04:04 |
pymagic | yes or no | 04:04 |
pymagic | sarnold, ? | 04:05 |
sarnold | pymagic: default sounds good, and yes, if you want to keep booting into ubuntu by default | 04:06 |
pymagic | sarnold, its now asking grub efi partition | 04:06 |
pymagic | and the only option it gives me is /dev/nvme0n1p1 - and not p2? | 04:06 |
pymagic | 536 Mb /boot/efi | 04:07 |
pymagic | say ok and select that - since i dont have a choice? | 04:07 |
sarnold | pymagic: yeah | 04:07 |
sarnold | pymagic: this is the EFI boot partiion, a smallish fat32 filesystem shared by all operating systems and uefi firmware on the system | 04:08 |
pymagic | now - reboot? | 04:08 |
sarnold | pymagic: if you're all done, yeah, give it a shot and lets see how it goes :) | 04:09 |
pymagic | sarnold, back to the bios screen | 04:12 |
pymagic | sarnold, :( | 04:12 |
sarnold | pymagic: oh no :( I had really hoped that dpkg-reconfigure was going to solve it all | 04:13 |
pymagic | sarnold, in my bios it only shows ubuntu 4.0 - 2TB - so it does not show the 512MB partition to boot from | 04:13 |
pymagic | isnt that an issue? | 04:13 |
sarnold | pymagic: that's probably fine | 04:13 |
pymagic | is there a way to chroot and see dmesg perhaps? - I am not even sure if the bios even tried to boot grub - it just hops back into the bios | 04:15 |
sarnold | pymagic: probably not.. try the rescue media again, and try efibootmgr -v -- here's my output https://paste.ubuntu.com/p/7bCc8qqWHr/ | 04:15 |
sarnold | pymagic: note that I've got windows listed here even though wiping windows was the first thing I did. the bootorder line describes which entries to try in which order.. and it takes the first 'working' one.. | 04:16 |
pymagic | sarnold, Trying | 04:17 |
pymagic | sarnold, with or without chroot? | 04:19 |
sarnold | pymagic: shouldn't matter, this one reads from the firmware settings | 04:20 |
pymagic | thanks - trying to boot into kubuntu | 04:20 |
pymagic | sarnold, http://paste.ubuntu.com/p/2KxWpWY6Ft/ | 04:24 |
pymagic | sarnold, not sure how i got ubuntu/grub to work with legacy mode so far - but it did work. The only thing that broke the system was - in some grub setting i changed GRUB_TIMEOUT=2 from 0, and ran update-grub - and that broke the system. Not sure if that helps | 04:27 |
sarnold | pymagic: well, I'm pretty well confused :( the order suggests using 1, 0, 2 | 04:29 |
sarnold | pymagic: 1 is labeled "flash drive" but has both "cdrom" and "usb" in the string | 04:30 |
sarnold | pymagic: 0 looks like the thing you want to boot.. | 04:30 |
pymagic | when i try 0 it goes back to bios after trying to boot - no grub screen | 04:30 |
sarnold | pymagic: try: efibootmgr -o 0,1,2 ? | 04:31 |
pymagic | k it set that | 04:31 |
pymagic | 0 = ubuntu | 04:31 |
pymagic | the problem is "ubuntu" = 0 - when i set it up from bios - tries to boot - then comes back to bios | 04:31 |
pymagic | I can reboot and try agian | 04:32 |
pymagic | efibootmgr -o 0,1,2 worked fine | 04:32 |
sarnold | pymagic: alright, I'm running very out of ideas, and it's time to run :( | 04:32 |
pymagic | I fired a reboot | 04:32 |
pymagic | Thanks for the help sarnold | 04:32 |
sarnold | pymagic: my last thought -- try getting back in to the rescue chroot, and from there, apt install --reinstall grub-efi-amd64 grub-efi-amd64-bin grub-efi-amd64-signed grub-common | 04:33 |
pymagic | k - will give it a try- thanks | 04:33 |
sarnold | https://paste.ubuntu.com/p/DhYyvj2gQ6/ | 04:34 |
sarnold | turns out I've also got a grub2-common package installed. no idea why there's several. | 04:34 |
pymagic | sarnold, 0 = ubuntu - did not boot - same problem | 04:34 |
sarnold | :( | 04:34 |
pymagic | ubuntu 20.04lts? | 04:34 |
sarnold | pymagic: good luck, I hope you can sort this thing out :) I'm cautiously optimistic with the --reinstall approach.. I hope it's not too much trouble ;) | 04:36 |
pymagic | thanks | 04:38 |
pymagic | sarnold, got it :) | 04:46 |
pymagic | Thanks for all the help. | 04:46 |
=== Wryhder is now known as Lucas_Gray | ||
=== pedro__ is now known as DodgeThis | ||
kre10 | hey guys, how are you? Can you please help me with something. By my mistake, I added 2 eth0 address on my ubuntu 64 server(raspberry pi 4). And now I have 2 eth0 addresses which is very confusing. | 13:54 |
sdeziel | kre10: how did you add them? | 13:59 |
kre1073 | sdeziel hey there | 13:59 |
kre1073 | sudo dhclient -r | 14:00 |
kre1073 | and sudo dhclient | 14:00 |
=== kre1073 is now known as kre10 | ||
sdeziel | kre10: a simple trick would probably be to reboot, if you can | 14:03 |
kre10 | yep, I rebooted a few times | 14:04 |
sdeziel | kre10: after rebooting, if you don't run those manual dhclient commands, do you still have the extraneous IPs? | 14:04 |
kre10 | yes | 14:04 |
=== kedar is now known as kedar_apte | ||
sdeziel | could you pastebin the output of 'ip a' | 14:05 |
kedar_apte | kre10: xenial or bionic or focal? | 14:05 |
kre10 | focal | 14:05 |
kedar_apte | can you see anything in the netplan? | 14:05 |
kedar_apte | in the folder /etc/netplan/ | 14:06 |
kedar_apte | there will be a yaml file | 14:06 |
kre10 | just a second | 14:06 |
kedar_apte | are u able to see two interfaces in the file? | 14:06 |
kre10 | eth0: | 14:06 |
kedar_apte | only one interface? | 14:06 |
kre10 | no, actually | 14:06 |
kre10 | yes | 14:07 |
kedar_apte | can you paste bin what u see? | 14:07 |
kre10 | Uploaded file: https://uploads.kiwiirc.com/files/e001cd861f42b0206e066e3601058174/pasted.txt | 14:07 |
kedar_apte | what is shown when u type .......... ip r | 14:07 |
kedar_apte | can u screen shot that and imgur it | 14:08 |
kre10 | OK | 14:08 |
kre10 | https://www.screenpresso.com/=qv43f | 14:09 |
kedar_apte | are you running bridged networks? | 14:10 |
kedar_apte | like for containers? | 14:10 |
kedar_apte | lxc / lxd / docker? | 14:10 |
kre10 | yes, I'm using docker | 14:11 |
kedar_apte | are u on the physicall server or ssh into the server? | 14:11 |
kedar_apte | can u exit and ssh again.... on the top you will see the disk usage and network details | 14:12 |
kedar_apte | can u screenshot that | 14:12 |
kre10 | ssh | 14:12 |
kre10 | ok | 14:12 |
kre10 | https://www.screenpresso.com/=NI5Zf | 14:13 |
kedar_apte | how many yaml files are you seeing in /etc/netplan/ ? | 14:15 |
kre10 | 1 | 14:16 |
kre10 | -rw-r--r-- 1 root root 416 Apr 1 20:23 50-cloud-init.yaml | 14:16 |
kedar_apte | have you tried doing this? ....... ip addr flush eth0 | 14:17 |
kedar_apte | also try doing this: ip link set dev eth0 down | 14:18 |
kedar_apte | u might loose connection with the server | 14:19 |
kedar_apte | do only if you have the ability to reboot or be on the server console | 14:19 |
kre10 | so after this command, I won't be able to login in the Pi? | 14:20 |
kedar_apte | not sure... wait a second.....just finding something usefl | 14:20 |
kre10 | ok | 14:21 |
kedar_apte | try this.... sudo ip addr del <ip address you want to remove> /24 dev eth0 | 14:22 |
kre10 | sudo ip addr del 192.168.0.109 /24 dev eth0 | 14:22 |
kre10 | ? | 14:22 |
kedar_apte | do not delete the ip adress with which you have ssh'd in the server | 14:22 |
kre10 | OK | 14:22 |
kre10 | now ? | 14:23 |
kedar_apte | have u run the command? | 14:23 |
kedar_apte | what was the output? | 14:23 |
kre10 | no output, still 2 IP's | 14:24 |
kre10 | should I reboot the system? | 14:24 |
kedar_apte | I doubt that will help... but no harm trying | 14:24 |
kre10 | I doubt too :( | 14:25 |
kedar_apte | no harm in trying | 14:26 |
kre10 | ok | 14:26 |
kedar_apte | if it has restaryed.... can u run this and tell me what it is ....... ps aux | grep dhc | 14:29 |
kre10 | zzlatev@playstation:~$ ps aux | grep dhc | 14:32 |
kre10 | root 243 0.0 0.0 0 0 ? I< 17:26 0:00 [sdhci] | 14:32 |
kre10 | root 1271 0.0 0.0 3172 2376 ? Ss 17:26 0:00 /usr/sbin/dhcpcd | 14:32 |
kre10 | zzlatev 3898 0.0 0.0 7684 660 pts/0 S+ 17:31 0:00 grep --color=auto dhc | 14:32 |
kre10 | sorry about that | 14:32 |
kre10 | kedar_apte still 2 IP's :( | 14:32 |
kedar_apte | systemctl disable dhcpcd.service | 14:33 |
kedar_apte | systemctl stop dhcpcd.service | 14:33 |
kedar_apte | and reboot | 14:33 |
kre10 | I think that 2 users are using eth0? because I ran this command with the new user - zzlatev which I created | 14:33 |
kre10 | OK | 14:33 |
kedar_apte | wait | 14:33 |
kedar_apte | wait | 14:33 |
kre10 | OK | 14:33 |
kedar_apte | both of the ip addresses are dhcp? | 14:33 |
kre10 | I think so, yes | 14:34 |
kre10 | both are from the router | 14:34 |
kedar_apte | ae both the ips reachable? | 14:34 |
kre10 | but I have to say that I have pihole which IP is the second one 192.168.0.109 | 14:34 |
kre10 | 192.168.0.111 is registred as reserved dhcp client in the router | 14:35 |
kedar_apte | also is the mac ip same for both or it is shwoing different? you can check that mac ip in the router dhcp list | 14:35 |
kre10 | ok | 14:35 |
kre10 | there's isn't a client with 192.168.0.109 | 14:36 |
kedar_apte | have you made any chage to /etc/network/interfaces? | 14:36 |
kre10 | nope | 14:38 |
kedar_apte | are all your containers using the same NIC? | 14:38 |
kre10 | sorry, NIC? | 14:38 |
kedar_apte | what is the default gateway for all containers? | 14:38 |
kedar_apte | NIC - network card | 14:38 |
kre10 | in /etc/network I have 4 folders - if-down.d , if-post-down.d , if pre-up.d, if-up.d | 14:39 |
kedar_apte | is there just one nic card? | 14:39 |
kre10 | I have one network card | 14:39 |
kedar_apte | what is the default gateway for all all containers? | 14:39 |
kedar_apte | what ip is being used as default gateway for all containers?> | 14:39 |
kedar_apte | 109 or 111 | 14:39 |
kre10 | 111 | 14:40 |
kedar_apte | and which IP is reserved on the router? | 14:41 |
kre10 | but I have access to the docker portainer with both IP's | 14:41 |
kre10 | 111 is reserved on the router | 14:41 |
kedar_apte | Honestly...I dont know... I have used up all my KB 🤔️ | 14:42 |
kre10 | here's all networks in docker | 14:42 |
kre10 | https://www.screenpresso.com/=reNlc | 14:42 |
kedar_apte | someone else could help | 14:42 |
kre10 | OK, thank you for trying! I appreciate it! | 14:42 |
kedar_apte | sure | 14:42 |
kre10 | hm, ifconfig -a shows only one eth0 | 14:47 |
RoyK | kre10: just learn to use the ip command and forget about ifconfig | 14:50 |
kre10 | Can you help me with it? | 14:51 |
kre10 | ip -s -s a f to 192.168.0.109/24 | 14:51 |
kre10 | should I try this? | 14:51 |
=== tds8 is now known as tds | ||
Slashman | hello, is there a way to skip the media integrity check for ubuntu server? | 16:56 |
Slashman | (20.04.1) | 16:56 |
lotuspsychje | Slashman: press the key combo it suggests | 16:57 |
lotuspsychje | ctrl + C it was? | 16:57 |
Slashman | didn't see that on ubuntu server media | 16:57 |
lotuspsychje | didnt test myself on server, but i assume the integrity checks are on all ubuntu 20.04 iso's | 16:58 |
Slashman | lotuspsychje: https://ibb.co/5rX9mkD | 17:07 |
Slashman | nothing I can do | 17:07 |
Slashman | super fun when installing from idrac where any read is from the network and ultra slow on a media that was already verified | 17:07 |
lotuspsychje | Slashman: you need to early press the combo | 17:07 |
lotuspsychje | Slashman: there used to be a bug on that, but it should be resolved by now | 17:08 |
Slashman | lotuspsychje: I should do a video, but there is no time | 17:09 |
Slashman | no message, nothing | 17:09 |
Slashman | I select expert mode, then it immediately goes to check integrity | 17:10 |
lotuspsychje | Ubuntu now defaults to checking the integrity of the medium in use when booting into live sessions. This can be skipped by hitting Ctrl-C, but due to a bug the message that tells you to hit this key is not shown in some flavours | 17:13 |
lotuspsychje | https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1870018 | 17:13 |
ubottu | Launchpad bug 1870018 in xubuntu-artwork (Ubuntu Focal) "Option (Ctrl-C) not shown to disable ISO verification" [Undecided,New] | 17:13 |
lotuspsychje | Slashman: wich iso did you use please? | 17:14 |
Slashman | lotuspsychje: http://www.releases.ubuntu.com/20.04/ubuntu-20.04.1-live-server-amd64.iso | 17:18 |
lotuspsychje | ok tnx Slashman lemme poke some ppl | 17:18 |
Slashman | lotuspsychje: thanks | 17:19 |
lotuspsychje | Slashman: did you wait long enough till the test is skipped, it might take some time on older machines/media | 17:23 |
=== StathisA- is now known as StathisA | ||
fretegi | howdy guys | 21:19 |
fretegi | quick question, have a running ubuntu server, bought a replacement.. both intel chipsets, dif gen tho. will the new board in theory boot the old drive? | 21:20 |
fretegi | to the point of being able to SSH in, from there i can obviously do what i need to do | 21:20 |
fretegi | server is running 16.04 if that helps | 21:21 |
RoyK | fretegi: should work unless the chipset is too new for the kernel to support it | 21:23 |
RoyK | fretegi: usually that'll be ethernet or wifi drivers | 21:23 |
RoyK | fretegi: you might want to try a usb live boot with the same distro version on the new motherboard first, just in case | 21:24 |
fretegi | royk, i was hoping for that! should be good i would think, current server is skylake, new one is haswell, intel nics in both cases | 21:24 |
RoyK | fretegi: or - well - just replace it and if the nics don't get online, make sure you have a console handy | 21:25 |
fretegi | well catch is.... i dont have a vga input monitor ha | 21:25 |
RoyK | heh | 21:25 |
fretegi | exactly lol | 21:25 |
fretegi | so hoping this thing boots my current install as i can ssh in and do what i need | 21:25 |
fretegi | just need a running environment | 21:25 |
RoyK | what sort of boot disk or disks do you have on the old system? | 21:26 |
fretegi | so i have 1 drive that the complete OS and then a raid array of data drives | 21:26 |
fretegi | data already backed up etc. so gonna build a new array on the new machine | 21:26 |
RoyK | ok, so perhaps put the new mobo on some non-conducting surface (a table cloth?) and connect the bootdisk and let it start up and check for results | 21:27 |
RoyK | should be a quick test | 21:27 |
fretegi | thats a thought, just never tried to boot one OS drive in another machine before | 21:28 |
RoyK | it usually works fine | 21:29 |
fretegi | Ubuntu installs pretty much all kernel modules right? loading whats needed at boot? | 21:29 |
RoyK | it's not like old windoze shite where everything is hardwired to whatever chipset you have | 21:29 |
shibboleth | it has separate module packages, -modules and -modules-extra | 21:29 |
fretegi | so unless u have hardware so new that proper support doesnt exist on your installed kernel, should be good | 21:30 |
RoyK | fretegi: the kernel will autoload whatever it finds needed according to the pci IDs. Those change sometimes with newer hardware, so it usually works, but not always | 21:30 |
shibboleth | the latter typically don't get installed if you choose a virt/minimal baseline | 21:30 |
fretegi | RoyK, fortunately for me, actually in a sense downgrading haha. going to older, but yet more capable gear | 21:30 |
RoyK | then it will probably work just fine :) | 21:31 |
fretegi | shibboleth, honestly dont recall, pretty sure i did a standard ubuntu server install | 21:31 |
shibboleth | dpkg -l | grep linux-modules | 21:32 |
fretegi | may even be the same nic chips, checking now and for modules | 21:32 |
fretegi | shibboleth, yup exactly, remoting in now | 21:32 |
RoyK | fretegi: really, if going to an older intel board, I don't see a problem here | 21:33 |
fretegi | shibboleth, yea got both linux-modules && linux-modules-extra should be solid! | 21:33 |
fretegi | RoyK, yea me neither. Perfect well thanks for confirming im not totally nuts guys | 21:33 |
fretegi | well at least with this anyhow | 21:33 |
shibboleth | also: later kernels (hwe) might enable support for more hw | 21:34 |
fretegi | shibboleth, yea good point | 21:38 |
fretegi | thanks guys, wish me luck, gonna fiddle with it this weekend if not sooner | 21:45 |
RoyK | shibboleth: if it's older hardware, I doubt that'll be a problem | 21:59 |
kre10 | hey guys, how are you? Can you please help me with something. By my mistake, I added 2 eth0 address on my ubuntu 64 server(raspberry pi 4). And now I have 2 eth0 addresses which is very confusing. | 22:17 |
=== kre1028 is now known as kre10 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!