odd ipv6 routing issue
-
I will know that for next time I wire a house. in the mean time, pfsense has been working fine for 5 years like this, it is just ipv6 that is giving me trouble and I am not investing in a switch/router/firewall over this so how do we make this work.
-
@techpro2004 said in odd ipv6 routing issue:
this so how do we make this work.
your machine need to be able to find the mac of their gateway.. Why that works on some machines and not others could have something to do with the bridge?
And you say it works just fine with IPv4.. Wouldn't be a firewall issue, because you can still arp and NDP even with firewall..
Did you mention these machines are multihomed? Have more than 1 interface?
What is the IP address of pfsense, both GUA, and the link-local. What does your client show for its gateway route print, what does it show in its neighbors table?
netsh int ipv6 show neighbors
-
I may have fixed it, not sure if it will survive a reboot.
I edited my bridge, clicked on advanced and put a check mark next to "enable ipv6 auto linklocal". and rebooted pfsense
thanks for all of your help.
will post back if it acts up again.
-
so I had ipv6 working but then I rebooted my win 11 machine and I am back where I was.
-
the system I currently am testing on has 2 nics
-
ipv6 address: 2600:4040:9afe:9c00:3eec:efff:fe3c:e916
lan kink local: e80::1:1%igb2
wan link local: fe80::3eec:efff:fe3c:e917%igb3
this may be interesting:
wan gateway: fe80::3e61:4ff:fe04:2cb4%igb3
-
@techpro2004 said in odd ipv6 routing issue:
so I built a 12port router out of an old server and 3x i350-t4 nics and installed pfsense on it.
Ouch!!!
Get a proper switch.
-
@techpro2004 so you have this box with 2 nics plugged into 2 different interfaces on pfsense that are bridged?
-
correct but the other box with trouble only has 1 nic
-
IT appears to me that when I reboot the windows 11 machines, pfsense is not detecting they went down and then trying to reuse the same data when reconnecting and failing. Is there a down time out setting I can adjust?
-
@techpro2004 said in odd ipv6 routing issue:
detecting they went down and then trying to reuse the same data when reconnecting and
Doesn't work that way.. What data do you think it would continue to use exactly?
For starters why would you plug the same machine into a bridge? That is just asking for problems - even if you don't just create a huge loop.
Here is what I would suggest, if your saying IPv4 works fine - then just forget IPv6.. It really has no valid use case currently anyway. Unless your behind a IPv4 nat and need it to host services to the part of the planet that does have IPv6.
Get a switch... I see a tplink 16 port smart switch on amazon for $80.. You could prob find a dumb 16 gig for like 60.. I see a 24 port tplink gig smart switch for $100..
You messing around with this you prob have burned thru way more than $100 of your time already. Prob sell 1 of those nics and pay for the switch ;)
-
I really am not fond of the switch idea as switches fail more often then my i350-t4 nics in pfsense. (if it was in windows, I would say the nics fail more often) I do have a x540-t2 lying around, so if you can recommend a cheap system (i5 or xeon) to put that in along with a single port intel pcie nic, I would be open to that. I would need 3 nics wan,lan and isolation. thanks.
-
@techpro2004 said in odd ipv6 routing issue:
really am not fond of the switch idea as switches
Well good luck.. Anyone that thinks its ok to bridge what like 10 to 8 interfaces together to make what they think is a working network.. Yeah good luck with that..
Been in the business for some 30 years, before there was even switches. Guess how many I have seen fail ;) hahahah.. Sure all things fail - but if that is your logic in running some 10 port bridge with interfaces vs a switch... Yeah have fun..
-
@johnpoz said in odd ipv6 routing issue:
Been in the business for some 30 years, before there was even switches.
So, you're a newcomer. I've been in the LAN business since early 1978, before there was Ethernet or IP. It was on the Air Canada reservation system, where the LAN used time division multiplexing over coax @ 2 Mb or triaxial cable @ 8 Mb. I started in telecom in May 1972.
