Why should the access to these update servers be enabled dynamically? What is
the security policy behind it? Are the clients i.e mobile devices?
Either you trust the targed or you do not. Do you want to control the traffic?
Or do you want to be sure that the all clients get the same softwa
Hi
Am 05.03.2015 um 20:40 schrieb Northe, Juergen [tux-net]:
> Hi,
> what should be the reason to change the rules ? Time based ? On demand from
> "outside" ? Port knocking?I
Most communication on my firewall towards the net is disabled by
default. In order to update the software dynamically I
Hi,
what should be the reason to change the rules ? Time based ? On demand from
"outside" ? Port knocking?
JN
Am Do. 5. Mär. 2015 20:18 CET, Erich Titl schrieb:
> Hi
>
> Am 05.03.2015 um 17:01 schrieb n22e113:
> >
> >> I need to temporarily allow HTTP connections from my shorewall based
Am 05.03.2015 um 17:48 schrieb Jeff Delinck:
> Shorewall is just a front end to IPtables. It would be easy enough to
> just issue the iptables command to add that in temporarily.
>
> iptables -I net2fw -p tcp --dport 80 -j ACCEPT
It used to be fw2net :-(
now it is fw-net
What a shame to change t
Hi
Am 05.03.2015 um 17:01 schrieb n22e113:
>
>> I need to temporarily allow HTTP connections from my shorewall based
>> LEAF box, preferrably without having to touch the shorewall files and be
>> able to stop this functionality again.
>>
>> I looked a bit at the very extensive shorewall docs, but
Am 05.03.2015 um 17:08 schrieb kp kirchdoerfer:
> Am Donnerstag, 5. März 2015, 16:39:02 schrieb Erich Titl:
>> Hi Folks
>>
>> I need to temporarily allow HTTP connections from my shorewall based
>> LEAF box, preferrably without having to touch the shorewall files and be
>> able to stop this functio
Hi Jeff
Am 05.03.2015 um 17:48 schrieb Jeff Delinck:
> Shorewall is just a front end to IPtables. It would be easy enough to
> just issue the iptables command to add that in temporarily.
>
> iptables -I net2fw -p tcp --dport 80 -j ACCEPT
Of course, as long as shorewall keeps its naming scheme th
Shorewall is just a front end to IPtables. It would be easy enough to
just issue the iptables command to add that in temporarily.
iptables -I net2fw -p tcp --dport 80 -j ACCEPT
(or fw2net depending on the direction desired) Use
iptables -nL --line-numbers
to find your rule, Then use
iptables -
Am Donnerstag, 5. März 2015, 16:39:02 schrieb Erich Titl:
> Hi Folks
>
> I need to temporarily allow HTTP connections from my shorewall based
> LEAF box, preferrably without having to touch the shorewall files and be
> able to stop this functionality again.
>
> I looked a bit at the very extensiv
> I need to temporarily allow HTTP connections from my shorewall based
> LEAF box, preferrably without having to touch the shorewall files and be
> able to stop this functionality again.
>
> I looked a bit at the very extensive shorewall docs, but nothing
> immediately caught my eyes. It would be
Hi Folks
I need to temporarily allow HTTP connections from my shorewall based
LEAF box, preferrably without having to touch the shorewall files and be
able to stop this functionality again.
I looked a bit at the very extensive shorewall docs, but nothing
immediately caught my eyes. It would be ni
11 matches
Mail list logo
