Linux-Networking Digest #81, Volume #11           Sat, 8 May 99 12:13:24 EDT

Contents:
  ? loopback: ping `hostname` (jianhong)
  Re: Redhat 6.0... the good, the bad, and the ugly (James Stafford)
  Kernel2.2.6 + SMB and AppleTalk (KLaus Vonstadl)
  Connect Linux box with Win95 using TCP/IP ([EMAIL PROTECTED])
  Re: fetchmail works -- but so does sendmail (Simon Child)
  diald/ppp dialing different phone numbers ("Tim Underwood")
  help needed configuring ip masquerade for debian - shaw@home (Constantine 
Karbaliotis)
  Re: viewing Linux Xserver Xfree86 on NT ? ("Michael P. Meyer")
  Re: ipfwadm and RedHat 6.0 (root)
  Re: Need Apache DB Advice ("Michael Taylor")
  .Shtml problem (Benjamin John)
  Re: Making Outlook Express work with Qmail ("Ryan Cleary")
  Re: Trying to get my new linux system to talk to @home (Mike Kerr)
  Re: ipfwadm and RedHat 6.0 (root)
  Re: Samba - Novell shareable flags, HOW? ("d. martin")
  Innd Access File..  ("Doug Pitek")
  Traffic Monitoring ("Rene Nieuwendijk")
  Re: How to make a linuxbridge bridge it's own traffic? (Vidar Andresen)

----------------------------------------------------------------------------

From: jianhong <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,comp.os.linux.misc
Subject: ? loopback: ping `hostname`
Date: Sat, 08 May 1999 01:43:02 -0700

Hello, Everyone,

I'm trying to get loopback to work on a stand alone machine, called
"slackbox",
with no network card, running slackware 3.5 Linux. My /etc/hosts is like
this,
#/etc/hosts
127.0.0.1     localhost    loopback
172.16.1.1   slackbox

`ping localhost` and `ping loopback` worked just fine, however,
`ping slackbox` FAILED with the error, "... network unreachable".

Can someone please enlight me on how to get this to work?
How do I let the computer loopback by referencing the hostname, i.e.,
        ping   `hostname`
        -------------------
By the way, slackware 3.5 doesn't support `ifconfig dummy ...`.

TIA.   Jianhong


------------------------------

From: James Stafford <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware,comp.os.linux.setup
Subject: Re: Redhat 6.0... the good, the bad, and the ugly
Date: Sat, 08 May 1999 02:00:58 -0700

Bill Unruh wrote:

> In <7go4ns$4oq$[EMAIL PROTECTED]> "Robert Brown" <[EMAIL PROTECTED]> writes:
>
> >Where is everyone getting RH6.0? I thought it wasn't available until the
> >10th May....
>
> Nope been out at least a week by now.
> www.redhat.com and all its mirrors. The pressing shops probably will not
> be shipping for another week however.

I was just at Fry's today and they had it there for$79.00 !!! That's more than I
paid for Winblows, more worth it... but still!!!

jamess


------------------------------

From: KLaus Vonstadl <[EMAIL PROTECTED]>
Subject: Kernel2.2.6 + SMB and AppleTalk
Date: 6 May 1999 11:32:35 GMT

Since I upgraded my Linux-PC with a second Processor 
(Kernel 2.2.6 with SMB), the netatalk-kit won't work anymore.
If boot with kernel without SMB-feature, it works.

If I boot with kernel with SMB support; the atalkd 
writes some error-lines in the logfile: 
"atalkd: setifaddr: function permitted..."
"atalkd: child exits with 1"

Thanks, 
Klaus

==================  Posted via SearchLinux  ==================
                  http://www.searchlinux.com

------------------------------

From: [EMAIL PROTECTED]
Subject: Connect Linux box with Win95 using TCP/IP
Date: Sat, 08 May 1999 13:06:42 GMT

I am trying to connect a Linux and a win95 box using TCP/IP. However, I have
not been able to connect the two. Both machines have working ethernet cards
and have the correct drivers installed. I think my main problem is
configuring the Linux side. I have read the NET-3-HOWTO, but it hasnt helped
me. In anycase, here is how I set up the linux side:

ifconfig lo 127.0.0.1
route add 127.0.0.1
ifconfig eth0 192.168.0.1
ifconfig eth0 netmask 255.255.255.0
ifconfig eth0 broadcast 192.168.0.255
route add 192.168.0.0 device eth0

