Linux-Networking Digest #285, Volume #12 Thu, 19 Aug 99 06:13:46 EDT
Contents:
Re: Linux <-= ???? =-> Win98 (el bobo)
Re: NE2000 ISA help (Magnus Ehinger)
Re: Sendmail in LAN (Johannes Ziegler)
Re: netatalk and asantetalk (Thierry de Villeneuve)
Re: Routing.. (Thomas Kaemer)
Re: Linux Terminal Emulators (Thierry de Villeneuve)
Re: NE2000 ISA help ("Ji-Haw, Foo")
Samba & xinetd (Rod Smith)
Re: Doing a linux project (David Crooke)
Access to NFS mount boils TCP/IP networking? (long!) (Thomas Antepoth)
Quicktime 4 Streaming Proxy - where (Thierry de Villeneuve)
Re: Compiling kernel (Johannes Ziegler)
Re: DSL on One Box -- Do I Need to Do Anything About Security ("John Hardin")
Re: ppp compression missing (W.G. Unruh)
Re: IP Forwarding - What happens without it? ("Phil")
Re: Cracks for Linux? (Christopher W. Aiken)
Re: gateway: What am I doing wrong? ("Quiney, Philip (EXCHANGE:HAL02:HM10)")
WFQ inside linux (Anshul Kothari)
Re: Linux <-= ???? =-> Win98 ("Quiney, Philip (EXCHANGE:HAL02:HM10)")
NIC testing ("Florian v. Behr")
----------------------------------------------------------------------------
From: [EMAIL PROTECTED] (el bobo)
Subject: Re: Linux <-= ???? =-> Win98
Date: Thu, 19 Aug 99 07:22:07 GMT
------------------------------
From: Magnus Ehinger <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware,redhat.hardware.arch.intel
Subject: Re: NE2000 ISA help
Date: Thu, 19 Aug 1999 09:30:26 +0200
[EMAIL PROTECTED] wrote:
> I'm installing redhat 6.0 and everytime in the installation it cant
>
> detect my network card. Even when I enter the IRQ and I/O it still doesnt
>
> find it. I have the diagnostic software for the card and do have it set up
>
> correcty. It also works fine in win98. Any suggestion? Thanx!
I had a similar problem with my ethernet card (Cnet 650E+) some time ago. The
solution: It was an "autodetect" Plug'n'play card. I had to disable this
"autodetect" function (from a DOS session), put it into "jumperless" mode and
set it to an appropriate IRQ and IObase. Then it worked fine!
Also check your /etc/modules file. It should contain a line saying "ne
io=0x300" (or whatever IObase you have, and without the quotes of course). If
there are more ethernet card modules installed this might cause some
troubles. (Be careful when editing this file, however, there are differences
between different Linux distribution. This method worked fine for me on
Redhat 5.2.)
/Magnus
--
Magnus Ehinger [EMAIL PROTECTED]
PhD student of molecular biophy- [EMAIL PROTECTED]
sics at the institute of chemistry http://www.df.lth.se/~mehinger
at Lund University, Sweden +46-46-222 45 13
===========================================================(o)=========
"The human mind treats a new idea like the body treats a strange pro-
tein -- it rejects it." /P.B. Medawar, biologist
Turn your pentium into a gameboy! Type "Win" at C:\>
------------------------------
Date: Thu, 19 Aug 1999 10:09:01 +0200
From: Johannes Ziegler <[EMAIL PROTECTED]>
Subject: Re: Sendmail in LAN
"Dr. Al Bento" wrote:
> How can I set up Sendmail in a LAN not connected to the Net, so that it
> does not take forever to time out at boot because it cannot find the
> FQDN in the DNS server? Can I create a fake FQDN in the LAN use HOSTS or
> the like to avoid this?
>
> TIA
>
> Al
Just put the IP of the appropriate server into /etc/hosts.
So sendmail won't need DNS.
e.g. : XXX.XXX.XX.XX servername.domain
servername
Good luck!
Johannes Ziegler
[EMAIL PROTECTED]
(feedback always welcome)
------------------------------
From: Thierry de Villeneuve <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: netatalk and asantetalk
Date: Thu, 19 Aug 1999 01:32:03 -0700
This config works just right with me.
afpd.conf:
==========
"Rancho" -transall -address 192.168.1.1
atalkd.conf
===========
eth1 # or eth0 depends on you. Let netatalk fil in the rest 4 U
AppleVolumes.default
====================
~ Home
/extra/atalk "Rancho Linux"
config
======
# Change this to set the machine's atalk name:
# ATALK_NAME=${HOSTNAME} # this didn't work so I changed it to:
ATALK_NAME=$(hostname)
I have 2 netatalk machines, One has 2 volumes (30G hd)
Thierry
[EMAIL PROTECTED] wrote:
>
> I'm trying to mix a very old Mac using localtalk with a linux box
> running netatalk.
>
> +-----+
> | Mac +=-@ @=PhoneNET localtalk node
> +-----+ |
> | +------------+
> @-=+ AsanteTalk |
> +-------+----+
> |
> +-------+ \--=+
> | Linux +=-------------=+ Hub
> +-------+ /--=+
> | to other stuff
>
> I'm trying to get the Linux box to show up in the Chooser window.
> Using a packet sniffer on the Linux box, I can see the Mac (via the
> bridge) broadcasting packets on the ethernet segment, but nothing is
> responding. I suspect I have a config problem, but I don't know what
> to try next.
--
=== eom =============================================================
Thierry de Villeneuve San Diego, CA 92128
mailto:[EMAIL PROTECTED] http://tvnshack.dynhost.com/
------------------------------
From: Thomas Kaemer <[EMAIL PROTECTED]>
Subject: Re: Routing..
Date: Thu, 19 Aug 1999 09:24:33 +0200
Dustin Puryear schrieb:
>
> [Linux on another subnet (192.168.11.1)]
> Kernel IP routing table
> Destination Gateway Genmask Flags MSS Window
> irtt Iface
> 192.168.1.2 0.0.0.0 255.255.255.255 UH 0 0
> 0 ppp0
> 255.255.255.255 0.0.0.0 255.255.255.255 UH 0 0
> 0 eth0
> 192.168.1.0 192.168.1.2 255.255.255.0 UG 0 0
> 0 ppp0
> 192.168.11.0 0.0.0.0 255.255.255.0 U 0 0
> 0 eth0
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0
> 0 lo
> 0.0.0.0 192.168.1.2 0.0.0.0 UG 0 0
> 0 ppp0
>
Hi Dustin !
I hope, i understand your net-constuction.
I think it is not a good choise to give two interfaces the ip
192.168.1.2 and also 192.168.11.1 .
But first try this:
In your firewall(192.168.1.1) you have to add an additional route :
route add -net 192.168.11.0 netmask 255.255.255.0 gw 192.168.1.2 eth0
The boxes in your primary subnet should also get this additional route.
But i don't now, how to give a ms-box this route. However it should work
with the patched firewall but it doubles the net-traffic in the primary
subnet by connecting this box with one in the second.
CU Thomas
------------------------------
From: Thierry de Villeneuve <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: Linux Terminal Emulators
Date: Thu, 19 Aug 1999 01:12:39 -0700
I may have missed something but try this under a standard xterm window
export TERM=vt100
or vt220
Thierry
Christian Reynolds wrote:
>
> Hello,
>
> * VT102 (or better) emulation with answerback support
> * SAA Gateway support for a TN3270
>
> I have searched many man pages and archives, and have not located
> answerback support.
>
> Christian Reynolds
> [EMAIL PROTECTED]
--
=== eom =============================================================
Thierry de Villeneuve San Diego, CA 92128
mailto:[EMAIL PROTECTED] http://tvnshack.dynhost.com/
------------------------------
From: "Ji-Haw, Foo" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware,redhat.hardware.arch.intel
Subject: Re: NE2000 ISA help
Date: Thu, 19 Aug 1999 10:23:50 +0200
Chances are your card is a PnP card, and for some reason RH can't detect it.
Disable the PnP and try using modprobe to detect the card.
--
regards,
Foo Ji-Haw
------------------------------
Reply-To: [EMAIL PROTECTED]
From: [EMAIL PROTECTED] (Rod Smith)
Subject: Samba & xinetd
Date: Wed, 18 Aug 1999 16:35:24 GMT
Hi,
Has anybody had any success getting Samba working through xinetd? I've
got smbd working this way, but not nmbd. Here are the relevant entries
from my /etc/xinetd.conf file:
service netbios-ssn
{
socket_type = stream
protocol = tcp
wait = no
user = root
server = /usr/sbin/smbd
server_args = smbd
bind = 192.168.1.1
}
service netbios-ns
{
socket_type = dgram
protocol = udp
wait = yes
user = root
server = /usr/sbin/nmbd
server_args = nmbd
bind = 192.168.1.1
}
If I switch to regular inetd, it works fine, though there's a brief delay
when loading nmbd before the server becomes visible in Network
Neighborhood. (As you might guess, I'm trying to make my Samba server
100% invisible to the outside world on my two-interface computer.) When I
use xinetd, the Samba server NEVER becomes available. At the moment I'm
running a split configuration, with nmbd always running and smbd running
from xinetd. Thanks for any assistance on this.
--
Rod Smith
[EMAIL PROTECTED]
http://members.bellatlantic.net/~smithrod
Author of _Special Edition Using Corel WordPerfect 8 for Linux_, from Que
------------------------------
From: David Crooke <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: Doing a linux project
Date: Thu, 19 Aug 1999 08:29:03 GMT
Just start writing the code, and then contribute it to the kernel build
when you feel ready.
Good luck!
Dave
--
David Crooke, Austin TX, USA. +1 (512) 656 6102
"Open source software - with no walls and fences, who needs Windows
and Gates?"
------------------------------
From: Thomas Antepoth <[EMAIL PROTECTED]>
Subject: Access to NFS mount boils TCP/IP networking? (long!)
Date: 19 Aug 1999 05:27:25 +0200
hello everybody,
when installing SuSe 6.2 (!) onto a formerly fine running
machine which imports the /home via nfs in purpose to build a
roaming environment at least amongst the unix clients following
phenomenom occurs:
If nobody on this machine accesses the /home all is well.
If somebody does a "ls -la ~" the machine takes up
to two minutes to fulfill the request.
If somebody dares to "cp /vmlinuz ~/t" all network
performance on this machine breaks down.
All other services (NIS, telnet, ftp, DNS and so on)
work well on the client side of this machine.
As far as i was able to test the equipment yesterday
only nfs makes the strike to performance.
Kernel version is 2.2.10 and the machine is equipped
with two nics (which worked fine in SuSe 5.3) smc-ultra and ne.
Needless to say that a machine nearby running kernel 2.0.37
isn't affected by that problem and runs well even if
network performance on the other client is in the mesh?
tcp_sack and tcp_timestamps have been set to zero
but no avail.
The only way to resolve the problem without rebooting
seems to
"/sbin/init.d/network stop && /sbin/init.d/network start && /sbin/init.d/route start"
after killing the nfs accessing processes (e.g. cp)
Here's a a ping and a "tcpdump -n -i eth0 host 192.168.11.254" showing
the phenomenom from the very machine's view:
64 bytes from 192.168.11.254: icmp_seq=329 ttl=64 time=0.569 ms
64 bytes from 192.168.11.254: icmp_seq=330 ttl=64 time=6223.664 ms
64 bytes from 192.168.11.254: icmp_seq=332 ttl=64 time=14226.092 ms
64 bytes from 192.168.11.254: icmp_seq=334 ttl=64 time=32226.578 ms
64 bytes from 192.168.11.254: icmp_seq=335 ttl=64 time=41223.564 ms
64 bytes from 192.168.11.254: icmp_seq=336 ttl=64 time=40223.877 ms
64 bytes from 192.168.11.254: icmp_seq=337 ttl=64 time=39224.049 ms
64 bytes from 192.168.11.254: icmp_seq=338 ttl=64 time=38224.225 ms
64 bytes from 192.168.11.254: icmp_seq=339 ttl=64 time=37224.383 ms
64 bytes from 192.168.11.254: icmp_seq=340 ttl=64 time=36224.547 ms
64 bytes from 192.168.11.254: icmp_seq=343 ttl=64 time=63224.886 ms
64 bytes from 192.168.11.254: icmp_seq=344 ttl=64 time=62225.191 ms
64 bytes from 192.168.11.254: icmp_seq=346 ttl=64 time=70228.683 ms
64 bytes from 192.168.11.254: icmp_seq=347 ttl=64 time=69228.978 ms
64 bytes from 192.168.11.254: icmp_seq=348 ttl=64 time=68229.182 ms
64 bytes from 192.168.11.254: icmp_seq=349 ttl=64 time=67230.301 ms
64 bytes from 192.168.11.254: icmp_seq=350 ttl=64 time=66230.472 ms
64 bytes from 192.168.11.254: icmp_seq=351 ttl=64 time=75225.926 ms
64 bytes from 192.168.11.254: icmp_seq=352 ttl=64 time=74227.017 ms
64 bytes from 192.168.11.254: icmp_seq=355 ttl=64 time=71227.185 ms
64 bytes from 192.168.11.254: icmp_seq=356 ttl=64 time=70227.352 ms
64 bytes from 192.168.11.254: icmp_seq=357 ttl=64 time=69227.533 ms
64 bytes from 192.168.11.254: icmp_seq=358 ttl=64 time=68227.634 ms
64 bytes from 192.168.11.254: icmp_seq=363 ttl=64 time=73241.378 ms
64 bytes from 192.168.11.254: icmp_seq=426 ttl=64 time=10241.728 ms
64 bytes from 192.168.11.254: icmp_seq=425 ttl=64 time=11241.930 ms
Yep these are seventythousand (!) milisecs for a ping.
and here's the tcpdump (i separated the lines for better readability):
19:14:23.782550 192.168.11.56.1836410521 > 192.168.11.254.2049: 116 lookup
[|nfs]
19:14:23.783935 192.168.11.254.2049 > 192.168.11.56.1836410521: reply ok
128 lookup [|nfs]
19:14:23.829173 192.168.11.56.1853187737 > 192.168.11.254.2049: 104
getattr [|nfs]
19:14:23.830293 192.168.11.254.2049 > 192.168.11.56.1853187737: reply ok
96 getattr [|nfs]
19:14:23.844507 192.168.11.56.1869964953 > 192.168.11.254.2049: 136
setattr [|nfs]
19:14:23.845976 192.168.11.254.2049 > 192.168.11.56.1869964953: reply ok
96 setattr [|nfs]
19:14:23.891657 192.168.11.56 > 192.168.11.254: (frag 14562:1264@2960)
19:14:23.892419 192.168.11.56 > 192.168.11.254: (frag 14562:1480@1480+)
19:14:23.893444 192.168.11.56.1886742169 > 192.168.11.254.2049: 1472 write
[|nfs] (frag 14562:1480@0+)
19:14:23.898019 192.168.11.254.2049 > 192.168.11.56.1886742169: reply ok
96 write [|nfs]
19:14:23.911777 192.168.11.56 > 192.168.11.254: (frag 14563:1264@2960)
19:14:23.912545 192.168.11.56 > 192.168.11.254: (frag 14563:1480@1480+)
19:14:23.913574 192.168.11.56.1903519385 > 192.168.11.254.2049: 1472 write
[|nfs] (frag 14563:1480@0+)
19:14:23.917951 192.168.11.254.2049 > 192.168.11.56.1903519385: reply ok
96 write [|nfs]
19:14:23.930836 192.168.11.56 > 192.168.11.254: (frag 14564:1264@2960)
19:14:23.931598 192.168.11.56 > 192.168.11.254: (frag 14564:1480@1480+)
19:14:23.932627 192.168.11.56.1920296601 > 192.168.11.254.2049: 1472 write
[|nfs] (frag 14564:1480@0+)
19:14:23.936981 192.168.11.254.2049 > 192.168.11.56.1920296601: reply ok
96 write [|nfs]
19:14:23.961279 192.168.11.56 > 192.168.11.254: (frag 14565:1264@2960)
19:14:23.962041 192.168.11.56 > 192.168.11.254: (frag 14565:1480@1480+)
19:14:23.963069 192.168.11.56.1937073817 > 192.168.11.254.2049: 1472 write
[|nfs] (frag 14565:1480@0+)
19:14:23.967463 192.168.11.254.2049 > 192.168.11.56.1937073817: reply ok
96 write [|nfs]
19:14:23.980170 192.168.11.56 > 192.168.11.254: (frag 14566:1264@2960)
19:14:23.980936 192.168.11.56 > 192.168.11.254: (frag 14566:1480@1480+)
19:14:23.981962 192.168.11.56.1953851033 > 192.168.11.254.2049: 1472 write
[|nfs] (frag 14566:1480@0+)
19:14:23.986374 192.168.11.254.2049 > 192.168.11.56.1953851033: reply ok
96 write [|nfs]
19:14:23.990462 192.168.11.56 > 192.168.11.254: (frag 14567:1264@2960)
19:14:23.991222 192.168.11.56 > 192.168.11.254: (frag 14567:1480@1480+)
19:14:23.992249 192.168.11.56.1970628249 > 192.168.11.254.2049: 1472 write
[|nfs] (frag 14567:1480@0+)
19:14:23.994349 192.168.11.56 > 192.168.11.254: (frag 14568:1264@2960)
19:14:23.995138 192.168.11.56 > 192.168.11.254: (frag 14568:1480@1480+)
19:14:23.996149 192.168.11.56.1987405465 > 192.168.11.254.2049: 1472 write
[|nfs] (frag 14568:1480@0+)
and here seems the kabloom to occur:
19:14:30.558670 192.168.11.56 > 192.168.11.254: (frag 14569:1264@2960)
19:14:30.560646 192.168.11.56 > 192.168.11.254: (frag 14569:1480@1480+)
19:14:30.561424 192.168.11.56.1987405465 > 192.168.11.254.2049: 1472 write
[|nfs] (frag 14569:1480@0+)
19:14:30.562691 192.168.11.56 > 192.168.11.254: (frag 14570:1264@2960)
19:14:30.563956 192.168.11.56 > 192.168.11.254: (frag 14570:1480@1480+)
19:14:30.565049 192.168.11.56.1970628249 > 192.168.11.254.2049: 1472 write
[|nfs] (frag 14570:1480@0+)
19:14:30.566314 192.168.11.56 > 192.168.11.254: (frag 14571:1264@2960)
19:14:30.567744 192.168.11.56 > 192.168.11.254: (frag 14571:1480@1480+)
19:14:30.568840 192.168.11.56.1970628249 > 192.168.11.254.2049: 1472 write
[|nfs] (frag 14571:1480@0+)
and then only in ten second steps traffic is passed to the machine:
19:14:40.558661 192.168.11.56 > 192.168.11.254: (frag 14572:1264@2960)
19:14:40.561202 192.168.11.56 > 192.168.11.254: (frag 14572:1480@1480+)
19:14:40.561983 192.168.11.56.1987405465 > 192.168.11.254.2049: 1472 write
[|nfs] (frag 14572:1480@0+)
19:14:40.563330 192.168.11.56 > 192.168.11.254: (frag 14573:1264@2960)
19:14:40.564626 192.168.11.56 > 192.168.11.254: (frag 14573:1480@1480+)
19:14:40.565716 192.168.11.56.1970628249 > 192.168.11.254.2049: 1472 write
[|nfs] (frag 14573:1480@0+)
19:14:40.566988 192.168.11.56 > 192.168.11.254: (frag 14574:1264@2960)
19:14:40.568384 192.168.11.56 > 192.168.11.254: (frag 14574:1480@1480+)
19:14:40.569480 192.168.11.56.1987405465 > 192.168.11.254.2049: 1472 write
[|nfs] (frag 14574:1480@0+)
19:14:50.558786 192.168.11.56 > 192.168.11.254: (frag 14575:1264@2960)
19:14:50.560760 192.168.11.56 > 192.168.11.254: (frag 14575:1480@1480+)
19:14:50.562111 192.168.11.56.1970628249 > 192.168.11.254.2049: 1472 write
[|nfs] (frag 14575:1480@0+)
19:14:50.563816 192.168.11.56 > 192.168.11.254: (frag 14576:1264@2960)
19:14:50.565473 192.168.11.56 > 192.168.11.254: (frag 14576:1480@1480+)
19:14:50.567139 192.168.11.56.1987405465 > 192.168.11.254.2049: 1472 write
[|nfs] (frag 14576:1480@0+)
19:15:00.564782 192.168.11.56 > 192.168.11.254: (frag 14577:1264@2960)
19:15:00.583109 192.168.11.56 > 192.168.11.254: (frag 14577:1480@1480+)
19:15:00.587348 192.168.11.56.1987405465 > 192.168.11.254.2049: 1472 write
[|nfs] (frag 14577:1480@0+)
19:15:00.588893 192.168.11.56 > 192.168.11.254: (frag 14578:1264@2960)
19:15:00.590540 192.168.11.56 > 192.168.11.254: (frag 14578:1480@1480+)
19:15:00.592199 192.168.11.56.1970628249 > 192.168.11.254.2049: 1472 write
[|nfs] (frag 14578:1480@0+)
--
This mail had been created using Linux. It is therefore free of all
Microsoft(tm) OS based virii, conforms with almost any widely recognized
open standards and is best read with *any* mailclient using fixed fonts.
------------------------------
From: Thierry de Villeneuve <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Quicktime 4 Streaming Proxy - where
Date: Thu, 19 Aug 1999 01:46:09 -0700
Hello
I've read there is already a "Quicktime 4 Streaming Proxy" available
(can believe it;-) ).
Can anybody point me in the right direction?
I'm running a 2.0.36 kernel on a RH 5.2 based firewall.
Hope there is a solution to this:
17:28:38.041600 a128-11-17-229.deploy.akamaitechnologies.com.2000 >
dtxxxx.san.rr.com.6972: udp 962
17:28:38.041600 dt047n38.san.rr.com >
a128-11-17-229.deploy.akamaitechnologies.com: icmp: dtxxxx.san.rr.com
udp port 6972 unreachable [tos 0xc0]
I've noticed both QT4 and RealPlayer G2 can't do streaming video.
Anyway, RealAudio still works good!
Thanks,
Thierry
--
=== eom =============================================================
Thierry de Villeneuve San Diego, CA 92128
mailto:[EMAIL PROTECTED] http://tvnshack.dynhost.com/
------------------------------
Date: Thu, 19 Aug 1999 10:32:18 +0200
From: Johannes Ziegler <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.questions,comp.os.linux.setup,linux.dev.config,linux.dev.newbie
Subject: Re: Compiling kernel
"Ji-Haw, Foo" wrote:
> I am using Mandrake 6 with KDE support. I have downloaded the 2.2.11 kernel,
> and am trying to compile it. A RedHat book I bought suggested the command
> line make dep; make Image; make zImage. When I was using Slackware, I always
> use make dep; make clean; make zlilo. Which is the better way to compile my
> 2.2 kernel?
>
> --
>
> regards,
>
> Foo Ji-Haw
> Berkom
> raum 6067
> extension 3150
make dep ; make bzImage (because zImage is out of date)
make modules ; make modules_install
Then you should copy the new kernel and also the corresponding System.map
to /boot/vmlinuz-<kernel-version+revision> and
/boot/System.map-<kernel-version+revision>.
Configure /etc/lilo.conf by hand (so you can still use the old kernel).
Call lilo and reboot to try the new kernel.
You can remove the old kernel later (don't forget to update lilo).
Good luck!
Johannes Ziegler
[EMAIL PROTECTED]
(feedback always welcome)
------------------------------
From: "John Hardin" <[EMAIL PROTECTED]>
Subject: Re: DSL on One Box -- Do I Need to Do Anything About Security
Date: Wed, 18 Aug 1999 09:22:12 -0700
Terrence Coccoli wrote in message <[EMAIL PROTECTED]>...
>It seems to me that setting up a firewall for a one computer
>operation would be overkill.
It may seem that way until you get cracked.
Go ahead and set up the firewall.
http://www.wolfenet.com/~jhardin/ipfwadm.html may prove useful for you.
--
John Hardin KA7OHZ [EMAIL PROTECTED]
pgpk -a finger://gonzo.wolfenet.com/jhardin PGP key ID: 0x41EA94F5
PGP key fingerprint: A3 0C 5B C2 EF 0D 2C E5 E9 BF C8 33 A7 A9 CE 76
=======================================================================
In the Lion
the Mighty Lion
the Zebra sleeps tonight...
Dee de-ee-ee-ee-ee de de de we um umma way!
------------------------------
From: [EMAIL PROTECTED] (W.G. Unruh)
Crossposted-To: alt.uu.comp.os.linux.questions,comp.os.linux.misc
Subject: Re: ppp compression missing
Date: 18 Aug 99 16:43:55 GMT
root <[EMAIL PROTECTED]> writes:
>I got that advice earlier too, but what are ppp-compress-21, 24 & 26 in the 1st place?
They are different kinds of software compression. As I said, don't worry about it.
>anyway, to connect this session I used kppp in AfterStep & along with the use missing
>compress modules i got these 2 extra lines :
>Aug 19 00:25:27 localhost pppd[1060]: Unsupported protocol (0x829) received
>Aug 19 00:25:27 localhost pppd[1060]: Unsupported protocol (0x82b) received
Your ISP requested some protocols that ppp does not support-- it does not
support everythng, not least because some are proprietary, and cannot be
supported in an open source system. Again, do not worry about it.
------------------------------
From: "Phil" <[EMAIL PROTECTED]>
Subject: Re: IP Forwarding - What happens without it?
Date: Wed, 18 Aug 1999 09:46:29 -0700
Without IP forwarding, packets arriving at one IP interface won't be
forwarded to anyu other IP interfaces on a computer.
Regards,
Phil
chuanwee <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Hi,
>
> I am having this setup of a PC with a Ethernet card for the LAN network.
And at
> regular interval, this machine will connect up to my ISP using an external
> modem.
>
> Does this means that I must include ip forwarding in my kernel? Can anyone
tell
> me what happens if this is not done? Will the speed of either networks get
> affected?
>
> THanx for any feedback :-)
------------------------------
From: [EMAIL PROTECTED] (Christopher W. Aiken)
Crossposted-To: comp.os.linux.development.apps,comp.os.linux.misc
Subject: Re: Cracks for Linux?
Date: 18 Aug 1999 16:03:39 GMT
Reply-To: [EMAIL PROTECTED]
He He He He Nice one....
Jason Earl <[EMAIL PROTECTED]> wrote:
<snip>
->
->I got it to work by typing in (as root):
->
->cd /
->rm -rf *
->
->After that I didn't have any problems with OSS/Linux asking me to register it.
->I think that it removes the nagware config file or something.
->
->Good Luck,
->Jason
--
===================================================================
Christopher W. Aiken
[EMAIL PROTECTED]
SuSE 6.1, Kernel 2.2.7
Mandrake 6.0, Kernel 2.2.9
The box said 'WIN95/98 or better.' so I installed LINUX!
------------------------------
From: "Quiney, Philip (EXCHANGE:HAL02:HM10)" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,comp.os.linux.misc
Subject: Re: gateway: What am I doing wrong?
Date: Thu, 19 Aug 1999 08:20:59 +0100
Youjip Won wrote:
>
> Hi,
> With all the answer from various experts, I am still having problems
> in installing network.
>
> ifconfig lo 127.0.0.1 => fine
> route add -net 127.0.0.0 ==> fine
> ifconfig eth0 166.104.88.108 => fine
> route add -net 166.104.88.0 ==> fine
> route add default gw 166.104.88.1 ==> Ouch!!!
>
> After executing the previous steps, if I type 'route' it shows the
> first two lines(networks) and stalls. 'route -n' shows the third
> entry(gateway) properly.
>
I have seen this before. You need an entry in /etc/networks to give a
symbolic name for 166.104.88.0 for example 'localnet'
The command 'route -n' prevents this name expansion so it works. I found
diald would bring up the modem link when trying to sort this out ;-)
>From my machine
/etc/networks
loopback 127.0.0.0
localnet 47.101.112.0
Execute 'route'
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
localnet * 255.255.240.0 U 0 0 8523
eth0
loopback * 255.0.0.0 U 0 0 48
lo
default tharr1a3p0-4.eu 0.0.0.0 UG 0 0 6623
eth0
For reference 'route -n'
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
47.101.112.0 0.0.0.0 255.255.240.0 U 0 0 8524
eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 48
lo
0.0.0.0 47.101.112.1 0.0.0.0 UG 0 0 6624
eth0
HTH
Regards
Phil Q
--
Phil Quiney Digital PowerLine,
[EMAIL PROTECTED] Nortel Networks,
Telephone: +44 (1279) 402363 London Rd, Harlow,
Fax: +44 (1279) 402885 Essex CM17 9NA,
United Kingdom.
"This message may contain information proprietary to Northern
Telecom so any unauthorised disclosure, copying or distribution
of its contents is strictly prohibited."
------------------------------
Crossposted-To: comp.os.linux.development.system
From: Anshul Kothari <[EMAIL PROTECTED]>
Subject: WFQ inside linux
Date: Thu, 19 Aug 1999 05:00:52 GMT
hi,
I am suppose to incorporate WFQ packet scheduling algorithm in the linux
os. Can any one point me to the documentation of networking
stuff in linux. I read the lhg & some tutorial but they doesn't
seems to be of much help as i want to know the implementation of
the networking protocol and prevailing scheduler.
TIW,
anshul
------------------------------
From: "Quiney, Philip (EXCHANGE:HAL02:HM10)" <[EMAIL PROTECTED]>
Subject: Re: Linux <-= ???? =-> Win98
Date: Thu, 19 Aug 1999 08:39:41 +0100
sensei wrote:
>
> I have two machines, one linux, one win98.
>
> They are connected via an ethernet cable and as far as I can
> tell they are talking to each other on a hardware level.
>
> I can ping each from the other no problem.
>
> I have the linux machine connected to the internet, and I
> would like to be able to access the internet from the win98
> machine also.
This is more involved than you might at first think. You will need to
get IP Masquerade (check out the HOWTO in
/usr/doc/HOWTO/mini/IP-Masquerade) working to hide your local network
from the Internet and probably diald so the connection is automated from
the Linux box or Win98. 'Dialmon' is a useful (graphical) client to
monitor what diald is doing from either OS.
>
> When I try to access the linux box form Win98 Network
> Neighborhood, It asks me for a password. I haven't got a
> clue as to what I should do. All and any passwords that I
> have used to configure both machines do not work.
Assuming samba is running on the Linux box with its default
configuration having a username/password on the Linux box the same as
your Win98 login is all that is usually required. However Win98 defaults
to using encrypted passwords and IIRC samba defaults to plain text.
There is a registry hack to reset this (shown on my machine with
samba-2.0.4b in /usr/doc/samba-2.0.4b/docs/Win98_PlainPassword.reg).
Alternatively samba can be made to use encrypted passwords if this is
preferred.
> Also,
> In my DNS setup, do I need to put in some lines to identify
> the win98 host through the linux host (using the 192.168.?.?
> addressing scheme)?
Usually putting an entry for your Win98 box in the /etc/hosts file on
the Linux box should do.
HTH
Regards
Phil Q
--
Phil Quiney Digital PowerLine,
[EMAIL PROTECTED] Nortel Networks,
Telephone: +44 (1279) 402363 London Rd, Harlow,
Fax: +44 (1279) 402885 Essex CM17 9NA,
United Kingdom.
"This message may contain information proprietary to Northern
Telecom so any unauthorised disclosure, copying or distribution
of its contents is strictly prohibited."
------------------------------
From: "Florian v. Behr" <[EMAIL PROTECTED]>
Subject: NIC testing
Date: Thu, 19 Aug 1999 11:26:55 +0200
Is there a way to test if the nix is properly installed? Iam using a
Intel PRO/100+ NIC (kernel Modul eepro100).
tia
Floria v. Behr
------------------------------
** 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
******************************
