Re: NATD question...
Hi, >>> On Mon, 28 Jul 2003 12:17:24 -0400, "Paul A. Howes" <[EMAIL PROTECTED]> said: > All, > > I am trying to redirect a port on my FreeBSD 5.1-based firewall to an > internal machine. My natd configuration contains a directive: > > redirect-port 192.168.x.x:http > > I performed a "kill -HUP" on the natd process, but it doesn't work. I can > verify that the internal Web server is functional, and accessible to the > internal network. I even added ipfw rules to allow for traffic on port > , but still nothing. > > Am I missing something obvious here? Thanks! That's a wrong directive. Use ``redirect_port''. ^ -- rushani ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NATD question...
>>> On Mon, 28 Jul 2003 18:54:17 -0400, "Paul A. Howes" <[EMAIL PROTECTED]> said: > I typed that wrong in the e-mail, but not in my configuration file. > > redirect_port 192.168.x.x:http > > The question still stands: Why didn't this work? Strange. It may take some minutes to reflect your natd config file. If you want to take effect of your change immediately, kill -TERM natd process and then perform "/sbin/natd -f ". -- rushani ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problem installing 4.7/4.8, etc
Hi, >>> On Wed, 25 Jun 2003 09:49:50 -0400, Thomas Dickey <[EMAIL PROTECTED]> said: > I'm setting up a new machine, and none of the current *BSD's install on it. > Linux works. The *BSD's choke during the device identification. Perhaps > someone on this list knows why. Attaching a copy of dmesg output from one > of the Linux's I installed. The *BSD's appear to be missing an interrupt > in the IDE/PCI bus hardware (about which I know little ;-) >From your attached dmesg, > PCI: Using IRQ router SIS [1039/0008] at 00:02.0 [...] > SIS5513: IDE controller on PCI bus 00 dev 15 > PCI: Found IRQ 5 for device 00:02.5 > SIS5513: chipset revision 0 > SIS5513: not 100% native mode: will probe irqs later > SiS5513 > ide0: BM-DMA at 0x4000-0x4007, BIOS settings: hda:DMA, hdb:DMA > ide1: BM-DMA at 0x4008-0x400f, BIOS settings: hdc:DMA, hdd:pio My first machine, that is about 8 years old model, has SiS 5513. It works here since I installed FreeBSD snapshot as of the end of 2003/05. atapci0: port 0xfe80-0xfe8f,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at device 1.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: simplex device, DMA on primary only ata1: at 0x170 irq 15 on atapci0 SiS 5513 supports WDMA2, However, some HDDs might freeze when they detected by kernel. I *have to* type in following instruction set hw.ata.ata_dma=0 at loader prompt (or put equivalent into /boot/loader.conf) in order to disable DMA and use PIO transfer for HDDs. Recent FreeBSD 4.x would fail to boot because it does not have src/sys/dev/ata/ata-chip.c, I think. Soren, My understanding is OK, isn't it? -- rushani ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NEWCARD support for Linksys Ethernet broken?
Hi,
>>> On Thu, 18 Jul 2002 02:06:15 -0600 (MDT), "M. Warner Losh" <[EMAIL PROTECTED]> said:
> In message: <[EMAIL PROTECTED]>
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> : Just upgraded my laptop to the latest -CURRENT ... everything boots fine,
> : but my ethernet no longer exists (it worked great on my June 6th kernel)
> : ...
>
> Used to work for me, but something seems to have busted it in recent
> versions of the kernel. So NEWCARD appears to be broken for ata, sio
> and ed. Wonderful. These all used to work at one point in the past.
Unfortunately, ed driver does not work here (OLDCARD), too. I cvsup'ed
and built world & kernel yesterday, and installed kernel. it worked
fine on my July 11th kernel.
I use Melco LPC3-TX and now have following error messages;
Jul 19 00:34:44 hoge pccardd[1363]: Card "MELCO"("LPC3-TX") [] [] matched
"MELCO"("LPC3-TX") [(null)] [(null)]
Jul 19 00:34:44 hoge pccardd[1363]: Ether=00:40:26:xx:xx:xx
Jul 19 00:34:49 hoge pccardd[1363]: driver allocation failed for MELCO(LPC3-TX):
Inappropriate ioctl for device
-- rushani
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: NEWCARD support for Linksys Ethernet broken?
>>> On Thu, 18 Jul 2002 09:50:54 -0600 (MDT), "M. Warner Losh" <[EMAIL PROTECTED]> said: > In message: <[EMAIL PROTECTED]> > Hideyuki KURASHINA <[EMAIL PROTECTED]> writes: > : Jul 19 00:34:49 hoge pccardd[1363]: driver allocation failed for MELCO(LPC3-TX): >Inappropriate ioctl for device > > recompile pccardd. The inappropriate ioctl for device is due to a > slight mismatch between kernel and pccardd. I recerntly change the > ioctl interface in current so that I could MFC some changes in a > binary compatible way in -stable (thus breaking binary compat in > -current). When I use /usr/obj/usr/src/usr.sbin/pccard/pccardd/pccard instead of /usr/sbin/pccardd, PC Card works again. :-) ed0 at port 0x340-0x35f iomem 0xd-0xd0fff irq 3 flags 0x3 slot 1 on pccard1 ed0: address 00:40:26:xx:xx:xx, type NE2000 (16 bit) Thanks! -- rushani To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
