On Thursday 07 June 2007 19:40, Tom Eastep wrote: > Tom Eastep wrote: > > Tom Eastep wrote: > >> Steven Jan Springl wrote: > >>> On Thursday 07 June 2007 15:47, Tom Eastep wrote: > >>>> Steven Jan Springl wrote: > >>>>> Tom > >>>>> > >>>>> Specifying the maclist option on a host file entry that defines a > >>>>> bport e.g. > >>>>> > >>>>> p1 eth1:10.1.1.0/24 maclist > >>>>> > >>>>> produces the following error: > >>>>> > >>>>> ERROR: Unable to determine the IP address(es) of eth1 > >>>> > >>>> Please test with r6479 (sorry that I don't have time to set up a test > >>>> case). > >>>> > >>>> -Tom > >>> > >>> Tom > >>> > >>> I have tested the maclist option when specified on a bridge in the > >>> interfaces file and on a bridge port when specified in the hosts file. > >>> Provided the bridge has an IP address, then it works. > >>> > >>> I have not been able to test it when the bridge (br0) does not have an > >>> IP address, as "shorewall start" produces the following error: > >>> > >>> ERROR: Unable to determine the IP address(es) of br0 > >> > >> I don't believe that configuration works with Shorewall-shell either - > >> have you tried it? > > > > Also, please try Shorewall-shell with the 'optional' option specified on > > the > > Make that '...please try Shorewall-perl...' > > -Tom Tom
The 'optional' option works. I will test the 'maclist' option and shorewall-shell and get back to you. Steven. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Shorewall-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-devel
