haaber
September 26, 2020, 9:25pm
1
Hello. I set up a new 19.07.04 on my TP N600 (WDR3600). I want to use it behind my ISP router which produces a 192.168.1.X local network. But OpenWrt by default as well.
Surprisingly, wireless works out of the box, and is routed over the TP-Link WAN port to my ISP box. This message is written that way
Can someone me find my way, please? Thanks!
trendy
September 26, 2020, 9:30pm
2
Disconnect the N600 from the ISP router.
uci set network.lan.ipaddr='10.0.0.1'
uci commit network
service network restart
What is the output of netstat -lnp | grep dnsma ?
haaber
September 26, 2020, 9:39pm
3
I put myself in extra trouble. The web-interface refuses my pwd, and the ssh port blocks me as well. I am close to a re-install
Can I run these commands in failsafe as well? I simply tried!
netstat command give EMPTY output.
The "service network restart" yields in 3 times "Failed to connect to ubus" after reboot, I am on 10.0.01 and DHCP seems to work.
haaber
September 26, 2020, 10:08pm
4
OK, I got ssh working again via the re-working webinterface.
netstat -lnp | grep dnsma ?
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 1723/dnsmasq
tcp 0 0 10.0.0.1:53 0.0.0.0:* LISTEN 1723/dnsmasq
tcp 0 0 192.168.1.88:53 0.0.0.0:* LISTEN 1723/dnsmasq
tcp 0 0 ::1:53 :::* LISTEN 1723/dnsmasq
tcp 0 0 fe80::6666:b3ff:fe4f:f536:53 :::* LISTEN 1723/dnsmasq
tcp 0 0 fd7b:61c4:d60b::1:53 :::* LISTEN 1723/dnsmasq
tcp 0 0 fe80::6666:b3ff:fe4f:f536:53 :::* LISTEN 1723/dnsmasq
tcp 0 0 fe80::6666:b3ff:fe4f:f537:53 :::* LISTEN 1723/dnsmasq
tcp 0 0 fe80::6666:b3ff:fe4f:f536:53 :::* LISTEN 1723/dnsmasq
tcp 0 0 fe80::6666:b3ff:fe4f:f535:53 :::* LISTEN 1723/dnsmasq
udp 0 0 127.0.0.1:53 0.0.0.0:* 1723/dnsmasq
1723/dnsmasq
udp 0 0 10.0.0.1:53 0.0.0.0:* 1723/dnsmasq
udp 0 0 192.168.1.88:53 0.0.0.0:* 1723/dnsmasq
udp 0 0 0.0.0.0:67 0.0.0.0:* 1723/dnsmasq
udp 0 0 ::1:53 :::* 1723/dnsmasq
udp 0 0 fe80::6666:b3ff:fe4f:f536:53 :::* 1723/dnsmasq
udp 0 0 fd7b:61c4:d60b::1:53 :::* 1723/dnsmasq
udp 0 0 fe80::6666:b3ff:fe4f:f536:53 :::* 1723/dnsmasq
udp 0 0 fe80::6666:b3ff:fe4f:f537:53 :::* 1723/dnsmasq
udp 0 0 fe80::6666:b3ff:fe4f:f536:53 :::* 1723/dnsmasq
udp 0 0 fe80::6666:b3ff:fe4f:f535:53 :::* 1723/dnsmasq
trendy
September 26, 2020, 10:17pm
5
Looks like it is working fine and has got the new IP for the lan.
haaber
September 26, 2020, 10:27pm
6
YES, it does now. Thanks !!
I have another question (new-topic?): in the web-interface is writen
wan => REJECT input: reject looks strange to me (but I don't understand these rules yet)
Also I do not understand why there are not 3 zones: LAN, Wireless, WAN. Then
LAN could have full access (if you can plug a cable, you own the machine anyways)
Wireless should have only acces only to WAN
WAN should have only acces to LAN/Wireless after them opening a connection.
trendy
September 26, 2020, 10:34pm
7
Wan is not allowed to forward to any other zone. Also all incoming traffic from wan is rejected.
By default there are lan and wan zones. Should you need more, you must create them.
1 Like
haaber
September 26, 2020, 10:52pm
8
Thank you trendy. I think it is reasonably safe to bidge LAN and wireless, at least to get started. If I feel paranoid I can still split them
But my impression is that the Wireless was bridged to WAN instead of LAN -- that confused me.
1 Like
system
October 6, 2020, 10:52pm
9
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.
I'd like to change the OpenWrt network range to 192.178.1.X though (LAN and wireless), that way I better understand where I am when I see an IP address. How can I do that "by hand" after SSH access? Also, I have no DHCP server on LAN, which is weired. How can I switch that on, by hand? I tried to find in the docs, but there are just OVERWHELMING and I get lost.