Ipv6 static /48
-
Instead of assuming, why don't just give them a call and ask? Because your assumptions clearly don't work.
-
It will not work with assumptions. Good Luck… Contemplate reply#2 & reply#8 again.
-
With assuming I meant, they told me so, it means I have to trust them.
-
I'm used to cisco, simple routing.
R1#configure terminal
R1(config)#interface gigabitEthernet 0/0
R1(config-if)#ipv6 address 2001:db8:0:1::1/64
R1(config-if)#no shutdown
R1(config-if)#exit
R1(config)#interface serial 1/0
R1(config-if)#ipv6 address fe80::1 link-local
R1(config-if)#no shutdown
R1(config-if)#exit
R1(config)#exit
R1#R2#configure terminal
R2(config)#interface gigabitEthernet 0/0
R2(config-if)#ipv6 address 2001:db8:0:2::1/64
R2(config-if)#no shutdown
R2(config-if)#exit
R2(config)#int serial 1/0
R2(config-if)#ipv6 address fe80::2 link-local
R2(config-if)#no shutdown
R2(config-if)#exit
R2(config)#interface serial 1/1
R2(config-if)#ipv6 address fe80::2 link-local
R2(config-if)#no shutdown
R2(config-if)#exit
R2(config)#exitand so on
we are connected via fiber, so they have a cisco router, simple routed our /48 to "our" gateway interface.
So DHCP is not a option. -
Ofcourse it is an option ! Did you try/test it …?
-
Not yet, looking for an cisco router….
Let you know. -
Well, I meant to say do test WAN-DHCP6(PD) with pfSense on the fiber-line with native IPv6…
Anyway, I think you want for an "Upstream Gateway" number outside your /48 domain.
And how do you connect by IPv4 ?
-
Your ISP is routing the /48 to something. That something is how your WAN interface's IPv6 should be configured.
It might be DHCPv6, it might be static, it might be link-local. Only they know.
It it's really a static /48 you'll be good to go once you get it sorted out.
-
Given the settings in the OP, it's static. The first /64 of the /48 is for WAN.
Looks like the only mistake made in the first post is that the prefix length on WAN should be /64 not /48. It's common for ISPs to use the first /64 of a routed block such as a /48 for the interconnect.
On the outside chance that the ISP actually made the /48 on WAN that's an error on their part, it should have the /48 routed to your 2a00:xxxx:aaaa:::2 with prefix set to /64.
Run a packet capture on WAN as you attempt to ping from a host on LAN, see what happens. If the ping leaves but doesn't come back at all, that's upstream routing. If the ping leaves and you see an NDP request on WAN for the LAN address, they fudged the prefix.
-
Yes /48 on the WAN was definitely wrong.
I had again contact with my ISP. They gave me now a transfernet /126 for my WAN. They routed the /48 to my WAN IP.
But still not working, I believe or better sure this is not a pfsense or my config error. I don't have confidence in my provider now.I'm able to ping from LAN side, even from a host (computer) to they're router - my gateway.
Asked them now to send there "show running-config ipv6", which they won't give me….
caputre:
no NDP request found. No response seen to ICMPv6 request in frame 38.
That's all about I see.Keep you posted.
