Although you could compile a kernel for your specific needs (always recommended, but not necessary), I think for your particular needs just using a module at boot time would be sufficient. Something you might consider however, if you do not specifically need something from Bering, I know that the Dachstein based LRP boxes are capable of doing this. I'm not trying to start a flame war, but I've seen this done more with help from Charles. Just a suggestion...
Joey -----Original Message----- From: Eric B Kiser [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 23, 2002 11:27 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: [Leaf-user] ip_masq_ipsec.o for bering damn... I have just been sitting here staring at my monitor while the reality of what I am trying to do has dawned on me. When Tom pointed me in the direction of the files ip_conntrack_ipsec.o and ip_nat_ipsec.o I began searching for them under the assumption that I would just load them like any other module. After reading your reply things suddenly came more into focus. If I understand this correctly, then what I am actually looking for is a patch that will make these options available for when I have to recompile the kernel. At which time, I can then select to either compile them as modules or to compile them directly into the kernel. Thanks Joey, for the offer of assistance. Any and all help would be graciously received. I am still a newbie here so if someone would be kind enough to either confirm or deny my assumptions about how to go about this I would appreciate it. Respectfully, Eric -----Original Message----- From: joey officer [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 23, 2002 10:05 PM To: Eric B Kiser Cc: [EMAIL PROTECTED] Subject: RE: [Leaf-user] ip_masq_ipsec.o for bering ahh.. I think I understand know.. so you need to have the packets passed through on the home machine so that you can make the connection to work. I understand now. There was another post earlier that mentioned the nameing difference for the Bering ipsec.o files. You might look there. I'm not familiar at all w/ Bering, but I'll be glad to assist you by looking as well, and if necessary, maybe I or someone else can compile this for you. joey At Tuesday, 23 April 2002, "Eric B Kiser" <[EMAIL PROTECTED]> wrote: >Joey, > >Thanks for the quick reply. Here is what I am looking at... > >[1] I have to use IPSec client software on an NT4.0 machine from inside my >network to make a connection to the company firewall/IPSec server to be able >to gain remote access into my company. Since we are unable to do both >"pass-through" and "termination" I am forced to set this box up to do >"pass-through" only. > >[2] I am planning on setting up a second box inside my network to act as an >IPSec server so that I can connect to my lab while on the road. > >I hope this helped to explain it a little better. > >Regards, >Eric > >-----Original Message----- >From: Joey Officer [mailto:[EMAIL PROTECTED]] >Sent: Tuesday, April 23, 2002 4:54 PM >To: Eric B Kiser; [EMAIL PROTECTED] >Subject: RE: [Leaf-user] ip_masq_ipsec.o for bering > >Are you sure that you need the ip_masq_ipsec.o file. I think that this is >only needed if you have an internal ipsec server. In my case I run the >ipsec server (I'm sure as does everyone else) on the actual gateway server / >leaf server... > >Joey > >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED]]On Behalf Of Eric B Kiser >Sent: Tuesday, April 23, 2002 3:27 PM >To: [EMAIL PROTECTED] >Subject: [Leaf-user] ip_masq_ipsec.o for bering > >Hello All, > >I need to be able to make an IPSec connection through my Bering 1.0-rc1 >firewall. If I understand correctly I will need the ip_masq_ipsec. o module >to be able to do this. I have been unable to find the ip_masq_ipsec. o for >Bering. I have already searched through all of the files in the modules >section online and did not come across it. Is it already compiled in to the >kernel or is it somewhere else or have I just missed it? > >Thanks in advance, > >Eric > >_______________________________________________ >Leaf-user mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/leaf-user > >_______________________________________________ >Leaf-user mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/leaf-user > _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
