ipv6: support interface name for scope lookup 21/235621/2 accepted/tizen_6.0_unified_hotfix tizen_6.0_hotfix accepted/tizen/6.0/unified/20201030.110007 accepted/tizen/6.0/unified/hotfix/20201102.235050 accepted/tizen/6.0/unified/hotfix/20201103.051054 accepted/tizen/unified/20200609.153644 submit/tizen/20200608.091544 submit/tizen_6.0/20201029.205502 submit/tizen_6.0_hotfix/20201102.192902 submit/tizen_6.0_hotfix/20201103.115102 tizen_6.0.m2_release
authorSeonah Moon <seonah1.moon@samsung.com>
Mon, 8 Jun 2020 06:20:12 +0000 (15:20 +0900)
committerSeonah Moon <seonah1.moon@samsung.com>
Mon, 8 Jun 2020 06:23:08 +0000 (15:23 +0900)
commit740d9e290bc8e4698c4a004f6dcd4d43be4a863c
treea9a2fa1ad7828390a528d0a9a56739186df4a49e
parente2854e24cb93a17a2a55d14ef6305d17fadadc35
ipv6: support interface name for scope lookup

Currently for ipv6, we look up the scope assuming we were given an interface ip for
binding.  But with ipv4, we also support giving an interface name.

Check it against an interface name first and return that if valid.

https://github.com/warmcat/libwebsockets/commit/280584ff8f147832f008b299d0e32fd4273024db

Change-Id: I9bd36dd680a90dce88e8b58547d0922a4f311122
lib/core-net/network.c