Messages

1

24.7 Production Series / Re: New Dashboard short-comings

« on: August 03, 2024, 04:47:26 pm »

**** Interface statistics was better in the old version with all details rather than the current PIE chart.****

Can we have it configurable ? with choose PIE chart or details like in old version ?

I also find it not useful. The older version of the Interface statistics was better. Hopefully we can get option to customize in future.

2

24.7 Production Series / Re: Interfaces widget missing VPN Interfaces in 24.7

« on: July 25, 2024, 05:16:17 pm »

Had a similar issue but theme I was using was tukan. I switched back to opnsense theme, and interfaces are visible now

3

22.7 Legacy Series / Re: ASIX AX88179A USB3 to Ethernet Adaptor

« on: January 17, 2023, 03:39:07 pm »

That is so strange.. I read somewhere that OPNSense brings in all native drivers from FreeBSD. Not sure why it doesn't work.
I understand using a USB adaptor is not the ideal thing to do, but currently don't have a L2 switch to make it work with a single NIC

4

22.7 Legacy Series / ASIX AX88179A USB3 to Ethernet Adaptor

« on: January 15, 2023, 10:28:27 am »

Hi

Opnsense 22.7.10_2
I want to use the USB to Ethernet Adaptor which has chipset Asix AX88179A. It gets detected by the system but it is continuously flapping. Is there any way to make it work??

Following are the charterstics

Code: [Select]

root@pghome:~ # usbconfig -d ugen0.4mp_device_desc
ugen0.4: <ASIX AX88179A> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=ON (46mA)

  bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0320
  bDeviceClass = 0x0000  <Probed by interface class>
  bDeviceSubClass = 0x0000
  bDeviceProtocol = 0x0000
  bMaxPacketSize0 = 0x0009
  idVendor = 0x0b95
  idProduct = 0x1790
  bcdDevice = 0x0200
  iManufacturer = 0x0001  <ASIX>
  iProduct = 0x0002  <AX88179A>
  iSerialNumber = 0x0003  <000000000088A6>
  bNumConfigurations = 0x0003

root@pghome:~ # usbconfig -d ugen0.4mp_all_config_desc | grep -i binterface
      bInterfaceNumber = 0x0000
      bInterfaceClass = 0x00ff  <Vendor specific>
      bInterfaceSubClass = 0x00ff
      bInterfaceProtocol = 0x0000
      bInterfaceNumber = 0x0000
      bInterfaceClass = 0x0002  <Communication device>
      bInterfaceSubClass = 0x000d
      bInterfaceProtocol = 0x0000
      bInterfaceNumber = 0x0001
      bInterfaceClass = 0x000a  <CDC-data>
      bInterfaceSubClass = 0x0000
      bInterfaceProtocol = 0x0001
      bInterfaceNumber = 0x0001
      bInterfaceClass = 0x000a  <CDC-data>
      bInterfaceSubClass = 0x0000
      bInterfaceProtocol = 0x0001
      bInterfaceNumber = 0x0000
      bInterfaceClass = 0x0002  <Communication device>
      bInterfaceSubClass = 0x0006
      bInterfaceProtocol = 0x0000
      bInterfaceNumber = 0x0001
      bInterfaceClass = 0x000a  <CDC-data>
      bInterfaceSubClass = 0x0000
      bInterfaceProtocol = 0x0000
      bInterfaceNumber = 0x0001
      bInterfaceClass = 0x000a  <CDC-data>
      bInterfaceSubClass = 0x0000
      bInterfaceProtocol = 0x0000
root@pghome:~ #

5

22.7 Legacy Series / Re: Effective Privileges under Systems > Access > Users

« on: August 03, 2022, 06:09:54 pm »

I reimaged my machine and now the option is visible again.
Not sure what broke in the previous imaging process. Used the same USB installer

6

22.7 Legacy Series / Re: Effective Privileges under Systems > Access > Users

« on: July 31, 2022, 05:34:22 pm »

Honestly.. Didn't understand.
Are you saying, it is working for you.
Mine is a fresh build. I had this field until 22.1.10

7

22.7 Legacy Series / Re: Effective Privileges under Systems > Access > Users

« on: July 31, 2022, 07:39:32 am »

The Language is already set to English under System > Settings > General

8

22.7 Legacy Series / Effective Privileges under Systems > Access > Users

« on: July 29, 2022, 05:00:56 pm »

The Effective Privileges Field is gone from Systems > Access > Users
Is it moved to some other page??

9

Virtual private networks / Re: Private Internet Access (PIA) WireGuard Guide/Script

« on: May 18, 2022, 05:26:24 pm »

Okay it turns out that opnsenseWGName was the issue.  I named it PIA_toronto, which apparently was causing the script to pull my existing PIA config from OPNsense.  When the script asked for a new wireguard key (using an existing WG public key), PIA refused the creation and caused the script to fail.