After doing this, I cant't even ping 192.168.0.1

Anyway, on the Win95 side, I have assigned it IP 192.168.0.2, and
assigned the gateway as IP 192.168.0.2. The Win95 box can ping itself but not
the linux box.

Can someone please explain what I am doing wrong? Thanks!
Rob

============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/       Search, Read, Discuss, or Start Your Own    

------------------------------

From: [EMAIL PROTECTED] (Simon Child)
Crossposted-To: uk.comp.os.linux,demon.ip.support.unix
Subject: Re: fetchmail works -- but so does sendmail
Date: 8 May 1999 12:06:41 GMT

On Sat, 08 May 99 10:32:28 GMT, Phil Hunt <[EMAIL PROTECTED]> wrote:

>I've tried not running sendmail, but this is no good because it causes
>fetchmail to stop working too (fetchmail tries to deliver its mail to 
>sendmail). There's nothing in the Demon section of the fetchmail FAQ,
>either.

Instead of starting sendmail from /etc/rc3.d/init.d or wherever Suse
does it, start it in /etc/inetd.conf with a -bs switch and it will
receive mail from fetchmail but not from Demon.

-- 
Simon Child       Spam trap in Email Address.
Send email to simon.at.child.demon.co.uk  (Replace .at.)
Send spam to [EMAIL PROTECTED]

------------------------------

From: "Tim Underwood" <[EMAIL PROTECTED]>
Subject: diald/ppp dialing different phone numbers
Date: Fri, 7 May 1999 21:34:15 -0500

Is it possible to get diald to dial different phone numbers, depending on
the destination address?

In other words, if I start up a telnet connection to a host at 172.16.1.1,
can I configure diald to dial a specific ppp configuration for that target
address, and another ppp configuration for anything else???



------------------------------

From: Constantine Karbaliotis <[EMAIL PROTECTED]>
Subject: help needed configuring ip masquerade for debian - shaw@home
Date: Sat, 08 May 1999 13:26:20 GMT

This is a multi-part message in MIME format.
==============F353B7285BAED6121D81314F
Content-Type: text/plain; charset=us-ascii; x-mac-type="54455854"; 
x-mac-creator="4D4F5353"
Content-Transfer-Encoding: 7bit

I am configuring a Mac II to do ip masquerading (which will pretty much
be its only purpose) to share my @Home connection. I am running the
Debian distribution for m68k, 2.0.36 -990223 kernel. I am have been
plugging away at this project for at least two months on and off; the
problem is that I can't find adequate directions for the Debian
distribution. I would erally appreciate some direction from people in
this newsgroup.

I think I can figure out the routing and IP masquerading, but the DHCP
configuration still escapes me. Too many of the documents refer to and
assume RedHat distributions. They either assume you have X running to
configure it  or tell you to edit files in places that do not exist (it
seems) on a Debian machine (such as
/etc/sysconfig/network-scripts/ifdhspc-done). I tried to get X running
on my machine solely for the purpose of simplifying configuration; that
proved to have configuration problems too, which still have no
resolution (maybe upgrade the frame-buffer software--easy once it is on
the net!). I gave up on that and resigned myself to figuring it out
using a command line interface.

At this point I can have both ethernet cards be pinged over the network;
I can set up route to permit this. I could not make eth1 acquire an ip
using dhcpcd; I thought it was because the kernel autodetected only eth0
(I could enable eth1 from the command line using ifconfig), so I
switched all the references to make eth0 be the connection to the
outside world, and eth1 be the connection to the internal network (using
192.168.1.1). Again, this works and I can ping both cards; but only if I
have given eth0 a static address of 10.0.0.1. No way, no how can I make
eth0 get its address from dhcp. The dhcpcd config file has IFACE=eth0;
the material on DHCP at
http://metalab.unc.edu/LDP/HOWTO/mini/DHCP-3.html suggests that in the
Debian installation, that no configuration is otherwise necessary.

At the same time, assigning the ip that is currently being assigned by
the dhcp server using ifconfig--treating it as  a static ip-- doesn't
seem to allow me to connect to the internet, even to test the
connection. So why doesn't it connect to the DHCP server? I need a
better reference that the man page for dhcpcd, or else some good
examples/directions from some of you good folks.

