You could Direct Message me here.
But why?
I am able to generate and use credentials successfully from wgcf.
root@OpenWrt:~# curl --interface cf https://ipinfo.io
{
"ip": "104.28.240.82",
"city": "Dhaka",
"region": "Dhaka",
"country": "BD",
"loc": "23.7104,90.4074",
"org": "AS13335 Cloudflare, Inc.",
"postal": "1000",
"timezone": "Asia/Dhaka",
"readme": "https://ipinfo.io/missingauth"
Works now but doesn't route to my phone
(That is not a direct/private message)
Btw had to fix this connection error I tried manual DNS 1.1.1.1 then after some tries it works accordingly
It works now but doesn't route to my phone help me for this
Not sure what that means. I thought this was setup on the OpenWrt.
I want it to route this warp vpn through all the devices connected to the router
Try: https://cloudflare.com/cdn-cgi/trace
I do this:
# in /etc/config/network
config route
option interface 'foo_warp1'
option target '0.0.0.0/0'
option table '1'
config rule
option src '192.168.1.0/24'
option dest '0.0.0.0/0'
option priority '1' #order in IP_rules
option lookup '1' #table_assigned
Some use a PBR package.
(If you want to name the table, it requires extra config.)
Reconfig your wg as this steps:
Duh I gained the necessary configurations and got my wireguard working but I have a task remaining that is I want all the connected devices to my router to be routed via the wireguard vpn on my router
Your interface name is: cf
NOT cf_foo1
To route all the network:
uci del network.cf.allowed_ips
uci add_list network.cf.allowed_ips='0.0.0.0/0'
uci set network.cf.route_allowed_ips='1'
uci commit
1 Like
Follow there: (forward to wg zone)
1 Like
This isn't gonna be easy I will try though
What do your firewall settings look like?
For direct routing through cf from a specific interface a rule like this could work.
config route
option table '10'
option target '0.0.0.0/0'
option interface 'cf'
config rule
option in 'lan'
option lookup '10'
This is only really useful if you have specific routing requirements. My use-case was routing a specific wireless network via WARP without option route_allowed_ips '1' on the wireguard interface.
Your requirement comes across as straightforward routing for all traffic to WARP as the WAN
So you really don't need to resort to adding tables and routes.
You only need this entry in your firewall (fw3)
config zone
option name 'wan'
list network 'wan'
list network 'wan6'
list network 'cf'
option input 'REJECT'
option output 'ACCEPT'
option forward 'REJECT'
option masq '1'
option mtu_fix '1'
config forwarding
option src 'lan'
option dest 'wan'
1 Like