Hi John, > The zone lan has settings > input accept > output accept > forward reject > masquerading yes > covered = lan > > What I want is for some lan computers to talk: > > 192.168.15.105 needs to connect to http://192.168.15.106:7001 > http://192.168.15.108:7001 http://192.168.15.104:7001 > and such. > > I think that needs a traffic rule. > Would that be under New forward rule: ? >
As I understood it, you want to exchange traffic between multiple computers in your LAN, right? Since all machines are in the same network and in the same firewall zone, they should be able to freely exchange traffic. You only need a forward rule, if you want to forward traffic to different networks/zones. > $ curl http://192.168.15.106/version > curl: (7) Failed connect to 192.168.15.106:80; Connection refused > core@cibocore05 ~ $ ping 192.168.15.106 > > ping works though... > > PING 192.168.15.106 (192.168.15.106) 56(84) bytes of data. > 64 bytes from 192.168.15.106: icmp_seq=1 ttl=64 time=0.107 ms cURL connects to port 80 by default, if you want it to connect to port 7001, you have to specify the port after the adress (adress:port): $ curl http://192.168.15.106:7001/version Are you sure that the host machines are not blocking the incoming traffic? Make sure the service is actually running and listening on 0.0.0.0:7001 or 192.168.15.106:7001. You can check that with the netstat command on one of the host machines: $ netstat -tpln I hope I could help you :) Regards, Jannis
signature.asc
Description: OpenPGP digital signature
_______________________________________________ openwrt-users mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
