IRC channel logs

<p4r4D0xum>running an update, postinst.d/zz_update_grub takes a lot of time, "stuck on 84%

<p4r4D0xum>is this a "normal" behaviour?

<p4r4D0xum>it's on 1.8-486-smp part

<damo22>p4r4D0xum: are you running smp kernel now?

<damo22>Pellescours: did you figure out more about the rumpnet issues?

<damo22>youpi: how do i intercept or log slirp packets between qemu guest and host?

<damo22>i am printing the packets sent and they seem to be sent, but receiving is a black hole

<damo22>sending packet: [ OK ] 42

<damo22>dtal=42 capl=42 hdrl=18

<damo22>exactly one packet

<damo22>112 bytes from 10.0.2.15: Destination Host Unreachable

<damo22>--- 10.0.2.2 ping statistics ---

<damo22>1 packets transmitted, 0 packets received, 100% packet loss

<youpi>there is a SLIRP_DEBUG environment variable

<youpi>it's processed with g_parse_debug_string

<youpi>there's the "call" value which is probably what you'd need

<damo22>is that a qemu option

<damo22>git/qemu$ git grep SLIRP_DEBUG

<damo22>you maintain libslirp in debian as well?

<damo22>ahh SLIRP_DEBUG=call

<damo22>net_rx_pkt_parsed RX packet parsed: ip4: 0, ip6: 0, l4 protocol: 0, l3 offset: 14, l4 offset: 0, l5 offset: 0

<damo22>does that mean its a malformed packet?

<damo22>i just used qemu> log trace:net_rx_*

<damo22> net_rx_pkt_parsed RX packet parsed: ip4: 1, ip6: 0, l4 protocol: 0, l3 offset: 14, l4 offset: 34, l5 offset: 42

<damo22>when i use the other driver and ping i get

<damo22>so i think the packet i am sending is malformed ip4

<damo22>so it doesnt get a response

<damo22>youpi: so i am getting logs in qemu with log trace:net_rx_* when i ping 10.0.2.2 or .3 but not if i ping other ips on the same subnet

<damo22>i assume that means the packets are being received by the host

<damo22>but are malformed

<damo22>what is destination mac address ff:ff:ff:ff:ff:ff ?

<damo22>is that a broadcast?

<p4r4D0xum>damo22: No, smp doesn't boot at all

<damo22>the kernel boots but it gets stuck at probing disk

<damo22>i sent a packet with a particular header and i got a reply with a different header

<damo22>s/packet/ethernet frame

<damo22>i sent src=0 dest=broadcast and i got back src=525400123456 dest=broadcast

<damo22>containing a simple ping packet

<damo22>but the ping command said 100% packet loss

<damo22>that means bpf is working?

<damo22>somehow the packet i read back had a different src hwaddr

<damo22>but there was no packet with dest=myhwaddr

2025-06-05.log