==============F353B7285BAED6121D81314F
Content-Type: text/x-vcard; charset=us-ascii;
 name="constantine.k.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for Constantine Karbaliotis
Content-Disposition: attachment;
 filename="constantine.k.vcf"

begin:vcard 
n:Karbaliotis;Constantine
x-mozilla-html:FALSE
adr:;;;;;;
version:2.1
email;internet:[EMAIL PROTECTED]
x-mozilla-cpt:;3
fn:Constantine Karbaliotis
end:vcard

==============F353B7285BAED6121D81314F==


------------------------------

From: "Michael P. Meyer" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc,comp.os.linux.x
Subject: Re: viewing Linux Xserver Xfree86 on NT ?
Date: Tue, 04 May 1999 03:48:49 GMT

1. Start your xserver on the pc.  You may need to configure it to run in
"Single window mode", or whatever.
2. Telnet into your linux box, login as your userid
3. set your DISPLAY variable:  "export DISPLAY=pcaddress:0.0"
4. run your .xinit or /etc/X11/xinit     verify these file locs first I
can't remember where they live.

Robin Jackson <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> In article <7E5X2.3438$[EMAIL PROTECTED]>,
> "Larry Brasfield" <[EMAIL PROTECTED]> wrote:
>
> >As they say at their site,
> >  http://www.microimages.com/freestuf/mix/
> >MicroImages is happy to make its X Server freely
> >available for use on any Macintosh or Windows computers.
> >
> >It installs very easily, works great, and can
> >pretty much be configured by referring to
> >the X documentation.
>
> Well I have MI/X on my Mac.
>
> HOW do I get the normal Xwindowx desktop that comes up on my Linux machine
> to come up under MI/X?
>
> ie I want to see the control Panel, desktop manager, start bar etc??
>
> I have tried setting DISPLAY but nothing seems to work?
>
> Robin
>
>
>



------------------------------

From: root <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: Re: ipfwadm and RedHat 6.0
Date: Sat, 08 May 1999 13:35:39 +0800

