On Tue, 5 Nov 2002, Andre Oppermann wrote:
It's time to change /etc/namedb/named.root.
I'm planning to do it tomorrow morning. They haven't actually loaded the
new zone yet, and probably won't till sometime near or after 3am
California time.
Doug
To Unsubscribe: send mail to [EMAIL
Hello.
I set up a machine to accept dial-in modem connections according to the suggestions in
the Handbook:
_ I set up my modem so as to lock its speed, don't echo commands, don't give any reply
code and auto-answer;
_ I modified rc.serial so as to set-up /dev/ttyd0 as a modem at 57600 bps;
_
After installing mpd-3.10
and using in mpd.conf:
set iface mtu 1400
XP works fine and fast.
There is no some tuning on the WinXP client I was make.
Many thanks for all.
Dmitry.
- Original Message -
From: Julian Elischer [EMAIL PROTECTED]
To: Dmitry A. Bondareff [EMAIL PROTECTED]
Cc:
FreeBSD 4.7-RELEASE
MPD-3.10
mpd.conf:
default:
load client1
client1:
new -i ng0 pptp0 pptp0
load client_standard
client_standard:
set iface disable on-demand
set iface enable proxy-arp
set iface idle 600
set bundle enable multilink
Hi,
Same pattern of garbage when pressing a key usually means wrong speed
in most cases, or parity/stop/start/data bits. It could be your serial
port or your modem at your end or remote end. Next time try and use -s
115200 with cu. That would set the serial port speed at 115200 and see
hey guys
we had a power cut yesterday..all went down at our home..
when we got electricity back, my internet wouldnot work..only my computer
atually..i found that my eth. card would not turn on..or actually i just
foung out now..it does turn on until it get to the 'dhclient dc0' lne in
From: alexis georges [mailto:floating_in_space_;hotmail.com]
hey guys
we had a power cut yesterday..all went down at our home..
when we got electricity back, my internet wouldnot work..only
my computer
atually..i found that my eth. card would not turn on..or
actually i just
foung out
http://www.freebsd.org/~sam/network.patch.gz
has a patch that contains a bunch of changes to the network interface layer
and related drivers. These changes are intended to reduce incompatibilities
between freebsd and netbsd so that work can be more easily exchanged/shared.
In particular, this
I am not sure if I am doing something completely wrong of if I have
found some sort of bug here, but I thought I would toss it out to see if
anyone else has ever seen this.
I have two ports on my switch configured for vlan id 5. Port 1 is
untagged and port 2 is tagged. The machine A is on port
Line:
It shows the frame leaving as vlan 2 (0x0020) (correct) ...
Should read:
It shows the frame leaving as vlan 2 (0x0002) (correct) ...
Sorry,
Jake
Jacob S. Barrett wrote:
I am not sure if I am doing something completely wrong of if I have
found some sort of bug here, but I thought I would
** Reply to note from Lefteris Tsintjelis [EMAIL PROTECTED] Tue, 05 Nov 2002
14:42:44 +0200
Hi,
Thanks a lot, this solved it, at least for now. However I'm quite sure that this will
happen again, so I'd like to
go through it all in order to solve it for good sooner or later.
Same
While it's important to make the change eventually, there is no
need to panic - named.root is used only at named start, and is
soon replaced internally by the actual list of roots. Also, named
works fine as long as at least one root's address is correct.
Also, the old address will continue to
Yeah, looks like they are 12 bits. I should I thought of that since the
Summit has a range of 0-4095 vlan IDs, which is 12 bits. So that
explains the chopping. Now if I can just solve the swapping all should
be good!
Thanks,
Jake
Barney Wolff wrote:
Dunno about the byte-order issue, but
Hi!
I am running FreeBSD 4.7-release and try to use ATEN UC10T USB-to-Ethernet
adapter. Unfortunately it causes my system to print something like:
kue0: watchdog timeout
kue0: usb error on tx: TIMEOUT
following by freeze. I got this problem while forwarding 50pps/64kbit UDP
packet stream which
Barney Wolff wrote:
While it's important to make the change eventually, there is no
need to panic
Umm.. yes, I know that. :) It's why I haven't made the change yet.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-net in the body of the message
Dear Hackers,
I would like to get some feedback on the idea i have.
Basically i would like Netgraph system to send kevents
whenever something happens. For example:
1) node X of type Y was created/destroyed
2) hook X was connected/disconnected to/from node Y
3) Data passed via hook X
4) Node X
Iasen Kostov writes:
As I experience system crushes at time of mbufs exhaustion I've compiled
a debug kernel and traced the problem. I seems the NFS functions
(nfsm_rpchead, nfsm_reqh ...) does *NOT* chek if they really have
allocated memory by MGET macro.
No check is necessary if M_WAIT is
Dmitry A. Bondareff writes:
Nov 5 14:30:46 wall mpd: [pptp0] exec: 1400 ng0 inet 1.1.1.1 10.0.2.2 user
Nov 5 14:30:46 wall mpd: [pptp0] exec: command returned 32512
This is a (harmless) bug in mpd 3.10, fixed by the patch below.
-Archie
It's not a bad idea.
On Tue, 5 Nov 2002, Maksim Yevmenkin wrote:
Dear Hackers,
I would like to get some feedback on the idea i have.
Basically i would like Netgraph system to send kevents
whenever something happens. For example:
1) node X of type Y was created/destroyed
2) hook X was
On Tue, 5 Nov 2002, Maksim Yevmenkin wrote:
Archie Cobbs wrote:
Maksim Yevmenkin writes:
I would like to get some feedback on the idea i have.
Basically i would like Netgraph system to send kevents
whenever something happens. For example:
1) node X of type Y was
From: Jason Carroll [EMAIL PROTECTED]
Hi Everyone--
Has anyone had trouble with gigabit (copper) interfaces dropping
multicast traffic? I've tried two different cards on both FreeBSD 4.5
and 4.7 and seen an alarmingly high loss of data over the gigabit
interface, even when the gigabit
Hi all,
I'm having problems setting my box as an ipv6 router. It's already
doing 6to4 using the following configuration without problems.
ipv6_enable=YES
ipv6_defaultrouter=2002:c058:6301:: # Use this for 6to4 (RFC 3068)
ipv6_prefix_xl1=2002:5143:8351:
Well it is a bug in the em driver. It works fine on the fxp device. I
am trying to debug and patch myself, but I am not familiar with the
driver code so it is slow going. If anyone has any pointers on where
exactly to focus or anything at all please let me know.
For the short term I have
Well I think I fixed it. It works for my card atleast. I am not sure
the of the correct route to get this checked and corrected in the main
source tree. Seems like such a simple fix but it may only work for the
chipset that I have, 82543, so someone should check on other chipsets.
24 matches
Mail list logo