This just keeps getting better :-)
Just after I sent the last message, I tried a traceroute that showed packets
going the wrong way. To my surprise (not) , the kernel routing table was once
again emptied of all BGP routes.
# netstat -rn | wc -l ; bgpctl show fib | wc -l
8
I added a simple "custom_options" field to /usr/local/pkg/openbgpd.xml and the
corresponding code to /usr/local/pkb/openbgpd.inc - although the modifications
are trivial, is there a correct way to submit a patch? (BTW: the $config
mechanism, coupled with the XML description files, looks quite s
2010/6/17 Adam Thompson :
>
> WTF is the garbage at the end of system.log?
>
It's a binary log, you can't tail it. Use clog -f
> One thing I do see (briefly!) in the routing table is a rather anomalous
> route for 192.139.69.160/28 via 192.139.69.161. > Which correlates perfectly
> with what H
Well, I'm seeing something similar but even odder.
The kernel route for the local subnet *appears* to be intact, but various
diagnostic tools seem to disagree on that.
The pfSense GUI page Diagnostics->Routes shows a fairly small IPv4 routing
table (20 routes including host routes for the LAN sub
On 06/17/2010 10:02 PM, Adam Thompson wrote:
So I've got OpenBGPd up and running fine on my pfSense 1.2.3-REL router (the
GUI makes setting things up so ridiculously simple it's amazing! Thanks, guys!)
but am now running into a secondary problem of some sort:
arplookup 192.139.69.161 failed: h
On Thu, Jun 17, 2010 at 04:46:00PM -0400, Chris Buechler wrote:
> On Thu, Jun 17, 2010 at 4:02 PM, Adam Thompson wrote:
> > So I've got OpenBGPd up and running fine on my pfSense 1.2.3-REL router
> > (the GUI makes setting things up so ridiculously simple it's amazing!
> > Thanks, guys!) but am
Adam Thompson wrote:
So I've got OpenBGPd up and running fine on my pfSense 1.2.3-REL router (the
GUI makes setting things up so ridiculously simple it's amazing! Thanks, guys!)
but am now running into a secondary problem of some sort:
arplookup 192.139.69.161 failed: host is not on local netw
Yes, it's the next-hop router on OPT1. It's also my BGP peer.
-Adam
--Original Message--
From: Chris Buechler
To: support list, pfSense
ReplyTo: support list, pfSense
Subject: Re: [pfSense Support] BGP & ARP problems
Sent: Jun 17, 2010 15:46
On Thu, Jun 17, 2010 at
On Thu, Jun 17, 2010 at 4:02 PM, Adam Thompson wrote:
> So I've got OpenBGPd up and running fine on my pfSense 1.2.3-REL router (the
> GUI makes setting things up so ridiculously simple it's amazing! Thanks,
> guys!) but am now running into a secondary problem of some sort:
>
> arplookup 192.139
So I've got OpenBGPd up and running fine on my pfSense 1.2.3-REL router (the
GUI makes setting things up so ridiculously simple it's amazing! Thanks, guys!)
but am now running into a secondary problem of some sort:
arplookup 192.139.69.161 failed: host is not on local network
arpresolve: can't a
10 matches
Mail list logo
