Re: BSD / Firewall / 0 window size problem

On Tue, 16 Jul 2002, Alex Dyas wrote: > I've attached a tcpdump of a Linux machine doing the same thing > (working.txt). > > the same 0 sized window can be seen: > > 17:15:56.094161 linuxbox.foo.com.3479 > solarisbox.foo.com.telnet: . ack 456 > win 5840 (DF) [tos 0x10] > 17:16:12.634540 solaris

UDP broadcasts and delivery to sockets

Hi all, I'm working with a few others to get everything in gear for the network at QuakeCon (www.quakecon.org). One part of that event is a huge Bring Your Own Computer LAN with a 1250 PC capacity, for which we will provide a number of servers running a ton of gameservers. One problem we've h

Re: Inconsistency between net/if.c and several ethernet drivers

On Tue, 16 Jul 2002, Bill Baumann wrote: > > In net/if.c in a couple of places, the ethernet address is needed. This > is stored in the arpcom structure. A couple lines of code in if.c require > struct arpcom be at the very begining of device softc structures. Nearly > all drivers observe this

Re: ARP risks

Since it came up on this list... Barney - Forwarded message from Fr?d?ric Raynal <[EMAIL PROTECTED]> - Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm Precedence: bulk List-Id: List-Post: List-Help: List-Unsubscribe:

Inconsistency between net/if.c and several ethernet drivers

In net/if.c in a couple of places, the ethernet address is needed. This is stored in the arpcom structure. A couple lines of code in if.c require struct arpcom be at the very begining of device softc structures. Nearly all drivers observe this. However, several do not. Sadly, this includes t

Re: BSD / Firewall / 0 window size problem

Wrong - the packet you're interpreting as "not freeze up" is an ack. The next data packet, which is a window probe in both cases, shows about the same delay with both OS's. On Tue, Jul 16, 2002 at 04:24:56PM +, Alex Dyas wrote: > Mike Silbersack wrote: > >On Thu, 11 Jul 2002, Alex Dyas wrote:

Re: BSD / Firewall / 0 window size problem

Mike Silbersack wrote: >On Thu, 11 Jul 2002, Alex Dyas wrote: > > >>The only clue I've managed to find as to what is going on is in a tcpdump >>of >>the session (attached). The trigger for the lock up seems to be a >>messages >>from the Otherbox machine setting the window size to 0 : >> >>10:41

mpd and bringing up routes at connect time

Is there any way with mpd to automatically bring up a route when a customer connects using pptp where multiple users are connecting ? The problem I am running into is that user X will PPTP into the server. As they will come in on different netgraph interfaces, the route needs to be pointed t

RE: Crashes in fxp driver with polling enabled

On Tuesday, July 16, 2002 1:10 AM, Song Bo Run [mailto:[EMAIL PROTECTED]] wrote: > Hello, Guy > > Here we are encountering almost exactly the same problem as you are, > except that we are using OpenBSD. We have ported Luigi's polling code > to OpenBSD 2.9 and are using fxp driver. Our testing atta

vr driver

Has anyone fixed yet the vr 'driver' "watchdog timeout" bug in STABLE ? -- -- === Christophe Prevotaux Email: [EMAIL PROTECTED] HEXANET SARLURL: http://www.hexanet.fr/ Z.A.C Les CharmillesTel: +33 (0)3 26 7

FreeBSD+IPFILTER+PPPoE+DHCP problem

Hello, I installed FreeBSD-4.6 on HP Vectra PC. I configured this machine as NAT gateway. Connection diagram: LAN---FreeBSD IPFILTER/NAT/DHCPADSL modem-ISP PPPoE and IPFilter/NAT/DHCP working normal. Problem is Windows 95/98/98SE users can to go through FreeBSD gateway machine, bu