> I just noticed something else weird.
>
> I did "arp -a" on my bridge, and one of the entries was for the bridge
> itself.
>
> In other words, the bridge had an ARP entry telling it its own hardware
> address (on its external, "xl0" interface, in case it matters).
> The superfluous ARP entry wa
> Ok, mea culpa
>
> I figured it out..
> Luigi.. does this fix it?
Thank you.
This patch fixes my ARP problem.
--
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
[Please trim CC list as necessary]
Hello,
Before starting import process for smbfs, I would like to
introduce new API which greatly simplifies process of packaging data into
mbufs and fetching it back (in fact, similar API already presented in the
tree, but it is private to the n
Let me apologize in advance for this shoddyish bug report.
In a recent -stable (since the new ipfw fixes) if you build
a kernel with options:
IPFIREWALL
IPFIREWALL_VERBOSE
IPFIREWALL_DEFAULT_TO_ACCEPT
IPDIVERT
BRIDGE
DUMMYNET
You wind up with a kernel that doesn't grok the ipfw 'via' keyword.
i assume you have upgraded the .h files in
/usr/include/net and /usr/include/netinet and recompiled
the userland ipfw, right ?
your report is kind of strange because none of the recent
changes (unless you mean the tcp security fixes) involves
additional specifiers in ipfw rules.
Sure the ipfw st
* Luigi Rizzo <[EMAIL PROTECTED]> [010206 10:41] wrote:
> i assume you have upgraded the .h files in
> /usr/include/net and /usr/include/netinet and recompiled
> the userland ipfw, right ?
Yes, buildworld/installworld was done.
> your report is kind of strange because none of the recent
> change
If all you want is sort out the MTU mess, you only need to download the
latest ppp sources from Brian's site at:
http://www.Awfulhak.org/ppp.html
Compile, install, and include:
enable tcpmssfixup
in your /etc/ppp/ppp.conf.
--Renaud
- Original Message -
From: "John Telford" <[EM
* Boris Popov <[EMAIL PROTECTED]> [010206 03:51] wrote:
> [Please trim CC list as necessary]
>
> Hello,
>
> Before starting import process for smbfs, I would like to
> introduce new API which greatly simplifies process of packaging data into
> mbufs and fetching it back (in fact, sim
I agree with Luigi's sentiments on the current bridging vs. netgraph.
I'll be more than happy to switch over to using netgraph bridging, as
soon as it has the features I need -- specifically, firewall filtering
via ipfw, ipfilter, or something equivalent. Lack of filtering in the
current netgraph
Has anyone else encountered showmount returning connections that do not
exist?
I have kill'ed the portmap, nfs*, and mountd processes with no luck. I
have even rebooted and the same mount information shows up, although no
attempt has been made to mount the directories from remote. Further, any
ne
< said:
> Has anyone else encountered showmount returning connections that do not
> exist?
Since NFS is usually connectionless, the best `showmount' can do is to
tell you which clients have *ever* received the root file handle for
the given filesystem. (Until such time as that file system is
re
> > The BIOS trace says the PXE is revision 2.0, build 68 : is there some other,
> > perhaps better version of it ? (the on-board NIC on the machine is an fxp)
>
> Build 068 is a disaster; you ideally want 082 or later.
is there some standard way to upgrade the pxe code on the cards ?
in case, w
> > > The BIOS trace says the PXE is revision 2.0, build 68 : is there some other,
> > > perhaps better version of it ? (the on-board NIC on the machine is an fxp)
> >
> > Build 068 is a disaster; you ideally want 082 or later.
>
> is there some standard way to upgrade the pxe code on the cards
Hello,
I'm trying to use the pxeboot loader from 4.2-RELEASE, to diskless
boot some rack-mount PCs.
Using documentation from Alfred Perlstein and Mike Smith, I've configured
a DHCP server and a tftp server, and I'm still having problems
with at least one machine not being able to start each ti
>
> The BIOS trace says the PXE is revision 2.0, build 68 : is there some other,
> perhaps better version of it ? (the on-board NIC on the machine is an fxp)
Build 068 is a disaster; you ideally want 082 or later.
> PS : As I've seen, rc has been modified to get rid of
> "early_nfs_mounts". Aft
> I haven't tracked these changes, and am still using some slightly older
> rc files. I've updated my rc.diskless stuff to use mdconfig now though;
> if there's interest I'll put it up for review.
yes please... i'd like to fix things as needed so that
diskless scripts work correctly in our ne
well i just tested things here and everything works fine.
"via" rules are accepted. i have the same set of options
that you mentioned IPFW DIVERT open firewall dummynet and bridge.
This is on an essentially up-to-date STABLE (net/ and netinet/
are same as in -stable).
cheers
luig
Another thought about the "dueling ARP reply" issue.
In one way, I suppose it's not a serious problem, because even if
the "wrong" hardware address gets cached, packets still get through,
and communication is not cut off.
On the other hand, it =may= be a problem from a security standpoint.
Suppo
> Another thought about the "dueling ARP reply" issue.
people, it's a minor bug, i am looking into fixing it, just be patient.
Securitywise, also remember that all bridges or switches can 'leak'
packets to interfaces other than the one where the designated receiver is.
cheers
lu
Mike Smith ([EMAIL PROTECTED]) wrote:
> > > > The BIOS trace says the PXE is revision 2.0, build 68 : is there some other,
> > > > perhaps better version of it ? (the on-board NIC on the machine is an fxp)
> > >
> > > Build 068 is a disaster; you ideally want 082 or later.
> >
> > is there some
On Tue, 6 Feb 2001, Alfred Perlstein wrote:
> Looks really cool, I can't get to http://www.butya.kz/~bp/mbuf/,
> but from the examples it looks very useful.
Sorry, server was brought down and I wasn't notified :(. It should
be ok now.
> I was wondering if you planned or already had an A
Boris Popov wrote:
[...]
> Since currently there isn't many consumers of this code I can
> suggest to define an option LIBMBUF in the kernel configuration file
and
> add KLD libmbuf (with interface libmbuf), so kernel footprint will
not be
I am in favor of such an option on the condition th
Thanks, thats now my plan.
Thanks to the pointer from Matthew Emmerton to your articles too, good
stuff.
I also got a bigger hard drive because I will have to update this thing
sooner or later so may as well start off with enough drive space.
I now have a new easy question for you all, watch for i
Hi All
Is there any function in 'C' to get ethernet hardware address from IP
address (not only for interfaces on the same machine... For any IP
address), equivalent to 'arp' command on FreeBSD? If there isn't any such
function, can you suggest me any other way of achieving this?
NOTE: I am no
Hi
Could you tell me how to implement the callback mechanism in FreeBSD?
Thanks!
ChunAn Li
-
IP Specialist
Advanced Internet Technologies Group
Nokia Research Center, Communication Systems Lab/Beijing
Hou
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [010206 22:19] wrote:
> Hi
> Could you tell me how to implement the callback mechanism in FreeBSD?
see the signal manpage for an example of how to specify a callback
paramter.
--
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]
"I have the heart
At 23:42 6-2-01 -0800, Alfred Perlstein wrote:
>* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [010206 22:19] wrote:
> > Hi
> > Could you tell me how to implement the callback mechanism in FreeBSD?
>
>see the signal manpage for an example of how to specify a callback
>paramter.
When I read his question
Hi, I cvsupped today and got all of Luigi's commit [the one where he
does 1.16.2.13 of bridge.c alongwith a few others], I also have David
Malone's fix to syslogd.c [1.59.2.5]
If I don't have the following sysctl
net.inet.ip.fw.verbose_limit=10
then dmesg gets busted as mentioned earlier and if
28 matches
Mail list logo
