nForce MCP network driver
Hi, I am in the final stages of porting the NVidia Linux nForce MCP network driver to FreeBSD-5.1 and am after some experienced users/developers with access to this hardware to do some testing to find out what breaks, and what doesn't work. My driver makes use of the Linux nvnetlib.o API library, and should therefore be compliant with the NVidia Linux distribution license. The driver currently appears to be stable on my hardware, although I haven't done much stress testing, nor do I have access to an nForce2 based motherboard. This is still very much a work in progress, but it has been stable enough for me to actually use productively so I thought I would share the wealth, so to speak, with the rest of the community. If you are interested in testing this, email me offline. I am also interested in how many people would like to see a FreeBSD-4.x version. PS: I am still waiting for NVidia to reply to any of my emails. :( -- Seeya...Q -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- _ / Quinton Dolan [EMAIL PROTECTED] __ __/ / / __/ / / /__ / _// / Gold Coast, QLD, Australia __/ __/ __/ / / - / Ph: +61 419 729 806 ___ / _\ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
NVidia nForce MCP network driver : Update
Hi, I would just like to give a quick update on the status of my NVidia nForce MCP network driver. So far the driver has proven to be stable on both FreeBSD 5.1-RELEASE and 4.9-RC, and works on all tested nForce and nForce2 motherboards. The driver is now available for public download, the source code and a few other components can be found here: http://www.onthenet.com.au/~q/nvnet/ Keeping in mind that it is still a work in progress. Unfortunately I don't expect that the Athlon64/Opteron nForce3 support will be quite so straight forward to support, but if someone can assist me in getting access to this hardware I will be able to investigate it further. -- Seeya...Q -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- _ / Quinton Dolan [EMAIL PROTECTED] __ __/ / / __/ / / /__ / _// / Gold Coast, QLD, Australia __/ __/ __/ / / - / Ph: +61 419 729 806 ___ / _\ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: squid to ftp and https
You can only transparently proxy unencrypted data streams. There is no point in proxying port 443 because the SSL protocol is designed to prevent exactly this from being possible. So port 443 is out.. but there are a few others that are still viable.. and it's not very hard to setup. Make sure you have to following set in squid: httpd_accel_host virtual httpd_accel_port 0 And then just add the necessary rules to ipfw like so: 00500 fwd 192.168.100.254,3128 tcp from 192.168.100.0/24 to any dst-port 80 00500 fwd 192.168.100.254,3128 tcp from 192.168.100.0/24 to any dst-port 81 00500 fwd 192.168.100.254,3128 tcp from 192.168.100.0/24 to any dst-port 8080 00500 fwd 192.168.100.254,3128 tcp from 192.168.100.0/24 to any dst-port 8081 You can also redirect 'ftp' (port 21) using the "Frox" port in exactly the same way, but ftp is a more complicated protocol, so it may break things for some client/server combinations. Seeya...Q On Mon, 2003-12-22 at 21:16, Eicke wrote: > Hi folks, > > I am using a FreeBSD server as transparent proxy server. To make this I use > ipfw to foward port 80 requests. > I have a doubt, I like that 443, 8080, 8000, 8081 ports and FTP pass through > proxy too. > How can I make this? > > > Thanks and regards. > Eicke. > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Intermittent problems with LAN transfer speeds
The first thing you should try is setting the ethernet card to use autosense. This enables the autosense pulse to be sent to the switch, without this some passive/unmanaged switches can get very confused and switch speeds and duplex at seemingly random intervals for a while before eventually sorting themselves out again. You should only ever set speed & duplex manually if you can set it at BOTH ends. The easiest way to identify this as the problem is to do a 'netstat -i' and check for collisions. If everything on that LAN segment is full duplex all the time, there should be none. You will most likely have to wait for the problem to occur again before the collisions appear. Seeya...Q On Thu, 2004-01-08 at 06:15, Adam McLaurin wrote: > Since I first installed FreeBSD 2 years ago, I have intermittent > problems with my LAN transfer speeds. It doesn't happen often, but when > it does, I've not found any solution other than rebooting the server. > > My network configuration looks like this: > cable modem --> freebsd 5.1-R --> dlink switch --> win2k workstation > > I normally get appx 10MB/s between my two machines. However, > occasionally I'll fire up a transfer and only get 50-200KB/s, which is > really awful. ... > Both the gateway's NIC and the workstations NIC are manually set to > 100Mbit full-duplex. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IPFW rules being weird?
The easiest way I have found to quickly resolve these kinds of problems
is to put a "permit all' rule at the bottom and start it up from there a
rule at a time until it works. When you work out which rule is causing
the problem, check out what it's blocking that you need and replace the
'permit all' with an appropriate rule. This method lets you get to the
heart of the problem quickly without a lot of head scratching.
Seeya...Q
On Fri, 2003-10-24 at 11:10, Dan wrote:
> Hello there.
> Odd query for you.
>
> My setup is that sis0 is the ethernet which has the business cable modem
> attached to it - which serves as a gateway. sis1 is the Ethernet which my
> laptop connects to (wirelessly through a HE501 wireless pc card, and HE102
> access point (both by Netgear)).
>
> The problem that is occuring, is that if I have the IPFW rules below,
> everything works GREAT!
>
> fwcmd="/sbin/ipfw"
> $fwcmd -f flush
> $fwcmd add divert natd all from any to any via sis0
> $fwcmd add allow all from any to any
> $fwcmd add allow icmp from any to any icmptypes 0,3,8,11,12,13,14
>
>
> However, the above is not "secure" as you might say.
> The script below stops the laptop from being able to access th enet and i have
> NO idea why!
>
> # Define the firewall command (as in /etc/rc.firewall) for easy
> # reference. Helps to make it easier to read.
> fwcmd="/sbin/ipfw"
>
> # Force a flushing of the current rules before we reload.
> $fwcmd -f flush
>
> # Divert all packets through the tunnel interface.
> $fwcmd add 50 divert natd all from any to any via sis0
>
> # Allow all connections that have dynamic rules built for them,
> # but deny established connections that don't have a dynamic rule.
> # See ipfw(8) for details.
> $fwcmd add check-state
> $fwcmd add pass tcp from any to any established
>
> # Allow all localhost connections
> ${fwcmd} add 100 pass all from any to any via lo0
> ${fwcmd} add 200 deny all from any to 127.0.0.0/8
> ${fwcmd} add 300 deny ip from 127.0.0.0/8 to any
>
> # Allow all connections from my network card that I initiate
> $fwcmd add allow tcp from me to any out xmit any setup keep-state
> $fwcmd add deny tcp from me to any
> $fwcmd add allow ip from me to any out xmit any keep-state
> $fwcmd add allow all from 192.168.0.0/24 to any
>
> # Everyone on the Internet is allowed to connect to the following
> # services on the machine. This example specifically allows connections
> # to sshd and a webserver.
> $fwcmd add allow tcp from any to any established
> $fwcmd add allow tcp from any to me 80 setup
> $fwcmd add allow tcp from any to me 21 setup
> $fwcmd add allow tcp from any to me 22 setup
>
> # This sends a RESET to all ident packets.
> $fwcmd add reset log tcp from any to me 113 in recv any
>
> # Enable ICMP: remove type 8 if you don't want your host to be pingable
> $fwcmd add allow icmp from any to any icmptypes 0,3,8,11,12,13,14
>
> # Deny all the rest.
> $fwcmd add deny log ip from any to any
>
>
> If you can help with this it'd be much appreciated.
> Thanks!!!
>
> Running FreeBSD 4.8-RELEASE.
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"nsubscribe, send any mail to
> "[EMAIL PROTECTED]"
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
if_rue and Wiretek UBRJ4 USB 1.1 To Fast Ethernet Converter
I recently bought this cheap USB ethernet dongle. When kldloading if_rue it is found a recives a ifconfig entry: kernel: rue0: REALTEK USB 10/100 LAN, rev 1.10/1.00, addr 3 kernel: miibus1: on rue0 kernel: ruephy0: on miibus1 kernel: ruephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto kernel: rue0: Ethernet address: 00:e0:4c:03:07:1f and dhclient gives it an ip correct. But when putting some load on the interface, (misc nfs and scp things) it starts giving troubles: kernel: rue0: watchdog timeout kernel: rue0: usb error on tx: IN_PROGRESS kernel: rue0: usb error on tx: TIMEOUT And all my pings etc stopped working, and ping started saying no buffer space... and such (but my irrsi still let me see some of the new privmesgs for a while) I stoppede the load and downed and upped the interface again and after a while it started to let me send packets again. But short after the same error occoured again and i gave up. Is this because of shitty crap hardware(it costed me about 10euros) or is there some solution with the driver ? kind regards Søren Vrist ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
