On Wed, 03 Jan 2001 12:26:21 EST, Alex Pilosov wrote:
> Sometimes in the course of human events it is necessary to break with
> compatibility ;) I believe netgraph is sufficiently advanced and well-made
> system that it should be used as much as possible.
Microsoft might argue the same about Wi
On Wed, 3 Jan 2001, C. Stephen Gunn wrote:
> I agree that you could educate ifconfig in the ways of netgraph
> and hide it all behind the command interface you propose. It's a
> migration to a broader view of interfaces for ifconfig(8). Right
> now, ifconfig(8) is basically a front-end for ioct
On Wed, 03 Jan 2001 09:50:41 MST, Wes Peters wrote:
>> We're on the same page. I was just observing that it was a software change
>> to ifconfig. We're teaching it tricks about creating/associating netgraph
>> nodes with interfaces. Not just configuring interfaces.
>
> That *is* configuring i
"C. Stephen Gunn" wrote:
>
> On Tue, 02 Jan 2001 10:23:23 MST, Wes Peters wrote:
>
> > > Well.. It's a change to ifconfig for normal interface configuraton.
> >
> > No, what I'm saying is that ifconfig would look exactly like it does now
> > for standard IP-over-EthII and for vlan id, and would
-On [20010103 06:00], C. Stephen Gunn ([EMAIL PROTECTED]) wrote:
>On Tue, 02 Jan 2001 10:02:20 MST, Wes Peters wrote:
>
>> Sure, but it would be nice to take over ARP too.
>
>FWIW. Jeoren <[EMAIL PROTECTED]> was looking at the NetBSD
>media-independant arp code. I'm not sure what he learned.
I
On Tue, 02 Jan 2001 10:23:23 MST, Wes Peters wrote:
> > Well.. It's a change to ifconfig for normal interface configuraton.
>
> No, what I'm saying is that ifconfig would look exactly like it does now
> for standard IP-over-EthII and for vlan id, and would be extended to handle
> other configur
On Tue, 02 Jan 2001 10:02:20 MST, Wes Peters wrote:
> Sure, but it would be nice to take over ARP too.
FWIW. Jeoren <[EMAIL PROTECTED]> was looking at the NetBSD
media-independant arp code. I'm not sure what he learned.
- Steve
--
C. Stephen Gunn URL: http://www.wat
"C. Stephen Gunn" wrote:
>
> On Mon, Jan 01, 2001 at 11:24:41PM -0700, Wes Peters wrote:
>
> > > I'm afraid to even contemplate the POLA and backward compatability
> > > issues involved.
> >
> > Why would we need to violate POLA? The obvious default would be to
> > extend ifconfig to configure
Julian Elischer wrote:
>
> Wes Peters wrote:
> >
> > Doing link-layer encapsulation modules is really not very difficult.
> > I've written pretty much the full complement, covering ethernet (10,
> > 100, and 1000), FDDI/CDDI, token ring, ATM, and Frame Relay. (Chuck,
> > I can identify that prot
< said:
> box a multihomed host, not a VLAN forwarder/router. The latter
> would require a mechnism to bridge/forward/filter packets between
> independant 802.1q encapsulated interfaces.
We have that. They are just interfaces -- the kernel doesn't treat
them at all differently. (I can't speak
Thierry Herbelot wrote:
>
> Wes Peters wrote:
> >
> > Thierry Herbelot wrote:
> > >
> > > Wes Peters wrote:
> > > >
> > > [SNIP]
> > > >
> > > > Doing link-layer encapsulation modules is really not very difficult.
> > > > I've written pretty much the full complement, covering ethernet (10,
> > >
On Mon, Jan 01, 2001 at 11:31:17PM -0700, Wes Peters wrote:
> Sorry to reply to my own message, but another thought hit me. Now that
> the swelling has gone down, I thought I should share it:
>
> This might even give us a start at a sticky problem that has been bugging
> VLAN switch makers fro
On Mon, Jan 01, 2001 at 11:24:41PM -0700, Wes Peters wrote:
> > I'm afraid to even contemplate the POLA and backward compatability
> > issues involved.
>
> Why would we need to violate POLA? The obvious default would be to
> extend ifconfig to configure the new protocol types, and to assume
>
On Tue, Jan 02, 2001 at 06:50:46AM -0800, Julian Elischer wrote:
> > > For example, you would no longer simply ``ifconfig xl'', but
> > > associate a netgraph link-layer node on top of the xl interface,
> > > and a netgraph interface node on top of the link-layer node, which
> > > would function
On Tue, 2 Jan 2001, Julian Elischer wrote:
> Thierry Herbelot wrote:
> >
> > Wes Peters wrote:
> > >
> > What about a netgraph-enabled ATM NIC driver ? (this seems the missing
> > piece to get bridged Ethernet over RFC1483 encapsulation on ATM)
>
> Someone was going to do this but I think I sto
Thierry Herbelot wrote:
>
> Wes Peters wrote:
> >
> > Thierry Herbelot wrote:
> > >
> > > Wes Peters wrote:
> > > >
> > > [SNIP]
> > > >
> > > > Doing link-layer encapsulation modules is really not very difficult.
> > > > I've written pretty much the full complement, covering ethernet (10,
> > >
Thierry Herbelot wrote:
>
> Wes Peters wrote:
> >
> [SNIP]
> >
> > Doing link-layer encapsulation modules is really not very difficult.
> > I've written pretty much the full complement, covering ethernet (10,
> > 100, and 1000), FDDI/CDDI, token ring, ATM, and Frame Relay. (Chuck,
>
> What abou
"C. Stephen Gunn" wrote:
>
> On Sun, 31 Dec 2000 15:33:36 EST, Garrett Wollman wrote:
>
> > Actually, no, it's not what you want (although the underlying code is
> > broken enough to let it ``work'' anyway). What you want is to fix the
> > parent network interface driver to indicate its readine
Wes Peters wrote:
>
> "C. Stephen Gunn" wrote:
> >
> > On Sun, 31 Dec 2000 19:54:19 PST, Julian Elischer wrote:
> >
> > > > The current VLAN (and Ethernet) implementaiton in FreeBSD needs work.
> > > > FreeBSD should should handle multiple ethernet encapsulations on
> > > > the same physical inte
Alex Pilosov wrote:
>
> On Tue, 2 Jan 2001, C. Stephen Gunn wrote:
>
> > For example, you would no longer simply ``ifconfig xl'', but
> > associate a netgraph link-layer node on top of the xl interface,
> > and a netgraph interface node on top of the link-layer node, which
> > would function (mo
"C. Stephen Gunn" wrote:
>
> On Sun, 31 Dec 2000 19:54:19 PST, Julian Elischer wrote:
>
> > > The current VLAN (and Ethernet) implementaiton in FreeBSD needs work.
> > > FreeBSD should should handle multiple ethernet encapsulations on
> > > the same physical interface, and relay packets to/from
Wes Peters wrote:
>
> Thierry Herbelot wrote:
> >
> > Wes Peters wrote:
> > >
> > [SNIP]
> > >
> > > Doing link-layer encapsulation modules is really not very difficult.
> > > I've written pretty much the full complement, covering ethernet (10,
> > > 100, and 1000), FDDI/CDDI, token ring, ATM, an
Wes Peters wrote:
>
[SNIP]
>
> Doing link-layer encapsulation modules is really not very difficult.
> I've written pretty much the full complement, covering ethernet (10,
> 100, and 1000), FDDI/CDDI, token ring, ATM, and Frame Relay. (Chuck,
What about a netgraph-enabled ATM NIC driver ? (this
Wes Peters wrote:
>
> "C. Stephen Gunn" wrote:
> >
> > Netgraph is an excellent technology. While your comment makes
> > sense, there are several issues that will need to be addressed.
> > For instance, the current ARP implementation in FreeBSD is
> > entangled with the generic ethernet code.
>
"C. Stephen Gunn" wrote:
>
> On Sun, 31 Dec 2000 19:54:19 PST, Julian Elischer wrote:
>
> > > The current VLAN (and Ethernet) implementaiton in FreeBSD needs work.
> > > FreeBSD should should handle multiple ethernet encapsulations on
> > > the same physical interface, and relay packets to/from
On Tue, 2 Jan 2001, C. Stephen Gunn wrote:
> For example, you would no longer simply ``ifconfig xl'', but
> associate a netgraph link-layer node on top of the xl interface,
> and a netgraph interface node on top of the link-layer node, which
> would function (mostly) like xl does now.
Interesting
On Sun, 31 Dec 2000 19:54:19 PST, Julian Elischer wrote:
> > The current VLAN (and Ethernet) implementaiton in FreeBSD needs work.
> > FreeBSD should should handle multiple ethernet encapsulations on
> > the same physical interface, and relay packets to/from some subordinate
> > interface. This
"C. Stephen Gunn" wrote:
>
> On Sun, 31 Dec 2000 15:33:36 EST, Garrett Wollman wrote:
>
> > Actually, no, it's not what you want (although the underlying code is
> > broken enough to let it ``work'' anyway). What you want is to fix the
> > parent network interface driver to indicate its readine
On Sun, 31 Dec 2000 15:33:36 EST, Garrett Wollman wrote:
> Actually, no, it's not what you want (although the underlying code is
> broken enough to let it ``work'' anyway). What you want is to fix the
> parent network interface driver to indicate its readiness to receive
> 1522-octet frames by s
< said:
> Yes, ifconfig mtu 1500 is what you want.
Actually, no, it's not what you want (although the underlying code is
broken enough to let it ``work'' anyway). What you want is to fix the
parent network interface driver to indicate its readiness to receive
1522-octet frames by setting its i
On Fri, Dec 29, 2000 at 05:59:19PM +0100, Andrea Franceschini wrote:
> > There is a patch for the xl driver, which can be found on
> > http://www.physics.purdue.edu/~csg/FreeBSD/xl_vlan.patch
Eek! That's still up on the net? I left Purdue Physics back in
August.. ;-)
> flags=8843 mtu 1496
>
>
Ferdinand Goldmann wrote:
>
> Hello!
>
> On Thu, 28 Dec 2000, Andrea Franceschini wrote:
>
> > But all works only if the packets excanged are very small (like telnet
> > session) but when i try to get a stream of packet (web or ftp or even a
> > ls during a telnet session) it hangs.
> >
> > Ma
Hello!
On Thu, 28 Dec 2000, Andrea Franceschini wrote:
> But all works only if the packets excanged are very small (like telnet
> session) but when i try to get a stream of packet (web or ftp or even a
> ls during a telnet session) it hangs.
>
> Maybe this related to the MTU issue in vlan inter
On Thu, Dec 28, 2000 at 09:10:24PM +0100, Andrea Franceschini wrote:
> Hi!
>
> i'm trying to use ipfw-divert based nat deamon with vlan interfaces.
>
> i'm experiencing very strange problems.
>
> The configurations seems to work, the packets are correctly aliased
> (according to natd log) and i
Hi!
i'm trying to use ipfw-divert based nat deamon with vlan interfaces.
i'm experiencing very strange problems.
The configurations seems to work, the packets are correctly aliased
(according to natd log) and i can even ping or telnet to an external
host.
But all works only if the packets exca
35 matches
Mail list logo