So, I changed opnsenseWGName to PIACA, and it created the interface just fine.

Not sure if the API doesn't like the underscore or the small caps ... but removing both allowed me to move forward!

I had exact same issue and I reported over github via https://github.com/FingerlessGlov3s/OPNsensePIAWireguard/issues/24
I am glad he has added the check in the code now for opnsenseWGName

10

Tutorials and FAQs / Re: HOWTO - Routing Opnsense traffic over SurfsharkVPN

« on: April 25, 2022, 04:51:49 pm »

Please do share your investigation outcome!

11

Tutorials and FAQs / Re: HOWTO - Routing Opnsense traffic over SurfsharkVPN

« on: April 19, 2022, 06:39:39 pm »

Is it working for anyone post upgrade to 22.1.6
For me the SURFSHARK_VPNV4 gateway is not marked as active. Hence no internet for the clients

12

21.7 Legacy Series / Re: IPv6 traffic not going through

« on: July 31, 2021, 09:00:16 pm »

Thanks
I added the LAN rule and I upgraded to 21.7 as well, but now getting mixed behavior
I can browse to IPv6.google.com
I can ping IPv6 address on the internet

Code: [Select]

ping www.hotstar.com

Pinging e35862.dscj.akamaiedge.net [2600:140f:2e00::685a:593] with 32 bytes of data:
Reply from 2600:140f:2e00::685a:593: time=6ms
Reply from 2600:140f:2e00::685a:593: time=11ms
Reply from 2600:140f:2e00::685a:593: time=13ms
Reply from 2600:140f:2e00::685a:593: time=6ms

Ping statistics for 2600:140f:2e00::685a:593:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 6ms, Maximum = 13ms, Average = 9ms
However, ipv6-test.com, test-ipv6.com and ipv6test.google.com fails the IPv6 tests
This all happens on one device (Microsoft surface)
In other device - Iphone / Ipad or MAC, I can only ping the IPv6 address but cant browse to ipv6.google.com and all the test website fails it. Infact I cant browse to opnsense.org while I have dual stack on Apple devices
Have checked the DNS settings also

Dont know where to troubleshoot further

13

21.7 Legacy Series / Re: IPv6 traffic not going through

« on: July 25, 2021, 05:59:16 pm »

Yes I have enabled it but still no traffic forwarding happening

14

21.7 Legacy Series / Re: IPv6 traffic not going through

« on: July 23, 2021, 06:12:47 pm »

Thanks
Let me try by enabling the IPv6 DNS
No Sensei, Suricata here
What IPv6 rules I should add on the WAN??

15

21.7 Legacy Series / IPv6 traffic not going through

« on: July 15, 2021, 04:49:03 pm »

Hi
I am running latest version 21.1.8
My ISP recently started IPv6 via DHCPv6 with PD. I could successfully configure for PD i.e. all the devices in a LAN are getting unique IPv6 address however I am not able to reach any of the IPv6 addresses on the Internet
The firewall rule is in place on the LAN to allow IPv6 traffic with all *
From the OPNSense Shell also I am unable to ping the IPv6 address

Code: [Select]

root@314-OPN:~ # ifconfig pppoe0
pppoe0: flags=88d1<UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST> metric 0 mtu 1492
inet6 fe80::4262:31ff:fe12:7e84%pppoe0 prefixlen 64 scopeid 0x9
inet6 fe80::4262:31ff:fe12:7e86%pppoe0 prefixlen 64 scopeid 0x9
inet6 2401:4900:1f30:xxxx::x:xxxx prefixlen 128
inet 182.68.xxx.xxx --> 122.161.xxx,xxx netmask 0xffffffff
nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
root@PGHOME-OPN:~ #

Code: [Select]

root@314-OPN:~ # ping google.com
PING google.com (142.250.194.46): 56 data bytes
64 bytes from 142.250.194.46: icmp_seq=0 ttl=119 time=7.169 ms
64 bytes from 142.250.194.46: icmp_seq=1 ttl=119 time=6.925 ms
64 bytes from 142.250.194.46: icmp_seq=2 ttl=119 time=6.934 ms
64 bytes from 142.250.194.46: icmp_seq=3 ttl=119 time=7.041 ms
64 bytes from 142.250.194.46: icmp_seq=4 ttl=119 time=6.808 ms
^C

Code: [Select]

root@314-OPN:~ # ping6 google.com
PING6(56=40+8+8 bytes) 2401:4900:1f30:xxxx::x:xxxx --> 2404:6800:4007:820::200e
^C
--- google.com ping6 statistics ---
16 packets transmitted, 0 packets received, 100.0% packet loss
root@314-OPN:~ #
PS:: It works with Ubiquiti Edgerouter