> >I have a network that allows my machines to communicate. I'm running
> >RH5.1, kernel 2.0.35. The rest of the "network" is one Windows98 machine.
> >I get a PPP connection from the linux gateway, and to the best of my
> >knowledge all of the settings on the '98 machine are correct. I've been
> >using the masquerading HOWTO as a guide. When the guide says to enter the
> >commands:
> >ipfwadm -F -p deny
> >ipfwadm -F -a m -S 192.168.1.0/24 0.0.0.0/0
> >The first command gives no feedback. The second command gives me:
> >ipfwadm: no ports allowed without specific protocol
> >Try `ipfwadm -h' for more information.
> >ipfwadm -h suppplies plenty of info, none of which I understand.
> >Has anyone encoutnered this problem? The HOWTO and a couple of other
> >resources I've consulted don't touch the subject, unless my sleepless eyes
> >are blind....

I just installed RedHat 6 which does not have ipfwadm anymore.  Apparently
there is ipfwadm-wrapper and ipchains modules to do the same thing.  Has
anyone managed to configure the new modules to do what many of us do with
ipfwadm.

Here is my internal ipfwadm configuration to share a single modem with my
intranet..

extract from my /etc/rc.d/rc.local
############################
echo "1" > /proc/sys/net/ipv4/ip_forward
/sbin/depmod -a
/sbin/modprobe ip_masq_ftp.o
/sbin/modprobe ip_masq_raudio.o
# deny all ips except specified ones
/sbin/ipfwadm -F -p deny
# allow only these ips
/sbin/ipfwadm -F -a m -S 192.168.10.2/24 -D 0.0.0.0/0 #bob
/sbin/ipfwadm -F -a m -S 192.168.10.3/24 -D 0.0.0.0/0 #jane
/sbin/ipfwadm -F -a m -S 192.168.10.4/24 -D 0.0.0.0/0 #mike
/sbin/ipfwadm -F -a m -S 192.168.10.5/24 -D 0.0.0.0/0 #kym
/sbin/ipfwadm -F -a m -S 192.168.10.6/24 -D 0.0.0.0/0 #paul
# add the route
/sbin/ifconfig eth0 192.168.10.1
/sbin/route add -net 192.168.10.0
echo "IP forwading completed"
###############################

My internal network is running on 192.168.10.x with this linux box/modem on
192.168.10.1.

Any help appreciated.



------------------------------

From: "Michael Taylor" <[EMAIL PROTECTED]>
Crossposted-To: comp.infosystems.www.servers.unix
Subject: Re: Need Apache DB Advice
Date: Sat, 8 May 1999 00:54:17 -0500

Well, I've done this using mqSQL and perl, running one on my RedHat box at
home and an internet server right now in fact.  Best of all, like Linux and
apache, you can get mySQL and perl for free.

MT
Anthony Ewell <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Hi,
>
>    I have to put together an internal company Apache server on a Red
> Hat Linux box.  The main application Apache need to run is a web
> page that is tied into a database and must have both read and write
> access to the database.
>
>    Does anyone have any opinions on what is the easiest, best way to
> go at this?  What is the easiest way to link Apache to the database,
> etc.?
>
>    Many thanks,
> --Tony
>



------------------------------

From: Benjamin John <[EMAIL PROTECTED]>
Crossposted-To: japan.www.server.apache,linux.redhat.misc
Subject: .Shtml problem
Date: 08 May 1999 07:37:57 PDT

I have .shtml enabled in apaches configuration

and working also

for one domain to which the DocumentRoot point to is at
/home/httpd/html
this works fine !

but i have another domain which points to
/apps/us-national

this is on another partition on the same machine

i cant get .shtml pages to work on this partition
any ideas why ?
if its on a different partition do you have to do anything special to
enable .shtml pages ?

Thanks.





------------------------------

From: "Ryan Cleary" <[EMAIL PROTECTED]>
Crossposted-To: comp.mail.sendmail
Subject: Re: Making Outlook Express work with Qmail
Date: Sat, 08 May 1999 01:54:33 -0400

In article <7gvesa$q7h$[EMAIL PROTECTED]> , [EMAIL PROTECTED]  wrote:

> Ok everyone,
>
> I managed to get qmail working on my machine. I now want to hook it up with
> IMAP on Microsoft Outlook Express. What program do I use to have qmail do
> this?

You need an IMAP daemon.  I use UW's software.
http://www.washington.edu/imap

I'm using it with the very same setup, running QMail and IMAPD on a RedHat
5.2 box, with Mac and Win clients running Outlook Express.

You just need to make sure that IMAPd looks for mail in the same place that
qmail delivers it to.  For my site, I edited the imapd source (instructions
are in the documentatino with IMAPD), and use procmail for mail delivery,
and a .procmailrc to deliver mail to the same place I specified in the imapd
source.  Two popular places are /var/imap/$USER/ or /home/$USER/mail,
depending on whether this machine mounts home directories via NFS.  (If
/home is mounted via NFS, put imap mail in /var/imap/$USER)

Ryan Cleary

------------------------------

From: Mike Kerr <[EMAIL PROTECTED]>
Subject: Re: Trying to get my new linux system to talk to @home
Date: Sat, 08 May 1999 14:40:16 GMT

Derek Smith wrote:
> 
> I just got done setting up a linux system and am having problems getting it
> to talk to thecox@home network. (static IP address) Linux is talking to the
> network card correctly, but won't resolve DNS or anything from the network.
> Is there anyone who has their system up and connected to the @home network
> that could give me some pointers? I'm using Red Hat 5.2. It's like the
> system works perfectly until I try to access something outside the machine.
> 
> Thanks
> 
> Derek Smith
> 
> Sound Technology Consultants
> [EMAIL PROTECTED]

I would check that your network card can work when connected to another
computer.

Mike

------------------------------

From: root <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: Re: ipfwadm and RedHat 6.0
Date: Sat, 08 May 1999 15:07:17 +0000

I  put some detector code in my firewall script and use a variable for either
IPFWADM or IPFWADM-WRAPPER.
My fragment looks like this:
    if [ -e /proc/net/ipfw-chains ]    # detect IPCHAINS in use
     then
              set IPFW = "/usr/sbin/ipfwadm-wrapper"
     else
              set IPFW = "/sbin/ipfwadm"
    fi

Then you can use $IPFW in the rest of your  firewall script.
root wrote:

> > >I have a network that allows my machines to communicate. I'm running
> > >RH5.1, kernel 2.0.35. The rest of the "network" is one Windows98 machine.
> > >I get a PPP connection from the linux gateway, and to the best of my
> > >knowledge all of the settings on the '98 machine are correct. I've been
> > >using the masquerading HOWTO as a guide. When the guide says to enter the
> > >commands:
> > >ipfwadm -F -p deny
> > >ipfwadm -F -a m -S 192.168.1.0/24 0.0.0.0/0
> > >The first command gives no feedback. The second command gives me:
> > >ipfwadm: no ports allowed without specific protocol
> > >Try `ipfwadm -h' for more information.
> > >ipfwadm -h suppplies plenty of info, none of which I understand.
> > >Has anyone encoutnered this problem? The HOWTO and a couple of other
> > >resources I've consulted don't touch the subject, unless my sleepless eyes
> > >are blind....
>
> I just installed RedHat 6 which does not have ipfwadm anymore.  Apparently
> there is ipfwadm-wrapper and ipchains modules to do the same thing.  Has
> anyone managed to configure the new modules to do what many of us do with
> ipfwadm.
>
> Here is my internal ipfwadm configuration to share a single modem with my
> intranet..
>
> extract from my /etc/rc.d/rc.local
> ############################
> echo "1" > /proc/sys/net/ipv4/ip_forward
> /sbin/depmod -a
> /sbin/modprobe ip_masq_ftp.o
> /sbin/modprobe ip_masq_raudio.o
> # deny all ips except specified ones
> /sbin/ipfwadm -F -p deny
> # allow only these ips
> /sbin/ipfwadm -F -a m -S 192.168.10.2/24 -D 0.0.0.0/0 #bob
> /sbin/ipfwadm -F -a m -S 192.168.10.3/24 -D 0.0.0.0/0 #jane
> /sbin/ipfwadm -F -a m -S 192.168.10.4/24 -D 0.0.0.0/0 #mike
> /sbin/ipfwadm -F -a m -S 192.168.10.5/24 -D 0.0.0.0/0 #kym
> /sbin/ipfwadm -F -a m -S 192.168.10.6/24 -D 0.0.0.0/0 #paul
> # add the route
> /sbin/ifconfig eth0 192.168.10.1
> /sbin/route add -net 192.168.10.0
> echo "IP forwading completed"
> ###############################
>
> My internal network is running on 192.168.10.x with this linux box/modem on
> 192.168.10.1.
>
> Any help appreciated.


