Since it deserved recognition, here's the bit from if_rl.c that John is
referring to:
* The RealTek 8139 PCI NIC redefines the meaning of 'low end.' This is
* probably the worst PCI ethernet controller ever made, with the possible
* exception of the FEAST chip made by SMC. The 8139 supports bus
Ermal is probably on the right track. Working in a load balanced
environment I've personally done three contiguous /20 blocks using
three loopback interfaces on linux hosts. I'd imagine that FreeBSD
should behave similarly. The only fancy thing the load balancer did
was as packets destined for one
Hello FreeBSD-Net,
Every once and a while I run into an issue wherein the symmetric NAT of pf
causes me grief. I've found some older mailing list entries asking about PF
and Cone or Full Cone NAT (such as this one from 2005:
http://www.mail-archive.com/freebsd-pf@freebsd.org/msg00804.html), but I
ting our ISP to route a /29
to their house and using binat (I already have a /29), but it would be nice
if there was the option to use 'nat on $wan_if from -> ($wan_if)
full-cone' in a ruleset to achieve the correct behaviour.
On Mon, Apr 30, 2012 at 1:45 AM, Darren Pilgrim wrote:
&g
Alright, here's a copy of my pf.conf:
http://pastie.org/private/yt7h3erbowgg4pf5v7fh5a
As for patches... unfortunately I'm not too sharp with C.
On Mon, Apr 30, 2012 at 10:24 PM, Darren Pilgrim
wrote:
> On 2012-04-30 17:44, Michael MacLeod wrote:
>
>> At the end of the da
Actually, multiple routing tables is the correct solution. I documented it
here:
http://www.mmacleod.ca/blog/2011/06/source-based-routing-with-freebsd-using-multiple-routing-table/
>From the post: "... But route-to and reply-to do not trump the default
routing table for traffic that originates or
I use pf+ALTQ to achieve some pretty decent traffic shaping results at home.
However, recently signed up to be part of an IPv6 trial with my ISP, and
they've given me a second (dual-stacked) PPPoE login with which to test
with. The problem is that the second login lacks my static IP or my routed
/2
On Fri, Jul 1, 2011 at 1:20 AM, Julian Elischer wrote:
> On 6/29/11 11:28 AM, Michael MacLeod wrote:
>
>> I use pf+ALTQ to achieve some pretty decent traffic shaping results at
>> home.
>> However, recently signed up to be part of an IPv6 trial with my ISP, and
>> t
I merged both of your responses below, so that the thread doesn't get
fragmented.
On Sat, Jul 2, 2011 at 4:07 AM, Julian Elischer wrote:
> **
> On 7/1/11 12:59 AM, Michael MacLeod wrote:
>
> On Fri, Jul 1, 2011 at 1:20 AM, Julian Elischer wrote:
>
>> On 6/29/11 11:28
Hello all,
I've got two DSL lines running to my house, and two WAN NIC's
installed in my FreeBSD router. I've been trying to get multilink ppp
working through my ISP (TekSavvy in Canada) for the last little while,
with mixed results. Each of my DSL lines sync's at 6016 kbits down and
800 kbits up.
On Jan 16, 2008 2:17 AM, Julian Elischer <[EMAIL PROTECTED]> wrote:
> 1/ when downloading, does the load on each incoming interface
> (I assume you have one ethernet to each modem) match?
This is a pretty rough way to estimate it, but starting/stopping
tcpdump on each of the interfaces at the same
On Jan 16, 2008 5:04 AM, Nikos Vassiliadis <[EMAIL PROTECTED]> wrote:
> On Wednesday 16 January 2008 09:44:05 Michael MacLeod wrote:
> > On Jan 16, 2008 2:17 AM, Julian Elischer <[EMAIL PROTECTED]> wrote:
> > > 1/ when downloading, does the load on each incoming inte
On Jan 16, 2008 5:21 PM, Alexander Motin <[EMAIL PROTECTED]> wrote:
> Mpd supports both. There were some mistakes in multilink transmission
> part of ng_ppp kernel module working in splitting mode that in some
> cases could lead to ineffective packet distribution, but they were fixed
> 8 months ago
On Jan 19, 2008 5:23 PM, Alexander Motin <[EMAIL PROTECTED]> wrote:
> This config is not completely correct for multilink case since
> mpd-4.0rc1 due to changes:
> - Auth configuration (set auth ...) moved from bundle layer to lcp. It
> works per link now.
> - Default argument of open/close com
I figured out the real source of the problem. Turns out Bell went and
screwed up the lantern test mappings on my connections, and dropped
the profile on one of them to 3 megabits (which I didn't know because
the lantern was mis-mapped). So I've spent the last several weeks
racking my brains trying
15 matches
Mail list logo
