Re: Re: vlan and iptables

darkstar <[email protected]>
Newsgroups gmane.linux.drivers.vlan
Message-ID <[email protected]>
[email protected] wrote:

> Same problem, I just upgrade to iptables 1.3.2.
>
> darkstar writes:
>
>> [email protected] wrote:
>>
>>> darkstar writes:
>>>
>>>> [email protected] wrote:
>>>>
>>>>> Why doesn't iptables works with vlans?
>>>>> iptables -t mangle -A FORWARD -i eth0 -o eth1.11 -j MARK --set-mark 4
>>>>> Gives me the error:
>>>>> host/network eth1.11 not found.
>>>>> I'm running kernel version 2.4.27. with iptables 1.2.9
>>>>> The eth1.11 exists works perfect.
>>>>> Seby,
>>>>
>>>>  
>>>>
>>>> May bi the problem is in iptables-version...
>>>
>>>
>>> And what version do you recomand me .?
>>>
>>>>
>>>> regards
>>>> _______________________________________________
>>>> Vlan mailing list
>>>> [email protected]
>>>> http://www.lanforge.com/mailman/listinfo/vlan
>>>
>>>  
>>>
>>>  
>>>
>>> ____________________________________________________________
>>> SC. FO Comunicatii SRL.
>>> Sebastian Ionita
>>> Administrator Sistem
>>> mobil: 0720 600016
>>> tel fix: 0264 450456
>>> _______________________________________________
>>> Vlan mailing list
>>> [email protected]
>>> http://www.lanforge.com/mailman/listinfo/vlan
>>>
>> hmm...
>> I am with
>> iptables v1.3.2
>> may be versions after 1.3.0 without patches are working...
>>    regards
>
Look at this:

 *  Most routines return pointers to static data that may change
 *  between calls to the same or other routines with a few exceptions:
 *  "host_to_addr", "parse_hostnetwork", and "parse_hostnetworkmask"
 *  return global static data.

Is this the only one rule in iptables chains, that corresponds with vlan?
Can you try to add a rule in other table and see what kind of message it 
will return?...
This is one of stupid problems.. and I cannot remember what is the 
reason for that...
but the problem is in your box...
Do you have another system with similar problems?

regards
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.