Linux-Networking Digest #838, Volume #10 Tue, 13 Apr 99 00:13:43 EDT
Contents:
ARP cache flush - INDUCED! ([EMAIL PROTECTED])
Forwarding VPN clients through firewall (Walter Hunt)
Re: ypcat problem (AG)
Re: Telnet and FTP woes ("James Mandy")
Dump from kernel after:ppp_dev_stats called ("Wilson Lam")
Re: Ipchains on a LAN...? (James Stevenson)
Re: Firewall+FTP Problems HELP!!! (James Stevenson)
Re: Linux NFS Server serving Solaris 2.6 (Alan Westhagen)
Re: network setup (Michael J Surette)
Re: Hacker 'SATANIC SERVER' on my LAN ("William Evans")
Re: Name resolution problems with PPP and Red Hat 5.2 (Dave Seyster)
Re: eth0 hangs ppp... modem/nic conflict? (Clifford Kite)
network setup ("cyberfiche")
Re: D-Link DFE 530TX driver/setup?! ("MarkT")
Re: Interesting Mail Server Setup (Michael J Surette)
Re: Telnet and FTP woes (hellraiser)
Re: automount/mount does not react (Mark Nielsen)
Re: SMB Client (Mark Nielsen)
Re: Machine name themes - what do you use? (Alan Anderson)
----------------------------------------------------------------------------
From: [EMAIL PROTECTED]
Subject: ARP cache flush - INDUCED!
Date: Wed, 07 Apr 1999 09:14:06 GMT
Hi,
Is there a standard mechanism to induce ARP cache flush for a router.
Can any external entity - say another machine induce such a flush of
the ARP cache? How? Say there is a Linux machine which wants to flush
the ARP cache of a CISCO router...
TIA
banibrata
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
Reply-To: [EMAIL PROTECTED]
From: [EMAIL PROTECTED] (Walter Hunt)
Subject: Forwarding VPN clients through firewall
Date: Tue, 13 Apr 1999 02:22:42 GMT
I have a Mac attached to my home network, which is firewalled
by a Linux machine running 2.2.5 and using ipchains and IP
masquerading.
This Mac needs to connect, via IntraPort, to a VPN at a company
I am doing consulting work for. IntraPort, as far as I can determine,
is based on the IPSec VPN method.
I've checked all the FAQs and HOWTOs I can find, and I can't
figure out what I need to do to make this connection work correctly.
The VPN HOWTO only has patches/info for Linux <= 2.0.36, although it
says work on a 2.2 patch is in progress.
Does anyone know of a way (short of waiting - I hate doing that)
to get the VPN client working through my firewall? Or any info on what
ports are used/necessary to make the whole thing work? I may be up to
hacking one of the existing protocol forwarding modules into one that
can forward the traffic if I can get specs on just *what* needs to be
able to go through.
Anyone have any ideas?
Thanks.
--
Walter Hunt
------------------------------
From: AG <[EMAIL PROTECTED]>
Subject: Re: ypcat problem
Date: Mon, 12 Apr 1999 22:14:48 -0400
You may want to make sure that you've *built* the passwd.byname map..
Do a "make" in /var/yp. This should build all of the necessary maps
provided that your Makefile is setup to build that particular map :)
The Makefile lives in /var/yp too....
[EMAIL PROTECTED] wrote:
>
> Hello,
>
> I'm usign slackware 3.6 and i have a problem with NIS:
>
> I can use NIS maps in my machine and i can do a
> ypmatch without a problem, but when i do a ypcat, i can't
> see the maps. I got this problem:
>
> No such map passwd.byname. Reason: YP server error
>
> Why i have this error?
>
> Thanks in advance
>
> Carlos Nava
>
> -----------== Posted via Deja News, The Discussion Network ==----------
> http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
--
Alfred
"Those who seek knowledge begin with humbleness.."
Unknown
___________________________________________________________
[EMAIL PROTECTED]
PERSONAL
http://www.eng.fsu.edu/~green
____________________________________________________________
------------------------------
From: "James Mandy" <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux,comp.os.linux.admin,comp.os.linux.help
Subject: Re: Telnet and FTP woes
Date: Tue, 13 Apr 1999 10:46:34 +0800
make sure there is nothing in /etc/hosts.allow
and nothing in /etc/hosts.deny
try a "killall -HUP inetd"
Cheers, James.
> Telnet gives me no message other than "connection closed". I never
> get a login.
> FTP gives me the message "Connection closed by remote host". I
> never get a login here either.
> Both clients are the simple programs that ship with Windows 95.
>
> I can ping my Linux box from Windows and vice-versa. I'm assuming I
> need to change some settings in my network, but I'll be damned
> if I know what they are. I have checked /etc/services and it shows
> both ftp and telnet as being set up. Do I need a telnet and ftp
> daemon running? Any information would be appreciated.
>
> Doug Haines
>
>
------------------------------
From: "Wilson Lam" <[EMAIL PROTECTED]>
Crossposted-To: comp.protocols.ppp
Subject: Dump from kernel after:ppp_dev_stats called
Date: 13 Apr 1999 00:58:48 GMT
Hi,
I installed ppp, mgetty in a Linux 2.0.36 (Redhat 5.2) and
configurated the modem. I can dial in the Linux box and start up
ppp connection. It seems everything working properly.
But I have found a lot of kernel dump(at lease 3 lines per minite)
from the syslog after line "ppp_dev_stats called".
Here is a sample:
Apr 10 01:46:19 fw PAM_pwdb[490]: (ppp) session closed for user
fw.yml.com.hk
Apr 10 01:46:19 fw pppd[490]: Connection terminated.
Apr 10 01:46:20 fw pppd[490]: Exit.
Apr 10 02:17:28 fw mgetty[555]: data dev=ttyS1, pid=555, caller='none',
conn='3'
Apr 10 02:17:28 fw pppd[555]: pppd 2.3.5 started by a_ppp, uid 0
Apr 10 02:17:28 fw kernel: ppp_tty_ioctl: set flags to 70000
Apr 10 02:17:28 fw kernel: ppp_tty_ioctl: set flags to 70000
Apr 10 02:17:28 fw pppd[555]: Using interface ppp0
Apr 10 02:17:28 fw kernel: ppp_tty_ioctl: set xasyncmap
Apr 10 02:17:28 fw kernel: ppp_tty_ioctl: set xmit asyncmap ffffffff
Apr 10 02:17:28 fw kernel: ppp_tty_ioctl: set flags to 70000
Apr 10 02:17:28 fw kernel: ppp_tty_ioctl: set mru to 5dc
Apr 10 02:17:28 fw kernel: ppp_tty_ioctl: set rcv asyncmap ffffffff
Apr 10 02:17:28 fw kernel: ppp_tty_ioctl: set flags to 70000
Apr 10 02:17:28 fw pppd[555]: Connect: ppp0 <--> /dev/ttyS1
Apr 10 02:17:32 fw kernel: ppp: successfully queued 25 bytes, flags =
f070000
Apr 10 02:17:32 fw kernel: ppp: successfully queued 26 bytes, flags =
f070000
Apr 10 02:17:32 fw kernel: ppp: successfully queued 22 bytes, flags =
f070000
Apr 10 02:17:32 fw kernel: ppp_tty_ioctl: set xmit asyncmap a0000
Apr 10 02:17:32 fw kernel: ppp_tty_ioctl: set flags to f070003
Apr 10 02:17:32 fw kernel: ppp_tty_ioctl: set mru to 5dc
Apr 10 02:17:32 fw kernel: ppp_tty_ioctl: set rcv asyncmap 0
Apr 10 02:17:32 fw kernel: ppp_tty_ioctl: set flags to f070003
Apr 10 02:17:32 fw kernel: ppp: successfully queued 23 bytes, flags =
f070003
Apr 10 02:17:32 fw PAM_pwdb[555]: (ppp) session opened for user william by
(uid)
Apr 10 02:17:32 fw pppd[555]: user william logged in
Apr 10 02:17:33 fw kernel: ppp_tty_ioctl: set flags to f070043
Apr 10 02:17:33 fw kernel: ppp: successfully queued 42 bytes, flags =
f070043
Apr 10 02:17:33 fw kernel: ppp: successfully queued 17 bytes, flags =
f070043
Apr 10 02:17:33 fw kernel: ppp: successfully queued 18 bytes, flags =
f070043
Apr 10 02:17:34 fw kernel: ppp: successfully queued 18 bytes, flags =
f070043
Apr 10 02:17:34 fw kernel: ppp: successfully queued 6 bytes, flags =
f070043
Apr 10 02:17:34 fw kernel: ppp: successfully queued 6 bytes, flags =
f070043
Apr 10 02:17:34 fw kernel: ppp_tty_ioctl: set flags to f0700c3
Apr 10 02:17:34 fw kernel: ppp: successfully queued 18 bytes, flags =
f0700c3
Apr 10 02:17:34 fw kernel: ppp_tty_ioctl: set maxcid to 16
Apr 10 02:17:34 fw kernel: ppp_tty_ioctl: set flags to f0700c7
Apr 10 02:17:34 fw kernel: ppp: channel ppp0 going up for IP packets!
Apr 10 02:17:34 fw pppd[555]: local IP address 164.120.230.10
Apr 10 02:17:34 fw pppd[555]: remote IP address 164.120.230.12
Apr 10 02:17:34 fw kernel: ppp: successfully queued 6 bytes, flags =
f070047
Apr 10 02:17:34 fw pppd[555]: CCP terminated by peer
Apr 10 02:17:34 fw kernel: ppp_tty_ioctl: set flags to f070047
Apr 10 02:17:34 fw pppd[555]: Compression disabled by peer.
Apr 10 02:17:35 fw kernel: ppp_dev_stats called<6>ppp_dev_stats
called<6>ppp_de4
Apr 10 02:19:40 fw kernel: 0C A4 78 E6 17 .x...x..
Apr 10 02:19:41 fw kernel: A4 78 E6 37 .x...x.7
Apr 10 02:19:44 fw kernel: 0C A4 78 E6 61 .x...x.a
Apr 10 02:19:48 fw pppd[555]: Protocol-Reject for unsupported protocol 0xd
Apr 10 02:19:48 fw pppd[555]: Protocol-Reject for unsupported protocol 0x0
Apr 10 02:19:48 fw kernel: ppp: successfully queued 67 bytes, flags =
f070047
Apr 10 02:19:48 fw kernel: ppp: successfully queued 9 bytes, flags =
f070047
Apr 10 02:19:48 fw pppd[555]: Protocol-Reject for unsupported protocol
0x6677
Apr 10 02:19:48 fw pppd[555]: Protocol-Reject for unsupported protocol
0x2077
Apr 10 02:19:48 fw pppd[555]: Protocol-Reject for unsupported protocol 0x6b
Apr 10 02:19:48 fw pppd[555]: Protocol-Reject for unsupported protocol 0xd
Apr 10 02:19:48 fw kernel: ppp: successfully queued 9 bytes, flags =
f070047
Apr 10 02:19:48 fw kernel: ppp: successfully queued 9 bytes, flags =
f070047
Apr 10 02:19:48 fw kernel: ppp: successfully queued 36 bytes, flags =
f070047
Apr 10 02:19:48 fw kernel: ppp: successfully queued 10 bytes, flags =
f070047
Apr 10 02:20:22 fw pppd[555]: Hangup (SIGHUP)
Apr 10 02:20:22 fw pppd[555]: Modem hangup
Apr 10 02:20:22 fw PAM_pwdb[555]: (ppp) session closed for user
fw.yml.com.hk
Apr 10 02:20:22 fw kernel: ppp: channel ppp0 closing.
Apr 10 02:20:22 fw kernel: ppp: channel ppp0 going down for IP packets!
Apr 10 02:20:23 fw pppd[555]: Exit.
Also found syslog echoed:
Message from syslogd@fw at Tue Apr 13 00:08:27 1999 ...
fw kernel: 7C DA E3 94 49 3E ..|...I>
Anybody know why?
Any help is appreciated!
Wilson
------------------------------
From: [EMAIL PROTECTED] (James Stevenson)
Subject: Re: Ipchains on a LAN...?
Date: Mon, 12 Apr 1999 19:47:44 +0000
Reply-To: [EMAIL PROTECTED]
Hi
are you masqurading ICMP?
it is required by ping
On 12 Apr 1999 17:33:23 GMT, Peter Woytiuk <[EMAIL PROTECTED]> wrote:
>: There should be a HOWTO for IP-Masqurading in the (for RH5.x)
>: /usr/doc/HOWTO/mini/ dir.
>: Good luck.
>: Thomas
>
> Yeah, I read that, but still no luck. I can't ping external
>computers, I can only ping stuff on the LAN. I've checked the settings
>in triplicate so it's not something I've mis-typed. Two questions:
>
>1) In the /lib/modules/2.2.4/ipv4 directory there's a 'ip_masq_user'
> module, should that be loaded? The HOWTO doesn't mention it.
>
>2) The host computer dual-boots Linux & Win98, with a proxy server
> running under Win98. The non-host computer is happy when the
> proxy server runs: it's set up to use 192.168.0.1:80. Should
> I have the masquerading/ipchains listening to a specific port?
> Or should I be tryin something as described in the Proxy ARP
> HOWTO? Or am I on glue and looking entirely in the wrong
> direction? <Some people may claim I'm on glue for using Win98 in
> the first place, which is probably true>
>
> I probably should've mentioned all this in the first place. If
>this makes things any clearer, let me know. Thanks in advance,
>
> Peter
>--
> [- Make it idiot-proof, and someone will make a better idiot -]
>
> ** Junk mail sent to this address will be subject to **
> ** a $100.00 proof-reading fee. Sending of such **
> ** material constitutes acceptance of these terms **
--
Check Out: http://www.users.zetnet.co.uk/james/
E-Mail: [EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (James Stevenson)
Subject: Re: Firewall+FTP Problems HELP!!!
Date: Mon, 12 Apr 1999 19:46:32 +0000
Reply-To: [EMAIL PROTECTED]
Hi
if you watch a ftp program in verbose mode you will see that it open more
ports
it uses a control line and then a another line when it needs it to
transfere data most are for incoming and will be blocked by your firewall
it would be more clear if you read the rfc on it
On Mon, 12 Apr 1999 17:51:42 +0200, postmaster <[EMAIL PROTECTED]> wrote:
>I have setup a firewall using RedHat 5.2 kernel 2.0.36 and easyfw
>version 1.1
>
>Outside 192.0.0.0/24 Inside 2.0.0.0/24
>
>My config is :
>
>Input rules : Default Policy DENY ALL
>Accept -P tcp -S 2.0.0.0/24 -D 0.0.0.0/0
>Accept -P tcp -S 192.0.0.0/24 -D 0.0.0.0/0 21 20 23 513 514 543 544 2105
>1521 187
>
>Output rule : Default Policy ACCEPT ALL
>
>Forwarding rules : Default Policy ACCEPT ALL
>masquerade -P tcp -S 192.0.0.0/24 -D 0.0.0.0/0
>
>
>My problem is that I can ftp to my servers. However, users cannot get
>nor put any file nor use the "ls" command.
>
>Any Hints ???
>
--
Check Out: http://www.users.zetnet.co.uk/james/
E-Mail: [EMAIL PROTECTED]
------------------------------
From: Alan Westhagen <[EMAIL PROTECTED]>
Subject: Re: Linux NFS Server serving Solaris 2.6
Date: Mon, 12 Apr 1999 17:54:47 -0700
[EMAIL PROTECTED] wrote:
>
> I need some help. I am trying to set up NFS to be mounted by a system running
> Solaris 2.6. I am running NFS2.2beta37 on RedHat 5.2, kernel 2.035, I think.
> So, in my initial testing I was able to mount from the nfs share from another
> Linux box. So, I was under the impression that I was in the clear. However,
> when I had the Solaris client attempt the mount I get the following in my
> /var/log/messages:
>
> NFS mount of /sys/oxf/upload attempted by (ipaddr)
> /sys/oxf/upload has been mounted by (ipaddr)
> Unauthorized access by NFS client (ipaddr)
>
> My /etc/hosts file has all NFS clients defined. My /etc/hosts.allow file has
> the NFS clients indicated as follows: ALL: (ipaddr). And my /etc/exports
> file has the following /sys/oxf/upload ipaddrofnfsclient(rw)
>
> These were the steps I took to get the Linux box up and running on NFS. I
> was told also that Solaris uses NFS version 3 and that may be the
> authentication problem. Any ideas? And if what I heard was correct there
> should be a command line switch to the Solaris 2.6 mount that will allow a
> NFS version 2 mount. What is the switch.
>
> Thanks much.
>
> Patrick Avery
> Network Manager
> Digital Imaging
>
> -----------== Posted via Deja News, The Discussion Network ==----------
> http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
A couple of weeks ago I got my Solaris 7 system to mount directory nodes
located on my Redhat 5.1 system. I'll just tell you what I did. If you
find something different, than what you did, you might give it a try.
My Solaris system is called sola.
My linux system is called thor.
This is my /etc/exports file on thor:
/home/alan loki(rw)
/home sola(rw)
/usr1/pub sola(rw)
/usr1/home/alan/.delta sola(ro)
After making changes, I run /usr/sbin/exportfs.
This is my /etc/vfstab file on sola:
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
#
#/dev/dsk/c1d0s2 /dev/rdsk/c1d0s2 /usr ufs 1 yes -
/proc - /proc proc - no -
fd - /dev/fd fd - no -
swap - /tmp tmpfs - yes -
/dev/dsk/c0t0d0s0 /dev/rdsk/c0t0d0s0 / ufs 1 no -
/dev/dsk/c0t0d0s1 - - swap - no -
/dev/dsk/c0t0d0s3 /dev/rdsk/c0t0d0s3 /space ufs 1 yes -
thor:/home - /home nfs - yes rw,hard,intr,rsize=1024,wsize=1024
thor:/usr1/pub - /pub nfs - yes rw,hard,intr,rsize=1024,wsize=1024
thor:/usr1/home/alan/.delta - /usr1/home/alan/.delta nfs - yes
ro,hard,intr,rsize=1024,wsize=1024
Note: I had trouble until I added the 'hard' attribute and set
rsize and wsize down to 1024 (which is small, but seems to be fast
enough for me).
Good luck.
Alan Westhagen <[EMAIL PROTECTED]>
------------------------------
From: Michael J Surette <[EMAIL PROTECTED]>
Subject: Re: network setup
Date: Mon, 12 Apr 1999 21:38:37 -0400
cyberfiche wrote:
> Hi there. I'm on a the network at NC State University. Win98 works fine
> with all the network and internet stuff. My Red Hat Linux 5.1, however,
> wont see the network. On boot up Linux stalls for a few minutes trying to
> connect. Then it just gives up and goes on. I've tried all sorts of stuff
> in the network configuration. What should I do?
Sounds like the voice of frustration.
When you type 'ifconfig' is there an eth0 device shown?
------------------------------
From: "William Evans" <[EMAIL PROTECTED]>
Subject: Re: Hacker 'SATANIC SERVER' on my LAN
Date: 12 Apr 1999 21:38:19 -0400
>>>>> "star" == star <[EMAIL PROTECTED]> writes:
star> # flush all other commands
star> ipchains forward -F
star> ipchains input -F
star> ipchains output -F
I think you have the command-line messed up. These should be:
ipchains -F input
ipchains -F forward
ipchains -F output
star> # default policy: deny all
star> ipchains forward -P deny
star> ipchains output -P deny
star> ipchains input -P deny
ipchains -P input deny
ipchains -P forward deny
ipchains -P output deny
star> # first deny spoofers from outside and log them
star> ipchains input -l -i eth0 -S 192.168.0.3/32 -j deny
star> ipchains input -l -i eth0 -S 192.168.0.0/24 -j deny
star> ipchains input -l -i eth0 -S 127.0.0.1/32 -j deny
# This first rule is really redundant, though, looking at the second
# rule. 192.168.0.3 is included in 192.168.0.0/24.
# ipchains -A input -l -i eth0 -S 192.168.0.3/32 -j deny
ipchains -A input -l -i eth0 -S 192.168.0.0/24 -j deny
ipchains -A input -l -i eth0 -S 127.0.0.1/32 -j deny
star> # deny all other special networks
star> ipchains input -l -i eth0 -S 192.168.0.0/16 -j deny
star> ipchains input -l -i eth0 -S 172.16.0.0/12 -j deny
star> ipchains input -l -i eth0 -S 10.0.0.0/8 -j deny
ipchains input -l -i eth0 -S 192.168.0.0/16 -j deny
ipchains input -l -i eth0 -S 172.16.0.0/12 -j deny
ipchains input -l -i eth0 -S 10.0.0.0/8 -j deny
Net truly necessary, but not a bad thing, necessarily. Granted, any
router that's configured correctly "out there" on the internet should
not be routing these subnets, but by blocking them yourself, I guess
that isn't *wrong*, per se.
However, by adding truly unnecessary rules to the chain of rules, you
are increasing the load on the server for routing purposes. If you
want to streamline it (and simplify it), these don't need to be here
(IMHO).
star> # forward
star> ipchains -A forward -j MASQ -s 192.168.0.1/32 -d 0.0.0.0/0
star> ipchains -A forward -j MASQ -s 192.168.0.2/32 -d 0.0.0.0/0
These are actually correct. If you are trying to make it ultra secure
(as in no other IP addresses can get out from the private lan), then
you're correct in your command lines. If you have other private
addresses that you do not want to have access (like 192.168.0.3), then
this is one correct way of doing it. However, you could simplify it
with something like:
ipchains -A forward -j MASQ -s 192.168.0.0/24 -d 0/0
assuming you have a 24-bit netmask (255.255.255.0). I don't think
that it's a security hole to do it this way. This also reduces the
number of rules that the routing code must parse through to check each
packet.
To cover the rest of the rules, I'd need to know the basic setup of
the entire networking. That is, two ethernet cards or one card and a
dialup link?
HTH
-bill
--
William Evans < william . evans @ computer . org >
------------------------------
From: [EMAIL PROTECTED] (Dave Seyster)
Subject: Re: Name resolution problems with PPP and Red Hat 5.2
Date: Tue, 13 Apr 1999 01:57:01 GMT
On Sun, 11 Apr 1999 20:59:22 -0400, Rich and Inna Nill <[EMAIL PROTECTED]> wrote:
>Hi,
>
>I have recently installed Red Hat 5.2 and I'm having problems getting
>PPP to work correctly. Before installing Red Hat, I was using an older
>Slackware Distribution and I had PPP working just fine.
>My /etc/hosts file:
>
>127.0.0.1 localhost
>0.0.0.0 spryaccount
^^^^^^^^^^^^^^^^^^^^^
I would remove this line from your /etc/hosts file.
>My /etc/ppp/options file:
>
>#-----/etc/ppp/options----
>#
>defaultroute
>debug
>/dev/modem
>57600
>netmask 255.255.255.0
>mtu 1500
>connect "/usr/sbin/chat -v ABORT BUSY ABORT 'NO CARRIER' ''
>'AT&F&H1&R2&B1S0=1&K1&M4' OK ATDT4716417 CONNECT '' ame spry07 UI
>spry773391 word myPassword"
I would add "noipdefault" to your /etc/ppp/options file. Do you really need
that initialization string? Check to see that your modem's default
configuration isn't just being duplicated here. That initialization string
probably doesn't hurt anything but I bet it's redundant.
Dave Seyster
------------------------------
From: kite@NoSpam.%inetport.com (Clifford Kite)
Subject: Re: eth0 hangs ppp... modem/nic conflict?
Date: 12 Apr 1999 20:07:25 -0500
Chris Leger ([EMAIL PROTECTED]) wrote:
: I seem to have a conflict between my modem and nic. Modem is USR 56K
: internal, nic is 3com 3c509. Here are some particulars:
..
: Here's some pertinent (I hope) info:
..
: [cleger@columbia /home/cleger]> more /etc/sysconfig/network
: NETWORKING=yes
: FORWARD_IPV4=yes
: HOSTNAME=columbia
: DOMAINNAME=
: GATEWAY=192.168.1.254
: GATEWAYDEV=eth0
If this does what I think then it's your problem. Pppd won't replace an
existing route with a defaultroute through the ppp0 interface even with
the pppd defaultroute option. Execute route. If route shows a default
gateway to eth0 configured through 192.168.1.254 then this *is* what
is happening.
In case this does turn out to be the problem the correct thing to do is
to remove this gateway route. You only need to have a network specific
route for a LAN with one subnet.
--
Clifford Kite <kite@inet%port.com> Not a guru. (tm)
/* The wealth of a nation is created by the productive labor of its
* citizens. */
------------------------------
From: "cyberfiche" <[EMAIL PROTECTED]>
Subject: network setup
Date: Mon, 12 Apr 1999 20:53:46 -0400
Hi there. I'm on a the network at NC State University. Win98 works fine
with all the network and internet stuff. My Red Hat Linux 5.1, however,
wont see the network. On boot up Linux stalls for a few minutes trying to
connect. Then it just gives up and goes on. I've tried all sorts of stuff
in the network configuration. What should I do?
------------------------------
From: "MarkT" <[EMAIL PROTECTED]>
Subject: Re: D-Link DFE 530TX driver/setup?!
Date: Tue, 13 Apr 1999 10:46:58 +1000
Which kernel are you using?
Via-rhine moduleor compiled in?
I had some trouble getting via-rhine to operate happly compiled into the
kernel until I hit 2.2.3.
Now I have two 530's very happy.
Lee Baxter wrote in message <[EMAIL PROTECTED]>...
>I've been trying to set up a D-Link DFE 530TX 10/100 NIC.
>It's a PCI card, and is jumperless. There also isn't a software
>package to set the IRQ and IO. PnP PCI.
>
>Any suggestions?
>Thanks,
> Lee
>
>[EMAIL PROTECTED]
------------------------------
From: Michael J Surette <[EMAIL PROTECTED]>
Subject: Re: Interesting Mail Server Setup
Date: Mon, 12 Apr 1999 23:01:57 -0400
Smith wrote:
> Hi there,
>
> I am trying to setup 2 linux servers at different locations to perform the
> below mentioned function. Windows 98 will be use as clients to connect to
> the linux server at each end and Outlook express (configured as IMAP and
> SMTP or POP and SMTP) will be run on the Windows 98 boxes.
>
> SETUP :-
>
> Windows 98 A =====Linux Server A -------PPP Link---------Linux Server
> B=======Windows 98 B
>
> |-------------Location A----------------------| Dial thru telephone
> |---------------Location B ---------------------|
>
> I would like Users at Windows 98 A to send mails out to Users at
> Windows 98 B and vice versa. Both Linux server must be able to accept mails
> from the other users (meaning Server A must receive mails from Users B) and
> store them onto the appropriate user mailbox or to pre-defined user at
> either end so that they can receive it.
>
> I know I need to setup both the Linux Server as PPP server and Dial On
> Demand server. What else is required and where can I find these information
> ??
> Do I need to run a DNS ??
> Other than Sendmail, what else can I use?
>
> I'm running Redhat 5.1, is there anything else I must take care of ??
>
> Thanks to everyone who answered in advance.
This is a big project.
Try mgetty with auto-ppp for your PPP server and diald for your Dial On Demand
server (or you could use pppd 2.3.7 in demand-dial mode).
DNS, you can't set up MX records without it, but if you're just going to
exchange mail between these two networks and nowhere else, you can avoid those.
A good place to start studying is the NAG (Network Administrator's Guide) which
is available in hardcopy from O'Reilly or in electronic format from the LDP at
sunsite.unc.edu/Linux. You might want to check out the relevant HOWTOs while
you're there.
------------------------------
From: hellraiser <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux,comp.os.linux.admin,comp.os.linux.help
Subject: Re: Telnet and FTP woes
Date: Mon, 12 Apr 1999 22:37:02 -0400
"Douglas A. Haines" wrote:
>
> Hi folks,
> I'm running RedHat Linux 5.1 (2.0.34 kernel). I finally have TCP
> networking operating after some kernel compile problems, yet I still
> have
> some issues. The one I'm working on now involves Telnet and FTP. I
> cannot connect my Windows machine to my Linux box with either;
> both clients on the Windows side indicate a closed connection.
>
> Telnet gives me no message other than "connection closed". I never
> get a login.
> FTP gives me the message "Connection closed by remote host". I
> never get a login here either.
> Both clients are the simple programs that ship with Windows 95.
>
> I can ping my Linux box from Windows and vice-versa. I'm assuming I
> need to change some settings in my network, but I'll be damned
> if I know what they are. I have checked /etc/services and it shows
> both ftp and telnet as being set up. Do I need a telnet and ftp
> daemon running? Any information would be appreciated.
you probly forgot to run the daemons
>
> Doug Haines
------------------------------
From: [EMAIL PROTECTED] (Mark Nielsen)
Crossposted-To: comp.os.linux.setup,de.comp.os.unix.linux.misc
Subject: Re: automount/mount does not react
Date: 12 Apr 1999 20:53:35 -0400
i didn't read your whole e-mail, and I apologize if I say something
stupid. Are you using autofs? If so, you can have it specify more than one
server in case a server goes down.
Mark
--
Mark Nielsen "Where 98 has no meaning."
www.tcu-inc.com [EMAIL PROTECTED]
The Computer Underground, Inc. 614-485-0506
computers, programming, networking, Perl, PHP, SQL, HTMl, Linux, Unix
------------------------------
From: [EMAIL PROTECTED] (Mark Nielsen)
Subject: Re: SMB Client
Date: 12 Apr 1999 20:50:47 -0400
Huh? Do you mean that you want to put a program in the kernel which will
automatically mount smb drives from other computers?
Well, if it works in autofs, that might solve your problem.
It might not be in the kernel, but if automounting is what you are
looking for, that might do it.
Mark
In article <[EMAIL PROTECTED]>,
Jon <[EMAIL PROTECTED]> wrote:
>Does anyone know of any plans to plug the smb client in at the file
>system level, with mount type options ?? Or am I just a victum of the
>MicoShaft in an insular NT world :-)
>
>[EMAIL PROTECTED]
>
>
>
--
Mark Nielsen "Where 98 has no meaning."
www.tcu-inc.com [EMAIL PROTECTED]
The Computer Underground, Inc. 614-485-0506
computers, programming, networking, Perl, PHP, SQL, HTMl, Linux, Unix
------------------------------
From: [EMAIL PROTECTED] (Alan Anderson)
Crossposted-To:
vmsnet.networks.misc,microsoft.public.windowsnt.domain,comp.unix.solaris,comp.os.os2.networking.server,comp.os.ms-windows.nt.admin.networking,comp.infosystems.www.servers.unix,comp.protocols.tcp-ip.domains
Subject: Re: Machine name themes - what do you use?
Date: 12 Apr 1999 16:25:15 GMT
Reply-To: [EMAIL PROTECTED] (Alan Anderson)
In <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (J.D. Baldwin) writes:
>In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
><[EMAIL PROTECTED]> wrote:
>> i name mine after american dictators
>>
>> eg reagan, johnson, kissenger, nixon etc
>
>What, no 'haig'?
AAAEIIIIIGGGHHHH!!!!!
I never understood until now the proposed name of the backup Novell
server for a local business. I always thought that the sysadmin was
planning to call it "The Hague".
Now I understand. If the main server goes down, haig is supposed to
come online and tell everyone "I'm in charge."
= === === === = = = === === === === = = === = = = === = = === =
# Alan Anderson # Ignorance can be fixed, but stupidity is permanent. #
# My employer and I do not speak for one another. # qo'mey poSmoH Hol #
= = = = = = = === = = = === = = = = === = = = = = = = ===
------------------------------
** 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
******************************
