Thanks for your prompt repply.
> > I am actualy trying to establish the communication between a cisco router
> > and my Free BSD machine.
> >
> > +---+ +---+
> > | cisco |serial interface | FreeBSD 4.1 |
> > | 3600 +---+ |
> >
Hi, all
I have a lot of such messages in my log file.
What do they mean? Is it a harware problem?
( PPP is in MP mode. FreeBSD 4.0R)
Feb 18 16:54:51 smtp ppp[58]: tun0: Phase: 1: HDLC errors -> FCS: 2, ADDR: 0, COMD: 0,
PROTO: 0
Feb 18 16:55:52 smtp ppp[58]: tun0: Phase: 1: HDLC errors -> FCS
In article
[EMAIL PROTECTED]> you
write:
>Hi
>
>how could i modify the amount of the maximum routes that freebsd allow?
Add more memory.
--
Jonathan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
On Tue, 20 Feb 2001, Ingo Flaschberger wrote:
> Hi
>
> how could i modify the amount of the maximum routes that freebsd allow?
>
> i have seen, that with more memory i could use more routes.
> some results from me:
> ram routes
> 128mb 75k
> 196mb 110k
> 256mb 150k
>
> is it possible to
> I updated the source and rebuilt a 4.2-stable machine this past weekend.
>
> sysctl -w net.link.ether.inet.log_arp_wrong_iface=0 is located in rc.conf
>
> and running that on the command line shows it's value to be 0 however, i
> still receive messages like this.
>
> Anyone know why this sysc
Hi people!
I cannot get FreeBSD's PPP to work with Win2K dialout network connection.
It connects and configures OK (as far as I can say from logs and ipconfig)
but (almost) no packets manage to get across the link. From
Win95/Win98/WinME/FreeBSD all work fine.
I wonder if somebody has encountere
Hi
I am newbie. Would you tell me how to write a timer in FreeBSD user space ?
Br.
Li ChunAn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
I updated the source and rebuilt a 4.2-stable machine this past weekend.
sysctl -w net.link.ether.inet.log_arp_wrong_iface=0 is located in rc.conf
and running that on the command line shows it's value to be 0 however, i
still receive messages like this.
Anyone know why this sysctl variable stop
Jean-Christophe Varaillon wrote:
>
> Thanks for your prompt repply.
>
> > > This is what dmesg | grep sr1 shows:
> > >
> > > sr1: Adapter 0, port 1.
> > > sr1 XXX: driver didn't set ifq_maxlen
> > > sr1: transmit failed, ST0 80, ST1 48, ST3 0f, DSR 01.
> > > ...
> > > sr1: transmit fai
