1
17.1 Legacy Series / Re: Problem with NAT
« on: June 05, 2017, 03:21:14 pm »
Did you set the destination address to OPT1 address?
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.
2
17.1 Legacy Series / Re: policy based routing, multiple routing tables
« on: June 05, 2017, 06:42:42 am »
I suspect that multiple routing tables will never be added unless it goes into the stock FreeBSD kernel, as they are generally not needed because policy based routing can be done with firewall rules.
3
17.1 Legacy Series / Re: Problem with NAT
« on: June 04, 2017, 04:14:35 pm »
You must set a destination address (generally WAN Address) and destination port
4
17.1 Legacy Series / Re: policy based routing, multiple routing tables
« on: June 04, 2017, 06:44:02 am »
You can use firewall rules to mostly accomplish this, setting a gateway on the rule.
5
17.1 Legacy Series / Re: Help with IPv6
« on: May 08, 2017, 04:27:15 pm »
Then honestly, the only thing i can suggest is that your ISP has a misconfiguration somewhere, there is no reason why you shouldn't be able to request both a an address and a prefix at the same time.
Does routing work when you only have a prefix delegation?
Does routing work when you only have a prefix delegation?
6
17.1 Legacy Series / Re: Help with IPv6
« on: May 08, 2017, 04:05:09 pm »
What happens if you set the WAN IPv6 config to SLAAC? do you get an ip address then?
7
17.1 Legacy Series / Re: Help with IPv6
« on: May 08, 2017, 03:58:25 pm »It sounds funny but I've seen this too. First boot is perfect, afterwards reconfigure takes a up to a minute or it fails. Next reboot is perfect again.
Taking up to a minute is likely due to having to wait for the next Router Advertisement when "Directly Send Solicit" is disabled. But when it completely fails, even with config that previously worked perfectly, it is some kind of bug.
What I've also seen is that although LAN is tracking, reloading LAN doesn't have any effect other than removing the IPv6, so you always want to reload WAN or better yet use the console option 11 to fully cycle the interface configuration.
All that is required to fix that is to send the HUP signal to the dhcp6c process of the "Parent Interface" when reconfiguring a Track Interface interface. This will cause it to reconfigure.
8
17.1 Legacy Series / Re: Help with IPv6
« on: May 08, 2017, 03:58:01 pm »
The log says that it seems to be still asking for an address, did you enable the request prefix only option? Perhaps the logs are from before?
9
17.1 Legacy Series / Re: Track Interface - RA Issue
« on: May 08, 2017, 03:52:24 pm »
Personally i think that Router Advertisements should be able to be configured for Track Interface interfaces.
Even the DHCPv6 server should be able to be configured, with Static Mappings, Range and Prefix Delegation Range config options being disabled when Track Interface is used. It should be easy enough to startup the DHCPv6 server when a valid range has been assigned to the interfaces, just like it starts up the RA deamon.
Even the DHCPv6 server should be able to be configured, with Static Mappings, Range and Prefix Delegation Range config options being disabled when Track Interface is used. It should be easy enough to startup the DHCPv6 server when a valid range has been assigned to the interfaces, just like it starts up the RA deamon.
10
17.1 Legacy Series / Re: Help with IPv6
« on: May 08, 2017, 03:37:50 pm »
Taomyn, can you try setting it to request ipv6 prefix only, and disable directly send solicit?
This should allow Router Advertisements to give you the IP, while letting dhcp6c to request the prefixes.
Make sure to reboot after making these changes to verify if they work.
This should allow Router Advertisements to give you the IP, while letting dhcp6c to request the prefixes.
Make sure to reboot after making these changes to verify if they work.
11
17.1 Legacy Series / Re: Help with IPv6
« on: May 07, 2017, 07:07:54 pm »
I will also note that in my own testing, with OPNsense as the DHCPv6 server, and another OPNsense being the client, that the client seems to start completely ignoring the server responses after a few reconfigurations of WAN, even with settings that previously worked perfectly fine. So you may need to reboot after every reconfiguration if you truely want to test which configurations work and which don't.
I have been trying to narrow down why this happens but so far have not had any luck.
I have been trying to narrow down why this happens but so far have not had any luck.
12
17.1 Legacy Series / Re: Help with IPv6
« on: May 07, 2017, 06:15:35 pm »
Do you remember which combination(s) gave you an address on the WAN but no delegated prefixes? I think that is where you'd need to start to figure out exactly how to get both address and prefix.
Also, who is your ISP?
Also, who is your ISP?
13
17.1 Legacy Series / Re: Help with IPv6
« on: May 07, 2017, 06:01:59 pm »
Does the WAN even need an address? The delegated prefixes should be routed by your ISP via the link-local address on your WAN. Are you getting an IPv6 default gateway?
BTW, there are at least 16 different combinations of the basic options (assuming you know the correct prefix size from the ISP), are you sure you tried every combination?
BTW, there are at least 16 different combinations of the basic options (assuming you know the correct prefix size from the ISP), are you sure you tried every combination?
14
17.1 Legacy Series / Re: Help with IPv6
« on: May 07, 2017, 04:42:53 pm »Code: [Select]Request only a IPv6 prefix: yes
So in the end, I currently have IPv6 addresses or the LAN interfaces but nothing on the WAN interface. Any idea how I can sort that out?
If you want an IPv6 address on the WAN, then you must disable "Request only a IPv6 prefix" as the purpose of this option is to not request an address, only a prefix.
15
17.1 Legacy Series / Re: Track Interface - RA Issue
« on: May 07, 2017, 04:35:57 pm »
Track interface automatically enables and configures Router Advertisements when it get's it's prefix delegation.