Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - newsense

#1261
No PPPoE involved, DHCP for WAN IPv4, Lan Prefix ID 0x0 and Vlan Prefix ID 0x10 -- not 100% sure the values are correct(?) but the interfaces get a GUA. Both are tracking the Wan interface.
#1262
So I get the following when pinging from client and OPNsense.


Ping google.com, source address vlan wiith GUA:

# /sbin/ping -6 -S '2001:56a:7db2:3c10:20d:b9ff:fe57:745f'  -c '3' 'google.com'
PING6(56=40+8+8 bytes) 2001:56a:7db2:3c10:20d:b9ff:fe57:745f --> 2607:f8b0:4020:804::200e

--- google.com ping6 statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss



Ping google.com, client with GUA on the same vlan mentioned above, Allow Any Out IPv6 in the vlan rules, no FW active on the client:

C:\>ping -6 google.com

Pinging google.com [2607:f8b0:4020:804::200e] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 2607:f8b0:4020:804::200e:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),



Ping from client with GUA on the Lan interface, I see some icmpv6 activity in the live log but it's coming from the link local address of the client

[root@manjaro-arm]# ping -6 2607:f8b0:4020:804::200e
PING 2607:f8b0:4020:804::200e(2607:f8b0:4020:804::200e) 56 data bytes
^C
--- 2607:f8b0:4020:804::200e ping statistics ---
287 packets transmitted, 0 received, 100% packet loss, time 292866ms




Back to OPNsense, ping google.com, source address "Default":

# /sbin/ping -6 -c '3' 'google.com'
PING6(56=40+8+8 bytes) 2001:56a:7db2:3c00:20d:b9ff:fe57:745f --> 2607:f8b0:4020:804::200e
16 bytes from 2001:56a:7db2:3c00:20d:b9ff:fe57:745f, icmp_seq=0 hlim=64 time=0.581 ms
16 bytes from 2001:56a:7db2:3c00:20d:b9ff:fe57:745f, icmp_seq=1 hlim=64 time=0.474 ms
16 bytes from 2001:56a:7db2:3c00:20d:b9ff:fe57:745f, icmp_seq=2 hlim=64 time=0.418 ms

--- google.com ping6 statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.418/0.491/0.581/0.067 ms



When I'm looking at the IPv6 assignments on OPNsense it  becomes apparent the "Default" source address is actually present on the Lan interface and that's the only time I get ping replies, while selecting the vlan as source does nothing.

#1263
Actually I just manage to capture this from the WAN interface, started the capture and went back to the interface setting the PD size back to /56 to toggle a DHCP6 request, so based on the pfSense guide these are the options on the interface that are set  if available:

Enable IPv6

If you haven't already, pfSense must have IPv6 support turned on. Under System > Advanced > Networking > IPv6 Options, enable Allow IPv6.

Next, configure your WAN interface:

    Interfaces > WAN > General Configuration:
    IPv6 Configuration Type: DHCP6
    Interfaces > WAN > DHCP6 Client Configuration:
    Request only an IPv6 prefix: Enabled
    DHCPv6 Prefix Delegation size: 56
    Send IPv6 prefix hint: Enabled
    Do not wait for a RA: Enabled (request a prefix from the Telus router immediately)
    Do not allow PD release: Enabled


and the PCAP details:

Interface Timestamp SRC DST output
WAN
igb0 2023-01-22
15:08:43.558984 00:0d:b9:57:74:5c 33:33:00:01:00:02 ethertype IPv6 (0x86dd), length 114: (hlim 1, next-header UDP (17) payload length: 60) fe80::20d:b9ff:fe57:745c.546 > ff02::1:2.547: [bad udp cksum 0x2c95 -> 0x1afa!] dhcp6 solicit (xid=193eec (client-ID hwaddr/time type 1 time 570277845 000db957745c) (IA_NA IAID:0 T1:0 T2:0) (elapsed-time 25587) (option-request DNS-server DNS-search-list))
WAN
igb0 2023-01-22
15:08:43.567313 f8:13:08:26:58:97 00:0d:b9:57:74:5c ethertype IPv6 (0x86dd), length 151: (class 0x40, hlim 255, next-header UDP (17) payload length: 97) fe80::fa13:8ff:fe26:5711.547 > fe80::20d:b9ff:fe57:745c.546: [udp sum ok] dhcp6 advertise (xid=193eec (server-ID hwaddr type 1 f81308265711) (client-ID hwaddr/time type 1 time 570277845 000db957745c) (IA_NA IAID:0 T1:0 T2:0 (status-code NoAddrsAvail)))
WAN
igb0 2023-01-22
15:09:04.018056 00:0d:b9:57:74:5c 33:33:00:01:00:02 ethertype IPv6 (0x86dd), length 90: (hlim 1, next-header UDP (17) payload length: 36) fe80::20d:b9ff:fe57:745c.546 > ff02::1:2.547: [bad udp cksum 0x2c7d -> 0x9d35!] dhcp6 solicit (xid=4b20ea (client-ID hwaddr/time type 1 time 570277845 000db957745c) (elapsed-time 0))
WAN
igb0 2023-01-22
15:09:04.020604 f8:13:08:26:58:97 00:0d:b9:57:74:5c ethertype IPv6 (0x86dd), length 104: (class 0x40, hlim 255, next-header UDP (17) payload length: 50) fe80::fa13:8ff:fe26:5711.547 > fe80::20d:b9ff:fe57:745c.546: [udp sum ok] dhcp6 advertise (xid=4b20ea (server-ID hwaddr type 1 f81308265711) (client-ID hwaddr/time type 1 time 570277845 000db957745c) (status-code UnspecFail))
WAN
igb0 2023-01-22
15:09:05.020173 00:0d:b9:57:74:5c 33:33:00:01:00:02 ethertype IPv6 (0x86dd), length 104: (hlim 1, next-header UDP (17) payload length: 50) fe80::20d:b9ff:fe57:745c.546 > ff02::1:2.547: [bad udp cksum 0x2c8b -> 0xf3ff!] dhcp6 request (xid=5a7099 (client-ID hwaddr/time type 1 time 570277845 000db957745c) (server-ID hwaddr type 1 f81308265711) (elapsed-time 0))
WAN
igb0 2023-01-22
15:09:05.023739 f8:13:08:26:58:97 00:0d:b9:57:74:5c ethertype IPv6 (0x86dd), length 104: (class 0x40, hlim 255, next-header UDP (17) payload length: 50) fe80::fa13:8ff:fe26:5711.547 > fe80::20d:b9ff:fe57:745c.546: [udp sum ok] dhcp6 reply (xid=5a7099 (server-ID hwaddr type 1 f81308265711) (client-ID hwaddr/time type 1 time 570277845 000db957745c) (status-code UnspecFail))
WAN
igb0 2023-01-22
15:09:05.473101 00:0d:b9:57:74:5c 33:33:00:00:00:02 ethertype IPv6 (0x86dd), length 70: (hlim 255, next-header ICMPv6 (58) payload length: 16) fe80::20d:b9ff:fe57:745c > ff02::2: [icmp6 sum ok] ICMP6, router solicitation, length 16
  source link-address option (1), length 8 (1): 00:0d:b9:57:74:5c
    0x0000:  000d b957 745c
WAN
igb0 2023-01-22
15:09:05.569563 f8:13:08:26:58:97 00:0d:b9:57:74:5c ethertype IPv6 (0x86dd), length 78: (class 0xe0, hlim 255, next-header ICMPv6 (58) payload length: 24) fe80::fa13:8ff:fe26:5711 > fe80::20d:b9ff:fe57:745c: [icmp6 sum ok] ICMP6, router advertisement, length 24
hop limit 64, Flags [none], pref medium, router lifetime 4500s, reachable time 0ms, retrans timer 100ms
  source link-address option (1), length 8 (1): f8:13:08:26:58:97
    0x0000:  f813 0826 5897
