Skip to content
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.

Sign up for GitHub

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

Jump to bottom

SmoothWAN in Hyper-V: Only 1 WAN is working #103

Closed
ccmks opened this issue Feb 15, 2023 · 12 comments
Closed

SmoothWAN in Hyper-V: Only 1 WAN is working #103

ccmks opened this issue Feb 15, 2023 · 12 comments

Comments

@ccmks
Copy link

ccmks commented Feb 15, 2023

1WAN
Hello,

I do noticed that only 1 WAN that is working at a time, instead of 3 of them.

How can I make all of them active? All of them have internet connection, but won't show as active in speedify

Thank you
@TalalMash
Copy link
Member

Im guessing this is hyper v from the other issue?
Can you post the configuration?

@ccmks
Copy link
Author

ccmks commented Feb 15, 2023 via email

@TalalMash TalalMash changed the title Only 1 WAN is working SmoothWAN in Hyper-V: Only 1 WAN is working Feb 15, 2023
@TalalMash
Copy link
Member

Hyper-V settings , network virtual switch manager screenshot, disable protected networking, hardware topology, post your /etc/config/network/ and ip route results here.

@ccmks
Copy link
Author

ccmks commented Feb 15, 2023

Here is the IP route
0.0.0.0/1 dev connectify0 scope link
default via 10.50.53.1 dev eth3 proto static metric 10
10.50.52.0/24 dev eth2 proto static scope link metric 10
10.50.53.0/24 dev eth3 proto static scope link metric 10
10.202.0.0/24 dev connectify0 proto kernel scope link src 10.202.0.2
123.123.123.123 via 10.50.53.1 dev eth3
128.0.0.0/1 dev connectify0 scope link
172.17.17.0/24 dev br-lan proto kernel scope link src 172.17.17.2
192.168.123.0/24 dev eth1 proto static scope link metric 10

Here is the /etc/config/network

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

config globals 'globals'
option ula_prefix 'fd06:cdd8:611c::/48'

config device
option name 'br-lan'
option type 'bridge'
list ports 'eth0'

config interface 'lan'
option device 'br-lan'
option proto 'static'
option netmask '255.255.255.0'
option ip6assign '60'
option ipaddr '172.17.17.2'

config interface 'wan'
option device 'eth1'
option proto 'dhcp'

config interface 'wan6'
option device 'eth1'
option proto 'dhcpv6'

config interface 'AutoUSBeth1'
option device 'eth1'
option proto 'static'
option ipaddr '192.168.123.29'
option netmask '255.255.255.0'
option gateway '192.168.123.1'
option metric '10'

config interface 'AutoUSBeth2'
option device 'eth2'
option proto 'static'
option netmask '255.255.255.0'
option gateway '10.50.52.1'
option ipaddr '10.50.52.129'
option metric '10'

config interface 'AutoUSBeth3'
option device 'eth3'
option proto 'static'
option netmask '255.255.255.0'
option gateway '10.50.53.1'
option ipaddr '10.50.53.129'
option metric '10'

config interface 'AutoUSB0'
option proto 'dhcp'
option device 'usb0'
option metric '40'

config interface 'AutoUSB1'
option proto 'dhcp'
option device 'usb1'
option metric '41'

config interface 'AutoUSB2'
option proto 'dhcp'
option device 'usb2'
option metric '42'

config interface 'AutoUSB3'
option proto 'dhcp'
option device 'usb3'
option metric '43'

config interface 'Speedify'
option proto 'none'
option device 'connectify0'

config device
option name 'eth2'

@TalalMash
Copy link
Member

TalalMash commented Feb 15, 2023 •
edited

Ah, you should set the metric to be different for each WAN, then the ip route command should show multiple default entries (as per WAN). The note in LuCI configuration page is dedicated to Wireless setup, not generally. (e.g 10 metric for new station)

These are usually predefined and configured, it seems like you have changed them from defaults. (by default its 10,20,30,40 etc)
You may also have to add the broadcast IP per WAN in OpenWRT, else it won't create default routes.

@ccmks
Copy link
Author

ccmks commented Feb 15, 2023

image
I am following the instruction note here, therefore all WAN will have same metric

@ccmks
Copy link
Author

ccmks commented Feb 15, 2023

I have followed your instruction above and I am getting only WAN1 and WAN3 connected, the WAN2 is not working

image

IP route

0.0.0.0/1 dev connectify0 scope link
default via 192.168.123.1 dev eth1 proto static metric 11
default via 10.50.52.1 dev eth2 proto static metric 12
default via 10.50.53.1 dev eth3 proto static metric 13
10.50.52.0/24 dev eth2 proto static scope link metric 12
10.50.53.0/24 dev eth3 proto static scope link metric 13
10.202.0.0/24 dev connectify0 proto kernel scope link src 10.202.0.2
123.123.123.123 via 192.168.123.1 dev eth1
128.0.0.0/1 dev connectify0 scope link
172.17.17.0/24 dev br-lan proto kernel scope link src 172.17.17.2
192.168.123.0/24 dev eth1 proto static scope link metric 11

/etc/config/network
config interface 'loopback'
option device 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'

config globals 'globals'
option ula_prefix 'fd06:cdd8:611c::/48'

config device
option name 'br-lan'
option type 'bridge'
list ports 'eth0'

config interface 'lan'
option device 'br-lan'
option proto 'static'
option netmask '255.255.255.0'
option ip6assign '60'
option ipaddr '172.17.17.2'

config interface 'wan'
option device 'eth1'
option proto 'dhcp'

config interface 'wan6'
option device 'eth1'
option proto 'dhcpv6'

config interface 'AutoUSBeth1'
option device 'eth1'
option proto 'static'
option ipaddr '192.168.123.29'
option netmask '255.255.255.0'
option gateway '192.168.123.1'
option broadcast '192.168.123.255'
option metric '11'

config interface 'AutoUSBeth2'
option device 'eth2'
option proto 'static'
option netmask '255.255.255.0'
option gateway '10.50.52.1'
option ipaddr '10.50.52.129'
option broadcast '10.50.52.255'
option metric '12'

config interface 'AutoUSBeth3'
option device 'eth3'
option proto 'static'
option netmask '255.255.255.0'
option gateway '10.50.53.1'
option ipaddr '10.50.53.129'
option broadcast '10.50.53.255'
option metric '13'

config interface 'AutoUSB0'
option proto 'dhcp'
option device 'usb0'
option metric '40'

config interface 'AutoUSB1'
option proto 'dhcp'
option device 'usb1'
option metric '41'

config interface 'AutoUSB2'
option proto 'dhcp'
option device 'usb2'
option metric '42'

config interface 'AutoUSB3'
option proto 'dhcp'
option device 'usb3'
option metric '43'

config interface 'Speedify'
option proto 'none'
option device 'connectify0'

config device
option name 'eth2'

@TalalMash
Copy link
Member

in terminal ping 10.50.52.1 to see if it's a connectivity issue

@ccmks
Copy link
Author

ccmks commented Feb 15, 2023

I can ping to it, not problem

image

@TalalMash
Copy link
Member

do ping -I eth2 1.1.1.1

@ccmks
Copy link
Author

ccmks commented Feb 15, 2023

I tried and no response. I just confirmed that WAN2 doesn't have active internet connection.

I will fix it.

Thank you for your support and great project!

@TalalMash
Copy link
Member

Great! will add the broadcast note in Wiki soon for static IP setups.
Feel free to reopen if more issues persist.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ccmks @TalalMash