------------------------------

From: "d. martin" <[EMAIL PROTECTED]>
Subject: Re: Samba - Novell shareable flags, HOW?
Date: Fri, 7 May 1999 04:31:11 -0500

Nothing needs to done. Multiple users will be able to have the file open and
readable by default.

Egelsbach Airport wrote in message <7gsn39$2j7$[EMAIL PROTECTED]>...
>Two weeks ago our fileserver running Novell Netware 3.11 broke.
>
>There was only one DOS-type application installed which we need to do our
>daily work.
>We are now trying to set up a Linux-Server with Samba to emulate Netware
>environment.
>The specific application needs to be run from three clients simultanously
>which obviously could be achieved.
>
>The problem now is that two of the clients need access to some files in the
>application�s directory at the same time - so those files need to be
>permanetly open/accessable.
>
>In fact - as the Novell-Server was still running - you had to type "flag
*.*
>s" in the aplication�s directory to make everything "shareable".
>
>I hope someone knows an answer which can solve the problem.
>
>I would really appreciate any commets...
>
>
>



------------------------------

From: "Doug Pitek" <[EMAIL PROTECTED]>
Subject: Innd Access File.. 
Date: Sat, 8 May 1999 11:11:56 -0400


i'm new to linux but I have an easy question, why do I get an "502 You have
no permission to talk.  Goodbye." error when I try to connect to my linux
box with a news client... I really haven't played with the conf files yet..
but any help on where to start would be great.. thanks

-dp



------------------------------

From: "Rene Nieuwendijk" <[EMAIL PROTECTED]>
Subject: Traffic Monitoring
Date: Sat, 8 May 1999 17:26:12 -0700

I've got an linux server for my cable modem and I want to see how much
everybody is using. I've searched on the internet and saw an example:
ipfwadm -A in -a -W eth1 -P tcp -D 192.168.37.1 www
The only problem is that I get the error
ipfwadm: setsockopt failed: Protocol not available
Does anybody know what this means or better, does anybody know how to let
this example work.

Thanks



------------------------------

From: [EMAIL PROTECTED] (Vidar Andresen)
Subject: Re: How to make a linuxbridge bridge it's own traffic?
Date: Sat, 08 May 1999 05:51:12 +0200