WAN
igb0 2023-01-22
15:09:06.033298 00:0d:b9:57:74:5c 33:33:00:01:00:02 ethertype IPv6 (0x86dd), length 143: (hlim 1, next-header UDP (17) payload length: 89) fe80::20d:b9ff:fe57:745c.546 > ff02::1:2.547: [bad udp cksum 0x2cb2 -> 0xa290!] dhcp6 solicit (xid=a2e21f (client-ID hwaddr/time type 1 time 570277845 000db957745c) (elapsed-time 0) (option-request DNS-server DNS-search-list) (IA_PD IAID:0 T1:0 T2:0 (IA_PD-prefix ::/56 pltime:4294967295 vltime:4294967295)))
WAN
igb0 2023-01-22
15:09:06.050816 f8:13:08:26:58:97 00:0d:b9:57:74:5c ethertype IPv6 (0x86dd), length 179: (class 0x40, hlim 255, next-header UDP (17) payload length: 125) fe80::fa13:8ff:fe26:5711.547 > fe80::20d:b9ff:fe57:745c.546: [udp sum ok] dhcp6 advertise (xid=a2e21f (server-ID hwaddr type 1 f81308265711) (client-ID hwaddr/time type 1 time 570277845 000db957745c) (IA_PD IAID:0 T1:7200 T2:10800 (IA_PD-prefix 2001:56a:7db2:3c00::/56 pltime:14400 vltime:14700)) (DNS-server 2001:568:ff09:10c::67 2001:568:ff09:10a::116))
WAN
igb0 2023-01-22
15:09:07.035027 00:0d:b9:57:74:5c 33:33:00:01:00:02 ethertype IPv6 (0x86dd), length 157: (hlim 1, next-header UDP (17) payload length: 103) fe80::20d:b9ff:fe57:745c.546 > ff02::1:2.547: [bad udp cksum 0x2cc0 -> 0x75c4!] dhcp6 request (xid=60262b (client-ID hwaddr/time type 1 time 570277845 000db957745c) (server-ID hwaddr type 1 f81308265711) (elapsed-time 0) (option-request DNS-server DNS-search-list) (IA_PD IAID:0 T1:0 T2:0 (IA_PD-prefix 2001:56a:7db2:3c00::/56 pltime:14400 vltime:14700)))
WAN
igb0 2023-01-22
15:09:07.499966 f8:13:08:26:58:97 00:0d:b9:57:74:5c ethertype IPv6 (0x86dd), length 179: (class 0x40, hlim 255, next-header UDP (17) payload length: 125) fe80::fa13:8ff:fe26:5711.547 > fe80::20d:b9ff:fe57:745c.546: [udp sum ok] dhcp6 reply (xid=60262b (server-ID hwaddr type 1 f81308265711) (client-ID hwaddr/time type 1 time 570277845 000db957745c) (IA_PD IAID:0 T1:7200 T2:10800 (IA_PD-prefix 2001:56a:7db2:3c00::/56 pltime:14400 vltime:14700)) (DNS-server 2001:568:ff09:10c::67 2001:568:ff09:10a::116))
#1264
Hi Fanco, thank you for answering on a Sunday. :)


In a nutshell, testing the connectivity on https://ipv6-test.com from the laptop that is provisioned with a GUA on the VLAN interface that has a GUA as well - having a rule on the VLAN to allow any IPv6 ight at the top (temporarily) ---and the result is on that page that only IPv4 is working.

The local DNS is resolving IPv6 as well:ping -6 isc.org

Pinging isc.org [2001:4f8:1:f::66] with 32 bytes of data:
Request timed out.



What appears to eb wrong, if my understanding is correct, is that I don't see a GUA on the WAN - so even if I could try to select the GW in the IPv6 rule, the available options ae as follows:
LAN_TRACK - fe80::
WAN_DHCP6 - No IPv6 Address
WAN_DHCP - expected IPv4 Address



