IPv6 testing
-
you can set that sysctl in the system tunables.
I think you just didn't reboot after gitsyncing. It's in the rc.bootup script.
-
I've noticed a couple of other issues. After rebooting my box when the git is first installs, I can't access the internet. When i try to ping from the box to yahoo, it says there is no route. If i go to interfaces-WAN then click save-apply; I'm able to access the internet. I have to do this every time I reboot the box. When I install http://gitweb.pfsense.org/pfsense/mainline.git or just perform an update to the firmware, everything is back to normal.
When I try get the gateway under routing. The box wont let me input the ipv6 address that i got from he.net. It says the subnet is not within the range. If I leave the gateway blank and click save, it puts the ipv6 address that i try to manually enter.
When creating the WANIP6 interface after creating the gateway, I don't get an option to select the gateway.. Only option is none.
My box is setup with a DHCP WAN from my ISP (TWC). 1 LAN, 2 OpenVPN connects(i didn't create interfaces for them, 1 roadwarrior, the other is a site2site). I have a few packages installed but snort is the only networking one that would touch the wan interface.
When i have time I will do a fresh install without restoring my config file and see if there is a difference.. I've been meaning to do this since I have issues with the traffic-shaper. I can't access the internet after using the shaper wizard.. Somthing is blocking the traffic but i dont see it in the logs…. But that issue is for another thread :-)
-
you can set that sysctl in the system tunables.
I think you just didn't reboot after gitsyncing. It's in the rc.bootup script.
Ahh, ok that must've been the issue. Yeah, I never rebooted.
Thanks!
Derek
-
Something that might be useful to those who are trying this code: once you've set up gitsync for the first time, there is an additional option on the firmware updater settings in the web gui to gitsync when an update has been installed. This way you won't need to run gitsync after the reboot (unless the gitsync failed for some reason). I might later add some kind of pre-update check to make sure it is possible to do the operations needed for the gitsync, like fetching the code, etc., and cancel the update if the gitsync will fail - useful for when it is critical that the gitsync succeeds.
-
Hi guys,
I really want to participate in the IPv6 fun here, but all my routers are running nanoBSD firmware and gitsync doesn't work there. What can I do?GB
-
We might need to investigate in somehow producing a build or snapshot based on this branch, we'll investigate.
-
Hi guys,
I really want to participate in the IPv6 fun here, but all my routers are running nanoBSD firmware and gitsync doesn't work there. What can I do?
GBgitsync should work on nanobsd? Just need to make the image rw before you run it?
-
Last time I tried, it ran out of space on /var trying to actually install git.
-
Custom images built from Seth's REPO:
http://cvs.pfsense.org/~sullrich/ipv6/
-
Custom images built from Seth's REPO:
http://cvs.pfsense.org/~sullrich/ipv6/
Nice, is it auto build like the normal snapshots?
-m4rcu5
-
I had time to run a fresh install. I changed my LAN IP, LAN dhcp range and WAN is set for dhcp by default. I install the git repository from http://gitweb.pfsense.org/pfsense/pfSense-smos.git. It does install some packages right after typing "playback gitsync" but then I get the prompt for the custom url. Rebooted the box and I still couldn't route to the internet. I save/apply my WAN interface and I was able to route to the internet again.. Did another reboot, and same results, cant route to the internet until save/apply my WAN interface.
Any ideas what is causing this? I had a similar issue with 1.2.3 a while ago if my cable modem would reboot.. I remember there was a package that fixed the issue.. Can't remember the name but its a package that was for 1.2.3 I believe. I don't see it under 2.0.
Thanks for all the work you guys have been making with ipv6…
-
My box here has a dhcp and it still works after a update and gitsync. Odd.
-
My box here has a dhcp and it still works after a update and gitsync. Odd.
It worked after the gitsync, it stopped working after the first reboot. The WAN DHCP client does pick up an ip address from my ISP(Its same IP for about 12-24months), it also grabs the DNS servers.. When I try to ping from the box to lets say google.com, I get a no route error.. After saving/applying the WAN interface page… Its able to ping.
-
When I try get the gateway under routing. The box wont let me input the ipv6 address that i got from he.net. It says the subnet is not within the range. If I leave the gateway blank and click save, it puts the ipv6 address that i try to manually enter.
When creating the WANIP6 interface after creating the gateway, I don't get an option to select the gateway.. Only option is none.
Cino, did you manage to solve this before you did a fresh install?
I seem to be running into the same problem, but a fresh install isn't feasible at the moment.Also, Databeestje: Awesome.
-
When I try get the gateway under routing. The box wont let me input the ipv6 address that i got from he.net. It says the subnet is not within the range. If I leave the gateway blank and click save, it puts the ipv6 address that i try to manually enter.
When creating the WANIP6 interface after creating the gateway, I don't get an option to select the gateway.. Only option is none.
Cino, did you manage to solve this before you did a fresh install?
I seem to be running into the same problem, but a fresh install isn't feasible at the moment.Also, Databeestje: Awesome.
I wasn't able to resolve the issue…
-
I too have a similar situation to the last two posters. The Gateway will not let me put in the correct info and if I leave it blank then it will put in dynamic instead and I get no ipv6 anymore. I had to change it back to the way I had it which never says online or does any of the gateway checks.
-
I have not gotten round to that, I'm doing this as time permits
-
Custom images built from Seth's REPO:
http://cvs.pfsense.org/~sullrich/ipv6/
Awsome. Thanks.
I had the same experience as Jim P. Git install fails on nanoBSD due to partition size limitations.GB
-
The subnet check on the gif interface should now properly work again. Have not verified yet, gitsync your install to get it.
You also get (hopefully) working traffic counters for ipv6 traffic.
IPv6 packet counts are logged but not graphed yet.
Menu banner shows IPv6 addresses now too.
ICMP6 rules have been relaxed so that we might have a shot at getting dhcp v6 messages out.
I also added unblockable ICMP6 rules to make sure basic connectivity is never blocked.
Addition of Bogon support for IPv6 prefixes, although a tad large at 30k entries -
I have just freshly installed latest snapshost and had my system synced with pfSense-smos repository.
I did follow this instructions and it still says "The gateway address 2001:470:1f0a:XXXX::1 does not lie within the chosen interface's subnet."I also noticed interesting behaviour. After gitsyncing with IPv6 repo, automatic checks for new firmware/auto update don't work anymore. It says "Unable to check for updates."