IpNat and 3 NIC
Hello, I have my FreeBSD 5.4 box with 3 NIC : Xl0 LAN with network 10.0.0.0/8 and 192.168.0.0/30 VR0 Wan 84.96.23.106/32 VR1 LAN with network 192.168.0.32/27 and 192.168.0.96/27 I use IPNAT and Ip filter. I'm doing NAT from Xl0 to Vr0, it's working fine I'm trying to do the same thing with vr1 to Vr0 but it's seems that traffic coming from vr1 are not translated. Is there a interface limitation with IPNAT ? Is there a way to do translation from both NIC ? Here is my ipnat.conf : map vr0 10.0.0.0/8 - 84.96.23.106/32 proxy port ftp ftp/tcp map vr0 10.0.0.0/8 - 84.96.23.106/32 portmap tcp/udp 2:6 map vr0 10.0.0.0/8 - 84.96.23.106/32 map vr0 192.168.0.0/30 - 84.96.23.106/32 portmap tcp/udp auto map vr1 192.168.0.32/27 - 84.96.23.106/32 portmap tcp/udp auto map vr1 192.168.0.32/27 - 84.96.23.106/32 map vr1 192.168.0.96/27 - 84.96.23.106/32 portmap tcp/udp auto map vr1 192.168.0.96/27 - 84.96.23.106/32 rdr xl0 0.0.0.0/0 port 80 - 10.0.0.254 port 3128 tcp rdr vr1 192.168.0.32/27 port 80 - 10.0.0.254 port 3128 tcp rdr vr1 192.168.0.96/27 port 80 - 10.0.0.254 port 3128 tcp Thanks for help. Cedric ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: IpNat and 3 NIC
Thanks you, it's working ! But why using vr0 instead of vr1 for map instruction ? Network 192.168.0.32/27 is attach to vr1 not vr0 ... Is it an IPNat mystery or have you an answer ? -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de fbsd_user Envoyé : jeudi 12 janvier 2006 16:43 À : cedric Gross; freebsd-questions@freebsd.org Objet : RE: IpNat and 3 NIC You have ipnat statements wrong. should be liked this map vr0 10.0.0.0/8 - 0.32 proxy port ftp ftp/tcp map vr0 10.0.0.0/8 - 0.32 portmap tcp/udp 2:6 map vr0 10.0.0.0/8 - 0.32 map vr0 192.168.0.0/30 - 0.32 portmap tcp/udp auto map vr0 192.168.0.32/27 - 0.32 portmap tcp/udp auto map vr0 192.168.0.32/27 - 0.32 map vr0 192.168.0.96/27 - 0.32 portmap tcp/udp auto map vr0 192.168.0.96/27 - 0.32 rdr xl0 0.0.0.0/0 port 80 - 10.0.0.254 port 3128 tcp rdr vr1 192.168.0.32/27 port 80 - 10.0.0.254 port 3128 tcp rdr vr1 192.168.0.96/27 port 80 - 10.0.0.254 port 3128 tcp Note map vr1 has been changed to vr0 If your public IP 84.96.23.106 is not dedicated to you by your ISP, then you should not be hard coding it in your IPnat rules. Read the Freebsd ipfilter documentation in the handbook for details. 0.32 = The IP address/netmask assigned by your ISP. The special keyword 0.32 tells ipnat to get the current public IP address of the interface specified on this statement and substitute it for the 0.32 keyword. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of cedric Gross Sent: Thursday, January 12, 2006 9:58 AM To: freebsd-questions@freebsd.org Subject: IpNat and 3 NIC Hello, I have my FreeBSD 5.4 box with 3 NIC : Xl0 LAN with network 10.0.0.0/8 and 192.168.0.0/30 VR0 Wan 84.96.23.106/32 VR1 LAN with network 192.168.0.32/27 and 192.168.0.96/27 I use IPNAT and Ip filter. I'm doing NAT from Xl0 to Vr0, it's working fine I'm trying to do the same thing with vr1 to Vr0 but it's seems that traffic coming from vr1 are not translated. Is there a interface limitation with IPNAT ? Is there a way to do translation from both NIC ? Here is my ipnat.conf : map vr0 10.0.0.0/8 - 84.96.23.106/32 proxy port ftp ftp/tcp map vr0 10.0.0.0/8 - 84.96.23.106/32 portmap tcp/udp 2:6 map vr0 10.0.0.0/8 - 84.96.23.106/32 map vr0 192.168.0.0/30 - 84.96.23.106/32 portmap tcp/udp auto map vr1 192.168.0.32/27 - 84.96.23.106/32 portmap tcp/udp auto map vr1 192.168.0.32/27 - 84.96.23.106/32 map vr1 192.168.0.96/27 - 84.96.23.106/32 portmap tcp/udp auto map vr1 192.168.0.96/27 - 84.96.23.106/32 rdr xl0 0.0.0.0/0 port 80 - 10.0.0.254 port 3128 tcp rdr vr1 192.168.0.32/27 port 80 - 10.0.0.254 port 3128 tcp rdr vr1 192.168.0.96/27 port 80 - 10.0.0.254 port 3128 tcp Thanks for help. Cedric ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Updating 5.2.1 Release #
Matthew Seaman On Thu, Jul 29, 2004 at 09:37:35AM -0500, Puna Tannehill wrote: Scott wrote: uname -a shows: FreeBSD 5.2.1-Release #0: I was expecting the release (version, revision# ?) number to be greater than #0. I think I've seen where the latest revision is #9 or so? Do I need to tell it to get the latest revision somehow? Do I need to change the cvs tag= to something else to get up to date? I thought the #number indicated the number of times the server has been rebooted based upon the last time the kernel was recompiled. Being that it is #0, it was your first book. Reboot the machine and check the number again. I believe that the #n is the number of times the kernel has been re-compiled since the last time the system was installed. It's probably not a very interesting datum except to kernel hackers who need to do a lot of recompiling. What the original poster was thinking of is the patchlevel that gets incremented every time a new security (or nowadays: errata) patch is applied to any of the -RELEASE branches. That modifies the OS name (ie. the output of 'uname -r'), so instead of: So what is the diff between uname -r and uname -v, which produce for me : Uname -r : 5.2.1-RELEASE Uname -v : FreeBSD 5.2.1-RELEASE #0: Mon Jun 14 14:52:08 CEST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CNV_TOTAL Extract from man page : -r Write the current release level of the operating system -v Write the version level of this release of the operating system So that's mean that there are several Release ( as relesase level) and inside each release level there are several version level, am'I understanding well ? Cedric. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Random Freeze
Thanks to all for answer. Effectively I use memtest86 to find a Bad module in my box, so I remove it and for the moment by box is running well. -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Robert Storey Envoyé : jeudi 22 juillet 2004 16:18 À : [EMAIL PROTECTED] Objet : Re: Random Freeze On Wed, 21 Jul 2004 15:41:56 +0200 Cedric GROSS [EMAIL PROTECTED] wrote: Hello, I'm running an AMD Duron 700 Box with freeBSD 5.2.1 - RELEASE, and sometimes the system freeze so I must reboot. I haven't anything in log. So, What could be the problem ? How could I obtain some clue of the problem (debug flag, something like that..) ? I had this and it turned out to be dust in the slots for add-on cards. Removing the cards, cleaning the terminals and blowing out the dust from the slots, fixed the problem. Overheating will produce the same symptoms. If you're in the northern hemisphere, this is time of year when you have to worry about this. Blowing out dust (pay attention to the cpu fan and power supply fan, which are dust traps) can make the difference. Of course, your problem may have nothing to do with the above. good luck, Robert ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Random Freeze
Hello, I'm running an AMD Duron 700 Box with freeBSD 5.2.1 - RELEASE, and sometimes the system freeze so I must reboot. I haven't anything in log. So, What could be the problem ? How could I obtain some clue of the problem (debug flag, something like that..) ? Thanks for help. Cedric ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
