In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Claudio Jeker) writes:
Please send some more infos. What version are you useing (did you test
-current). Please show the config and necessary ospfctl output. The last
time I have issues like this was some time ago with point-to-point
Linden Varley [EMAIL PROTECTED] wrote:
Bringing up an old-topic here, but just letting everyone know
I have the exact same problem. It occurs quite often.
Surely we can't be the only two people seeing this issue?
It's quite fundamental to ospfd working properly..
-Paul-
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Paul Civati) writes:
This ospfd talks to the loopback interface on a JunOS box.
For sake of clarity, over a normal ethernet interface, no PtP.
-Paul-
I have a fairly simple set-up, where I have ospfd announcing
a few routes to a Juniper router.
Twice now, when the Juniper has been unreachable and has then
come back on-line, the ospf routes have not reconverged on
the Juniper end.
It has taken a restart of the OSPF on the Juniper to resync
the
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Stuart Henderson) writes:
4.1 has ospfctl reload which does this for vlan, I am not convinced
it works for carp* yet but haven't had chance to investigate (I only
noticed today).
Just tested but it doesn't work for vlan with me on 4.1
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Paul Civati) writes:
With ospfd running I create new vlan and carp interfaces and assign
IP addresses.
Currently, unless I restart ospfd these are not picked up.
(This is on 4.0 release).
Of course, as soon as I mail this, I read
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Reyk Floeter) writes:
2000 and XP will support authentication using X.509 (ie. SSL
like) certificates, only XP will support PSK (pre-shared-key).
i won't necessarily defeat windows, but 2000 and xp do support
kerberos 5, x.509 _and_
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Reyk Floeter) writes:
My understanding is, if you want to support the simple connection
of Windows clients, using the built-in VPN connector (eg. control
panel - network - make new connection - VPN - L2TP), the
server side needs:
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Bryan Irvine) writes:
Also[1], there may be the need for an occasional connection from users
just using the windows vpn client. Anybody doing this? I rarely even
see windows so I'm not sure what to look for there.
Do I need to import
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (C. Bensend) writes:
Needed:
* 1+ PCI-X slot, 64-bit 133MHz (one required)
* Intel Pentium IV, don't care what socket
* Minimum 2GB RAM capacity
* PC3200 RAM, if possible (already have 1GB stick just sitting around)
Supermicro
In article [EMAIL PROTECTED],
[EMAIL PROTECTED] (Chris Cappuccio) writes:
I haven't had good luck with AMD64 so far. The server I built not
a year ago has had more kernel panics and funky-ass behavior than
Be careful about what kind of motherboard and RAM you buy in the future...
11 matches
Mail list logo
