please create a ticket for the original problem (creating more than one bridge 
on releng_1_2) so it doesn't get lost. thanks.

Holger

> -----Original Message-----
> From: Tom Müller-Kortkamp [mailto:[EMAIL PROTECTED] 
> Sent: Friday, October 19, 2007 11:37 AM
> To: [email protected]
> Subject: Re: [pfSense Support] Problem with indipendent 
> Bridges in 1.2RC
> 
> I found another bug with this setup:
> Disabled DMZ to just have sis0 and ath0 for LAN-Interfaces:
> DHCP is not working on ath0 when sis0 is LAN and ath0 is bridged.
> 
> When I enable ath0 as LAN interface dhcp works on WLAN (ath0) 
> but not on sis0.
> 
> In both cases there is just a rule missing to pass udp.68 to 
> 255.255.255.255:67.
> 161983 rule 56/0(match): block in on ath0: 0.0.0.0.68 >
> 255.255.255.255.67: BOOTP/DHCP, Request [|bootp] I think this 
> rule should be added automatical when bridging those Interfaces ...
> 
> Am 18.10.2007 um 18:05 schrieb Holger Bauer:
> 
> > From a quick discussion here on the hackathon this might be 
> something 
> > that we need to prohibit for 1.2. So we most likely will setup some 
> > sanity check that won't let you setup another bridge.
> > This seems to require code that is available in the headbranch and
> > 1.2 is too close to release to backport this now. Thanks 
> for reporting 
> > this.
> >
> > Holger
> >
> >> -----Original Message-----
> >> From: Tom Müller-Kortkamp [mailto:[EMAIL PROTECTED]
> >> Sent: Thursday, October 18, 2007 5:49 PM
> >> To: [email protected]
> >> Subject: [pfSense Support] Problem with indipendent 
> Bridges in 1.2RC
> >>
> >> hi,
> >>
> >> I have 4 Networkinterfaces 3xLan (sis0=LAN, sis1=WAN,
> >> sis2=DMZ) 1xWLAN (=ath0).
> >> I want to bridge LAN + WLAN as one
> >> and WAN and DMZ as another bridge.
> >>
> >> When i do this i get one bridge-interface with all other 
> interfaces 
> >> as Members:
> >>
> >> bridge0: 
> flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> >>          ether ee:71:ea:c4:8e:e8
> >>          priority 32768 hellotime 2 fwddelay 15 maxage 20
> >>          member: sis1 flags=7<LEARNING,DISCOVER,STP>
> >>                  port 3 priority 128 path cost 55 forwarding
> >>          member: sis2 flags=7<LEARNING,DISCOVER,STP>
> >>                  port 4 priority 128 path cost 55 disabled
> >>          member: sis0 flags=3<LEARNING,DISCOVER>
> >>          member: ath0 flags=3<LEARNING,DISCOVER>
> >>
> >> Fill bugreport or is this a known one?
> >>
> >>
> >> Tom Müller-Kortkamp
> >> --
> >> kommunity GmbH & Co.KG
> >> Goseriede 4, D-30159 Hannover
> >> ------------
> >> Phone +49 (0)5 11 - 80 72 58 - 0
> >> Fax +49 (0)5 11 - 80 72 58 - 10
> >> ------------
> >> Sitz der Gesellschaft: Hannover,
> >> Registergericht: Amtsgericht Hannover, Handelsregisternummer HRA 
> >> 26721
> >>
> >>
> >> Persönlich haftende Gesellschafterin:
> >> kommunity Verwaltungsgesellschaft mbH vertreten durch den 
> >> Geschäftsführer Tom Müller-Kortkamp Sitz der Gesellschaft: 
> Hannover,
> >> Registergericht: Amtsgericht Hannover, Registernummer HRB 60200
> >>
> >>
> >>
> >>
> >> 
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [EMAIL PROTECTED] For 
> >> additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >>
> >
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED] For 
> additional 
> > commands, e-mail: [EMAIL PROTECTED]
> >
> 
> --
> kommunity GmbH & Co.KG
> Goseriede 4, D-30159 Hannover
> ------------
> Phone +49 (0)5 11 - 80 72 58 - 0
> Fax +49 (0)5 11 - 80 72 58 - 10
> ------------
> Sitz der Gesellschaft: Hannover,
> Registergericht: Amtsgericht Hannover,
> Handelsregisternummer HRA 26721
> 
> 
> Persönlich haftende Gesellschafterin:
> kommunity Verwaltungsgesellschaft mbH
> vertreten durch den Geschäftsführer
> Tom Müller-Kortkamp
> Sitz der Gesellschaft: Hannover,
> Registergericht: Amtsgericht Hannover,
> Registernummer HRB 60200
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED] For 
> additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to