Hi folks,
I plan to make an edge router out of a freebsd system with OpenBGPD +
FreeBSD 10, or such.
I've been reading up, and noticed that the net.inet.ip.fastforwarding
flag provides rather nice performance benefits.
My issue is, my upstream networks insist on using TCP MD5 authentication
Thank you for responding!
On 9/21/2014 午後 07:26, Ermal Luçi wrote:
If for you is an option pfSense has all the hard work done for you and
you can use it for such installations.
On Sun, Sep 21, 2014 at 12:08 PM, Paul S. <mailto:cont...@winterei.se>> wrote:
Hi folks,
I plan to
Interesting.
Would you happen to know where I could obtain sources to their version
of OpenBGPD, then?
Thanks!
On 9/21/2014 午後 07:35, Ermal Luçi wrote:
On Sun, Sep 21, 2014 at 12:31 PM, Paul S. <mailto:cont...@winterei.se>> wrote:
Ermal,
I'd prefer a raw BSD inst
to configure the SPDs.
Cheers!
On 9/21/2014 午後 07:35, Ermal Luçi wrote:
On Sun, Sep 21, 2014 at 12:31 PM, Paul S. <mailto:cont...@winterei.se>> wrote:
Ermal,
I'd prefer a raw BSD installation (Call it a comfort thing, if you
will).
Has the pfSense project ac
Hi,
I've been deploying FreeBSD as customer edge routers for customers with
sites that do not require high throughput (>1g/s).
Each site has two ISPs (Mostly Telstra + Verizon/Optus), and take full
routes via OpenBGPd and BIRD. I use next-hop self on all received routes.
The FreeBSD boxes h
Joe,
That was it, thank you! I looked over net.inet.ip and ip6, icmp never
crossed my mind.
George, thank you as well.
On 3/10/2015 午後 11:40, Joe Holden wrote:
On 10/03/2015 13:16, George Neville-Neil wrote:
On 10 Mar 2015, at 11:26, Paul S. wrote:
Hi,
I've been deploying FreeB
Hi,
Seeing this on 10.1-release p5.
FreeBSD ipfw-0.syd.fqdn.tld 10.1-RELEASE-p5 FreeBSD 10.1-RELEASE-p5 #0
r278455: Mon Feb 9 07:18:21 UTC 2015
r...@ipfw-0.syd.fqdn.tld:/usr/obj/usr/src/sys/qfkern amd64
Basically, I have a static arp entry that I cannot remove. This in
itself is not a pro
I just noticed that when obfuscating the IP, I added two dots.
Please excuse them, the IP is proper (110.62.211.87 for the purposes of
this thread)
On 3/19/2015 午前 11:20, Paul S. wrote:
Hi,
Seeing this on 10.1-release p5.
FreeBSD ipfw-0.syd.fqdn.tld 10.1-RELEASE-p5 FreeBSD 10.1-RELEASE-p5
van Gyzen wrote:
On 3/19/2015 午前 11:20, Paul S. wrote:
root@ipfw-0:~ # arp -d 110.62..211.87
arp: writing to routing socket: Invalid argument
I have a vague memory of similar behavior when I had a misconfigured
route. I think there was a route for a local interface address with an
off-box gateway
Additionally, pmacct doesn't seem to really work in FreeBSD -- as far as
the latest versions go.
Their use of 'return' (with no args) on functions that are meant to
return an int flat out makes it unable to compile on FreeBSD.
If you fix those by hand, it compiles, but just seems to segfault
Can confirm that anything to do with netif restart on a forwarding
interface also creates the same problem.
On 4/25/2015 午前 01:46, Nikos Vassiliadis wrote:
Hi,
Just saw this. Can somebody re-produce this?
root@m4fh2:~ # sysctl net.inet.ip.forwarding
net.inet.ip.forwarding: 1
root@m4fh2:~ # i
On my production systems, I've never seen it deviate without hardware
changes.
Are you seeing otherwise?
On 6/29/2015 午後 04:23, Wei Hu wrote:
Hi,
On a FreeBSD system with multiple NICs, ie, multiple MAC addresses, is there a
way to keep the same network interface name to MAC address mapping
12 matches
Mail list logo