Filtering for DHCP Debug messages in System: Log Files: General doesn't reveal anything abnormal that I could see...
2023-01-22T08:21:13-08:00 Notice opnsense-devel /interfaces.php: plugins_configure monitor (,WAN_DHCP)
2023-01-22T08:21:13-08:00 Notice opnsense-devel /interfaces.php: plugins_configure monitor (execute task : dpinger_configure_do(,WAN_DHCP6))
2023-01-22T08:21:13-08:00 Notice opnsense-devel /interfaces.php: plugins_configure monitor (,WAN_DHCP6)
2023-01-22T08:21:13-08:00 Notice dhcp6c RTSOLD script - Sending SIGHUP to dhcp6c
2023-01-22T08:21:11-08:00 Notice opnsense-devel /interfaces.php: plugins_configure dhcp (execute task : dhcpd_dhcp_configure(,inet6,Array))
2023-01-22T08:21:11-08:00 Notice opnsense-devel /interfaces.php: plugins_configure dhcp (,inet6,Array)
2023-01-22T08:13:48-08:00 Notice dhcp6c dhcp6c REQUEST on igb0 - running newipv6



Please let me know whether there's any other, more useful info that I could provide here.


Thanks again.
#1265
Hi again,

The first time I bumped into this issue was back in December, so this is not 23.1 specific, posting it here since the FW is already on 23.1.RC2.



I'm seeing this weird behavior  on a FW connected to Telus Canada where the WAN doesn't get a routable 2001:: IP yet based on the prefix delegation received the internal network interfaces get configured with 2001::/64 just fine tracking the WAN.


The only information I could find pertains to Edgerouter or pfSense configuration and it's not really 1:1 when compared to the options in the GUI:

https://heald.ca/configuring-telus-optik-ipv6-ubiquiti-edgerouter/

https://www.zacharyschneider.ca/2020/12/pfsense-ipv6-telus/


I tried toggling On and Off "Request only an IPv6 prefix" and  "Send IPv6 prefix hint" along with requesting a different PD Size other than the /56 but it wasn't helpful.




Any guidance on how to move foward troubleshooting this issue is most welcome.



Thank you.

#1266
Quote from: pmhausen on January 20, 2023, 10:39:00 PM
Still confused. What is "23.1.r_20" and how do I get the supposedly released RC2?

Thanks,
Patrick

Hi Patrick,



RC1 showed up in the GUI as 23.1.r_6 and RC2 is showing up as 23.1.r_20 - or at least that's my understanding after performing the upgrades on my FWs.


I am on the development train in Settings-Firmware and will switch back to Community after the official release, then look for any missing updates/changes up from RC2.


After  you are set on the Dev train this is the better avenue to upgrade from RC1 according to a similar question on Twitter answered by the team, and it's what I used to get to RC2 as well:
opnsense-update -bkr 23.1.r2

It doesn't look like a reboot is mandatory, I did it nevertheless to see if everything comes up nicely, and I have nothing to report no matter how simple/complex the configuration is. :)




The one bit of feedback that I have fo the OPNsense team would be to adopt a similar approach as seen in TrueNAS. Development would always be the -devel version and major versions with Betas and RCs once published are selectable in a dropdown menu. I'm not sure if the work required would justify the time - whatever the decision will be (if not already made) will be fine with me. :)
#1267
OPNsense has nothing to do with supporting hardware chipsets, this is either a FreeBSD issue in the kernel or a faulty HW implementation - check if a newer BIOS is available.

If you could find a working or partially working combo by tinkering with the existing options that may be helpful should this lead to a FreeBSD bug report.
#1268
22.7 Legacy Series / Re: PLEASE HELP! WAN FLAPPING!
January 14, 2023, 05:29:52 PM
Quote from: SolarCzar on January 14, 2023, 12:43:56 PM

So, later that Friday when I was finished in the work day (and when no one was home), I upgraded back to 22.7.10_2 for giggles.  No problems so far. As of now, all my LAN elements are back connected and my network appears stable.  If that changes, I'll report back.

