-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ddns-scripts: Get 'l3 device' (for pppoe connection) for bind_network using curl #14431
Conversation
You should adjust the error log message as well, it still mentions |
provider ydns.io
wan config:
default behavior with curl: when PR is applied: So, we can see curl is used right interface pppoe-wan as bind interface with patch applied. |
If pppoe is used for wan access. script set 'eth1' as interface for curl call. The correct interface is however 'pppoe-wan'. The script uses 'network_get_physdev' function to get real device for bind_network but this is wrong. We need instead the l3_device of the the logical interface. In case if we don't use pppoe connection - 'l3_device' is equal to real device. This was reported by the github user `welderpb` with P/R: #14431 Signed-off-by: Florian Eckert <fe@dev.tdt.de>
If pppoe is used for wan access. script set 'eth1' as interface for curl call. The correct interface is however 'pppoe-wan'. The script uses 'network_get_physdev' function to get real device for bind_network but this is wrong. We need instead the l3_device of the the logical interface. In case if we don't use pppoe connection - 'l3_device' is equal to real device. This was reported by the github user `welderpb` with P/R: #14431 Signed-off-by: Florian Eckert <fe@dev.tdt.de> (cherry picked from commit 036079b)
If pppoe is used for wan access. script set 'eth1' as interface for curl call. The correct interface is however 'pppoe-wan'. The script uses 'network_get_physdev' function to get real device for bind_network but this is wrong. We need instead the l3_device of the the logical interface. In case if we don't use pppoe connection - 'l3_device' is equal to real device. This was reported by the github user `welderpb` with P/R: openwrt/packages#14431 Signed-off-by: Florian Eckert <fe@dev.tdt.de>
If pppoe is used for wan access. script set 'eth1' as interface for curl call. The correct interface is however 'pppoe-wan'. The script uses 'network_get_physdev' function to get real device for bind_network but this is wrong. We need instead the l3_device of the the logical interface. In case if we don't use pppoe connection - 'l3_device' is equal to real device. This was reported by the github user `welderpb` with P/R: openwrt/packages#14431 Signed-off-by: Florian Eckert <fe@dev.tdt.de>
If pppoe is used for wan access. script set 'eth1' as interface for curl call. The correct interface is however 'pppoe-wan'. The script uses 'network_get_physdev' function to get real device for bind_network but this is wrong. We need instead the l3_device of the the logical interface. In case if we don't use pppoe connection - 'l3_device' is equal to real device. This was reported by the github user `welderpb` with P/R: openwrt/packages#14431 Signed-off-by: Florian Eckert <fe@dev.tdt.de>
If pppoe is used for wan access. script set 'eth1' as interface for curl call. The correct interface is however 'pppoe-wan'. The script uses 'network_get_physdev' function to get real device for bind_network but this is wrong. We need instead the l3_device of the the logical interface. In case if we don't use pppoe connection - 'l3_device' is equal to real device. This was reported by the github user `welderpb` with P/R: openwrt/packages#14431 Signed-off-by: Florian Eckert <fe@dev.tdt.de>
If pppoe is used for wan access. script set 'eth1' as interface for curl call. The correct interface is however 'pppoe-wan'. The script uses 'network_get_physdev' function to get real device for bind_network but this is wrong. We need instead the l3_device of the the logical interface. In case if we don't use pppoe connection - 'l3_device' is equal to real device. This was reported by the github user `welderpb` with P/R: openwrt/packages#14431 Signed-off-by: Florian Eckert <fe@dev.tdt.de>
If pppoe is used for wan access. script set 'eth1' as interface for curl call. The correct interface is however 'pppoe-wan'. The script uses 'network_get_physdev' function to get real device for bind_network but this is wrong. We need instead the l3_device of the the logical interface. In case if we don't use pppoe connection - 'l3_device' is equal to real device. This was reported by the github user `welderpb` with P/R: openwrt/packages#14431 Signed-off-by: Florian Eckert <fe@dev.tdt.de>
If pppoe is used for wan access. script set 'eth1' as interface for curl call. The correct interface is however 'pppoe-wan'. The script uses 'network_get_physdev' function to get real device for bind_network but this is wrong. We need instead the l3_device of the the logical interface. In case if we don't use pppoe connection - 'l3_device' is equal to real device. This was reported by the github user `welderpb` with P/R: openwrt/packages#14431 Signed-off-by: Florian Eckert <fe@dev.tdt.de>
If pppoe is used for wan access. script set 'eth1' as interface for curl call. The correct interface is however 'pppoe-wan'. These scripts use 'network_get_physdev' function to get real device for bind_network but this is wrong. We need instead the l3_device of the the logical interface. In case if we don't use pppoe connection - 'l3_device' is equal to real device. Follow P/R: openwrt#14431 Signed-off-by: Coia Prant <coiaprant@gmail.com>
If pppoe is used for wan access. script set 'eth1' as interface for curl call. The correct interface is however 'pppoe-wan'. These scripts use 'network_get_physdev' function to get real device for bind_network but this is wrong. We need instead the l3_device of the the logical interface. In case if we don't use pppoe connection - 'l3_device' is equal to real device. Follow P/R: openwrt#14431 Signed-off-by: Coia Prant <coiaprant@gmail.com> Signed-off-by: Coia Prant <coiaprant@gmail.com>
If pppoe is used for wan access. script set 'eth1' as interface for curl call. The correct interface is however 'pppoe-wan'. These scripts use 'network_get_physdev' function to get real device for bind_network but this is wrong. We need instead the l3_device of the the logical interface. In case if we don't use pppoe connection - 'l3_device' is equal to real device. Follow P/R: openwrt#14431 Signed-off-by: Coia Prant <coiaprant@gmail.com>
Maintainer: none
Compile tested: mips_24kc
Run tested: mips_24kc, REVISION 'r15449-936220186d'
Description:
ddns is not working for ipv4, if pppoe is used for wan access. script set 'eth1'
as interface for curl in my case. The correct interface is 'pppoe-wan'.
script uses 'network_get_physdev' function to get real device for bind_network.. So this pull request change function to 'network_get_device'. In case if we don't use pppoe connection - 'l3 device' is equal to real device.
in my case:
root@OpenWrt:~# ifstatus wan
{
"up": true,
"pending": false,
"available": true,
"autostart": true,
"dynamic": false,
"uptime": 8914,
"l3_device": "pppoe-wan",
"proto": "pppoe",
"device": "eth1",
......
Signed-off-by: Pavel Bukhatkin welder_pb@bk.ru