search

fakemanhk / openwrt-jp-ipoe

Configure OpenWRT to work with Japan NTT IPv6 service
132 stars 14 forks source link

Could you share your /etc/config/network? #16

Closed alexisfrjp closed 1 year ago

alexisfrjp commented 1 year ago

Hey, could you share your /etc/config/network file?

You assumed we already have access to Luci and all the interfaces exist already but it isn't the case. After creating the WAN6 interface, I don't get an IPv6 address... only the IPv6-PD.

config interface 'wan6'
        option proto 'dhcpv6'
        option device 'eth2'
        option ip6prefix '2400:XXXX:XXXX:XXXX::/56'
        option reqaddress 'try'
        option reqprefix 'auto'

I wonder what I need to setup, everything by default in Luci.

Thank you!

fakemanhk commented 1 year ago

Mine is more or less same as yours, however I have no Hikari Denwa so I only have a /64 prefix, you have /56 which looks different, what's your plan and provider? Anything suspicious in System Logs regarding your eth2?

alexisfrjp commented 1 year ago

I also tried to spoof the wan's mac address of the NTT XG-100NE router just in case there is any protection. My plan is NTT Hikari Cross (10G) wth ぷらら as the ISP but it shouldn't really matter, it still uses prefix delegation and MAP-E. Maybe there is something more needed if the prefix is <64.

Nothing special in the System Logs, I'll check again, thank you!

fakemanhk commented 1 year ago

If I am not wrong, here seems showing ぷらら 10G is using transix/ds-lite??

alexisfrjp commented 1 year ago

Looks like the NTT router doesn't have an ip address for its WAN, then it's fine. I was able to get an IP for the LAN.

It's definitely map-e, I have the XG-100N not PR500* modem, and I got all the information from the NTT router. image

fakemanhk commented 1 year ago

Looks like the NTT router doesn't have an ip address for its WAN, then it's fine. I was able to get an IP for the LAN.

OK I get what you mean, so for IPv6, some ISP will not assign Global Unicast Address (GUA) to your router WAN interface, instead they use link-local address to communicate (you can probably use console to check the route table of your WAN side), this is called unnumbered IP distribution. when a device connecting to ISP with a non-zero prefix delegation size there should be no GUA address given (your router usually has non-zero delegation size). Normally router end WAN link should not request GUA but only the prefix, and then your router can based on the given prefix with your own DHCPv6 or SLAAC arrangement to give clients proper GUA.

I recall that in old days when I use pfSense, WAN link IPv6 setting it allows me to "Request prefix only without requesting address", which is exactly same thing.

There is a drawback for this implementation, if your ISP HGW is connecting to an older client which can't handle this implementation properly will end up with no GUA, so ISP is assuming you have proper equipment, or they already provide you the equipment to handle this after HGW.

alexisfrjp commented 1 year ago

I'm very new in the IPv6 world. ISP definitely assumes I have the proper equipment and provide their NTT router anyway that is way too basic, can't even add static routes... that's why I'm trying to get rid of it. Thanks for your help!

fakemanhk commented 1 year ago

ISP definitely assumes I have the proper equipment

Because they've given at least one to you already :) Basic or not is not really their concern, as long as it's "just work".

We are already a lot better than those using SoftBank, from what I know their 4-over-6 implementation is based on something similar to 4rd which is kind of legacy.

prijkes commented 1 year ago

These are the interface settings when I used Hikari Cross (NTT+PLALA+XG-100N+MAP-E)):

config interface 'loopback' option ifname 'lo' option proto 'static' option ipaddr '127.0.0.1' option netmask '255.0.0.0'

config globals 'globals' option ula_prefix 'fd03:6236:b223::/48'

config interface 'lan' option ifname 'eth0.1' option proto 'static' option netmask '255.255.255.0' option ip6assign '60' option type 'bridge' option mtu '9014' option ipaddr '192.168.1.101'

config device 'lan_eth0_1_dev' option name 'eth0.1' option macaddr 'fc:ec:da:7b:30:f6'

config device 'wan_eth0_2_dev' option name 'eth0.2' option macaddr 'fc:ec:da:7b:30:f7'

config interface 'wan6' option ifname 'eth0.2' option proto 'dhcpv6' option reqaddress 'try' option reqprefix 'auto' option mtu '9014'

config switch option name 'switch0' option reset '1' option enable_vlan '1'

config switch_vlan option device 'switch0' option vlan '1' option ports '1 2 3 4 6t'

config switch_vlan option device 'switch0' option vlan '2' option ports '0 6t'

config interface 'WAN6_MAPE' option proto 'map' option offset '6' option ipaddr '153.252.240.0' option ip4prefixlen '20' option ip6prefixlen '38' option psidlen '6' option ealen '18' option encaplimit 'ignore' option tunlink 'wan6' option ip6prefix '2400:4150:7c00::' option peeraddr '2001:380:a120::9' option mtu '9014'

The mtu is set to support fast speeds, but not necessarily. I don't remember how I set it up anymore, but I remember getting disconnected every few minutes. I don't know if it's because I used a virtual server or my settings are invalid. I did have connection however.

fakemanhk commented 1 year ago

ISP definitely assumes I have the proper equipment and provide their NTT router anyway that is way too basic, can't even add static routes... that's why I'm trying to get rid of it.

So now I noticed the setting in OpenWrt WAN6 interface, from the drop down list you should probably choose "disable" to stop it from requesting address, and it will go straight to get the prefix from CPE only

