if_wb w89c840af winbond card
Hi, I wonder if there is somebody who has a working winbond ethernet card. My card has a W89C840 chip and an AC104 PHY. The driver doesn't find the AC104 and as a result the kernel panics. The fix to avoid the panic is very easy, but i started to wonder if it is the AC104 that is causing this or that the driver is disfunctional for all PHYs. I am trying to determine why the PHY is not detected, but it helps to know if the code is completely broken or not. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
if_wb driver problem - need help
Hi, I have a Winbond based card with an Altima AC104 media interface. No matter what I do i am not able to recognize the AC104 through the SIO interface. The BMSR register value stays at zero. I have the datasheets of both the Winbond and the Altima and everything looks ok. So far i see the frame to request the contents of the bmsr C24 is send ok to the AC10t thru the management interface. The ACK is never coming. Who has tips trying to make this thing work? I have also tried NetBSD without success. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
vlan traffic over ipsec tunnel
Hi All, I'd like to accomplish the following: I have two locations, connected via an IPSEC tunnel. Is it possible to connect the vlans at both ends through the tunnel. Is this possible with existing software? What would it take to do something like this? Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
multiple gateways
Hi, I know this topic has been brought up numerous times. I have 4 IP4 internal networks (sf0 .. sf3) I have a cable modem connection ep0 and a DSL ep1 connection too. I'd like to route all traffic from sf0 and sf1 to the DSL connection and the others to the cable modem. At the same time I'd like to offer the protection of ipfilter. Traffic on sf0 should not see traffic on sf1 etc. Since this seems not possible with the both stable and current, I would like to make a solution for it, inside the kernel. I am thinking of creating a routing table based on source address and designate the right gateway. Thoughts and opinions are very welcome. Where do you suggest I start? Peter P.S. If this functionality exists (without bridging) I'd like to know as well To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
mpd netgraph pptp server
Hi, I have a gateway/firewall which is the spider in the web for different IP segments. From two segments 192.168.2.0/24 and 192.168.10.0/24 I am trying to setup PPTP tunnels. I have two different pptp sections (pptp1 and pptp2) in both mpd.conf and mpd.links with unique names. Each pptp section has its own "pptp self" listen address. The problem is that the mpd daemon only listens on the first pptp (pptp1) section and doesn't listen on the 2nd (pptp2). When I load pptp2 first before pptp1 it is the other way around. I am using sockstat -l to confirm where mpd is listening on? Am I doing something wrong here? See attachments Thx, Peter default: load pptp1 load pptp2 pptp1: new -i ng1 pptp1 pptp1 log +auth +ccp +chat +fsm +iface +pptp +ipcp +lcp +link +phys set iface disable on-demand set iface enable proxy-arp set iface idle 0 set bundle disable multilink set link yes acfcomp protocomp set link no pap chap set link enable chap set link keep-alive 10 60 set ipcp yes vjcomp set ipcp ranges 192.168.10.1/32 192.168.10.2/32 set ipcp dns 192.168.1.1 set ipcp nbns 192.168.1.135 set bundle enable compression set ccp yes mppc pptp2: new -i ng2 pptp2 pptp2 log +auth +ccp +chat +fsm +iface +pptp +ipcp +lcp +link +phys set iface disable on-demand set iface enable proxy-arp set iface idle 0 set bundle disable multilink set link yes acfcomp protocomp set link no pap chap set link enable chap set link keep-alive 10 60 set ipcp yes vjcomp set ipcp ranges 192.168.2.1/32 192.168.2.2/32 set ipcp dns 192.168.2.1 set ipcp nbns 192.168.2.1 set bundle enable compression set ccp yes mppc pptp1: set link type pptp set pptp self 192.168.10.1 set pptp enable incoming set pptp disable originate pptp2: set link type pptp set pptp self 192.168.2.1 set pptp enable incoming set pptp disable originate
Re: mpd netgraph pptp server
On Tuesday 02 July 2002 21:14, Archie Cobbs wrote: > Peter J. Blok writes: > > I have a gateway/firewall which is the spider in the web for different IP > > segments. From two segments 192.168.2.0/24 and 192.168.10.0/24 I am > > trying to setup PPTP tunnels. I have two different pptp sections (pptp1 > > and pptp2) in both mpd.conf and mpd.links with unique names. Each pptp > > section has its own "pptp self" listen address. > > > > The problem is that the mpd daemon only listens on the first pptp (pptp1) > > section and doesn't listen on the 2nd (pptp2). When I load pptp2 first > > before pptp1 it is the other way around. I am using sockstat -l to > > confirm where mpd is listening on? > > Mpd only supports listening on one IP address for PPTP connections. > > Can you try changing both IP addresses to 0.0.0.0? Yes, I have done that after I looked at the source. The problem remained that it was picking the wrong link. Then I saw that based on the pptp peer address the best link is picked, which is what I use right now. Thx for the help anyway, Peter > > -Archie > > __ > Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
Re: mbuf denied problem
On Sunday 21 May 2006 21:28, Robert Watson wrote: > On Sat, 20 May 2006, Robert Watson wrote: > > On Fri, 19 May 2006, OxY wrote: > >> i have a problem with mbuf... when all my free memory is gone ( i have > >> 2gb ram) and memory allocation looks like this: > > > > I recently received an informal problem report that there is a problem > > with the "denied" statistics gathering, so I think it's likely that's > > what is going on here. I'll follow up with the submitter and see if we > > can't figure out something more definite. > > I have received some further information on the problem from the reporter. > Could you give this patch a try and see what effect it has? I already had made an identical patch and it worked. This seems to be the problem. > > Index: uma_core.c > === > RCS file: /home/ncvs/src/sys/vm/uma_core.c,v > retrieving revision 1.136 > diff -u -r1.136 uma_core.c > --- uma_core.c11 Feb 2006 19:20:56 - 1.136 > +++ uma_core.c21 May 2006 19:25:56 - > @@ -2413,8 +2413,7 @@ >* If nothing else caught this, we'll just do an internal free. >*/ > zfree_internal: > - uma_zfree_internal(zone, item, udata, SKIP_DTOR, ZFREE_STATFAIL | > - ZFREE_STATFREE); > + uma_zfree_internal(zone, item, udata, SKIP_DTOR, ZFREE_STATFREE); > > return; > } > > Technically, there has been an allocation failure in this case in > identifying a bucket to return the item to, but since the overall case is a > free, generating a failure statistics update seems undesirable. > > Thanks, > > Robert N M Watson > > > Robert N M Watson > > > >> Mem: 30M Active, 1607M Inact, 245M Wired, 84M Cache, 214M Buf, 3028K > >> Free Swap: 695M Total, 695M Free > >> > >> mbuf starts to deny... > >> netstat -m show 0 deny till has memory, after that i see this: > >> > >> Field root# netstat -m > >> 629/466/1095 mbufs in use (current/cache/total) > >> 512/176/688/65536 mbuf clusters in use (current/cache/total/max) > >> 512/133 mbuf+clusters out of packet secondary zone in use > >> (current/cache) 0/0/0/0 4k (page size) jumbo clusters in use > >> (current/cache/total/max) 0/0/0/0 9k jumbo clusters in use > >> (current/cache/total/max) > >> 0/0/0/0 16k jumbo clusters in use (current/cache/total/max) > >> 1181K/468K/1649K bytes allocated to network (current/cache/total) > >> 7410219/101093/101499 requests for mbufs denied > >> (mbufs/clusters/mbuf+clusters) > >> 0/0/0 requests for jumbo clusters denied (4k/9k/16k) > >> 0/0/0 sfbufs in use (current/peak/max) > >> 0 requests for sfbufs denied > >> 0 requests for sfbufs delayed > >> 25288 requests for I/O initiated by sendfile > >> 65 calls to protocol drain routines > >> > >> this is my sysctl.conf: > >> net.inet.tcp.delayed_ack=0 > >> net.inet.ip.intr_queue_maxlen=400 > >> net.inet.tcp.inflight.enable=0 > >> net.route.netisr_maxqlen=512 > >> kern.ipc.somaxconn=1024 > >> > >> should i attach any other conf/log,etc? > >> thanks! > >> ___ > >> freebsd-net@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-net > >> To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > > > ___ > > freebsd-net@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-net > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > ___ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FAST_IPSEC issue
Hi, So here is FAST_IPSEC user # 4, or is it 5 ;-) Initially I was not able to make FAST_IPSEC work. I had a working environment with normal IPSEC, but after I switched on FAST_IPSEC it didn't work anymore. The tcpdump looked ok, but now I realize I have missed a tiny detail. To make FAST_IPSEC work, you also have to allow proto ipencap to pass ipfilter. With the original IPSEC only proto esp was enough. Peter ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
OpenBSD enc interface on FreeBSD
Hi, Is somebody already taking efforts to include the OpenBSD enc device in FreeBSD? If not, I would like to give it a try. Peter ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Adaptec Quad Nic Problem
Hi, I have the same card working since 4.5 I believe. Even under massive load I do not have any issues. As a matter of fact I have two of those in one box. However, I have seen this once in a different PC. It turned out to be an interupt conflict. Peter On Wednesday 10 September 2003 16:27, Alexandre Biancalana wrote: > Hi All, > > I have a Firewall/Gateway running FreeBSD 4.8-STABLE connected to an > internet link of 2.5Mbits/s througth an Quad-NIC Adaptec ANA6944A, that > when having a high""traffic the switch port where the machine is connected > points that's is down and the following messages appear in > /var/log/messages: > > Sep 8 10:53:41 Krusty /kernel: sf0: watchdog timeout > Sep 8 10:54:59 Krusty /kernel: sf0: watchdog timeout > Sep 8 11:01:53 Krusty /kernel: sf0: TX ring full, resetting > Sep 8 11:01:57 Krusty /kernel: sf0: watchdog timeout > Sep 8 11:14:37 Krusty /kernel: sf0: watchdog timeout > Sep 8 11:20:11 Krusty /kernel: sf0: TX ring full, resetting > Sep 8 11:20:14 Krusty /kernel: sf0: TX ring full, resetting > Sep 8 11:45:26 Krusty /kernel: sf0: TX ring full, resetting > Sep 8 12:03:38 Krusty /kernel: sf0: TX ring full, resetting > Sep 8 12:03:41 Krusty /kernel: sf0: TX ring full, resetting > > The transfers don't exceed 1/2 off total bandwitch available in this link, > that's 2.5Mbit/s but the transfers don't exceed 700 Kbit/s. > > After google, I have seen some case about that but without an solution. > Someone can help me !? > >Best Regards, > > Alexandre Biancalana > ___ > [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]"
Giga-bit switches
Hi, This is just a warning. I am setting up a Giga-bit network trying to use Jumbo frames. For NIC the ability to do larger frames is usually listed, but that doesn't seem to be the case for switches. I have bought a Netgear GS104 switch, which does list a buffer per port of 12K. However, according to Netgear support, it is not supported and working. They just say that there is no mentioning of Jumbo frame support, therefore it is not supported. Even on the more expensive Netgear switches it is not listed, so it is trial-on-error policy. My understanding is that the Giga-bit definition includes large frame support and if you claim to have a Giga-bit switch you should support large frames, unless specifically excluded. So be warned. Peter ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