In article <[EMAIL PROTECTED]>,
Erik Gustavsson <[EMAIL PROTECTED]> wrote:
>I have a setup like this at home:
>
>100Mbps HUB <------> Linux box <------> 10Mbps HUB.
>
>I have setup a bridge on the Linux box, and the 10Mbps machines can talk
>to the 100Mbps machines, and the other way around. The 100Mbps machines
>can talk to the Linux box, but the 10Mbps machines can't.

They can, even with your setup.  Try for a test:

1)

To telnet from any machine connected to the 10Mbps HUB into a machine
connected to the 100Mbps HUB.

And then start a telnet from that login to your 192.168.0.1. It works.

2)

To telnet from any machine connected to the 100Mbps HUB into a machine
connected to the 10Mbps HUB.

And then start a telnet from that login to your 192.168.0.1.  It will
not work.

3)

To telnet from your linux bridge to any machine connected to the
100Mbps HUB.

And then start a telnet from that login to any machine connected to
the 10Mbps HUB. It works.

(and so on.. )

>I've setup the 100Mbps NIC with IPnr 192.168.0.1, and the 10Mbps NIC is
>"configured" at 0.0.0.0.
>Is there any way to make the Linux bridge code handle it's own traffic,
>I mean to decide which way stuff from the Linux box itself goes just
>like it does with the traffic on the wire? As it is now, whenever the
>Linux box tries to connect or reply to a 10Mbps machine, the data is
>only sent to the 100Mbps wire. Maybe there is a patch or some smart
>solution to my problem?  I really don't want to subnet and use normal
>routing, I want the bridging to be 100% transparent...

The bridging is transparent. For the machines connected to the hubs.

And you dont want subnetting or routing.  OK.  With that limitation i
rant on...

If you had "configured" both nic's at the bridge to 0.0.0.0 i am not
sure the bridge could have been reached at all.  It becomes invisible.
Transparent for all other machines. Why not.

If you give the second nic a IPnr of let say 192.168.0.2, it does not
automatically help.

But if you then do an 'ifup eth1', voila, then the brigde is visible
and can speak to the machines connected that way.

And the other way is lost.

hmm..

So the problem is maybe how to be seen from all sides without any
routing.  Maybe some kind of alias on the second nic will help.  But
then i guess your machine will not know where to send replies.  As
long as it seems like the last nic 'ifup eth*' is the one abel to
speak with other machines.  (The bridging itself remains
undisturbed, you can 'ifup eth1', and test, and so 'ifup eth0' and
test.)

So i dont know.  If you give both nic's the IPnr of 192.168.0.1 i
wonder what happens.. It might work, but strange things may happen ;-)

man arp
man tcpdump

(and if you have enough nic's to experiment with; And dont mind
playing; the result may be confusing (at best?).

   Configure the two nic's (eth0, eth1) already in your machine to
   0.0.0.0

   Put another nic (eth2?) into the linux box, and give it a IPnr, say
   192.168.0.1, and do _not_ bridge that nic.  Connect that nic to any
   of the hub's.

   Start the bridge. (on eth0 and eth1)

   Do a 'ifup eth2' on the nic to be 192.168.0.1

I guess that will be the way out for your linux box, and i guess it
will be reached from all sides.  Not very economic.  I guess traffic
to your machine then will go (in a loop) from the machines connected to
the other HUB, trough the bridge, to the hub, and then to your
192.168.0.1.

I dont know if it will work.  If you use the 'bridgex-0.2' turn on
debug.  Listening after arp-request with tcpdump is also informative.
with luck the eth2 is found as 'just another nic' connected to the hub
and learned by the bridge that way.)

I once placed two linux-bridges back to back, eth0 to et0, and eth1 to
eth1, crossover tp.  And it generated a lot of traffic...  I dont do
that anymore..


Mvh Vidar Andresen


------------------------------


** FOR YOUR REFERENCE **

The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:

    Internet: [EMAIL PROTECTED]

You can send mail to the entire list (and comp.os.linux.networking) via:

    Internet: [EMAIL PROTECTED]

Linux may be obtained via one of these FTP sites:
    ftp.funet.fi                                pub/Linux
    tsx-11.mit.edu                              pub/linux
    sunsite.unc.edu                             pub/Linux

End of Linux-Networking Digest
******************************

Reply via email to