Linux-Networking Digest #664, Volume #10 Sun, 28 Mar 99 22:13:40 EST
Contents:
Re: Slow PPP Connection But Minicom Connection Fine (Bill Unruh)
Re: HELP!! Final attempt at Samba installation (John Myers)
Re: Using Linux instead of NT Server in home environment.... ("Systemic")
Re: ttyS? ?? (M. Buchenrieder)
module/depmod problem..... ("Mike")
Re: Using Linux instead of NT Server in home environment.... (jedi)
Re: Using Linux instead of NT Server in home environment.... (jedi)
Re: Using Linux instead of NT Server in home environment.... (Johan Kullstam)
IDENT on masquerade? ("D. C. & M. V. Sessions")
Re: Linux + 2 Ethernet cards ([EMAIL PROTECTED])
Re: modprobe not working ("James Mandy")
----------------------------------------------------------------------------
From: [EMAIL PROTECTED] (Bill Unruh)
Subject: Re: Slow PPP Connection But Minicom Connection Fine
Date: 29 Mar 1999 01:14:25 GMT
In <[EMAIL PROTECTED]> chris turner <[EMAIL PROTECTED]> writes:
>I have a USR/3Com 56K Faxmodem (ISA PnP). I have set up the correct
>IRQs, ports, etc. and verified that they are working fine. When I dial
>out with Minicom, I get a good connection, usually at around 50K. But
>when I dial the same number with a chatscript running under pppd I only
>get a 9.6K connection. I can get a 50K connection from the chatscript if
>I run it AFTER I have dialed the same number from Minicom and then
>exited. The modem init strings for both Minicom and chat are the same
>(AT&F1), and I have all the settings in pppd as recommended (pppd
>connect 'chat -v -f /etc/ppp/chatscript -detach crtscts modem
>defaultroute /dev/modem 115200 user'myusername'). Any ideas on what is
This is a strange set of commands since you never terminate the quotes
starting just befor chat. I suspect what your pppd is getting is the
default stuff (which is 9600 Bd).
Try
/usr/sbin/pppd /dev/ttySx 115200 defaultroute -detach crtscts connect
"chat -f -f /etc/ppp/chatscript"
(ttySx should be whichever port you are connected to_)
>causing this and how to fix it?
>Thanks in advance
>Chris Turner
------------------------------
From: John Myers <[EMAIL PROTECTED]>
Subject: Re: HELP!! Final attempt at Samba installation
Date: 29 Mar 1999 01:31:56 GMT
M. Buchenrieder wrote:
>
> John Myers <[EMAIL PROTECTED]> writes:
>
> >Current "configuration" (using the word loosely!):
> >
> >Linux system;
> >486/66, 16Mb, 4.3Gb, SVGA (Trident9000),3C503
>
> Did yu setup your networking properly ? Is your 3C503 card
> detected at startup ? What does "ifconfig" tell you ?
Yes, I believe so (setup), but that's actually the theme of my question
(s). Yes, linux detects card at startup.
ifconfig -a returns the following:
lo Link encap: Local Loopback
inet addr: 127.0.0.1 Bcast 127.255.255.255 Netmask 255.0.0.0
BROADCAST LOOPBACK MTU:3584 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frames:0
TX packets:0 errors:0 dropped:0 overruns:0 frames:0
Collisions:0
eth0 Link encap: Ethernet HWaddr: 02:60:8C:A1:5A:AA
inet addr: 0.0.0.0 Bcast 0.0.0.0 Netmask 0.0.0.0
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frames:0
TX packets:0 errors:0 dropped:0 overruns:0 frames:0
Collisions:0
Base Address: 0x300 Memory: dc000-de000
After issuing command: ifconfig eth0 192.168.0.1 netmask 255.255.255.0 up
The second ifconfig -a returns:
lo Link encap: Local Loopback
inet addr: 127.0.0.1 Bcast 127.255.255.255 Netmask 255.0.0.0
BROADCAST LOOPBACK MTU:3584 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frames:0
TX packets:0 errors:0 dropped:0 overruns:0 frames:0
Collisions:0
eth0 Link encap: Ethernet HWaddr: 02:60:8C:A1:5A:AA
inet addr: 192.168.0.1 Bcast 192.1683.0.255 Netmask 255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frames:0
TX packets:0 errors:0 dropped:0 overruns:0 frames:0
Collisions:0
Interrupt:5 Base Address: 0x300 Memory: dc000-de000
>
> >Debian linux- (works...doesn't do much without apps of course)
>
> If you have Debian, you do have the apps right there at your hands.
While installing "packages" I selected several that sounded like working
applications, but have no idea where they are stored, or how to invoke any
of them.
> >X-Windows- (works...not sure what, if any, useful apps available)
X-Windows gives me a pitiful little clock, and 3 "windows", each of which
seems to be just a "brighter" version of the command line console. If
this is what it is supposed to do, I would just as soon uninstall it and
free up the wasted space.
>
> See above. It's just a matter of what you installed.
>
> >Samba (doesn't seem to do anything...)
>
> Samba per se doesn't do anything unless you setup your networking
> correctly.
>
> >
> >smb.conf- Have edited, written, re-written, copied (examples from every
> >imagineable source), modified, and re-modified file countless times.
> >No error messages, but no apparent ability to connect to Win 95 system.
>
> [...]
>
> You wouldn't perhaps want to tell us
>
> - what your networking setup does look like,
I assume you are asking about hardware.
Stripped down to the simplest possible configuration, just to get a
connection established:
(1) Win 95 "workstation" with 16bit Ethernet card, 10 base T cat 5
cabling, 8 port hub, (1) seemingly impotent "linux box",with 3c503 card
Regarding software configuration of Samba, have used so many different
smb.conf files I wouldn't know where to begin. Have currently reverted to
example smb.conf from "Tridge" site that reportedly is used with
Win95 "workstations" I added users to mimick the setup described in the
smb.conf file...users does not seem to be a problem though...can't even
get that far. I can't even see the linux box from the Win95 system
- what "ifconfig" and "route -n" are telling you,
> - what "dmesg" has to say about your NIC ?
route -n seems to give column headers without any info:
Destination Gateway Genmask Flags Metric Ref Use IFace
dmesg returns normal info about drive(s), ports, etc. Network specific
info follows:
3c503.c: Presently autoprobing (not recommended0 for a single card
3c503.c: v1.10 9/23/93 Donald Becker...
eth0: 3c503 at i/o base 0x300, node 02 60 8c a1 5a aa, using internal xcvr
eth0: 3c503 8Kb RAM, 8 Kb shared mem window at 0xdc000-oxddfff
>
> Unless you can provide useful information, I'm tempted to assume that
> you're just trolling.
Took me an hour to find out what "trolling" meant. The answer is, no.
Hope the information provided is "useful"
Thanks very much for the response,
John Myers
> Michael
> --
> Michael Buchenrieder * [EMAIL PROTECTED] *
http://www.muc.de/~mibu
> Lumber Cartel Unit #456 (TINLC) & Official Netscum
> Note: If you want me to send you email, don't munge your address.
================== Posted via SearchLinux ==================
http://www.searchlinux.com
------------------------------
From: "Systemic" <[EMAIL PROTECTED]>
Crossposted-To:
microsoft.public.windowsnt.misc,microsoft.public.windowsnt.setup,comp.os.linux.misc,comp.os.linux.setup,micorosft.public.outlook
Subject: Re: Using Linux instead of NT Server in home environment....
Date: Sun, 28 Mar 1999 17:42:35 -0800
Reply-To: "Systemic" <[EMAIL PROTECTED]>
Alexander I. Butenko <[EMAIL PROTECTED]> wrote in message
news:#H7f6dVe#GA.267@cppssbbsa03...
> Well,, I'd beter think that there is a Server for the client, not
> vice-versa. And one more - the question was about the OS for the home.
MOst
> hom eusers can't even properly configure Win98, so the most correct answer
> about the Server was not linux but WIndows NT. Anyway I do not wasn to
> continue this flame as most of this group members seem to gain nothing
from
> it.
Actually, I would probably recommend to the "average" home user to just use
a Windoze 95/98 peer-to-peer setup. Realistically, they're not going to
understand security issues, much less NT or a *nix of any kind. Hell, most
Windoze users that are clients of mine still think the're running
Windoze[insert current year here] and think the Internet is owned by AOL.
Now, the guy who originally posted this message seemed quite literate and
would probably be able to handle NT or Linux. His original post
specifically asked that a flame war like this one not be started. He stated
that NT was not right for his immediate need; his question was how well
LINUX handled his laundry list of requirements. In fact, to paraphrase the
last bit of that message:
=======snip=================================================================
========================
"What are your experiences when taking this approach? Does one have to
sacrifice many windas niceties in order to take advantage of Linux? &
please, no barking about how well Linux handles these services - I
know - I just want to know how well it compares to NT on the
usability/feature-wise scale."
=======snip=================================================================
========================
I haven't really heard anyone answer any of this gentleman's questions yet.
I don't have a really great answer so I'll defer on this. I just wanted to
point out that we seem to have lost the point and we're all (Linux groups
and NT groups) looking like over-zealous freaks who can't even answer
relatively straight forward questions.
My only comment would be that Linux will handle everything that NT will
handle. If you are using Outlook 98 on a Windoze 98 client, you can use
sendmail or some equivelent on the Linux server in place of Exchange. If
you really want to know how well everything integrates, think about the
Internet. At least 70% of all client machines that connect somehow to the
Internet are connecting and using services backboned by some Unix variant.
The only thing Linux requires is that you actually know something about all
of the hardware on your system. Not just, "I've got an STB video-card".
You have to know specifics. That may be a stretch for your average
PC-Magazine PHD.
I'll just stop now before I continue into a tirade about NT administrators,
who I try to deal with peacefully, on a day-to-day basis.
Systemic
------------------------------
From: [EMAIL PROTECTED] (M. Buchenrieder)
Subject: Re: ttyS? ??
Date: Sun, 28 Mar 1999 22:09:50 GMT
[EMAIL PROTECTED] (Thomas Laus) writes:
>I am running Linux 2.2.3 and there is a reference to using the cua0 -
>cua3 designations for outgoing serial ports for modems on page 397 of
>the SuSE Linux 6.0 book
Then please tell the folks at SuSE that they should update their
manual. cua* devices will not work anymore with recent kernels.
Michael
--
Michael Buchenrieder * [EMAIL PROTECTED] * http://www.muc.de/~mibu
Lumber Cartel Unit #456 (TINLC) & Official Netscum
Note: If you want me to send you email, don't munge your address.
------------------------------
From: "Mike" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: module/depmod problem.....
Date: Sun, 28 Mar 1999 19:43:46 -0500
I have upgraded from Redhat 5.1 to 5.2. When I boot I get error messages
that it cannot find modules net-pf-4 and 5 which are appletalk and ipx. I
have compiled my kernel to NOT include, these yet I still get the error.
My /etc/conf.modules file is bare except for the nic's aliases. The
/lib/modules/* path does not contain the offending calls.... When I do
modprobe -c I get the aliases that indicated the call to net-pf-4 and 5...
Where is this being stored for call???
Please help,
please copy [EMAIL PROTECTED] if you can...
TIA,
Mike
------------------------------
From: [EMAIL PROTECTED] (jedi)
Crossposted-To:
microsoft.public.windowsnt.misc,microsoft.public.windowsnt.setup,comp.os.linux.misc,comp.os.linux.setup,micorosft.public.outlook
Subject: Re: Using Linux instead of NT Server in home environment....
Date: Sun, 28 Mar 1999 17:46:04 -0800
On Sun, 28 Mar 1999 17:01:22 -0600, Ovidiu Popa <[EMAIL PROTECTED]> wrote:
>Johan, allow me to share a recent experience. I met some times ago a
>couple of genial (and I mean it) Linux programmers. Ones of the very
>few having "access" to Linus, having major contributions to Slack
>kernel, etc...
>
>Can you figure out what pissed me off about these guys? They turned
>out to be extremely appreciated programmers, one working (say 9 to 6)
>for a major software company, the other one being self-employed, both
>raising big bucks, as Windows C/S programmers. And they spend
>afternoons and nights aggressively bitching and hating NT in the
>usenet world, (and also on their web sites). Now, they do this on
>their time and dime, but don't ask me to appreciate their moral
>profiles. I might look old fashioned, but I can't spit the place which
>provides my beers, bread and butter.
>
>I asked them why are they not starting to write a decent GUI, some
>more friendly administration tools, reliable GUI development tools,
>able to allow the entry on the desktop and SOHO markets (I am not
>going to deny the Linux excellent performances, as server). Guess what
>answer I got... "Yuk man, it's no fun doing that".
>
>My personal opinion: soon, they will built a better Linux TCP/IP stack
>:-) Unfortunately, these genial programmers (and unfortunately Linux)
It is better that those that have the itch to scratch
or the interest in that area do the programming. Linux
works as well as it does because of the user programmer,
not the 'knight in shining armour' doing grunt coding for
someone else.
>will stay away from the desktop and SOHO markets, until some major
>company will get involved. BUT can a major software company afford to
>stay in the open source initiative mainstream, as far as they are
>supposed to make profits? Only time will tell...
>
>Ovidiu Popa
>MS-MVP (DTS)
>
>Johan Kullstam wrote in message ...
>>"Alexander I. Butenko" <[EMAIL PROTECTED]> writes:
>>
>>> ANyway I greatly doubt that Linux will be easier to use than NT
>>> Server. I'm sure that NT Server will be a ideal use for a small
>home
>>> network, becaus eit's very easy to configure comparable to Linux
>and
>>> supports most network clients better.
>>
>>since we're talking a server OS, don't we want to support network
>>*servers* better and not clients? who cares if netscape looks better
>>on NT than linux. what we really want to know is who can dole out
>>webpages better, both faster and more reliably.
>>
>>and once we are talking service, NT is going to lose hard.
>>
>>apache runs better on linux than NT. apache blows MS's offering
>>(what's it called, IIS?) away in speed, price and marketshare. samba
>>runs better on linux than NT can do it's own filesharing protocol.
>>NFS is better in linux than on NT. ftp servers (ftpd) are easier and
>>work better in linux than NT. MTAs like qmail blow the crap out of
>>exchange. the list just goes on and on.
>>
>>a final note, what about uptimes? linux is *much* more robust than
>NT
>>(unless you consider BSOD to be a debug mode and not downtime).
>>
>>--
>> J o h a n K u l l s t a m
>> [[EMAIL PROTECTED]]
>> Don't Fear the Penguin!
>
--
"I was not elected to watch my people suffer and die |||
while you discuss this a invasion in committe." / | \
In search of sane PPP docs? Try http://penguin.lvcm.com
------------------------------
From: [EMAIL PROTECTED] (jedi)
Crossposted-To:
microsoft.public.windowsnt.misc,microsoft.public.windowsnt.setup,comp.os.linux.misc,comp.os.linux.setup,micorosft.public.outlook
Subject: Re: Using Linux instead of NT Server in home environment....
Date: Sun, 28 Mar 1999 17:44:15 -0800
On Sun, 28 Mar 1999 23:13:52 +0300, Alexander I. Butenko <[EMAIL PROTECTED]> wrote:
>Well,, I'd beter think that there is a Server for the client, not
>vice-versa. And one more - the question was about the OS for the home. MOst
>hom eusers can't even properly configure Win98, so the most correct answer
>about the Server was not linux but WIndows NT. Anyway I do not wasn to
In which case, they are going to be wide open the moment the
put that bugger on the net. Subsequently securing it will be
no less difficult than dealing with ip-chains or samba.
>continue this flame as most of this group members seem to gain nothing from
>it.
[deletia]
--
"I was not elected to watch my people suffer and die |||
while you discuss this a invasion in committe." / | \
In search of sane PPP docs? Try http://penguin.lvcm.com
------------------------------
Crossposted-To:
microsoft.public.windowsnt.misc,microsoft.public.windowsnt.setup,comp.os.linux.misc,comp.os.linux.setup,micorosft.public.outlook
Subject: Re: Using Linux instead of NT Server in home environment....
From: Johan Kullstam <[EMAIL PROTECTED]>
Date: 28 Mar 1999 17:34:02 -0500
"Alexander I. Butenko" <[EMAIL PROTECTED]> writes:
> Well,, I'd beter think that there is a Server for the client, not
> vice-versa.
*boggle* what exactly are you trying to say? this sentence doesn't
make any sense to me.
> And one more - the question was about the OS for the home. MOst
> hom eusers can't even properly configure Win98, so the most correct answer
> about the Server was not linux but WIndows NT.
but if you can't do win98, wtf are you doing with nt server? windows
nt is kind of like windows 98. they are different enought that once
you get under the skin lot of stuff is different so that a competent
win98 user may get lost. they are alike enough that someone who can't
do win98 won't be able do windows nt.
so they can't configure win98 properly. i readily admit, *i* can't
configure win98 (more truthfully, i can't abide by it but i digress).
i, however, *can* do linux!
> Anyway I do not wasn to continue this flame as most of this group
> members seem to gain nothing from it.
perhaps that is because they cannot/will not change their minds no
matter what.
--
J o h a n K u l l s t a m
[[EMAIL PROTECTED]]
Don't Fear the Penguin!
------------------------------
From: "D. C. & M. V. Sessions" <[EMAIL PROTECTED]>
Subject: IDENT on masquerade?
Date: Mon, 29 Mar 1999 02:18:20 +0000
I'm stumped. The IP masquerade *seemed* to be running well,
but transfers just died in the middle. Finally tracked it
down to a port 113 (ident) transaction which (duh!) the
firewall machine couldn't give a user ID for the stream.
This may be a _DUH!_ case but couldn't find it in the usual
places. The _Linux_Network_Toolkit_ is totally silent on
the subject. Anyone have a clue how to fake up a fix?
(BTW, news reading is unreliable till I get this fixed.
Please mail. dcs)
--
He either fears his fate too much, or his deserts are small,
That puts it not unto the touch to win or lose it all.
D. C. & M. V. Sessions [EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Linux + 2 Ethernet cards
Date: Mon, 29 Mar 1999 02:15:49 GMT
In article <[EMAIL PROTECTED]>,
"William R. Mattil" <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
>
> > In article <[EMAIL PROTECTED]>,
> > "William R. Mattil" <[EMAIL PROTECTED]> wrote:
> > > Tom Neilson wrote:
> > >
> > > > [EMAIL PROTECTED] wrote:
> > > > : In article <[EMAIL PROTECTED]>,
> > > > : Raymond Doetjes <[EMAIL PROTECTED]> wrote:
> > > > :> Read the Multi Homed howto. There you see how to add a eth1 as lilo
> > > > :> parameters this does work.
> > > > :>
> > > > :> Raymond
> > > > :>
> > > >
> > > > : I looked everywhere for this "Multi Homed howto," but couldn't find
it.
> > Does
> > > > : anyone know where I can find this?
> > > >
> > > > : --Daniel
> > > >
> > > > : -----------== Posted via Deja News, The Discussion Network
==----------
> > > > : http://www.dejanews.com/ Search, Read, Discuss, or Start Your
Own
> > > >
> > > > Practical example:
> > > >
> > > > # LILO configuration file
> > > > # generated by 'liloconfig'
> > > > #
> > > > # Start LILO global section
> > > > append="eth0,0x210,9 eth1,0x6780,5"
> > > > boot = /dev/hda
> > > > vga = normal
> > > > # End LILO global section
> > > > # Linux bootable partition config begins
> > > > image = /boot/zImage
> > > > root = /dev/hda1
> > > > label = linux
> > > > read-only
> > > > # Linux bootable partition config ends
> > > >
> > > >
> > >
> > > This will only work if support for the NIC's is compiled directly into the
> > kernel.
> > > Not supported as modules. IIRC this is the most glaring error in the
Multi0NIC
> > > Howto.
> > >
> > > Regards
> > > Bill
> > >
> > > --
> > > William R. Mattil | Fred Astaire wasn't so great.
> > > [EMAIL PROTECTED] | Ginger had to do it all backwards
> > > (972) 399-4106 | and... in high heels.
> > >
> > >
> >
> > I beg to differ. I finally got my two cards recognized using the lilo.conf
> > method of initializing the cards. Unless I am mistaken, my drivers are not
> > directly compiled into the kernel. I.e., it is an out of the box
installation
> > of TurboLinux 1.0 and during the installation, I specifically skipped auto-
> > probing and loading of my network card drivers.
> >
> > Works like a charm.
> >
> > BUT, it is very important to mention, another thing I did to REALLY make the
> > bad boy work in its entirety (is that how you spell entirety???)
> >
> > In my /etc/conf.modules I entered the following:
> > alias eth0 lance
> > options lance io=0xfce0 irq=11
> > alias eth1 3c59x
> >
>
> Let me see if I get this right, You are telling me that I am wrong and then
in the
> very same response you confirm exactly what I said ???? Curious.......
>
> But make no mistake about it, LILO will not pass parameters to the modules.
Read
> through the source code if you have any real doubts. And please don't confuse
the
> issue for those are are already confused enough on this issue.
>
> > (For some reason, options were REQUIRED to make my lance driver load, while
my
> > 3c59x driver REFUSED to work, IF I entered options. Go figure).
> >
> > Going back to my previously mentioned /etc/lilo.conf set up, here is what I
> > did: append "ether=0,0,eth0 ether=0,0,eth1"
> >
> > Oh, one more thing, out of the box, both cards shared the same IRQ 11. As
> > there were no jumpers to let me reset these IRQs, or the necessary
> > configuration software that everyone claims is shipped with 3com cards, I
was
> > forced to go into the BIOS setup (F2 while the machine boots up), and change
> > each PCI Bus setting from "Auto-Detect" to my desired settings, in this case
> > IRQ11 for PCI bus 1, and IRQ10 for PCI bus 3. (PCI Bus 2 was being used by
> > the monitor and was set to IRQ 9).
> >
> > Very simple to implement, very difficult to troubleshoot and pin down.
Hours
> > of trial and error, rounds of sleepless nights.
>
> >
> > Just for reference, I have an HP Vectra XA, an AMD PCnet PCI network card
(the
> > lance.o driver), and a 3Com 3c905B card (the 3c59x driver).
> >
> > Whew.
> >
> > --Daniel G. Rodriguez
> >
> >
>
> On the island of the blind a one eyed man would be king
>
> Bill
> --
> William R. Mattil | Fred Astaire wasn't so great.
> [EMAIL PROTECTED] | Ginger had to do it all backwards
> (972) 399-4106 | and... in high heels.
>
>
Hi William. The last thing I want to do is confuse others. As a matter of
fact, I want to help others.
Maybe I was off on some theory about how NICs are compiled into the kernel, so
for clarification:
- At what point exactly is the NIC compiled into the kernel? There are three
main steps described above--I edit the lilo.conf, then the conf.modules, then
reboot the system. Does this in essence, "compile the driver into the
kernel???"
- If not, when is it compiled into the kernel?
- When you say the NIC, are you referring specifically to each card's
respective driver?
--Daniel
P.S. I made no bold assertions as to WHY and HOW things worked, I simply
explained step by step what worked for me in hopes of assisting someone else
stuck with the same problem. I recently switched from MS Windows to Linux and
am still trying to learn HOW things work. My apologies to all those who I may
have lead astray.
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: "James Mandy" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.questions,comp.os.linux.help
Subject: Re: modprobe not working
Date: Mon, 29 Mar 1999 10:29:19 +0800
did you do a "make dep" "make zImage" "make modules" "make modules_install"
~$ cd /etc
~$ vi lilo.conf
add the entry for your new kernel. rename the old one to linux-old or
something so you can still boot it if required.
~$ lilo
~$ shutdown -r now
You must make modules and make modules install. then restart lilo. Then
again I spose you would have restarted lilo and so on, coz otherwise you
wouldnt be getting the new errors.
I recommend updating your kernel to 2.2.1 + (2.2.4 pref) Also remove "Kernal
auto loader" or whatever it is in the config of your kernel.
Cheer's James.
> Hi,
> Hope someone could give me some answers, I've been looking for the
> last 4 day's for the answer. I'm using Redhat 5.2 as my server and
> gateway to access the internet through @home. I re-compiled my kernel
> (2.0.36) and after I compiled it, and rebooted it now gives me the
> following errors messages on boot up.
>
> /lib/modules/2.0.36/fs/binfmt_aout.o: unresolved symbol(s)
> /lib/modules/2.0.36/misc/ipx.o: unresolved symbol(s)
> /lib/modules/2.0.36/misc/appletalk.o: unresolved symbol(s)
> /lib/modules/2.0.36/net/eql.o: unresolved symbol(s)
> /lib/modules/2.0.36/net/bsd_comp.o: unresolved symbol(s)
> /lib/modules/2.0.36/ipv4/ip_masq_quake.o: unresolved symbol(s)
> /lib/modules/2.0.36/ipv4/ip_masq_vdolive.o: unresolved symbol(s)
> /lib/modules/2.0.36/ipv4/ip_masq_cuseeme.o: unresolved symbol(s)
> /lib/modules/2.0.36/ipv4/ip_masq_raudio.o: unresolved symbol(s)
> /lib/modules/2.0.36/ipv4/ip_masq_irc.o: unresolved symbol(s)
> /lib/modules/2.0.36/ipv4/ip_masq_ftp.o: unresolved symbol(s)
>
> Also now the ipfwadm does not work on startup. I have to do it
> manually. The following is inserted into my "rc.local" file which is
> located in /etc/rc.d/.
>
> /sbin/depmod -a
> /sbin/modprobe ip_masq_ftp
> /sbin/modprobe ip_masq_raudio
> /sbin/modprobe ip_masq_irc
>
> /sbin/ipfwadm -F -p deny
> /sbin/ipfwadm -F -a m -S xxx.xxx.xxx.xxx/24 -D 0.0.0.0/0
> /sbin/ipfwadm -F -a m -S xxx.xxx.xxx.xxx/24 -D 0.0.0.0/0
>
> xxx.xxx.xxx.xxx is not my real setting, it has a valid Class IP.
>
>
> Hope soomeone can help?
------------------------------
** 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
******************************
