Make sure the prefix is in the routing table of the issuing mikrotik. make sure the PC you're pinging from passes through a router that contains the issue route.
I assume the issuing mikrotik and "office router" are the same in this instance? Tim On Nov 1, 2016 3:51 PM, "Art Stephens" <asteph...@ptera.com> wrote: > > OK.. so we can not use static addressing then... > > So I programmed a Mikrotik to do DHCP-PD and connected it to our server network. > [admin@MikroTik] /ipv6 dhcp-server> pr > Flags: D - dynamic, X - disabled, I - invalid > # NAME INTERFACE ADDRESS-POOL PREFERENCE LEASE-TIME > 0 server1 ether2 pool1 255 3d > Flags: D - dynamic > # NAME PREFIX PRE EXPIRES-AFTER > 0 pool1 xxxx:xxxx:3::/60 64 > > > I gave that Mikrotik an address in the IPV6 address space. > [admin@MikroTik] /ipv6 address> pr > Flags: X - disabled, I - invalid, D - dynamic, G - global, L - link-local > # ADDRESS FROM-POOL INTERFACE ADVERTISE > 0 G xxxx:xxxx:0:32::77/64 ether2 yes > 1 DL fe80::20c:42ff:fe20:caa7/64 ether3 no > 2 DL fe80::20c:42ff:fe20:caa6/64 ether2 no > > I can ping from xxxx:xxxx:0:32::77 from our office router (xxxx:xxxx:0:32::32) > I can not ping xxxx:xxxx:0:32::77from my office desk which can ping other addresses on that network. > > And when I set the customer ASUS router to native IPV6 DHCP-PD enabled and plug it into the server network. > Nothing happens. > > > > On Fri, Oct 28, 2016 at 4:11 PM, Tim Way <t...@way.vg> wrote: >> >> Art, >> >> Are you talking about the DHCPv6-PD allocation ranged I talked about? If so those prefixes are intentionally different than what would be present in the routing table. Those prefixes would normally be injected into the tower agent by the router performing DHCP relaying and / or the DHCPv6-PD server. If you are just labbing add the customer prefix to to the router where appropriate. >> >> As far as routing protocols you will only be able to use EIGRP, OSPF, RIPv6 and BGP. >> >> You likely want the relay agent, tower router, to learn the routes. In Cisco land you have to tell the router to snoop on the DHCP packet it relays and to inject the route. >> >> Tim >> >> >> On Oct 28, 2016 6:03 PM, "Art Stephens" <asteph...@ptera.com> wrote: >>> >>> So the only IPV6 routing I can get to work is with Mikrotik/Cisco using OSPFv3 only. >>> >>> Directly plugged into the IPV6 network with a PC both physical and virtual works. >>> >>> But when I try to static setup IPV6 on a router as if I was a customer no luck. >>> >>> I have tried Netgear, ASUS, Linksys and Mikrotik. No routing thru the router. >>> >>> The closest that came to working was the Mikrotik. >>> Can only ping directly connected devices though. >>> I can ping the gateway and dns server from the Mikrotik router but I can not ping from the customer PC behind the Mikrotik router. This is the same PC that works if I plug directly in. >>> >>> IPV6 Things do not appear to work as advertised when it comes to static configs. >>> >>> Is it just me or is anyone else running into this? >>> If you solved it care to share? >>> >>> >>> >>> -- >>> Arthur Stephens >>> Senior Networking Technician >>> Ptera Inc. >>> PO Box 135 >>> 24001 E Mission Suite 50 >>> Liberty Lake, WA 99019 >>> 509-927-7837 <509-927-7837> >>> ptera.com <http://ptera.com> | >>> facebook.com/PteraInc <http://facebook.com/PteraInc> | twitter.com/Ptera >>> ----------------------------------------------------------------------------- >>> "This message may contain confidential and/or propriety information, and is intended for the person/entity to whom it was originally addressed. >>> Any use by others is strictly prohibited. Please note that any views or opinions presented in this email are solely those of the author and are not intended to represent those of the company." >>> >>> _______________________________________________ >>> Wireless mailing list >>> Wireless@wispa.org <Wireless@wispa.org> >>> http://lists.wispa.org/mailman/listinfo/wireless <http://lists.wispa.org/mailman/listinfo/wireless> >>> >> >> _______________________________________________ >> Wireless mailing list >> Wireless@wispa.org <Wireless@wispa.org> >> http://lists.wispa.org/mailman/listinfo/wireless <http://lists.wispa.org/mailman/listinfo/wireless> >> > > > > -- > Arthur Stephens > Senior Networking Technician > Ptera Inc. > PO Box 135 > 24001 E Mission Suite 50 > Liberty Lake, WA 99019 > 509-927-7837 <509-927-7837> > ptera.com <http://ptera.com> | > facebook.com/PteraInc <http://facebook.com/PteraInc> | twitter.com/Ptera > ----------------------------------------------------------------------------- > "This message may contain confidential and/or propriety information, and is intended for the person/entity to whom it was originally addressed. > Any use by others is strictly prohibited. Please note that any views or opinions presented in this email are solely those of the author and are not intended to represent those of the company." > > _______________________________________________ > Wireless mailing list > Wireless@wispa.org <Wireless@wispa.org> > http://lists.wispa.org/mailman/listinfo/wireless <http://lists.wispa.org/mailman/listinfo/wireless> >
_______________________________________________ Wireless mailing list Wireless@wispa.org http://lists.wispa.org/mailman/listinfo/wireless
