reachable from everywhere, so it
seems to work, but they cannot reach each other..
erich
sure.. my fault, just assume the networks are right.
and this is not my problem ;)
Alexander Hall schrieb:
Erich wrote:
hi,
is there a way to announce the same AS an different locations?
lets say 123.123.123.0/23 is mine and i want to have
123.123.123.0/24 @location1 and 23.123.124.0/24
Claudio Jeker schrieb:
On Tue, Feb 26, 2008 at 09:51:05AM +0100, Erich wrote:
hi,
is there a way to announce the same AS an different locations?
lets say 123.123.123.0/23 is mine and i want to have
123.123.123.0/24 @location1 and 23.123.124.0/24 @location2,
right now i have the problem
i now have a session i turned on update loging ob bpgd but the routes do not
get inserted. any ideas?
AS41412: update 123.123.123.0/24 via xxx..xx. ( the router where
the network is, yes pingable)
Erich schrieb:
Claudio Jeker schrieb:
On Tue, Feb 26, 2008 at 09:51:05AM +0100, Erich
yes thx guys, it worked :)
Claudio Jeker schrieb:
On Thu, Feb 28, 2008 at 08:14:09AM +0100, Erich wrote:
i now have a session i turned on update loging ob bpgd but the routes do
not
get inserted. any ideas?
AS41412: update 123.123.123.0/24 via xxx..xx. ( the router where
the
OSEN
and
responder_recv_HASH_SA_NONCE: peer proposed invalid phase 2 IDs:
initiator id 59caa34e: xxx.xxx.xxx.xxx, responder id 50be811a:
xx.xx.xxx.xxx
isakmpd is running with -Ka like suggested in man bgpd.conf and keys
have been copied to each side.
do i have anything forgotten?
Erich schrieb:
yes thx guys,
tic routes or is there a way to configure
stuff like that in bgpd?
thx in advance, erich.
Erich schrieb:
do i have to restart bgpd in order to get "ipsec esp ike" for a
session / nei working or is a reload and nei up/down enough?
i got
Oct 20 13:21:23 router-mt-1 isakmpd[13070]:
Claudio Jeker schrieb:
On Fri, Feb 29, 2008 at 02:10:09PM +0100, Erich wrote:
another routing problem ist that now the ibpg routes get insertet
but also announcend to the ebgp peer since its the same as and
i announce "self" to the ebgp peers. problems is now that the
network is
Mar 1 21:00:58 interoute bgpd[30449]: neighbor 10.65.0.6 (iBGP):
received notification: HoldTimer
expired, unknown subcode 0
Mar 1 21:10:26 interoute bgpd[30449]: neighbor 10.65.0.6 (iBGP):
received notification: HoldTimer
expired, unknown subcode 0
what does this mean?
erich
there was nothing in the logs of the peer router.
any other ideas howto debug/solve this?
Stuart Henderson schrieb:
On 2008-03-01, Erich <[EMAIL PROTECTED]> wrote:
Mar 1 21:00:58 interoute bgpd[30449]: neighbor 10.65.0.6 (iBGP):
received notification: HoldTimer
expired, unknown sub
hi,
if comment stuff like this in bgpd.conf(filter and a prefix but commented):
allow from 123.123.123.123 #prefix 194.123.123.0/24
is the whole line ignored?
erich
kind of ibgp with an route reflector? how would such a
setup look like?
thx in advance,
erich
fib couple
nothing helped so far, but a complete restart of the bgpd did it a last, is
this a normal behavior?
im using the bgpd version which was shipped with openbsd 4.0, a little bit
older, but did a good job so far.
mfg
erich
**
t to check?
mfg erich
+0200, Erich wrote:
hi,
i have successfully setup a carp setup with 10 carp devices. on box is
master and another box is backup, so if the master fails the backup box
takes over.
i have sysctl net.inet.carp.preempt=1 and the backup box announces with
"advskew 100".
most of the time
for all devices?
You might also want to set different passwords for each carp device,
just to go sure they don't interfere with each other.
krgds /markus
Erich wrote:
the backup system is in a state where the carp devices are in a
mixed state. carp3 and carp4 for example are still MASTE
}
if $carp_down
set-state backup
}
state backup {
init {
run "route delete -inet 192.168.0.0/24"
run "route add -inet 192.168.0.0/24 192.168.100.2"
}
if $carp_up
set-state primary
}
thx in advance
erich
closed: Operation now i
n progress
what is needed to do for debuging here?
erich
Peter Bristow schrieb:
Hi
I've had a couple of problems with OpenBGPD.
I have an Extreme Networks switch that has a session to 4.2-RELEASE and
4.3-RELEASE OpenBSD route servers.
1 of each. Today I saw both Ope
I am running current. For a few snapshots, sshd has been putting errors in
my authlog:
Sep 2 23:33:56 openbsd sshd[22922]: Server listening on 0.0.0.0 port 22.
Sep 2 23:33:56 openbsd sshd[22922]: Server listening on :: port 22.
Sep 2 23:34:01 openbsd sshd[28174]: rexec line 76: Unsupported opti
19 matches
Mail list logo
