RE: [pfSense Support] bridging WAN to LAN again - you neeed reboot pfsense system
I will a little bit laboring with bridge, and result is, that if in bridge mode you don`t be able access from one to other bridged interface, there helps a reboot pfsense system /cold reboot from menu pfsense/ Is it bug or normal??? Bob. -Original Message- From: jason [mailto:[EMAIL PROTECTED] Sent: Friday, September 16, 2005 3:29 PM To: support@pfsense.com Subject: [pfSense Support] bridging WAN to LAN again Hi, I am trying to setup a firewall in bridging mode as apposed to using nat basically, i want to: 1. Leave my severs on the LAN with their public facing Ips in the range 212.87.85.xxx 2. Configure the WAN to effectively filter/forward packets to the servers on the LAN, just basic port blocking stuff I've installed pfsense 0.84 and configured static ips on both the LAN & WAN and bridged the LAN > WAN >From the LAN I can see out across the WAN as I have this default rule >on the LAN Prot: Source: Port: Destination: Port: Gateway: Description * Lan NET * * * * Deafult Lan > any Problem is I cannot get into the LAN from the WAN side at all, no ping, http infact any protocol. I have the following rule on the WAN: Prot: Source: Port: Destination: Port: Gateway: Description * ** Lan NET * * Surley the above rule on the WAN side should let absolutley everything through? I have read on the mailing list serveral posts regarding bridging. I have only 2 interfaces in the dell server. Is the above scenario possible with just two interfaces, if so should I have an IP address/gateway assigned to the LAN? Or do I need 3 interfaces? My knowledge of FreeBSD/Linux is quite limited but I'm happy to send my XML config to any body who can help or point me in the right direction Jason Brown. New Media Director.Monochrome www.monochrome.co.uk - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- * www.inMail.sk - Vasa emailova adresa na cely zivot ZDARMA * www.EuropskaDomena.sk - bezplatna predregistracia domen .EU * www.php5.sk - novy freehosting s php5 a MySQL, forum o php5 -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.11.0/103 - Release Date: 15.9.2005 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.11.0/103 - Release Date: 15.9.2005 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] bridging WAN to LAN again - you neeed reboot pfsense system
First of all I have no idea what yoru saying. Second of all please do not start new conversations for the same posts. Thats what _REPLY_ is for! Scott On 9/16/05, Robo.K. <[EMAIL PROTECTED]> wrote: > I will a little bit laboring with bridge, and result is, that if in bridge > mode you don`t be able access from one to other bridged interface, there > helps a reboot pfsense system /cold reboot from menu pfsense/ > Is it bug or normal??? > > Bob. > > -Original Message- > From: jason [mailto:[EMAIL PROTECTED] > Sent: Friday, September 16, 2005 3:29 PM > To: support@pfsense.com > Subject: [pfSense Support] bridging WAN to LAN again > > Hi, > > I am trying to setup a firewall in bridging mode as apposed to using nat > basically, i want to: > > 1. Leave my severs on the LAN with their public facing Ips in the range > 212.87.85.xxx 2. Configure the WAN to effectively filter/forward packets to > the servers on the LAN, just basic port blocking stuff > > I've installed pfsense 0.84 and configured static ips on both the LAN & WAN > and bridged the LAN > WAN > > >From the LAN I can see out across the WAN as I have this default rule > >on > the LAN > > Prot: Source: Port: Destination: Port: Gateway: Description > * Lan NET * * * * Deafult Lan > any > > Problem is I cannot get into the LAN from the WAN side at all, no ping, http > infact any protocol. I have the following rule on the WAN: > > Prot: Source: Port: Destination: Port: Gateway: Description > * ** Lan NET * * > > Surley the above rule on the WAN side should let absolutley everything > through? I have read on the mailing list serveral posts regarding bridging. > I have only 2 interfaces in the dell server. Is the above scenario possible > with just two interfaces, if so should I have an IP address/gateway assigned > to the LAN? > > Or do I need 3 interfaces? My knowledge of FreeBSD/Linux is quite limited > but I'm happy to send my XML config to any body who can help or point me in > the right direction > > > Jason Brown. > New Media Director.Monochrome > www.monochrome.co.uk > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] For additional > commands, e-mail: [EMAIL PROTECTED] > > > > -- > * www.inMail.sk - Vasa emailova adresa na cely zivot ZDARMA > * www.EuropskaDomena.sk - bezplatna predregistracia domen .EU > * www.php5.sk - novy freehosting s php5 a MySQL, forum o php5 > > > -- > No virus found in this incoming message. > Checked by AVG Anti-Virus. > Version: 7.0.344 / Virus Database: 267.11.0/103 - Release Date: 15.9.2005 > > > -- > No virus found in this outgoing message. > Checked by AVG Anti-Virus. > Version: 7.0.344 / Virus Database: 267.11.0/103 - Release Date: 15.9.2005 > > > > - > 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]
Re: [pfSense Support] bridging WAN to LAN again - you neeed reboot pfsense system
On Fri, 16 Sep 2005 15:33:46 +0200 "Robo.K." <[EMAIL PROTECTED]> wrote: > I will a little bit laboring with bridge, and result is, that if in bridge > mode you don`t be able access from one to other bridged interface What do you mean by that? You send send traffic through the bridge ? >, there > helps a reboot pfsense system /cold reboot from menu pfsense/ > Is it bug or normal??? > > Bob. > > -Original Message- > From: jason [mailto:[EMAIL PROTECTED] > Sent: Friday, September 16, 2005 3:29 PM > To: support@pfsense.com > Subject: [pfSense Support] bridging WAN to LAN again > > Hi, > > I am trying to setup a firewall in bridging mode as apposed to using nat > basically, i want to: > > 1. Leave my severs on the LAN with their public facing Ips in the range > 212.87.85.xxx 2. Configure the WAN to effectively filter/forward packets to > the servers on the LAN, just basic port blocking stuff > > I've installed pfsense 0.84 and configured static ips on both the LAN & WAN > and bridged the LAN > WAN > > >From the LAN I can see out across the WAN as I have this default rule > >on > the LAN > > Prot: Source: Port: Destination: Port: Gateway: Description > * Lan NET * * * * Deafult Lan > any > > Problem is I cannot get into the LAN from the WAN side at all, no ping, http > infact any protocol. I have the following rule on the WAN: > > Prot: Source: Port: Destination: Port: Gateway: Description > * ** Lan NET * * > > Surley the above rule on the WAN side should let absolutley everything > through? I have read on the mailing list serveral posts regarding bridging. > I have only 2 interfaces in the dell server. Is the above scenario possible > with just two interfaces, if so should I have an IP address/gateway assigned > to the LAN? > > Or do I need 3 interfaces? My knowledge of FreeBSD/Linux is quite limited > but I'm happy to send my XML config to any body who can help or point me in > the right direction > > > Jason Brown. > New Media Director.Monochrome > www.monochrome.co.uk > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] For additional > commands, e-mail: [EMAIL PROTECTED] > > > > -- > * www.inMail.sk - Vasa emailova adresa na cely zivot ZDARMA > * www.EuropskaDomena.sk - bezplatna predregistracia domen .EU > * www.php5.sk - novy freehosting s php5 a MySQL, forum o php5 > > > -- > No virus found in this incoming message. > Checked by AVG Anti-Virus. > Version: 7.0.344 / Virus Database: 267.11.0/103 - Release Date: 15.9.2005 > > > -- > No virus found in this outgoing message. > Checked by AVG Anti-Virus. > Version: 7.0.344 / Virus Database: 267.11.0/103 - Release Date: 15.9.2005 > > > > - > 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]
