| View previous topic :: View next topic |
| Author |
Message |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 55340
Location: 56N 3W
|
 Posted: Sun May 25, 2025 5:37 pm Post subject: |
 |
|
leyvi,
The manual commands at the root shell work for you too.
You showed that.
I don't understand why netifrc fails because it does it same thing.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
 |
leyvi
Guru
Joined: 08 Sep 2023
Posts: 420
|
| Posted: Thu Jun 05, 2025 8:25 am Post subject: |
|
|
I don't know if this will help, but: | Code: | root /etc (0) $ sysctl --values net.ipv6.conf.br0.accept_ra
1 |
This is despite me setting it correctly to 2. Also, these lines appeared in syslog since I booted today: | Code: | root /var/log (0) $ grep br0 syslog | tail --lines=18
Jun 5 10:12:36 fast-penguin kernel: br0: port 1(eno1) entered blocking state
Jun 5 10:12:36 fast-penguin kernel: br0: port 1(eno1) entered disabled state
Jun 5 10:12:36 fast-penguin kernel: br0: entered promiscuous mode
Jun 5 10:12:37 fast-penguin avahi-daemon[2793]: Joining mDNS multicast group on interface br0.IPv4 with address 10.0.0.54.
Jun 5 10:12:37 fast-penguin avahi-daemon[2793]: New relevant interface br0.IPv4 for mDNS.
Jun 5 10:12:37 fast-penguin avahi-daemon[2793]: Registering new address record for 10.0.0.54 on br0.IPv4.
Jun 5 10:12:37 fast-penguin avahi-daemon[2793]: Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1.
Jun 5 10:12:37 fast-penguin avahi-daemon[2793]: New relevant interface virbr0.IPv4 for mDNS.
Jun 5 10:12:37 fast-penguin avahi-daemon[2793]: Registering new address record for 192.168.122.1 on virbr0.IPv4.
Jun 5 10:12:37 fast-penguin dnsmasq-dhcp[2918]: DHCP, sockets bound exclusively to interface virbr0
Jun 5 10:12:42 fast-penguin kernel: br0: port 1(eno1) entered blocking state
Jun 5 10:12:42 fast-penguin kernel: br0: port 1(eno1) entered listening state
Jun 5 10:12:44 fast-penguin kernel: br0: port 1(eno1) entered learning state
Jun 5 10:12:46 fast-penguin kernel: br0: port 1(eno1) entered forwarding state
Jun 5 10:12:46 fast-penguin kernel: br0: topology change detected, propagating
Jun 5 10:12:48 fast-penguin avahi-daemon[2793]: Joining mDNS multicast group on interface br0.IPv6 with address fe80::417:87ff:fe93:780.
Jun 5 10:12:48 fast-penguin avahi-daemon[2793]: New relevant interface br0.IPv6 for mDNS.
Jun 5 10:12:48 fast-penguin avahi-daemon[2793]: Registering new address record for fe80::417:87ff:fe93:780 on br0.*. |
I haven't touched net.br0 but it seems to be changing state somehow? |
|
| Back to top |
|
|
leyvi
Guru
Joined: 08 Sep 2023
Posts: 420
|
| Posted: Mon Jun 09, 2025 2:07 pm Post subject: |
|
|
I think the fact that net.ipv6.conf.br0.accept_ra is getting reset to 1 is the problem here; I just have no idea why it's happening. I have a project due soon that requires IPv6 to develop, so any help would be appreciated.
Edit: I fixed that, accept_ra is set correctly again.
Last edited by leyvi on Tue Jun 10, 2025 12:13 pm; edited 1 time in total |
|
| Back to top |
|
|
leyvi
Guru
Joined: 08 Sep 2023
Posts: 420
|
| Posted: Tue Jun 10, 2025 12:13 pm Post subject: |
|
|
I noticed something:
All router advertisement packets come from fe80::1 and are sent to ff02::1 (multicast). The route I get is fe80::/64 dev br0 proto kernel metric 256 pref medium. Here is a router advertisement packet from Wireshark: | Code: | Frame 751: 142 bytes on wire (1136 bits), 142 bytes captured (1136 bits) on interface br0, id 0
Ethernet II, Src: TPLink_93:54:b4 (5c:62:8b:93:54:b4), Dst: IPv6mcast_01 (33:33:00:00:00:01)
Internet Protocol Version 6, Src: fe80::1, Dst: ff02::1
Internet Control Message Protocol v6
Type: Router Advertisement (134)
Code: 0
Checksum: 0x4be5 [correct]
[Checksum Status: Good]
Cur hop limit: 64
Flags: 0x48, Other configuration, Prf (Default Router Preference): High
Router lifetime (s): 30
Reachable time (ms): 0
Retrans timer (ms): 0
ICMPv6 Option (Prefix information : 2a06:****:****:****::/64)
Type: Prefix information (3)
Length: 4 (32 bytes)
Prefix Length: 64
Flag: 0xc0, On-link flag(L), Autonomous address-configuration flag(A)
Valid Lifetime: 300 (5 minutes)
Preferred Lifetime: 120 (2 minutes)
Reserved
Prefix: 2a06:****:****:****::
ICMPv6 Option (Recursive DNS Server fe80::1)
Type: Recursive DNS Server (25)
Length: 3 (24 bytes)
Reserved
Lifetime: 10 (10 seconds)
Recursive DNS Servers: fe80::1
ICMPv6 Option (MTU : 1500)
Type: MTU (5)
Length: 1 (8 bytes)
Reserved
MTU: 1500
ICMPv6 Option (Source link-layer address : 5c:62:8b:93:54:b4)
Type: Source link-layer address (1)
Length: 1 (8 bytes)
Link-layer address: TPLink_93:54:b4 (5c:62:8b:93:54:b4) |
So I think my computer's getting a route, but it isn't using it right, because I don't think I can just route everything IPv6 to fe80::. |
|
| Back to top |
|
|
leyvi
Guru
Joined: 08 Sep 2023
Posts: 420
|
| Posted: Wed Jun 11, 2025 11:25 am Post subject: |
|
|
HOLLY COW I FOUND THE ISSUE!
It was my switch; shitty TP-Link Archer C64 spyware-ridden piece of ewaste doesn't support IPv6 in switch mode. I fixed it! |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