I can't say I understand it and maybe one of you smart guys can, but all I can assume is there is something sensitive in the electrical aspects of the 1GbE & 2.5GbE ports.  Oh and the unmanaged switch is 1GbE ports for reference.

By adding the switch in between you isolated the problem - which still occurs imo - from the Topton. Setting the port speed to 1Gbps full duplex should have had the same result. So your FW was never the cause of the issue but at the receiving end of it - and reacting as expected whenever a link changes

The next step would be to call your ISP, explain the problem and ask them to fix it - or if you have access to that ISP managed device and can set the port manually on 1Gbps full duplex it should take care of the faulty auto-negotiation ---> which appears to be the root cause here.
#1269
The /dev/md43 and superblock entries at the bottom might be related to some data corruption, and in any case they're highly unusual for that moment in the boot up process.

I'd simply reinstall and restore the config or now.
#1270
22.7 Legacy Series / Re: PLEASE HELP! WAN FLAPPING!
January 09, 2023, 03:40:36 AM
You seem to be he only one reporting an issue with a Topton (or similar) machine. In the unfortunate one actually stumbles on a bug the following pattern will quickly emerge:

a) a bunch of #Me2 replies in your thread

b) devs become aware of the issue, offering a patch to test in your thread, and depending on the severity and applicability either a hot-patch will be released or if it's something that is likely to affect your particular setup only then it will become generally available on the next . release

Neither a) nor b) happened here.

QuoteThis all started with 22.7.10.  I reverted back to 22.7.9 and it was worse.

The rush to quickly revert - how could it get worse ?

QuoteThis was working fine for months.


Sometimes a brownout or a power outage can cause issues. If you're aware or suspect such a thing might have happened right around the time your issue started you could gracefully shutdown the FW then unplug everything from it for 15 minutes - and also power off the modem/ISP device if possible.

Also, depending on the NIC the FW plugs into you could set the WAN pot speed to either 1GB or 2.5Gb - there's rarely a need to keep it on auto-negotiation there.


All things considered, this doesn't seem to be an OPNsense or FreeBSD issue. Whenever in doubt, your best bet is to be on the latest version - and troubleshoot from there.






#1271
Quote from: alh on December 27, 2022, 09:44:54 PM
manually restart the service in the dashboard to have wg0 up and running.

There's little to no justification to still use wireguard-go. The kmod-wireguard works perfectly fine with multiple WG instances alongside OpenVPN or without it.

Side note - once the kmod is installed the Dashboard is not usable anymore and it shows the service being down, which is technically accurate since it pertains to the Go implementation.

pkg install wireguard-kmod

#1272
Unsure what you mean by
QuoteIf I'm home and using wireless everything works fine


By the looks of it you're missing a port forward rule as follows:

Source WiFi_Vlan (or Device_IP) Destination Wan_IP:Wireguard_Port --Redirect to 127.0.0.1:Wireguard_Port

This would make your transition in and out of home WiFI seamless on WG side.
#1273
22.7 Legacy Series / Re: Failing DNS services
December 31, 2022, 07:11:02 PM
If DNScrypt is a must, use the latest version in a docker container. The one in OPNsense is quite old, unsure where the issue is there but I wouldn't use it on the internet until it is upgraded to current.

Bind -- zone management on the FW wouldn't be my first choice.

For anything else Unbound is more than fit for the job, and latest version as well.


Removing one or two if possible from the chain would help you narrow down the DNS issues.

#1274
Turns out I spoke too soon, the old install only got a bump from ~400-500 entries in the past few days to ~ 3471, so it looks like not everything might be OK/consistent server side just yet.
#1275
Restart Crowdsec and give it a few minutes, you'll see the number of IPs in the alias o up, currently 13652.

This is confirmed both on an old install manually upgraded to 1.4.3 and a new one with 1.4.1


The issue was never on the OPNsense side.