A little help setting up a connection
-
OK that looks fine. Looks like em0 is LAN and igb0 is WAN.
Do the IPv6 settings on the interfaces in Status > Interfaces match those logs?
What is your IPv6 default gateway? Note that the default gateway is obtained using a router solicitation/advertisement. It is not assigned via DHCP6 like IPv4 is. What is the whole entry in Status > Gateways for the IPv6 on that interface?
-
Yes. Em0 is my LAN and igb0 is my WAN.
Status > Interfaces shows me the address designed to these interfaces. I am new to this thing but it seems correct.
I don't know what is my default gateway. In Status > Gateways shows only that ipv6 gateway is "pending".
Do I have to check "Send IPv6 prefix hint" in dhcp6 client configuration?
-
What are the actual contents of the entire pending gateway line?
A pending gateway will work. My he.net tunnel shows a pending gateway and it works fine.
-
Name: WAN_DHCP6
Gateway: dynamic
Monitor:
RTT: Pending
LOSS: Pending
Status: Pending
Description: Interface WAN_DHCP6 Gateway -
Looks like you are not getting a Router Advertisement. Not sure. What is the output of
netstat -rnfinet6??Particularly interested in the
defaultline. -
@derelict said in A little help setting up a connection:
netstat -rnfinet6
This command show this table:
(/assets/uploads/files/1535461707419-print.jpg) -
@trendkill99 said in A little help setting up a connection:
No default line ....
It should look like this :
[2.x.y-RELEASE][admin@pfsense.b**-h***-f*****.net]/root: netstat -rnfinet6 Routing tables Internet6: Destination Gateway Flags Netif Expire default 2001:470:****:5c0::1 UGS gif0 ::1 link#4 UH lo0 2001:470:****:5c0::1 link#8 UH gif0 2001:470:****:5c0::2 link#8 UHS lo0 2001:470:****:5c0::/64 link#3 U fxp0 2001:470:****:5c0:2::1 link#3 UHS lo0 2001:470:****:2::/64 link#9 U ovpns1 2001:470:****:2::1 link#9 UHS lo0 fe80::%rl0/64 link#1 U rl0 fe80::2e0:4cff:fe80:4b18%rl0 link#1 UHS lo0 fe80::%sis0/64 link#2 U sis0 fe80::20f:b5ff:fefe:4ee7%sis0 link#2 UHS lo0 fe80::%fxp0/64 link#3 U fxp0 fe80::212:3fff:feb3:5875%fxp0 link#3 UHS lo0 fe80::%lo0/64 link#4 U lo0 fe80::1%lo0 link#4 UHS lo0 fe80::%gif0/64 link#8 U gif0 fe80::2e0:4cff:fe80:4b18%gif0 link#8 UHS lo0 fe80::%ovpns1/64 link#9 U ovpns1 fe80::2e0:4cff:fe80:4b18%ovpns1 link#9 UHS lo0 -
Thanks for your reply. In this case what should i do ?
-
My IPv6 is more a static setup - and rather special because of the usage of a GIF interface (whatever that my be ... but it works).
Yours is a more basic DHCP version IPv6 - so, IP's, DNS and gateway are assigned to you by your ISP, although every ISP does things "somewhat different".Something - I can't detail more - isn't functioning right .... the default route is assigned for some reason.
No "help me" PM's please. Use the forum, the community will thank you.
Edit : and where are the logs ?? -
But my previous cisco router (rv340) worked with this cable modem (arris tg1692). At certain point the router loses ipv6 connection and needed a reboot to bring back ipv6 connectivity.
In my case, is there a way to pfsense send router solicitation to my cable modem ?
-
So the Cisco didn't really work either. That points upstream.
You will probably have to capture traffic on the WAN and become one with looking at IPv6 router solicitations and advertisements so you can go back to the ISP and tell them what's what.
They should be periodically advertising a default route that your WAN interface would pick up on and should respond to the solicitations that should be periodically going out WAN.
https://en.wikipedia.org/wiki/Neighbor_Discovery_Protocol
-
@gertjan said in A little help setting up a connection:
Yours is a more basic DHCP version IPv6 - so, IP's, DNS and gateway are assigned to you by your ISP
Gateways are never assigned by DHCPv6. They are found using NDP.
-
Cisco work for 2-3 days then go down. After a reboot the ipv6 comes back.
There is no chance to get support from my isp. Is there a way to do this using pfsense?
I have tried this solution https://forum.netgate.com/topic/40344/how-to-bring-interface-up-from-pfsense-commandline/7 but with no success.
-
Again, this works in pfSense if the ISP does what it is supposed to be doing, as is evidenced by at least my DHCP6 connection to Cox that pretty much never goes down and countless others.
I would packet capture on WAN for IPv6 for a while (set 100000 packets or something), pull it into Wireshark and see what's there.
-
I did the packet capture on my wan interface. I have opened the .cap file but there is no ipv6 packets.
When I capture any traffic it returns a lot of stuff.
-
How long did you let it run for? I would edit/save WAN (no changes necessary) while capturing. I would only capture on address family IPv6.
-
-
FWIW, my upstream (Cox) sends an RA every 4 seconds or so.
Internet Control Message Protocol v6 Type: Router Advertisement (134) Code: 0 Checksum: 0xfa70 [correct] [Checksum Status: Good] Cur hop limit: 64 Flags: 0xc0, Managed address configuration, Other configuration, Prf (Default Router Preference): Medium Router lifetime (s): 1800 Reachable time (ms): 3600000 Retrans timer (ms): 0 ICMPv6 Option (Source link-layer address : 2c:86:d2:89:20:19) Type: Source link-layer address (1) Length: 1 (8 bytes) Link-layer address: 2c:86:d2:89:20:19 ICMPv6 Option (MTU : 1500) Type: MTU (5) Length: 1 (8 bytes) Reserved MTU: 1500 -
I don't know where can I see this info.
My wireshark capture now have some things related to ipv6
-
Yeah. See those router solicitations in the second screen shot that aren't being responded to?
There's your problem. pfSense is asking, they're not responding.
You can limit the capture to protocol ICMPv6 to eliminate a lot of that noise too.
