Hi again..
Hmm, I solved it by removing -i flag stuff.. then it worked just fine.
But I don't quite get it... what's the interface flag good for anyway?
I know you can use it wildcards, specify netmasks and use it on interfaces that
aren't up all the time, ie. ppp0.
Over that, is there any real benefit by using it? In what cases is it being
used?
Rickard �berg <[EMAIL PROTECTED]>
On 14-Oct-99 Axalon Bloodstone wrote:
>> Hi.
>>
>> I didn't know where to ask this and this isn't perhaps the right place, but I
>> figured I might ask anyway.
>> I have some problems using ipchains with the interface flag, it just refuses
>> to work as I want it to work... maybe I've done something really wrong but
>> I don't know.
>>
>> I want to DENY... works just fine :)
>> # Default policy DENY for input
>> ipchains -P input DENY
>>
>> This rule works as it should... I can ping eth0 and all traffic passes by.
>> # Accept ALL connections on eth0
>> ipchains -A input -j ACCEPT -i eth0 -s 0.0.0.0/0 -d 192.168.50.43/32
>>
>> But this one doesn't doesn't work... I can't ping eth1 and no traffic goes
>> by.
>> # Accept ALL connections from our own network on eth1
>> ipchains -A input -j ACCEPT -i eth1 -s 192.168.50.0/24 -d 192.168.50.65=
>>
>> Does anyone have any ideas... shouldn't I be able to ping eth1 from my own
>> network with these rules, or?
>>
>> Thanks...
>
>
>output of 'ipchains -L -nvx' would be better
>
>--
>MandrakeSoft http://www.mandrakesoft.com/
> --Axalon
