8.1 bridge locking up

2010-10-16 Thread Aragon Gouveia
Hi, I have a FreeBSD 8.1-RELEASE-p1 system configured with two bridge interfaces. Every few hours or days the system stops responding or locks up. This is a system that had been running without problems before I upgraded it from a year old 8.0-STABLE a week ago. Most times when it locks up

please review my ppp(8) patch

2010-10-28 Thread Aragon Gouveia
http://www.freebsd.org/cgi/query-pr.cgi?pr=151400 ___ 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: please review my ppp(8) patch

2011-01-04 Thread Aragon Gouveia
*bump* On 10/29/10 02:17, Aragon Gouveia wrote: http://www.freebsd.org/cgi/query-pr.cgi?pr=151400 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-uns

FreeBSD 7 routing/ppp changed?

2008-06-26 Thread Aragon Gouveia
Hi, I recently migrated a 6.2 system to 7.0-STABLE. One of the system's functions was a PPPoE gateway that performed Proxy ARP for its PPP clients. In 6.2 days when a connection was made the route entry for the PPP client showed: 192.168.9.245 192.168.9.2UH 01 tu

iwn(4) doesn't like hardware RF switches

2009-07-06 Thread Aragon Gouveia
Hi, Is it just me, or does the iwn driver in -CURRENT not play well with hardware RF switches on notebooks? For me the only resemblence of an event I see is when I switch off RF - the kernel sends a log to syslog. wpa_supplicant doesn't pick it up, and neither does devd. The result is that

Re: iwn(4) doesn't like hardware RF switches

2009-07-07 Thread Aragon Gouveia
Paul B. Mahol wrote: The only way to handle hardware RF switch is via devd(8). ACPI notify devd(8) about state change and devd than can react on that change. iwn(8) can do nothing about this. What notebook do you have? Dell XPS M1330 Thanks, Aragon

anyone know libalias(3) well?

2009-07-31 Thread Aragon Gouveia
Hi, In sys/netinet/libalias/alias_db.c, SetStateIn() and SetStateOut() reference ALIAS_TCP_STATE_CONNECTED and ALIAS_TCP_STATE_DISCONNECTED. Does anyone know where/how these macros are defined? Thanks, Aragon ___ freebsd-net@freebsd.org mailing lis

mpd PPTP dropped packets

2004-07-13 Thread Aragon Gouveia
Hi, I'm having a wierd problem I can't seem to narrow down. I've tried posting to the mpd-users list, but didn't receive a response. Am hoping someone here can help me out. Here's a quick pic of my connectivity layout: Notebook <- ADSL -> VPN server <- Ethernet -> FTP server The notebook

Re: mpd PPTP dropped packets

2004-07-16 Thread Aragon Gouveia
Hey Archie, | By Archie Cobbs <[EMAIL PROTECTED]> | [ 2004-07-15 18:00 +0200 ] > Try applying these patches to the 4.10 machine and rebuilding mpd... > > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netgraph/ng_pptpgre.c.diff?r1=1.2.2.14&r2=1.2.2.15

Wierd tunnel+MTU issue

2004-09-20 Thread Aragon Gouveia
Hi, A while ago I setup a vtun tunnel between a FreeBSD 4.10-RELEASE machine and a 5.2.1-RELEASE-p9 machine. Initially everything appeared to work great, but I've just stumbled upon a seriously wierd problem that I can't figure out. I know this is not a support forum for the vtun package, but th

Re: Wierd tunnel+MTU issue

2004-09-21 Thread Aragon Gouveia
t; | [ 2004-09-21 08:02 +0200 ] > On Mon, 20 Sep 2004 20:44:31 +0200 > Aragon Gouveia <[EMAIL PROTECTED]> wrote: > > It looks like your PMTUD doesn't work. Have you somehow disabled > incoming ICMP traffic to the box you

Re: Wierd tunnel+MTU issue

2004-09-21 Thread Aragon Gouveia
| By Andre Oppermann <[EMAIL PROTECTED]> | [ 2004-09-21 10:51 +0200 ] > Could you please file a PR with all information you have provided so far > and your observations etc. Just merge your emails together and submit it > as text. Then give me the PR numbe

Re: Wierd tunnel+MTU issue

2004-09-21 Thread Aragon Gouveia
| By Andre Oppermann <[EMAIL PROTECTED]> | [ 2004-09-21 10:51 +0200 ] > You are onto something. It seems tcp_output() doesn't handle the error > cases it gets from ip_output() all too well these days. I suspect this > is the same problem we have in kern/71