RE: Intel WiFi 5100/5300
Hi Bernhard, I'm trying to use your driver but i have a problem: iwn0: mem 0xde00-0xde001fff irq 16 at device 0.0 on pci2 iwn0: MIMO 1T2R, MoW, address 00:21:6b:2b:78:04 iwn0: [ITHREAD] iwn0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps iwn0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps iwn0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps iwn0: 11na MCS: 15Mbps 30Mbps 45Mbps 60Mbps 90Mbps 120Mbps 135Mbps 150Mbps 30Mbps 60Mbps 90Mbps 120Mbps 180Mbps 240Mbps 270Mbps 300Mbps iwn0: 11ng MCS: 15Mbps 30Mbps 45Mbps 60Mbps 90Mbps 120Mbps 135Mbps 150Mbps 30Mbps 60Mbps 90Mbps 120Mbps 180Mbps 240Mbps 270Mbps 300Mbps wlan0: Ethernet address: 00:21:6b:2b:78:04 iwn0: iwn_init_locked: radio is disabled by hardware switch I load iwnfw.ko before if_iwn.ko. But i have all time the message: iwn0: iwn_init_locked: radio is disabled by hardware switch But when i press the button nothing change, no options in the bios too. Have you an idea where the problem come from ? Thanks in adavance, Nicolas. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Intel WiFi 5100/5300
Hi Bernhard, Thanks for your response, Yes i have a status indicator, the led for the wifi is always orange, i think if it's work that the led become white. I try to load/unload a few times but nothing changes, always the same message ! Another idea ? Nicolas. I have no clue.. Do you have any status indication for the button, LED or something? Try press it a few times and kldunload/kldload if_iwn again ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
iwn(4): Porting Intel 5100/5300 support from OpenBSD?
Hi, I'm also interested. If you have a patch, I can test it, I have a 5100 card. Thanks in advance, Niko. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
dhclient stops trying to get a new lease
Hi, I have a cable modem with dynamic IP, and a FreeBSD 5.3 server just behind. This server gets its IP with the help of dhclient. Today I got a huge down because of a problem on the ISP side. During that time, dhclient made his job trying to get a lease every 4 minutes, unsuccessfully of course. But at 10 AM, after 10 hours of trying to get a lease every 4 minutes (unsuccessfully of course), dhclient completely stopped trying. Thus, when the line came back up, it didn't got its lease. I had to manually tell him to get that new lease... Why did it stopped trying ? What should I do to tell him to try forever until it can acquire a lease ? Here is a part of my /var/log/messages : /* the line went down at midnight. dhclient gets a "fake" IP */ Jan 28 00:00:44 sun dhclient: New IP Address (vr0): 192.168.100.11 Jan 28 00:00:44 sun dhclient: New Subnet Mask (vr0): 255.255.255.0 Jan 28 00:00:44 sun dhclient: New Broadcast Address (vr0): 192.168.100.255 /* 4 minutes later, it retries */ Jan 28 00:04:55 sun dhclient: New IP Address (vr0): 192.168.100.11 Jan 28 00:04:55 sun dhclient: New Subnet Mask (vr0): 255.255.255.0 Jan 28 00:04:55 sun dhclient: New Broadcast Address (vr0): 192.168.100.255 /* [...same thing repeating over and over...] */ /* another time... */ Jan 28 09:57:59 sun dhclient: New IP Address (vr0): 192.168.100.11 Jan 28 09:57:59 sun dhclient: New Subnet Mask (vr0): 255.255.255.0 Jan 28 09:57:59 sun dhclient: New Broadcast Address (vr0): 192.168.100.255 /* the last dhclient-related block.. This time it's a bit different. ** after that block dhclient no more tries anything... */ Jan 28 10:00:45 sun kernel: vr0: Using force reset command. Jan 28 10:00:45 sun dhclient: New IP Address (vr0): 192.168.100.11 Jan 28 10:00:45 sun dhclient: New Subnet Mask (vr0): 255.255.255.0 Jan 28 10:00:45 sun dhclient: New Broadcast Address (vr0): 192.168.100.255 /* finally I had to restart dhclient to get my "real" IP, once the ** cable came back */ Jan 28 19:34:18 sun kernel: vr0: Using force reset command. Jan 28 19:34:57 sun dhclient: New IP Address (vr0): 81.66.254.111 Jan 28 19:34:57 sun dhclient: New Subnet Mask (vr0): 255.255.254.0 Jan 28 19:34:57 sun dhclient: New Broadcast Address (vr0): 81.66.255.255 Jan 28 19:34:57 sun dhclient: New Routers: 81.66.254.1 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Any reason to not implement VRRP in FreeBSD?
Hi all, Currently, i'm investigating solutions in order to ensure some redundancy at the IP level. More specifically, i'm looking into CARP and VRRP. As i'm having a look at the CARP implementation, one question did arise: Is there currently any reason to not have an implementation of VRRP inside FreeBSD? I understand that this made sense at a time due to CISCO patents, but according to Wikipedia, it seems that those patents did expire some years ago. So, would there still be legal issues about this or is FreeBSD now free to have its own VRRP implementation? Regards, Nicolas Masse.
Re: attempting VPN again
On Fri, 20 Apr 2007 08:24:17 -0400, "Jim Stapleton" <[EMAIL PROTECTED]> wrote: > /usr/local/etc/mpd/mpd.conf > > vpn: > new -i nve0 vpn vpn > > set iface session 28800 > set bundle authname "WORK-DOMAIN\\WORK-USERNAME" > set bundle enable compression > set ccp yes mppc > set ccp yes mpp-e40 > set ccp yes mpp-e56 > set ccp yes mpp-e128 > # set this to your correct routing information > set iface route EXTERNAL-WORK-VPN-IP/24 > set link enable no-orig-auth > open > In mpd.conf, you need to set the interface to a valid netgraph interface name, e.g. ng0. mpd will create it for you if it does not exist. The physical interface (e.g. nve0) is specified in mpd.links, not here. Additionally, you have a blank line between the "new" command and the first "set" command. I suspect that's causing the "no bundles defined" errors: > mpd: no bundles defined > mpd: no bundles defined > mpd: no bundles defined > mpd: no bundles defined > mpd: no bundles defined > mpd: no bundles defined > mpd: no bundles defined > mpd: no bundles defined > mpd: no bundles defined > mpd: no bundles defined -- Nicolas Gieczewski ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Download speed and TCPIP window sizing
On Thu, 31 May 2007 22:06:39 +0800, Pang <[EMAIL PROTECTED]> wrote: > Recently, I have leased a rack in Asianetcom and some bandwidth. > However, the speed for my curcuit is substantially slower than my > provider's company site. > [...] > *This server is using FreeBSD 6.2 patch 4 with Apache in the port tree. > The kernel is custom built but I haven't made any modification in sysctl > > I have asked many techs in Asianetcom and they blamed on TCPIP window > sizing. I used to have the same problem with my FreeBSD dedicated servers in the U.S. when I was living in South America with a latency of ~200 ms. Given identical hardware and connectivity, I could max out my download speed when downloading from a server running Linux, but would get no more than 100-150 KB/s when downloading from an otherwise identical FreeBSD box. The solution was to increase the size of the TCP send window on the FreeBSD server to about 128 KB--the default of 32 KB turned out to be way too small. # sysctl net.inet.tcp.sendspace=131072 After modifying this value, you need to restart any processes (e.g. Apache) that you want to take advantage of the change. Hope it helps. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD NFS server not responding to TCP SYN packets from Linux/SunOS clients
Portmap V2 GETPORT Call (Reply In 26) 25 0.007020 TCP sunrpc > 913 [ACK] Seq=1 Ack=61 Win=49172 Len=0 TSV=613133117 TSER=4294753264 26 0.007452 Portmap V2 GETPORT Reply (Call In 24) 27 0.007475 TCP 913 > sunrpc [ACK] Seq=61 Ack=33 Win=5840 Len=0 TSV=4294753265 TSER=613133117 28 0.007598 TCP 913 > sunrpc [FIN, ACK] Seq=61 Ack=33 Win=5840 Len=0 TSV=4294753265 TSER=613133117 29 0.007712 TCP 911 > 32785 [FIN, ACK] Seq=93 Ack=77 Win=5840 Len=0 TSV=4294753265 TSER=613133117 30 0.007766 TCP sunrpc > 913 [ACK] Seq=33 Ack=62 Win=49232 Len=0 TSV=613133118 TSER=4294753265 31 0.007816 TCP sunrpc > 913 [FIN, ACK] Seq=33 Ack=62 Win=49232 Len=0 TSV=613133118 TSER=4294753265 32 0.007839 TCP 913 > sunrpc [ACK] Seq=62 Ack=34 Win=5840 Len=0 TSV=4294753265 TSER=613133118 33 0.007893 TCP 32785 > 911 [ACK] Seq=77 Ack=94 Win=49232 Len=0 TSV=613133118 TSER=4294753265 34 0.008012 TCP 32785 > 911 [FIN, ACK] Seq=77 Ack=94 Win=49232 Len=0 TSV=613133118 TSER=4294753265 35 0.008145 TCP 911 > 32785 [ACK] Seq=94 Ack=78 Win=5840 Len=0 TSV=4294753265 TSER=613133118 36 0.008553 TCP 799 > 2049 [SYN] Seq=0 Ack=0 Win=5840 Len=0 MSS=1460 TSV=4294753266 TSER=0 WS=2 37 0.008790 TCP 2049 > 799 [SYN, ACK] Seq=0 Ack=1 Win=49232 Len=0 TSV=613133118 TSER=4294753266 MSS=1460 WS=0 38 0.008836 TCP 799 > 2049 [ACK] Seq=1 Ack=1 Win=5840 Len=0 TSV=4294753266 TSER=613133118 Thanks, -- Nicolas ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD NFS server not responding to TCP SYN packets from Linux/SunOS clients
Mike Silbersack <[EMAIL PROTECTED]> writes: > On Fri, 14 Oct 2005, [EMAIL PROTECTED] wrote: > >> Nicolas KOWALSKI wrote: >>> Our FreeBSD 4.10 NFS server has some problems serving files by NFS >>> on TCP (no problem with UDP) when the Linux (2.6) or Solaris (5.9) >>> clients shut down in an unclean manner (power failure). When the >>> clients try to mount the shares from the server after an unclean >>> shutdown, the mount process hang during several minutes (delay is >>> varying), then succeeds. >> >> That is just a wild guess, but NFS mounting would happen always at >> the same stage of the boot, so maybe with the same source port >> number and you could be facing the problem that the connection is >> waiting for termination on the server (close_wait or fin_wait or >> something)... Se source port in working example is 798 and source >> port in failing example is 799 certainly not random. > > The socket on the server would still be in the ESTABLISHED state, > which is even worse than the close_wait or fin_wait states in this > case. The SYN will be accepted if it's greater than the previous > sequence number, so that's a 50% chance it'll work. Thanks for this explanation. > Assuming that port reuse is the problem, there is no quick fix for > this, just resetting connections when a SYN comes in would be a > really big security problem. Really? Are Linux and Solaris that insecure because of this behaviour? > Actually, there may be a quick fix for this specific machine. If you > set net.inet.tcp.keepidle to 1 minute (60*whatever kern.hz is), > that'll cause keepalive packets to be sent every minute to an idle > connection, rather than every 2 hours. That would kill the stuck > connections much quicker. Unfortunately, this does not work as expected. I just tested with my workstation (Linux 2.6), with NFS filesystems mounted with TCP; when the station rebooted abruptely, mounting the same NFS filesystems hung more than 1 minute (15 minutes just now). During this hang, I saw on the server, using netstat, the nfsd process related to my workstation in ESTABLISHED state. Any other tip? Many Thanks in advance, -- Nicolas ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
gateway+multi-PPPoE
Hi! I'm triyng to set-up a Gateway that will use 3 different PPPoE (to the same provider) adsl connection (3 modem , 3 account), to distribute it back to a soho network. In instance to get the more bandwith possible. I've been able to set-up the gateway with one modem by using netgraph and PPP. I tought that using mpd would allow me to to get the maximun of these three connections. It seem to work well on the gateway. But the rest of the network is dead (the gate way see everybody and vice versa) but station dont see the net. If somebody have any idea how to make that thing work it will be a great help. P.S. I try that solution, if there's other who work better, please tell me . thanks Nicolas Beauchesne [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
Interrupts / No interrupts
Hi! I'm working on an IP encapsulation protocol, a la IPSec. Since I need to manage sessions, I have "shared datum" among several IP packets, so I need to splnet() / splx() the code. A simple way to do it is just to protect my whole code inside a splnet(), and then splx() when it exits. I that a bad idea? Should I only protect some portions, and why? Thanks Nicolas Fritsch Software Engineer To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
Re: Rename of MSIZE kernel option..
Note: I'm just a lurker here, but thought I'd give my 2 cents on this discussion as well. On Mon, 14 Oct 2002, Andrew Gallatin wrote: > > Would people be open to renaming the 'MSIZE' kernel option to something > > more specific such as 'MBUF_SIZE' or 'MBUFSIZE'? Using 'MSIZE' can > > No. > > MSIZE is a traditional BSDism. Everybody else still uses it. > Even AIX and MacOS. I really don't like the idea of changing this. True, but John is right, it's too generic a name. The argument "it's been forever so we can't change it" seems a bit fallacious to me: that's with that line of thinking that one ends up with breakages no one can figure out years down the road. You end up having to keep pieces of code no one really knows what they're doing anymore, but if you take them out, the whole thing crashes and burns. Not that I'm saying it would be the case for something as obvious as MSIZE, but still... > Renaming MSIZE to ISA_IVAR_MEMSIZE seems right to me. I agree. Don't use something like MSIZE at all. The name is not explicit enough. For a transition period, one could define both an MSIZE and an MBUF_SIZE equivalent to MSIZE for a couple of versions (say the whole 5.x series), clearly stating MSIZE is deprecated and shouldn't be used anymore, and then it could be completely removed in 6.x. -- Nicolas Christin Ph.D. Candidate, University of Virginia, Computer Science http://www.cs.virginia.edu/~nicolas To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
Re: IP bad cksum (0!)
On Fri, 11 Oct 2002, soheil hassas yeganeh wrote: > ip->ip_sum = in_cksum(m,hlen); > > When i make a dump it says that it has bad cksum 0! > > 12:25:11.858759 62.217.112.165 > 66.201.71.98: icmp: echo reply (ttl 42, id > 17879, len 84, bad cksum 0!) I'm not that familiar with the code, but I'd be surprised if ICMP packets were handled by IP functions. (ICMP is not IP.) Not sure where your checksum problem comes from. -- Nicolas Christin Ph.D. Candidate, University of Virginia, Computer Science http://www.cs.virginia.edu/~nicolas To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
Re: hping strange behaviour
(Fri, Dec 27, 2002 at 02:33:00PM +0100) jeremie le-hen wrote: > yoda:tataz# hping -n -I tun0 -V --icmp --dontfrag --icmp-addr 193.252.50.1 > using lo0, addr: 127.0.0.1, MTU: 1500 > HPING 193.252.50.1 (lo0 193.252.50.1): icmp mode set, 28 headers + 0 data bytes > [send_ip] sendto: Can't assign requested address. > > This seems obious that hping doesn't use the right interface tun0 to send his > datagrams. > Note that I'm connected to Internet through a DSL connexion, using PPPoE. My Hmmm, can you provide output of hping -v and your command with -D switch? I have the same problem using pppX interfaces. If you do not use -I, hping should select the correct interface. > So does anyone have an idea on my problem ? Thanks in advance. Yet another bug :) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
Re: Quad ethernet question
On Fri, 3 Jan 2003, Barry Irwin wrote: > kseel wrote: > > > Anyone using one of these? > > > > >http://www.corpsys.com/store/prodinfo.asp?number=ANA6944&variation=&aitem=60&mitem=62 > > If so, is the performance good? > > > I have a similar card ( also adaptec 4 port) in a number of firewalls. > FreeBSD uses the sf driver. Been running these for about 18 months with no > hastles. Well, I have had problems with it. I can't remember the exact wording of the error message I was getting, but under a very high load (all four ports spitting out about 90 Mbps), the card would frequently complain that some buffer was full and it couldn't send anymore. The only way to get the card back was to do an ifconfig down up on all four ports... It looked very much like mbuf exahustion except that mbuf's were still available according to what I was seeing. I guess there is a small problem in the sf driver, but I didn't get around to trying to fix it. (Device driver tweaking is not really my area of expertise...) If there is interest I can try to dig up the old email in which I was describing the problem... I don't think I posted it to this list at the time, it's more likely I sent a private email to the driver's author. Then again, these problems occured under 4.3 and 4.5, can't tell if this was fixed in more recent revisions of the driver. Best, -- Nicolas Christin Ph.D. Candidate, University of Virginia, Computer Science http://www.cs.virginia.edu/~nicolas To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
Re: Quad ethernet question
On Fri, 3 Jan 2003, Nicolas Christin wrote: > If there is interest I can try to dig up the old email in which I was > describing the problem... Following is a more accurate description of the problem I saw with the card mentioned in this thread. I don't seem to have a printout of the available mbuf's at hand, but I distinctly remember that everything looked fine on that front. --Nicolas I am experiencing some problems with the sf driver, which I use on the following quad card: Adaptec ANA-62044 SGLQuartet 64 10/100Base TX The driver works just fine most of the time, I can transmit/receive data on all four ports. However, when the link governed by the sf driver gets overloaded, I sometimes get the following error: nc2y@tin $ ping 10.0.4.2 PING 10.0.4.2 (10.0.4.2): 56 data bytes ping: sendto: No buffer space available where sf0 is configured as follows: nc2y@tin $ ifconfig sf0 sf0: flags=8843 mtu 1500 inet 10.0.4.1 netmask 0xff00 broadcast 10.0.4.255 inet6 fe80::200:d1ff:feee:3ff1%sf0 prefixlen 64 scopeid 0x3 ether 00:00:d1:ee:3f:f1 media: 100baseTX status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP none Interestingly enough, when pinging 10.0.4.1 from 10.0.4.2, I do not get any error, and ICMP replies actually manage to make it. This experiment was run on an Intel Pentium III running FreeBSD 4.3. (I don't think there are any changes to the sf driver in FreeBSD 4.4.) [Note: the same problem is present in 4.5.] -- Nicolas Christin Ph.D. Candidate, University of Virginia, Computer Science http://www.cs.virginia.edu/~nicolas To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
pf(4) port?
Hello, I would like to know if anyone knows of a port (or a porting project in progress) of OpenBSD's pf(4) to FreeBSD. I couldn't find anything... (I know some guy started porting it to NetBSD, but haven't seen anything FreeBSD-related.) Best regards, -- Nicolas To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
nge and vlans
Hi there ! Sorry for the cross post from freebsd-question, but I need help on this... We are trying to setup a router with freebsd and an asante 3548 swicth. The switch is connected to the bsd box via an asante giganix (nge driver) card. I searched this list for answer on this question, searching for nge and vlan reveals to me the same problem I have : Packets that go trought vlans on the switchs are shown in tcpdump on nge0 with the incorrect vlan tags : http://www.freebsd.org/cgi/getmsg.cgi?fetch=2102763+2107441+/usr/local/www/db/text/2003/freebsd-questions/20030413.freebsd-questions http://www.freebsd.org/cgi/getmsg.cgi?fetch=1816764+1821123+/usr/local/www/db/text/2003/freebsd-questions/20030413.freebsd-questions Mike Hogsett and Cejka Rudolf seems to have found also this problem. So I wounder if there is a solution to this problem ? Thanks, Nicolas Ross ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Samba: Marginal performance & pauses in transfers
Hello everybody, I have a FreeBSD 4.8-STABLE server running Samba 2.2.8a and a workstation running Windows 2000 SP4. Whereas FTP transfers between these boxes average 700 KB/s (10 mbps LAN), Samba transfers are never beyond ~120 KB/s. Trust me, I have tried *everything* I've run into as far as tuning goes, but this is a different problem. The main problem lies in the fact that transfers are not consistent and undergo VERY long, random pauses. My hub's activity LED shows that, during a Samba transfer between these two boxes, no packets are transferred about 70% of the time. Yep, only during about 30% of the total time a transfer takes there is actual network activity--the remaining 70% of the time is taken up by random (both length- and interval-wise) pauses. All my network cards are propery configured, both media- and duplex- wise. There are nearly no collissions, and the 700 KB/s rate I can achieve in FTP transfers shows that Samba has the problem. I can do SMB transfers between the Windows 2000 box and another Windows 98 box at about 600 KB/s, so the culprit is obviously Samba on the FreeBSD box. Because most of the time a transfer takes to complete is wasted on those random pauses, anything I could tune concerning buffer sizes and the like is almost useless because it only takes effect while data is actually being transferred, not during the pauses. I have fiddled with buffer sizes and, by looking at the hub's activity light, I could (visually and easily) see how more or less data was transferred in between the pauses depending on the buffer sizes I chose. However, the pauses stayed consistent throughout all my tests. By using larger buffer sizes, all I could do was push more data through in between the pauses, but my tuning never affected the length or interval of the pauses themselves. Does anyone happen to know what could be causing this problem? Cheers, Nicolas Gieczewski Nix Software Solutions http://www.nixsoftware.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ALTQ integration
Fabien, On Sun, 10 Aug 2003, Fabien THOMAS wrote: > What is the status of the ALTQ framework integration into FreeBSD ? I refer you to the current threads in <http://www.rofug.ro/mailarchive/freebsd-altq.2003-08/>. The short answer is "some people are working on it". > OpenBSD have native support but i think the merge with pf is a bad idea > that do not allow third party classifier. Well - it has been discussed (especially on netbsd-tech, and sometimes in pretty harsh terms), and it is the road that is seemingly followed, according to the recent commits in the KAME tree. See for instance the changelog for July 10 at <http://orange.kame.net/dev/cvsweb.cgi/kame/kame/sys/altq/altq_cbq.c>. Regards, -- Nicolas ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
TCP IPv4 connections problem
Hello, I have a very strange problem on a router (R1): it stop to reply to TCP IPv4 connections on one of its network interfaces after a random time but it don't stop to reply to TCP IPv6 connections and ICMP IPv4/IPv6. The network is composed of 3 routers with the same hardware and software (FreeBSD 5.0): R1, R2 and R3. Interfaces on R1: ti0: to R2 ti1: to R3 ti2: to LAN1 Interfaces on R2: ti0: to R1 ti1: to LAN2 Interfaces on R3: ti0: to R1 ti1: to LAN3 Each interface have both IPv4 and IPv6 address. R3 <-> R1 <-> R2 When the problem occur (between 3 and 24 hours after reboot): LAN3 <-> R3: ICMP IPv4/IPv6 and TCP IPv4/IPv6 is OK LAN3 <-> R1: ICMP IPv4/IPv6 and TCP IPv6 is OK, TCP IPv4 is not OK LAN3 <-> R2: ICMP IPv4/IPv6 and TCP IPv4/IPv6 is OK R3 <-> R1: ICMP IPv4/IPv6 and TCP IPv6 is OK, TCP IPv4 is not OK R3 <-> R2: ICMP IPv4/IPv6 and TCP IPv4/IPv6 is OK LAN1 <-> R1: ICMP IPv4/IPv6 and TCP IPv4/IPv6 is OK LAN2 <-> R1: ICMP IPv4/IPv6 and TCP IPv4/IPv6 is OK LAN2 <-> R2: ICMP IPv4/IPv6 and TCP IPv4/IPv6 is OK R1 <-> R2: ICMP IPv4/IPv6 and TCP IPv4/IPv6 is OK When i try to establish a TCP IPv4 connection directly to R1 through the ti1 interface of R1 it dont work, but when i try to establish a TCP IPv4 connection directly to R1 through the ti0 or ti2 interface of R1 it work. I can establish from R3 a TCP IPv4 connection directly to R2 through R1. Do you have an idea how fix the problem ? Thanks Best Regards, -- Nicolas DEFFAYET, NDSoftware NDSoftware IP Network: http://www.ip.ndsoftware.net/ FNIX6 (French National Internet Exchange IPv6): http://www.fnix6.net/ EuroNOG: http://www.euronog.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Adding IP_PEERCRED?
Hello, I would like to enquire about the possibility of adding an IP_PEERCRED socket option to ip(4) which would be similar to LOCAL_PEERCRED for unix(4). Such a option, when requested via getsockopt(2) on a not-connectionless IP (v4 or v6) socket, would either - return credentials of the remote side (as a xucred structure) in the case of a loopback (non-cross-jail) socket; - fail (with EINVAL?). The intended use-case of such a functionnality would be for processes to provide services only to a given user, instead of the local host, while using IP sockets. For instance, an SSH client could use this feature to provide port forwards for a given user, instead of providing it to all users. While bapt@ thought at first glance that it might be a good idea, neither of us know whether it would be reasonable to implement. Any though on this? Best, Nicolas PS: Credit for this idea should go to David Madore (in CC), who blogged about it (in French): http://www.madore.org/~david/weblog/d.2014-10-16.2234.html signature.asc Description: PGP signature
Re: FRR on FreeBSD 12 - problems with OSPFv3
On Fri, 2019-10-11 at 16:14 -0700, BulkMailForRudy wrote: Hello, > Thanks for the questions, good for me to think about it some more. > Short response: > > I don't think it is the FRR config, but the routes received that > are > crashing it or ospf6d has some other issue. FRR 7.1, the last release have a lot of ospf6d issues making it very unreliable. The only way to have reliable ospf6d is to keep quagga unfortunately. I have troubles in routes exchanges with ospf6d but never get daemon crash. On my loopback, I have an IPv4 address with /32 netmask and an IPv6 address with /64 netmask. If your configuration work fine with Quagga, and you add a router-id statement at the root of configuration (FRR have moved router-id statement outside of 'router ospf6' statement), it should work with FRR. If it didn't works, open a bug: https://github.com/FRRouting/frr/issues -- Nicolas DEFFAYET ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
netstat -ib Obytes empty for alias on main interface
Hi all, I want to know the total of bytes in and out of each IP address assigned as an alias to an bce0 interlace. if I run netstat -ib I get something like this: > netstat -ib NameMtu Network Address Ipkts Ierrs Idrop IbytesOpkts Oerrs Obytes Coll bce0 1500 78:2b:cb:71:aa:7f 1733163 0 0 199210984 1562794 0 339429658 0 bce0 1500 174.142.192.0 hostserver225655 - - 33210469 1588858 - 317543703 - bce0 1500 fe80::7a2b:cb fe80::7a2b:cbff:f 0 - - 00 - 0 - bce0 1500 174.142.193.5 jail19930 - - 5335770 - 0 - bce0 1500 174.142.193.5 jail2130567 - -2690495790-0 - bce0 1500 174.142.193.5 jail3 264 - - 140720 - 0 - bce0 1500 174.142.193.5 jail4 978747 - - 945046390-0 - bce0 1500 174.142.193.5 jail5 329095 - - 1173228430-0 - bce0 1500 174.142.193.5 jail6 260 - - 139980- 0 - bce0 1500 72.55.175.68/ jail7141953 - - 450704070-0 - ... ... lo1 16384 424903 0 0 30341272 424880 0 30338825 0 lo1 16384 172.16.13.0 172.16.13.1 30415 - - 2173077 30361 - 2172801 - lo1 16384 172.16.13.2/3 172.16.13.2 104842 - - 8848322 40993 - 3957589 - lo1 16384 172.16.13.3/3 172.16.13.3 8696 - - 351244 8668 - 349132 - lo1 16384 172.16.13.30/ 172.16.13.30344856 - - 23862253 344856 - 23862253 - I only have Input bytes per IP but not Obytes for the alias on bce0 but I do have the Ibytes and Obytes for the lo1 cloned interface, also any idea of how to avoid truncating the output, the network IP's display part of the IP not the full address, my idea is to use this output to create some stats. Any ideas ? thanks in advance. regards. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: netstat -ib Obytes empty for alias on main interface
Here is the output with a better formatting: http://pastebin.com/arrRsM78 What I would like to understand is why lo1 shows Obytes (incrementing) while bce0 IP's don't lo1 is a using NAT also the sum of lo1 (not including the Hi all, I want to know the total of bytes in and out of each IP address > assigned as an alias to an bce0 interlace. > > if I run netstat -ib I get something like this: >> netstat -ib > NameMtu Network Address Ipkts Ierrs Idrop > IbytesOpkts Oerrs Obytes Coll > bce0 1500 78:2b:cb:71:aa:7f 1733163 0 0 > 199210984 1562794 0 339429658 0 > bce0 1500 174.142.192.0 hostserver225655 - > - 33210469 1588858 - 317543703 - > bce0 1500 fe80::7a2b:cb fe80::7a2b:cbff:f 0 - > - 00 - > 0 - > bce0 1500 174.142.193.5 jail19930 > - - 5335770 - >0 - > bce0 1500 174.142.193.5 jail2130567 - > -2690495790-0 - > bce0 1500 174.142.193.5 jail3 264 > - - 140720 - > 0 - > bce0 1500 174.142.193.5 jail4 978747 - > - 945046390-0 - > bce0 1500 174.142.193.5 jail5 329095 - > - 1173228430-0 - > bce0 1500 174.142.193.5 jail6 260 > - - 139980- >0 - > bce0 1500 72.55.175.68/ jail7141953 - > - 450704070-0 - > ... > ... > lo1 16384 424903 > 0 0 30341272 424880 0 30338825 0 > lo1 16384 172.16.13.0 172.16.13.1 30415 - - > 2173077 30361 - 2172801 - > lo1 16384 172.16.13.2/3 172.16.13.2 104842 - - >8848322 40993 - 3957589 - > lo1 16384 172.16.13.3/3 172.16.13.3 8696 - > - 351244 8668 - 349132 - > lo1 16384 172.16.13.30/ 172.16.13.30344856 - > - 23862253 344856 - 23862253 - > > > I only have Input bytes per IP but not Obytes for the alias on bce0 but > I do have the Ibytes and Obytes for the lo1 cloned interface, also any > idea of how to avoid truncating the output, the network IP's display > part of the IP not the full address, my idea is to use this output to > create some stats. > > Any ideas ? > > thanks in advance. > > regards. > > > > ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: VirtualBox, if_bridge and bridged networking
Try creating a tap interface and later bridge your VM to that tap. in your host create a bridge containing re0 and tap0. regards. On 04/16/2013 09:31, Stefan Bethke wrote: > Hey, > > I'm a bit stumped getting a (FreeBSD guest) VM to use bridged networking to > work. The same VM works fine on a Mac OS X and an Ubuntu host, so I'm > certain it's not the VMs setting. > > I'm running > # pkg info -g virtualbox* > virtualbox-ose-4.2.6 A general-purpose full virtualizer for x86 > hardware > virtualbox-ose-kmod-4.2.6_4VirtualBox kernel module for FreeBSD > on FreeBSD 9.1-STABLE r249476 amd64. > > My LAN gets to the host via vlan1 (attached to re0); which in turn is bridged > via bridge0. IP configuration is on bridge0. > > It appears that frames sent from the guest make it to the host and machines > connected to the LAN, but no replies appear to be getting back to the guest. > I've tried bridging the guest to bridge0 as well as vlan1. > > If I configure the guest's network manually, I can see arp requests arriving > on the host and the LAN; inside the guest I can't see any frames arriving. > If I add arp entries manually on the guest, I can see pings going out, but > the replies never make it back. > > I am running pf, but I don't see any rejected packets of pflog0 that > correlate in any way. > > Is there a magic configuration bit that I'm missing? Or is there some > incompatibility between if_bridge and ng_ether? > > > Thanks, > Stefan > ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: VirtualBox + FreeBSD 9-STABLE == Frozen Ethernet
When using bridge mode, use tap interfaces otherwise you will get problems when using more than one VM. regards On 05/08/2013 03:49, Marc G. Fournier wrote: > On 2013-05-06 2:49 PM, Norbert Beckmann wrote: >> To Marc G. Fournier >> >> I do not think it's an issue with VirtualBox. I am running VirtualBox >> under Solaris. And I never had problems with it. >> Guests: ubuntu, Windows 7, Linux Mint, FreeBSD, Chrome OS. >> But the people of VirtualBox themselves state that Windows is somewhat >> delicate (don't remember whether they meant as guest or as host, I >> think both). >> Which would be comprehensible, because Windows has never become a real >> multi user / multi process system as Unix was by birth (nearly). >> I can neither help concerning the freezing Ethernet nor did I encounter >> similar things (as far as I remember). > My first thought is that its something in the vboxnet kernel module > when using a bridge ... I think the problem has been getting > progressively worse, with each upgrade, but since I upgrade both vBox > and the kernel in tandem, I'm currently working on going 'back in > time' with the code, see if I can find some 'stable point' ... > > If anyone with more knowledge can suggest any commands I can run to > provide debug info, or such ... ? I don't mind debugging, just dont' > know what to provide that is useful ... > > > ___ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
3Com OfficeConnect Wireless 108Mbps 11g XJACK PC Card
Hi all, I was using NDIS for a (ath0) wifi 3Com OfficeConnect Wireless 108Mbps 11g XJACK PC Card under 5.3-stable I upgraded my src and hove now 5.4-PRERELEASE but now the card is not working well, when I ping to my gateway I get very high response times and I start to loose conection. the card acts like if there where a very poor signal, any idea of what could it be wrong? regards. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