Screenshot 2023-04-02 16 42 56

alexisfrjp commented 1 year ago

Thanks! I was able to have it working following a youtube video. I didn't need to have any hard coded prefix or values in the config files, it just worked. The WAN didn't need to have an IP address (it doesn't do NAT anyway).

Thanks all!

Softbank deserves to go bankrupt if they support proprietary protocols.

fakemanhk commented 1 year ago

Thanks! I was able to have it working following a youtube video. I didn't need to have any hard coded prefix or values in the config files, it just worked. The WAN didn't need to have an IP address (it doesn't do NAT anyway).

Thanks all!

Softbank deserves to go bankrupt if they support proprietary protocols.

I saw that you have /56 prefix assigned by ISP, actually this is a good sign that you have much less trouble on IPv6 setup because as what I stated in "problem" part is the "/64 prefix" which causes headache. But MAP-E of course is another big trouble.

SoftBank technically is not using proprietary protocol, it's just a kind of faded out implementation and keep using it as is, I know that someone had written an add-on script for OpenWrt 18.x to use it, just unsure if it still works now :p

There will be upcoming 23.x release, I hope this MAP-E fix survives that update...

alexisfrjp commented 1 year ago

I think that's the least acceptable for a 10G connexion. Don't worry, only OpenWrt changes, not the map-e protocol. If needed we will change the script ;) the joy of open-source.

fakemanhk commented 1 year ago

Don't worry, only OpenWrt changes, not the map-e protocol. If needed we will change the script ;) the joy of open-source.

This is my original intention to write this thing, I know things can be improved but I might not have all the knowledge/time into it, I'm glad that I had made a good start and now achieved more observable improvements.

For your case I will update my page again to indicate the difference to others so that they won't worry about the WAN6 assignment.

alexisfrjp commented 1 year ago

So was I but I found you first ;) thanks! And actually we should push the updated script to the OpenWrt repo.

fakemanhk commented 1 year ago

Currently I do not have enough information about the MAP-E/MAP-T implementation in other countries, from my previous search I saw some ISPs in EU has MAP-E/MAP-T as well, but I don't know if they do the same thing so I am hesitating on pushing this to official repo. If we can find some users there to test it would be great.

alexisfrjp commented 1 year ago

We still can add a special interface type for Japan if the implementation changes depending on the country...

cre8ivejp commented 9 months ago

Thanks! I was able to have it working following a youtube video. I didn't need to have any hard coded prefix or values in the config files, it just worked. The WAN didn't need to have an IP address (it doesn't do NAT anyway).

Thanks all!

Softbank deserves to go bankrupt if they support proprietary protocols.

@alexisfrjp, hi.

Is it possible for you to share the YouTube video? I also have the /56 ipv6 prefix, which only shows the IPV6-PD in the WAN6. You mentioned that the WAN doesn't need to get the IP address, and it worked. Did you configure everything as described in the README? If you could share the video or your settings, I would greatly appreciate any help.

I'm using the 10G V6 Plus plan from En Hikari (enひかり). Router NTT XG-100NE. OpenWRT 23.05.

Update: My lan interface didn't get the IPV6 address when the IPV6-DP was shown.

alexisfrjp commented 9 months ago

I spent time reading and trying. From my history, here are the 2 youtube videos I've watched at that time. I believe they helped me understanding IPv6 with openwrt.

As for the config file, I can't find it anymore (in the end we use the existing NTT router with the special page for port forwarding).

Hope it helps! Good luck!

For reference, here are the links I stored for the future (can be relevant or not)

cre8ivejp commented 9 months ago

I spent time reading and trying. From my history, here are the 2 youtube videos I've watched at that time. I believe they helped me understanding IPv6 with openwrt.

As for the config file, I can't find it anymore (in the end we use the existing NTT router with the special page for port forwarding).

Hope it helps! Good luck!

For reference, here are the links I stored for the future (can be relevant or not)

Thank you so much!

His videos are the best. I have been watching it to configure the VLANs and the Firewall. One of the reasons that I wanted to switch to OpenWRT is the port forwarding because the NTT router doesn't support it. I didn't know about that special page. Where did you find it? Is there any website talking about it?

alexisfrjp commented 9 months ago

It must be written in one of the links or github: http://192.168.123.1/t/ and oviously, change the IP.

Then follow: image

image

It'll give you the list of ports you can use when you setup a port forwarding.

cre8ivejp commented 9 months ago

Awesome! Thank you!

cre8ivejp commented 9 months ago

Mine is not showing the option. It says 1 block though. But you can't click on it. I'm using the latest firmware version 04.00.0002. I will take a look deeper after work.

Screenshot 2024-01-22 at 11 38 11 AM

alexisfrjp commented 9 months ago

You can't click on it? here is the link http://192.168.123.1/fj/com.ntt.mape/mape/index.html

cre8ivejp commented 9 months ago

@alexisfrjp, thanks for sharing the link. I tried to access it while logged in, but it says the page doesn't exist, 404. So I gave up.

But, after watching the videos you suggested, everything became clear, and I could make it work using the correct settings for my case. Once again, thank you so much!

alexisfrjp commented 9 months ago

Too bad, they might have blocked it for newer versions... Good to know!

fakemanhk commented 8 months ago

Too bad, they might have blocked it for newer version... Good to know!

I'm not surprised, just like the SO-NET one, initially you have some way to hack into it to enable bridge mode to use your own router, then they pushed new firmware which closed the loophole.