Linux-Networking Digest #883, Volume #9 Fri, 15 Jan 99 03:14:07 EST
Contents:
Re: You won't crack this one... ("Charles Stack")
Newbie with card problems ("Trotter")
DNS/DHCP behavior (Yan Seiner)
Help with PPP InternetMCI (CWIX) ("Tim Underwood")
PPP dial-out to ISP problem ... (The Blaster)
Where is SO_RCVLOWAT? (Claus Ritter)
Re: IP Masq. Puzzler (Kevin Martin)
Re: ppp-on connects, but no routing (schlemiel)
Re: ip-up problem (Larry Rivera)
Re: Lunux questions (jamie)
VPN / PPTP (Yan Seiner)
Compilation of 3c59x.c result in some errors. (Chang-Cheng (Eric, Chao))
Setting up imapd: how to check? (S P Arif Sahari Wibowo)
Re: PPP dial-out to ISP problem ... (Mark Cooperstein)
Revamped dialin server setup guide (Josh Gentry)
Re: Net-Tools help! (jamie)
3c509 ("Kris Jordan")
Re: IP Forwarding To Web Server (Raymond Doetjes)
Re: I know nothing (John Wolanski)
Re: Obtaining MAC address from remote computer ("Sander Pilon")
----------------------------------------------------------------------------
From: "Charles Stack" <[EMAIL PROTECTED]>
Subject: Re: You won't crack this one...
Date: Thu, 14 Jan 1999 09:42:34 -0500
Perhaps your cable (or port if you are using a hub) is bad?
cjs
Martin Edelius wrote in message <[EMAIL PROTECTED]>...
>Whoever cracks this one is not from this world...
>
>I have a RH 5.2 box that I'm about to develop some SQL on. Since I'm not
>that comfortable with Linux setup and config I had a good friend of mine
>that works as an sysadmin at Chalmers (large Swedish tech university) help
>me out. He helped me install the latest RH distr, MySQl, PHP3, Apche,
>whatever. We ran a bunch of tests and everything worked fine.
>
>When I came back to my office I hooked up the Linux box to our network and
>nothing happens. It boots without any problems but it's absolutely dead as
>far as networking is concerned.
>
>If I do a tcpdump it's completely silent and I can't ping to the Linux box
>or from it. There's absolutely no activity on the hub when I do a ping to
my
>PC, tcpdump displays a "arp who-has 192.168.92.100 tell 192.168.92.99" but
>that's it. I've been reconfiguring ifcfg-eth0, nsswitch.conf, network and
>just about every other network related file I can think of about a billion
>times but to no use. If I add an entry to the arp cache manually (my PC for
>instance) I can ping out and get activity on the hub and tcpdump displays a
>request for an icmp echo from 192.168.92.100 (my PC) but there's no reply.
>
>When we ran tcpdump on my friends net there was activity like hell but not
a
>damn thing here. And I didn't change a thing! I unplugged it from his
>network and plugged it in here. We even configured the Linux box with my
>settings (ip, gw, etc.) and it ran just fine in his net. Not at all in
mine.
>
>Any ideas are more than welcome. I'm going nuts here...
>
>
>
>Martin Edelius
>[EMAIL PROTECTED]
>(Remove the nospam part in my e-mail when you reply directly)
>
>
------------------------------
From: "Trotter" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware,comp.os.linux.questions
Subject: Newbie with card problems
Date: Fri, 15 Jan 1999 04:54:09 GMT
Hi, I just installed Redhat 5.2. I am using an intel etherexpress 16
network card and the semi-auto detect thing will not see it. I have clicked
every intel etherexpress thing they have and the auto-probe thing says "I
can't detect this device on your system." Does Linux hate me and not
support my card or am I do something wrong? thanks.
- Trotter
------------------------------
From: Yan Seiner <[EMAIL PROTECTED]>
Subject: DNS/DHCP behavior
Date: Thu, 14 Jan 1999 08:33:25 -0500
Reply-To: [EMAIL PROTECTED]
I have both DNS (named) and DHCP (dhcpd) running. On the linux box, DNS
fails to resolve any requests for machines given IPs by DHCP.
DNS requests over the network are resovled.
SO, on the linux box, ping othello produces unknown host, but on a NT WS
on the network ping othello produces the correct result.
named is bound to eth0, and apparently it is ignoring any requests
coming in locally.
How do I get DNS to resolve the names on the linux box?
Yan
------------------------------
From: "Tim Underwood" <[EMAIL PROTECTED]>
Subject: Help with PPP InternetMCI (CWIX)
Date: Thu, 14 Jan 1999 15:18:38 GMT
There were a couple of posts a week or two ago that someone had solved the
login to MCI/CWIX on RH 5.2. If anyone has gotten this to work, please
email me and/or post a www site with the "how I did it".
I've been through umpteen sites, FAQs, etc. to no avail.
I use minicom to check it out, the modem connects I get what appears to be a
terminal node id.
Something like: (601486)
Hitting enter just returns back the same prompt, until the connection times
out.
Keying in anything else, like my 16 digit user ID, 24 digit password (ala
PAP/CHAP), or anything else simply returns with "******* host not found
********"
------------------------------
Date: Fri, 15 Jan 1999 02:19:07 +1100
From: The Blaster <[EMAIL PROTECTED]>
Subject: PPP dial-out to ISP problem ...
Hello -
I have a problem dialing out to my ISP from my Linux box ...
I have RedHat Linux kernel 2.0.34, running pppd 2.3.3 (haven't had the
chance to upgrade the kernel
yet, ok ???)
When I dial out to the ISP, the log shows me that I get as far as being
able to receive an IP from the
ISP, but after about 5-10 secs, the connection just drops out ...
The ISP is using PAP and I have an allocated IP from the ISP ... I
believe that I have configured the
scripts necessary correctly (or I suppose the dial-out wouldn't be
getting as far as it is getting) ...
My brain is fried from trying to figure out why the line keeps dropping
...
I'd heard that there might have been a problem with the PAP script, but
I'm not sure if that's valid
or not ...
Hopefully, someone can point out what might be the problem so I can
finally get some sleep ...
Much obliged ...
PS: If I dial out to an ISP which has dynamic allocation of IPs, I don't
seem to have any problems
keeping the connection ...
------------------------------
From: Claus Ritter <[EMAIL PROTECTED]>
Subject: Where is SO_RCVLOWAT?
Date: Thu, 14 Jan 1999 16:27:06 +0100
Hi
I want to use the select mechanism to inform threads if
data can be read or write from/to a socket
You can adjust the send/receive buffer low water mark
to optimize this.
I'm using redhat linux 5.2(i-386) and I couldn't find
a header which contains SO_RCVLOWAT or
SO_SNDLOWAT, although the man page of
getsockopt described them as possible parameters.
On solaris it was no problem, and I could find it
in sys/socket.h.
Obviously it is not implemented yet, so does anybody
know what the alternative for this is?
Thanx
Claus
------------------------------
From: [EMAIL PROTECTED] (Kevin Martin)
Subject: Re: IP Masq. Puzzler
Date: Thu, 14 Jan 1999 15:35:07 GMT
In article <[EMAIL PROTECTED]>, it says
[EMAIL PROTECTED] (Chris Deever) wrote:
>I've found that I get different performace with IP Masq. with
>different ISPs - but the performance difference occurs only through
>masqerading and I'm not sure why.
Check your MTU settings.
------------------------------
From: schlemiel <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,linux.redhat.misc
Subject: Re: ppp-on connects, but no routing
Date: Thu, 14 Jan 1999 10:44:26 -0500
I'm also having a similar problem except when I type ifconfig I don't see the lo
device. I have red hat 5.1 so I think routing is compiled into the kernel.
Furthermore I cannot ping my self or log into my own computer (using rlogin and
the ip adress given by ifconfig).
A.G. wrote:
> I have managed to make my RH5.2 installation dial and connect to my ISP
> finally. But the connection is not working. I just can't reach any remote
> site.
>
> When I ping myself on my 'inet addr' from "ifconfig", everything's fine Ping
> the server at its IP doesn't work at all...
>
> Here are printouts of "ifconfig" and "netstat -nr" commands:
>
> [root@localhost /root]# ifconfig
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
> UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1
> RX packets:83 errors:0 dropped:0 overruns:0 frame:0
> TX packets:83 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0
>
> ppp0 Link encap:Point-to-Point Protocol
> inet addr:209.90.132.98 P-t-P:209.90.128.82 Mask:255.255.255.0
> UP POINTOPOINT RUNNING MTU:1500 Metric:1
> RX packets:5 errors:0 dropped:0 overruns:0 frame:0
> TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0
> Memory:16a0038-16a0c04
>
> [root@localhost /root]# netstat -nr
> Kernel IP routing table
> Destination Gateway Genmask Flags MSS Window irtt
> Iface
> 209.90.128.82 0.0.0.0 255.255.255.255 UH 1500 0 0
> ppp0
> 127.0.0.0 0.0.0.0 255.0.0.0 U 3584 0 0 lo
> 0.0.0.0 209.90.128.82 0.0.0.0 UG 1500 0 0
> ppp0
>
> [root@localhost /root]# ping 209.90.128.82
> PING 209.90.128.82 (209.90.128.82): 56 data bytes
>
> Can you see anything abnormal in these printouts?
>
> Any input greately appreciated.
>
> A.G.
------------------------------
From: Larry Rivera <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Crossposted-To: linux.redhat.ppp
Subject: Re: ip-up problem
Date: Thu, 14 Jan 1999 11:55:06 -0400
Jonas wrote:
>
> Thanks Larry. This was a realy good explanation 'bout LRP. I'm realy new on
> this so every information I can get helps.
>
> I have seen the rules in /etc/inet.d/network.sh and used the to forward
> packets but I thought that I had to use ip-up because I don't have a static
> ip so the only way is to do a firewall script that uses the ip adress I get
> from pppd at the time of each connection.
> Can this realy be done from /etc/inet.d/network.sh? If so can anybody
> (Larry) post some examples on how this should look with dynamic ip.
>
> TIA /Jonas
It would help if you could say exactly what type of routing you are
going to implement. LRP can do all kinds of routing, e.g., proxyarp vs.
straight through routing, etc. What is your exact scenario and intent?
LR
------------------------------
From: [EMAIL PROTECTED] (jamie)
Subject: Re: Lunux questions
Reply-To: [EMAIL PROTECTED]
Crossposted-To: alt.linux,alt.os.linux,hk.comp.os.linux,tw.bbs.comp.linux
Date: Fri, 15 Jan 1999 00:30:27 -0600
Glenn Davy <[EMAIL PROTECTED]> wrote:
funny, most of the ones you didn't answer I thought were self
explanatory
>>boot ------------ ??
files used to boot the partition, like the system map.
>>root -------- ?????
the home directory for the root account
>>tmp ---------- ??????
temporary files
>>lost+found --------- ????
This one is obscure, and I don't think I've had to fish a file out of
lost+found since sometime in the '80s. If I remember correctly, if when a
disk error causes a file to lose its path and filename, it ends up here.
Similar to when DOS checkdsk would output FILECHK.001 FILECHK.002 with
files that had lost their names.
--
jamie ([EMAIL PROTECTED])
"There's a seeker born every minute."
------------------------------
From: Yan Seiner <[EMAIL PROTECTED]>
Subject: VPN / PPTP
Date: Thu, 14 Jan 1999 09:54:26 -0500
Reply-To: [EMAIL PROTECTED]
has anyone been successful in setting up a VPN between a linux server
and a Win95 machine?
The win95 box has a IP address that changes every time I log on. The
linux box has a fixed IP.
Any pointers to FAQs, HOWTOs, etc. would be welcome.
I have read the sunsite HOWTO and it does nto apply to win32 :-(
Yan
------------------------------
From: [EMAIL PROTECTED] (Chang-Cheng (Eric), Chao)
Subject: Compilation of 3c59x.c result in some errors.
Date: Fri, 15 Jan 1999 05:46:39 GMT
I went into some compilation errors when compiling 3c59x.c V0.99H
11/17/98 (the latest driver). These are the errors:
3c59x.c:94: parse error before `<'
3c59x.c: In function `vortex_probe1':
3c59x.c:879: stray '\' in program
3c59x.c:879: parse error before `;'
3c59x.c:926: `mii_preamble_required' undeclared (first use this
function)
3c59x.c:926: (Each undeclared identifier is reported only once
3c59x.c:926: for each function it appears in.)
3c59x.c: In function `mdio_read':
3c59x.c:2047: `mii_preamble_required' undeclared (first use this
function)
3c59x.c: In function `mdio_write':
3c59x.c:2079: `mii_preamble_required' undeclared (first use this
function)
===========
If you know what is the problem, please tell me. Also I'm wondering is
there any site that has a pre-compiles version for kernel 2.0.36 (I'm
using Red Hat 5.2). Thanks.
Chang
------------------------------
From: S P Arif Sahari Wibowo <[EMAIL PROTECTED]>
Crossposted-To: comp.mail.imap,comp.os.linux.setup,comp.mail.pine,linux.redhat.install
Subject: Setting up imapd: how to check?
Date: Fri, 15 Jan 1999 00:33:14 -0600
Hi!
I just setting up the imapd from pine 4.05 package in a RedHat linux
system, however when I try to login using Netscape from other machine, it
always fail to login (as if it was from wrong password).
Any idea on this? How I check what actually happened?
Thanks.
S. P. Arif Sahari Wibowo
_____ _____ _____ _____ [EMAIL PROTECTED]
/____ /____/ /____/ /____ http://www.uiuc.edu/ph/www/arifsaha
_____/ / / / _____/
------------------------------
From: [EMAIL PROTECTED] (Mark Cooperstein)
Subject: Re: PPP dial-out to ISP problem ...
Date: Thu, 14 Jan 1999 16:06:16 GMT
in your shell scripts that start up pppd (whatever your using: ifup, ipup, or
whatever...) you want to make sure that you have "debug" as an pppd command
line option. Then, you can look in /var/log/messages and see what transpired
during the actual connection/negociation with your ISP. Without the debug
option, you don't see all of the negociation that chat attempted with your
modem/isp, etc.
Another thing is to put the following entry in /etc/syslog.conf
# this will enable ppp logging
daemon.* /var/log/ppp-log
Next time you boot, or restart syslogd it will start logging ppp activity in
/var/log/ppp-log
Maybe this will help?
Regards,
Mark
In article <[EMAIL PROTECTED]>, The Blaster
<[EMAIL PROTECTED]> wrote:
>Hello -
>
>I have a problem dialing out to my ISP from my Linux box ...
>
>I have RedHat Linux kernel 2.0.34, running pppd 2.3.3 (haven't had the
>chance to upgrade the kernel
>yet, ok ???)
>
>When I dial out to the ISP, the log shows me that I get as far as being
>able to receive an IP from the
>ISP, but after about 5-10 secs, the connection just drops out ...
>
>The ISP is using PAP and I have an allocated IP from the ISP ... I
>believe that I have configured the
>scripts necessary correctly (or I suppose the dial-out wouldn't be
>getting as far as it is getting) ...
>My brain is fried from trying to figure out why the line keeps dropping
>....
>
>I'd heard that there might have been a problem with the PAP script, but
>I'm not sure if that's valid
>or not ...
>
>Hopefully, someone can point out what might be the problem so I can
>finally get some sleep ...
>
>Much obliged ...
>
>PS: If I dial out to an ISP which has dynamic allocation of IPs, I don't
>seem to have any problems
>keeping the connection ...
>
>
** Remove ".nospam" when replying or email will bounce back to you...
------------------------------
From: [EMAIL PROTECTED] (Josh Gentry)
Subject: Revamped dialin server setup guide
Date: Thu, 14 Jan 1999 22:35:56 -0800
Folks,
A few weeks ago I posted a message that I had written a report of setting up
a Linux dialin server. There
was some positive response, which prompted me to write a new, much expanded
and hopefully much
improved document. http://www.swcp.com/~jgentry/dialin.html
Josh
*** Posted from RemarQ - http://www.remarq.com - Discussions Start Here (tm) ***
------------------------------
From: [EMAIL PROTECTED] (jamie)
Subject: Re: Net-Tools help!
Reply-To: [EMAIL PROTECTED]
Crossposted-To: alt.linux,alt.os.linux,comp.os.linux.help,linux.redhat.misc
Date: Fri, 15 Jan 1999 00:37:45 -0600
Jeff Volckaert <[EMAIL PROTECTED]> wrote:
>Redhat 5.x (blantly assuming you use this like I do) has masq support built
>into the kernel. After a fresh install with both nics working you should be
>able to just run your ipfwadm commands.
just curious, I've never used Redhat, just Slackware,
and I've always compiled my own kernel and modules after upgrading.
Does Redhat just come with some humongous kernel compiled with support
for everything turned on?
--
jamie ([EMAIL PROTECTED])
"There's a seeker born every minute."
------------------------------
From: "Kris Jordan" <[EMAIL PROTECTED]>
Subject: 3c509
Date: Thu, 14 Jan 1999 20:40:17 -0800
I have a 3c509 card in a computer and it seems to work perfectly fine for
only awhile. After that while it seems to just stop working, especially if
I start to send large files over it. This does not happens when I use this
card with windows. I don't see any errors.
I'm not sure if this is related, but when I installed RedHat on this
computer, awhile through the setup, things start to go real slow, because it
starts to access the cdrom or floppy a lot every time I press a key. I
think it could be the network card, since it happed in another computer, but
I also had it happen with out the network card in.
Also, when this computer shuts down it seems not to want to shut some of the
programs off properly, no such pid. rpc.mountd, sendmail, smbd, named and
related. Those are network stuff.
I think I have changed the settings on the nic it self with no solution, but
maybe I have not found the correct combination.
Thanks for any help given,
Kris Jordan
------------------------------
From: Raymond Doetjes <[EMAIL PROTECTED]>
Subject: Re: IP Forwarding To Web Server
Date: Thu, 14 Jan 1999 17:08:25 +0100
This is a multi-part message in MIME format.
==============C2F96E69B9262494C45ECD05
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
If I understand correctly you've got a gateway server and behind that
gateway server you've got a other machine running as a WWW server.
Masquerading isn't a portforwarding service.
What you need is rinetd. rinetd is a deamon service wich runs in the
background. You have a /etc/xxx (dunno the exact name, but in there your
write the ip address on wich your webserver is and the port number wich it
runs on forinstance 192.168.1.2 80
This forwards every IP call on port 80 towards the ip address 192.168.1.2.
It works with almost every protocoll except for FTP since FTP uses multiple
sockets per session.
Raymond
David Khait wrote:
> I have a local network and a gateway which performs Masquerading and
> Forwarding work. Now I'd like to set up a Web server BEHIND the
> gateway. Unfortunately, using the line mentioned in the Firewall HOWTO
> didn't do it: requests to gateway's web port end up on gateway's web
> server. The line is:
>
> # Forward Web connections to your Web Server
> ipfwadm -F -a accept -b -P tcp -S 0.0.0.0/0 1024:65535 -D 192.168.1.3 80
>
> Furthermore, doing the above-mentioned thing seemed to eventually (not
> even right away) screw up my firewall. I wonder if the HOWTO is right:
> the idea seems to be to forward all tcp packets to the port 80 of web
> server. Notice that this line comes after I run
>
> ipfwadm -F -p deny
> ipfwadm -F -a m -S 192.168.1.0/255.255.255.0 -D 0.0.0.0
>
> to set up my regular services.
>
> Boris
==============C2F96E69B9262494C45ECD05
Content-Type: text/x-vcard; charset=us-ascii; name="vcard.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for Raymond Doetjes
Content-Disposition: attachment; filename="vcard.vcf"
begin: vcard
fn: Raymond Doetjes
n: Doetjes;Raymond
org: SYNAPSES IT
adr: Overijsselhaven 47;;;Nieuwegein;Utrecht;3433 PH;The Netherlands
email;internet: [EMAIL PROTECTED]
title: programmeur VAB
tel;work: 030 6066411
tel;fax: 030 6067871
x-mozilla-cpt: ;0
x-mozilla-html: FALSE
version: 2.1
end: vcard
==============C2F96E69B9262494C45ECD05==
------------------------------
From: John Wolanski <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: I know nothing
Date: Thu, 14 Jan 1999 11:28:56 -0500
I have to date not set this up with Slackware (will actually be doing it
this weekend, though!), but have done so with RedHat with complete
success! The first important thing you have to know is if your cable
modem provider uses DHCP (Dynamic Host Configuration Protocol). DHCP is
a type of networking connectivity where a server gives a client an IP
address (internet address, basically), and quite possibly a different
one every time they logon to the service. This is quite common. The
only problem you'll have if they DO use it is that (I believe) Slackware
3.4 doesn't come with the necessary software to utilize DHCP.
I have RoadRunner service for my cable modem and found all that I needed
at links from this website:
http://home.tampabay.rr.com/philip1/cable.htm
At the following website, I got information specific to RR in Columbus,
Ohio, but alot of the setup instructions would be similar (besides the
authorization server which you might or might not need to know,
depending on your provider):
http://www.vortech.net/rrlinux/rrlogin1.htm
Also go here for more info about masquerading:
http://www.indyramp.com/masq/
Ok. Now you're going to need to have two network cards in the Linux
computer (which I'll call the server from here on out). One is going to
connect to the cable modem and the other to the internal network (your
Windows computers which I'll call clients). You should also give
yourself a 16Megabyte swap partition in the installation. The rest of
what you need should fit just fine on what you have left.
When you install Slackware, try not to install stuff that you know you
won't need such as games, printer programs and X Windows. You WILL need
good text editors to edit all the stuff you'll have to do to get
everything up and going, though. The default text editor that comes
with Slackware is called elvis (heheh) and will be just fine for your
editing needs. You will, however, need to know how to work it. For
this, I recommend looking for a cheap, small, "using Linux" book of any
kind that gives tutorials on using the text editor called vi (which
elVIs is just a small clone of anyway....). The Quick Reference Edition
of Linux for Dummies is good for this -- try looking in closeout racks
for older books!
The first thing you need to do is to get networking set up in the
server. I would recommend first experimenting with just getting all the
computers on the internal network to recognize each other (via the
ping command and pinging each computer's IP address from the other).
Get familiar with setting up networking BEFORE you launch yourself
head-first into masquing because it'll make masquing all that much
easier to do (actually, once you have the cable connection working and
the internal network running, the masquing is the EASY part and only
requires two commands - hehehe).
Now try to get the Linux computer to connect to the cable modem by
following the information on the pages above (if you have RoadRunner).
If your cable modem company gives you a static (i.e. - nonchanging) IP
address then setting all this up will be a breeze! At any time, you can
test your internet connection out by pinging a common internet address,
such as: 152.2.254.81 (which is the address for sunsite.unc.edu, by
the way). If you get a reply that gives you an ammount of time in
milliseconds, then you're all set! Now you have to make sure that you
have your nameservers set up correctly. If you use DHCP, this will
happen automatically (at least it should). If not, you'll have to edit
the /etc/resolv.conf file and add them in by hand.
I recommend that, once you get everything tested and can comfortably set
up a network and connect to the internet that you then re-install Linux
because all sorts of files and such are going to be messed with and when
you go for the final run, you'll want a nice, clean system again. What
the hey! You've got the time, right?
You can email me at: jpwolanski at juno dot com
for help with setting up the network cards, etc., as giving a beginner's
course on that would be too much for this post right now...
Common IP addresses for an internal, private network are:
192.168.1.1 <---for the server
192.168.1.2 <---for client #1
192.168.1.3 <---for client #2
etc.....
Additionally, you will have the following addresses assigned to the
computers as well:
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.1 <----for the clients
Broadcast Address: 192.168.1.255
Primary Nameserver (DNS): for both primary and secondary nameservers,
you'll need the name servers from your cable modem provider. These can
be found out by running winipcfg.exe from Windows and going into the
"details" box.
For these addresses, the address, with the last number replaced by a
zero is what's called your "network address" -- not to be confused with
host address (which is the address of the individual computer). So the
network address for the above setup would be: 192.168.1.0 You'll need
this number for when you set up the masquing.
To set up masquerading is easy. Remember, the entire internal network
as well as the server's connection to the internet must all be fully
functional before you do this! Otherwise, nothing'll work the way you
want.
Once everything is set up, you'll use the program ipfwadm (I do hope
that Slackware comes with it, I'll have to check.....) and issue it like
this:
ipfwadm -F -p deny
ipfwadm -F -a m -S 192.168.1.0/24 -D 0.0.0.0/0
And that's all there is to it! Assuming that the network is working
properly, along with the internet connection, you should be all set!
Greg wrote:
>
> I am about to configure a server (486 dx4-100) to be my router. It
> will take in my cable modem and spread it to 3 other windows-based
> computers. This server is going to have Slackware V 3.4 (i think
> that's the right version) installed. I don't know what I'm up
> against, however. I know that I can set up IP masking to give
> everyone access to the cable modem, but don't know how. I will have a
> 100 MB HD and 8 megs of ram. What should I install and how do I use
> it when it is installed? I have 2 older ODI network cards that I will
> be using to link the win 95.98 based network to the modem. I would
> also like to set up a firewall, but again, I have no clue how to do
> it. Does anyone know what I need to do or if there is a web site that
> will take me step by step through it? This is my first time using
> Linux or configuring a network, so go easy on me. Any assistance will
> be greatly valued!
>
> Thanks
> Greg Wilson
> [EMAIL PROTECTED]
--
-John Wolanski
Remove the "_removethis" from my email address to reply.
------------------------------
From: "Sander Pilon" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.system
Subject: Re: Obtaining MAC address from remote computer
Date: Thu, 14 Jan 1999 17:25:47 +0100
I dont WANT the ethernet card MAC address.
I want a *COMPLETELY* transparant forwarder/NAT-device.
Meaning I want to send out packets with other machines MAC addresses.
Regards,
Sander
Dave Hearn wrote in message <77ks28$9ji$[EMAIL PROTECTED]>...
>Err - your ethernet card will insert the mac stuff for you
>
>
>Sander Pilon wrote in message <77kljl$aom$[EMAIL PROTECTED]>...
>
>>
>>Maybe I should've mentioned I want to do this in C on a per-packet basis.
>>
>>A packet arrived on eth0, I'm going to forward it to eth1 and I have to
>>insert a new MAC
>>address.
>>
>>Regards,
>>
>>Sander
>>
>>
>
>
------------------------------
** 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
******************************
