|
On 11/12/2016 06:19 PM, deloptes wrote:
Ok, this confuses me a little. I thought the modem was 10..12? Nevertheless, it sounds like you have the ability to connect to something on the 10. network. Therefore, I would suspect the settings on the 10. machine that you are not able to communicate with. Also, the 192. machine could be blocking (on the input chain) all communications from 10. except from the specific ip address of the modem. One of the other respondents indicated that posting a (sanitized) copy of your ruleset would help, this is indeed the case.Joe wrote:On Sat, 12 Nov 2016 22:15:45 +0100 deloptes <deloptes@gmail.com> wrote: The firewall on the modem should not affect the communications between 192. and 10. from what I understand of your setup. You have a firewall machine with two NICs one on the 192. network and one on the 10. network. The modem is on the 10. network along with some other machines (presumably with a switch or router) and the firewall is acting as a bridge between the 192. and the 10.On the modem there is also firewall. I tried disableing it but it did not help. Again, posting the exact ruleset would be helpful.And you can bet there is restriction - basically it is pretty tight and is opened only what is needed to intranet and basically all to modem netThe SNAT should not be an issue, it can handle all protocols transparently, and ssh uses the same tcp protocol as http. If there are iptables restrictions on outgoing protocols, you need to find the rule permitting tcp/80 to be forwarded, copy it and replace 80 with 22. Once this is working, we can restrict the destination to the 10. network, as presumably any existing port 80 rule allows connection to anywhere and you may not want that for ssh.there is nothing regarding the output - no rules based on ports thanks |