"
Is there a particular reason why you have "Request only a IPv6 Prefix" enabled? I would think that you'd also want the WAN interface to get an IPv6 address from DHCPv6?
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.
#31
17.1 Legacy Series / Re: Issue with IPv6 on 17.1.4 - transmit failed: Can't assign requested address
April 03, 2017, 03:34:35 PM #32
17.1 Legacy Series / Re: NAT Port Forwarding broken in v17.1.4 nano x64
April 03, 2017, 03:30:29 PM
When you say "router has a public IP address", are you refering to the OPNsense, or a separate device?
#33
17.1 Legacy Series / Re: Issue with IPv6 on 17.1.4 - transmit failed: Can't assign requested address
April 03, 2017, 07:31:05 AM
Can you please screencap the DHCPv6 section of the wan interface settings? This could help in determining what the problem might be.
#34
17.1 Legacy Series / Re: NAT Port Forwarding broken in v17.1.4 nano x64
April 03, 2017, 07:27:38 AM
How exactly are you testing the port forwards? From inside the LAN or externally?
#35
17.1 Legacy Series / Re: Issue with IPv6 on 17.1.4 - transmit failed: Can't assign requested address
April 02, 2017, 07:33:48 PM
LAN is meant to get a /64, it doesn't matter if the prefix from the isp is bigger. This allows you to divide the prefix up into multiple /64s, do you have the LAN interface set to track interface?
#36
17.1 Legacy Series / Re: Help with IPv6
April 01, 2017, 06:50:25 AM
You will want to run this command from ssh:
clog -f /var/log/dhcpd.log
and watch it while applying interface settings on WAN; you should see log entries from dhcp6c.
clog -f /var/log/dhcpd.log
and watch it while applying interface settings on WAN; you should see log entries from dhcp6c.
#37
17.1 Legacy Series / Re: Help with IPv6
April 01, 2017, 02:07:54 AM
are you using the advanced mode for dhcpv6 config on your wan? if so disable it, also, make sure you are not using the same ID on both the internal connections for track interface, and you can take a look at the dhcp log file for hints at why it is not working properly, it could be that you have the wrong prefix size set
#38
17.1 Legacy Series / Re: Help with IPv6
March 31, 2017, 04:37:49 PM
The LAN IPv6 setting should be set to "Track Interface", this will setup the delegated prefix automatically
#39
17.1 Legacy Series / Re: Port Forwarding Issues
March 29, 2017, 07:00:00 AM
I would suggest setting the Destination IP to "WAN Address"
#40
17.1 Legacy Series / Re: Low internetspeed
March 26, 2017, 05:08:39 PM
I would suggest disabling intrusion detection and testing the speed.
#41
17.1 Legacy Series / Re: squid.conf reset to default, on reboot only at access_log point.
March 26, 2017, 12:59:36 AM
If all you are looking for is that small logging change, then I would suggest a feature request to add a setting for log type at https://github.com/opnsense/core/issues
#42
17.1 Legacy Series / Re: squid.conf reset to default, on reboot only at access_log point.
March 25, 2017, 05:19:12 PMQuote from: gaurovsoni on March 25, 2017, 03:50:04 PM
Figure It out :
/usr/local/opnsense/service/templates/OPNsense/Proxy/squid.conf <-- edited here :)
All your changes in that file will be overwritten when you upgrade opnsense.
#43
17.1 Legacy Series / Re: IPsec traffic blocked by Firewall despite allow rules - works in 16.7.14
March 24, 2017, 02:51:14 PM
Please try the kernel here: https://forum.opnsense.org/index.php?topic=4804.0
#44
17.1 Legacy Series / Re: OpenVPN CSO only works for "default tunnel network"
March 23, 2017, 05:04:29 PM
I suspect you are missing an outbound NAT rule for the admin network source, you may need to manually add it.
#45
17.1 Legacy Series / Re: UPnP not working at all
March 23, 2017, 02:29:40 PM
Make sure you enable one or both of these options (I would recommend both):
Allow UPnP Port Mapping
Allow NAT-PMP Port Mapping
Allow UPnP Port Mapping
Allow NAT-PMP Port Mapping
