VLAN bug (was Re: [m0n0wall] setting VLAN)

Roberto Greiner <[email protected]>
Newsgroups gmane.comp.security.firewalls.m0n0wall
Message-ID <[email protected]>
Ok,

I´m now pretty sure I´ve hit on a bug with vlans on 1.3

I´ve downgraded the machine to version 1.235, then created the vlan via 
console. It worked immediately. The same procedure with 1.3 is not 
working. I´ve tried to set vlan both via Web interface and through 
console, and neither of them gets vlans working. What would be now the 
appropriate way to fill a bug report? Should I just send a mail to the 
development mail list?

One curiosity is that 1.235 indicated the name of the interfaces as rl0 
and rl1, while 1.3 is indicating re0 and re1. I guess that´s because 
they are using FreeBSD 4 and FreeBSD 6, respectively.

Tks,

Roberto Greiner


On 14/12/2009 11:19, Roberto Greiner wrote:
> I´ve made another test, installing a sniffer checking the output of 
> the box. To my surprise, despite the configurations I mentioned 
> (Creting the VLAN, assigning it tom the LAN interface, setting the LAN 
> IP address), the packets are coming out from the interface without the 
> 802.1q headers.
>
> Now, is it a bug (Monowall is not creating;using 802.1q), or did I 
> miss some step to force monowall to use the VLAN?
>
> Tks,
>
> Roberto
>
>
>
> On 14/12/2009 10:35, Roberto Greiner wrote:
>> It´s on the LAN interface, which by default has a 'permit any any' 
>> rule, which I didn´t change. In any case, just to be sure, I changed 
>> the default rule, removing the source address limitation (form 'LAN 
>> subnet' to 'any'), but still no results.
>>
>> Any ideas on somewhere else I could be missing something?
>>
>> Thanks,
>>
>> Roberto
>>
>> On 11/12/2009 19:23, Jewell, Michael wrote:
>>> Firewall rules?  No rules means default deny.
>>>
>>>> -----Original Message-----
>>>> From: Roberto Greiner [mailto:[email protected]]
>>>> Sent: Friday, December 11, 2009 2:58 PM
>>>> Cc: [email protected]
>>>> Subject: [m0n0wall] setting VLAN
>>>>
>>>> Hi,
>>>>
>>>> I'm struggling somewhat with something that should be easy.
>>>>
>>>> Inside a XenCitrix Box, I've set a virtual monowall 1.3. I would 
>>>> like to
>>>> set the LAN interface to work in a given VLAN (say vlan 10).
>>>>
>>>> To do that, in Interfaces(assign)/VLAN I've create the VLAN with id 
>>>> 10,
>>>> on the internal physical interface (re1 here. re0 is the WAN 
>>>> interface).
>>>>
>>>> Next, in Interfaces(assign)/VLAN I've set the LAN interface to be this
>>>> new VLAN.
>>>>
>>>> After reboot, I've set the IP address (172.16.0.2, for tests).
>>>>
>>>> Unfortunately, it did not work. Other virtual machines in the same
>>>> physical server do manage to acess this same vlan properly (Tested 
>>>> with
>>>> a Debian install). From the Monowall install, with icmp, I can't reach
>>>> other machines, and neither do other machines reach the server.
>>>>
>>>> Did I miss something? According to 
>>>> http://m0n0.ch/wall/hardware.php, re
>>>> interfaces do support vlans.
>>>>
>>>> Thank you for your help,
>>>>
>>>> Roberto Greiner
>>>>
>>>> -- 
>>>>     -----------------------------------------------------
>>>>                   Marcos Roberto Greiner
>>>>
>>>>      Os otimistas acham que estamos no melhor dos mundos
>>>>       Os pessimistas tem medo de que isto seja verdade
>>>>                                     James Branch Cabell
>>>>     -----------------------------------------------------
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [email protected]
>>>> For additional commands, e-mail: [email protected]
>>
>>
>
>


-- 
   -----------------------------------------------------
                 Marcos Roberto Greiner

    Os otimistas acham que estamos no melhor dos mundos
     Os pessimistas tem medo de que isto seja verdade
                                   James Branch Cabell
   -----------------------------------------------------
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.