On Wed, 21 Nov 2001, Greg Black wrote:
>
> I took the easy way out here and just ran
>
> ifconfig xl0 inet 10.0.0.1
>
Why put an IP address on it?
ifconfig xl0 up
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
> I want to add my encryption algorithm of ESP, an
> algorithm like DES, into FreeBSD kernel so as to make
> kernel recognize it. I added its definitions in
> /usr/src/sys/net/pfkeyv2.h, added specific functions
> implementation into /usr/src/sys/netinet6/esp.core.c
> and added a new subdirector
Mike Silbersack writes:
> > I have seen the problem occur on two different machines, one is running
> > code 4.3-STABLE FreeBSD 4.3-STABLE #0: Thu May 10 15:13:04 CST 2001
> > the other is 4.3-STABLE FreeBSD 4.3-STABLE #0: Mon May 28 16:10:27 CST
> > 2001 Both machines showed named requests taking
On Wed, 21 Nov 2001, Ian West wrote:
> I have seen the problem occur on two different machines, one is running
> code 4.3-STABLE FreeBSD 4.3-STABLE #0: Thu May 10 15:13:04 CST 2001
> the other is 4.3-STABLE FreeBSD 4.3-STABLE #0: Mon May 28 16:10:27 CST
> 2001 Both machines showed named requests
Dear all:
I encounter a problem that I cannot receive AppleTalk packets with NS
gigabit NIC.
I use the netatalk and it does work with Intel's 82544.
I find that the driver (if_nge.c) would drop the packets at line 1370.
if(!(rxstat & NGE_CMDSTS_PKT_OK)) {
ifp->if_ierrors++;
n
On Tue, Nov 20, 2001 at 08:45:31PM -0600, Mike Silbersack wrote:
>
> On Wed, 21 Nov 2001, Ian West wrote:
>
> > Hi, I have been looking at the code in ip_ouput in relation to a problem
> > I have had with named using the wrong route for talking to forwarders
> > after route changes occur. There
> Greg Black wrote:
> Now, the final question: I have to implement something similar
> on a 4.1-R system several thousand km away. There's no question
> of upgrading it from 4.1 and I can't afford to have it panic.
> Is it reasonable to expect that PPPoE will work OK provided I
> add the netgrap
Brian Somers wrote:
| > Dynamic loading of negraph modules is still broken, and probably won't be
| > fixed until 5.0 (at least that's what the comments on the zillion PRs
| > about this problem say.)
| >
| > Add 'options NETGRAPH_ETHER' and 'options NEGRAPH_SOCKET' to your kernel
| > config fil
On Wed, 21 Nov 2001, Ian West wrote:
> Hi, I have been looking at the code in ip_ouput in relation to a problem
> I have had with named using the wrong route for talking to forwarders
> after route changes occur. There is a check for cached routes, and a
> check for validity, but not as far as I
< said:
> I am looking at the ip_output routines, but so far cannot see any check
> for expiry of cached routes ? Can anyone point me in the right
> direction (or confirm they don't expire unless the route is physically
> unavailable ?)
Routes which are in use do not have timers on them, and the
Hi, I have been looking at the code in ip_ouput in relation to a problem
I have had with named using the wrong route for talking to forwarders
after route changes occur. There is a check for cached routes, and a
check for validity, but not as far as I can see a check for expiry.
The situation is
the way to debug this is to run tcpdump on the ethernet card in question
tcpdump knows how to interpret pppoe packets
and it's good to see what is coming over from the other end..
On Tue, 20 Nov 2001 [EMAIL PROTECTED] wrote:
>
> > What is happening is that when ppp starts on bootup (ppp -quie
>
> > What is happening is that when ppp starts on bootup (ppp -quiet -ddial
> > pppoe), the last entry is "dial -> carrier" and nothing else. Normally
>
> Looks like that the ethernet connection between your host and the modem is
> broken. I get the same message when I unplug my ethernet wire.
>
> Dynamic loading of negraph modules is still broken, and probably won't be
> fixed until 5.0 (at least that's what the comments on the zillion PRs
> about this problem say.)
>
> Add 'options NETGRAPH_ETHER' and 'options NEGRAPH_SOCKET' to your kernel
> config file and rebuild your kernel.
I
> What is happening is that when ppp starts on bootup (ppp -quiet -ddial
> pppoe), the last entry is "dial -> carrier" and nothing else. Normally
Looks like that the ethernet connection between your host and the modem is
broken. I get the same message when I unplug my ethernet wire.
Cheers
Mar
I'm trying to get mpd-netgraph to work so that I can log in to my ISP that
uses PPTP VPN software. I'e read the docs, writen a config file, but it
doesn't seem to be able to connect (or I think it connects, but doesn't
negotiate/authenticate). Stranger still is that when running mpd from the
I've got a bunch of FreeBSD 4.4 boxes doing PPPoE using netgraph and
PPP. They've been doing this quite happily for a few months, but now one
of the boxes is sick.
[ Disclaimer: I'm 150 miles away from the box, so I don't have exact log
messages. What you see below is my simple paraphrasing.
Dynamic loading of negraph modules is still broken, and probably won't be
fixed until 5.0 (at least that's what the comments on the zillion PRs
about this problem say.)
Add 'options NETGRAPH_ETHER' and 'options NEGRAPH_SOCKET' to your kernel
config file and rebuild your kernel.
--
Matthew Emme
18 matches
Mail list logo
