Dear LEAF list,
having upgraded from 2.3 to 3.0 Beta 2, I notice small quirk(?).
I am using the OpenVPN package from the ISO image and want to remove the
client config file, as I did on the 2.3 version.
When I do this (delete from /etc/openvpn/ and save config), I am
rewarded with a fresh
Bob
Bob von Knobloch wrote:
Dear LEAF list,
having upgraded from 2.3 to 3.0 Beta 2, I notice small quirk(?).
I am using the OpenVPN package from the ISO image and want to remove the
client config file, as I did on the 2.3 version.
When I do this (delete from /etc/openvpn/ and save
Hi All,
I can use the command rdate -p to get a valid time
using Debian, but when I use the same time server and
the same command with Bering-uClibc there is an error
message, saying my router was not allowed to connect.
Consequently, the corresponding function in the daily
cron-job fails
Mats
Mats Erik Andersson wrote:
Hi All,
I can use the command rdate -p to get a valid time
using Debian, but when I use the same time server and
the same command with Bering-uClibc there is an error
message, saying my router was not allowed to connect.
Consequently, the corresponding
Hi Erich, Bob,
Bob
Bob von Knobloch wrote:
Dear LEAF list,
having upgraded from 2.3 to 3.0 Beta 2, I notice small quirk(?).
I am using the OpenVPN package from the ISO image and want to remove the
client config file, as I did on the 2.3 version.
When I do this (delete from /etc/openvpn/
Erich Titl wrote:
Mats
Mats Erik Andersson wrote:
Hi All,
I can use the command rdate -p to get a valid time
using Debian, but when I use the same time server and
the same command with Bering-uClibc there is an error
message, saying my router was not allowed to connect.
Hi all Bering-users and in particular Erich Titl,
my problem with rdate has been solved since the
posting
of Erich Titl made thinking matters through. It turned
out I had forgotten it is port 37/tcp , i.e. time,
which is used by rdate. My focus was on ntp 123/tcp
all the time as I tried to
Hi Mats,
Hi all Bering-users and in particular Erich Titl,
my problem with rdate has been solved since the posting of Erich Titl made
thinking matters through. It turned out I had forgotten it is port 37/tcp
, i.e. time,
which is used by rdate. My focus was on ntp 123/tcp all the time as I
On the other hand, one interesting phenomenon did turn
up from this: every entry in shorewall.log reporting
REJECT TCP (whatever) 37
has time stamp Jan 1 00:00:00, but every entry
before and after retain very plausable time stamps.
Is this to be expected?
This has come up
Fellow Bering-users,
in case you will never use a floppy based Bering
system, please stop reading now in order not to waste
your time. Possibly, you could record for future use
that a maniac wrote something and you will be able to
find it in the list archive, should need arise. The
end
in case you will never use a floppy based Bering
system, please stop reading now in order not to waste
your time.
Up till Bering-uClibc 2.3x, I was still using a single /dev/fd0u1680! With the
arrival of 3.x, a single floppy is less useful and instead, I am using a CD Rom
and one single
Hi Mats
Mats Erik Andersson wrote:
Hi all Bering-users and in particular Erich Titl,
my problem with rdate has been solved since the
posting
of Erich Titl made thinking matters through. It turned
out I had forgotten it is port 37/tcp , i.e. time,
which is used by rdate. My focus was on
12 matches
Mail list logo
