Linux-Networking Digest #322, Volume #10 Sat, 27 Feb 99 16:13:52 EST
Contents:
Re: NIC for Linux ("Evangelos K. Koutsavdis")
Re: Appletalk, anyone? (brucekey)
tftp pointers (HAITHAM ESSAM ISMAIL ABDEL-AL)
Re: IP to process network interface? (Kip Rugger)
NIS - no shadow password (Matthias)
Re: ISDN T/A - going to be the death of me ("fertile")
Re: IIOP CORBA (mico?) and IP Maskerading on a Linux cluster ("Alain Coetmeur")
IP tunneling with iproute2 and kernel 2.2.1 ([EMAIL PROTECTED])
Re: compuserve dial-in script? (Ralph W. Crane)
Accounting the time for using the proxy server ("Margus")
ifwadm (tommy)
Remote CVS Access Broke With RedHat 5.2 Linux Upgrade (David Heddle)
IP Forwarding?? (Darren Ehmke)
Named dies. (Carter Koch)
Netgear 310tx ("Rob")
----------------------------------------------------------------------------
From: "Evangelos K. Koutsavdis" <[EMAIL PROTECTED]>
Subject: Re: NIC for Linux
Date: Fri, 26 Feb 1999 13:23:52 -0500
==============C600B665DF9B50700518AF92
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
David Lamich wrote:
Thank you Dave, very useful information.
Vangelis.
==============C600B665DF9B50700518AF92
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
David Lamich wrote:
<pre>Thank you Dave, very useful information.</pre>
<pre></pre>
<pre>Vangelis.</pre>
</html>
==============C600B665DF9B50700518AF92==
------------------------------
From: brucekey <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc,comp.os.linux.setup
Subject: Re: Appletalk, anyone?
Date: Thu, 25 Feb 1999 15:38:40 -0800
I'm curious, what kind of NIC are you using in your PC to talk on the
Appletalk? A tops card? I've got a pant load of them laying around, it
would come in handy to hook up my Fujitsu Laserprinter....
Mohd H Misnan wrote:
>
> Aaron Dershem <[EMAIL PROTECTED]> wrote:
> >Does anyone have any experience with AppleTalk on Linux? I bought an iMac
> >for my girlfriend and would like to connect her to the network. I'm using
> >RH 5.2 configured as a server (installation choice).
>
> I've netatalk working flawlessly on my Linux. What you need is a package
> called netatalk-1.4b2+asun2.1.2-2.i386.rpm from contrib directory in
> ftp.redhat.com and btw, grab the atalk-sysv.tar.gz from the net too. It
> took me less than 5 minutes to get my iMac sees my Linux notebook and
> start transfering files etc. Naw, I dunnot need MS to do file sharing
> with iMac ;) And uhh, surely you need to compile in the AppleTalk DPP
> support in your kernel, may be as a module.
>
> --
> |Mohd H Misnan | [EMAIL PROTECTED] + [EMAIL PROTECTED] |i
> | | [EMAIL PROTECTED] + [EMAIL PROTECTED]|M
> |http://www.geocities.com/SiliconValley/3319/ : Disclaimer? |a
> |Linux 2.2.1/AMD K6-2/300Mhz notebook + Original iMac G3/233 RevB |c
------------------------------
Date: Thu, 25 Feb 1999 18:58:30 +0200
From: HAITHAM ESSAM ISMAIL ABDEL-AL <[EMAIL PROTECTED]>
Subject: tftp pointers
i need to run a tftp server... the inetd.conf seems to be in place
however it is not working... would anybody know any pointers to places
where i can find tftp info that is extra than the standard man and gnu
documentation???
what r the permissions and the ownership info for the directory that i
should tftp from... also how would the client know that....
thanks...
yehia..
PS please reply to [EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (Kip Rugger)
Crossposted-To: comp.os.linux.development.system
Subject: Re: IP to process network interface?
Date: 25 Feb 1999 10:58:15 -0600
>Is there a way to get an IP network interface into the kernel so
>that the kernel can operate on it as any network interface, but
>have the interface really connect via a process on that machine?
>
>Any IP packets sent to that interface would be given to the process,
>and any packets that process produces through the appropriate API to
>this facility, would "arrive" into the IP stack in the kernel.
Sounds like the ethertap device is what you want:
CONFIG_ETHERTAP
If you say Y here (and have said Y to "Kernel/User network link
driver", above) and create a character special file /dev/tap0 with
major number 36 and minor number 16 using mknod ("man mknod"), you
will be able to have a user space program read and write raw
Ethernet frames from/to that special file. tap0 can be configured
with ifconfig and route like any other Ethernet device but it is not
connected to any physical LAN; everything written by the user to
/dev/tap0 is treated by the kernel as if it had come in from a LAN
to the device tap0; everything the kernel wants to send out over the
device tap0 can instead be read by the user from /dev/tap0: the user
mode program replaces the LAN that would be attached to an ordinary
Ethernet device. Please read the file
Documentation/networking/ethertap.txt for more information.
------------------------------
From: Matthias <[EMAIL PROTECTED]>
Subject: NIS - no shadow password
Date: Thu, 25 Feb 1999 18:02:19 +0100
Hi!
My linux box wants to be NIS-Client. ypdomainname is set correct.
/var/yp and /etc/yp.conf exists.
'ypcat passwd' gives me my yp-passwd file. When i do login, syslog tells
me:
no shadow password for `user' on `ttype'
after giving my password:
invalid password for `user' on `ttype'
Anybody knows??
Thank you!!
Matthias
------------------------------
From: "fertile" <[EMAIL PROTECTED]>
Subject: Re: ISDN T/A - going to be the death of me
Date: Thu, 25 Feb 1999 17:02:33 -0000
The kisdn looks like it may help a lot, thanks for the tip :)
One seemingly simple problem ? i am having installing it though
let me paste from irc where i was ignored..
�fertile� i just installed QT libs .. the qt-1.42 and the qt-devel-1.42 ,
they went in n/p but everytime i try and rpm a particualr package at the
moment, i get a failed dependency .. qtlib >= 1.40 is required by blah
blah.rpm .. anyone know whats going on here ? :)
the blah blah.rpm abopve was the kisdn that requires the new QT .. but i did
succesfully have both the devel and the normal libs in as part of kde ..and
an rpm -q -a reports them both ..
but still when i go for the rpm -Uvh kisdn...etc it gives me the failed
dependency
thanks anyway for the advice
kev
Erik Hensema <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> fertile wrote:
> [...] an essay
You need a completely different pppd, ipppd, and should configure the card
> using isdnctrl.
> Maybe you could use kisdn (kisdn.headlight.de) for configuring the card,
> I've never tried it.
>
> Also, visit this page: www.wurtel.demon.nl (however, I could be in dutch,
> I'm not sure).
>
> --
> Erik Hensema ([EMAIL PROTECTED])
------------------------------
From: "Alain Coetmeur" <[EMAIL PROTECTED]>
Crossposted-To: comp.object.corba
Subject: Re: IIOP CORBA (mico?) and IP Maskerading on a Linux cluster
Date: Thu, 25 Feb 1999 17:51:17 +0100
Derek Viljoen a �crit dans le message <[EMAIL PROTECTED]>...
>I've got exactly the same setup at home. My FreeBSD box is multihomed (on the local
>10.0.0.* net, and a PPP connection through the modem). I was told by a co-worker
>(who knows) that I can get the source code to a SOCKS-based proxy server that will
>perform the IP proxying for me. The idea is that you dynamically "instrument" the
>application you want to run on the client (I guess it's some kind of tunneling) and
>the SOCKS server with know how to route the packages back to you.
I've found good papers
at
http://www.technosec.com/
especially
http://www.technosec.com/whitepapers/corba/corbafw/cfw.html#Products
but also one about a socksified orbacus, and another about
a gatewayed mico throug TIS gateway...
the gateway solution seems to be very static,
and quite equivalent to a linux IP masquerade.
the socks could be OK but I'm not using IP masquerade.
they talk about a "proxyfying" IOR that have to be implemented
by the ORB ? they seems to think about it at the OMG...
------------------------------
From: [EMAIL PROTECTED]
Subject: IP tunneling with iproute2 and kernel 2.2.1
Date: Fri, 26 Feb 1999 18:09:34 GMT
Reply-To: [EMAIL PROTECTED]
I'm having difficulty setting up an IP tunnel. Any assistance would
be greatly appriciated.
I'm trying to appear as though I sit in a public network even though
I am actually in a private one.
local agent in public network: 207.223.13.69/255.255.255.224
remote agent in private network(me): 172.17.42.50/255.255.255.0
I would like to appear as though I am 207.223.13.75
| ^
| src: any | src: 207.223.13.75
| dst: 207.223.13.75 | dst: any
| |
V |
------------------------------------------------------------------
| encapsulate decapsulate |
| -------------------------- --------------------------- |
| | src: any | | src: 172.17.42.50 | |
| | dst: 172.17.42.50 | | dst: 207.223.13.69 | |
| | ---------------------- | | ---------------------- | |
| | | src: any | | | | src: 207.223.13.75 | | |
| | | dst: 207.223.13.75 | | | | dst: any | | |
| | ---------------------- | | ---------------------- | |
| -------------------------- --------------------------- |
------------------------------------------------------------------
| ^ host: 207.223.13.69
| | ARP for: 207.223.13.75
| |
| |
| src: any | src: 172.17.42.50
| dst: 172.17.42.50 | dst: 207.223.13.69
| |
| |
V |
------------------------------------------------------------------
| decapsulate encapsulate |
| -------------------------- --------------------------- |
| | src: any | | src: 172.17.42.50 | |
| | dst: 172.17.42.50 | | dst: 207.223.13.69 | |
| | ---------------------- | | ---------------------- | |
| | | src: any | | | | src: 207.223.13.75 | | |
| | | dst: 207.223.13.75 | | | | dst: any | | |
| | ---------------------- | | ---------------------- | |
| -------------------------- --------------------------- |
------------------------------------------------------------------
host: 172.17.42.50
wants to be: 207.223.13.75
This models an IP tunnel in both directions. This is a neccesity
due to the fact that the network router admin in charge of the
router between these networks is savy enough to realize that all
traffic leaving the private network should have a source address
inside the private network! Spoof-proof! ;-|
One can only hope that the router is not denying packets of
protocol type IPIP.
Notice that on the remote host the interface needs to communicate
as though it were 172.17.42.50 but the application layer needs to
communicate as though it were 207.223.13.75
I have compiled and installed the 2.2.1 Linux kernel on both
machines. I have also installed the iproute2 package. I believe
the exact version is iproute2-990107-23.
The network features of the kernel on both boxes look like this:
#
# Networking options
#
CONFIG_PACKET=y
CONFIG_NETLINK=y
CONFIG_RTNETLINK=y
CONFIG_NETLINK_DEV=y
CONFIG_FIREWALL=y
CONFIG_NET_ALIAS=y
CONFIG_FILTER=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
CONFIG_RTNETLINK=y
CONFIG_NETLINK=y
CONFIG_IP_MULTIPLE_TABLES=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_TOS=y
CONFIG_IP_ROUTE_VERBOSE=y
# CONFIG_IP_ROUTE_LARGE_TABLES is not set
CONFIG_IP_ROUTE_NAT=y
# CONFIG_IP_PNP is not set
CONFIG_IP_FIREWALL=y
CONFIG_IP_FIREWALL_NETLINK=y
CONFIG_NETLINK_DEV=y
CONFIG_IP_ALWAYS_DEFRAG=y
CONFIG_IP_TRANSPARENT_PROXY=y
CONFIG_IP_MASQUERADE=y
CONFIG_IP_MASQUERADE_ICMP=y
# CONFIG_IP_ROUTER is not set
CONFIG_NET_IPIP=y
CONFIG_NET_IPGRE=y
# CONFIG_NET_IPGRE_BROADCAST is not set
# CONFIG_IP_MROUTE is not set
CONFIG_IP_ALIAS=y
CONFIG_SYN_COOKIES=y
CONFIG_INET_RARP=y
CONFIG_IP_NOSR=y
CONFIG_SKB_LARGE=y
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
Yes, this is a tad excesive, but I was desperate.
The /etc/rc.d/rc.local script also contains:
echo "1" > /proc/sys/net/ipv4/ip_forward
*********************************************************
Here is the setup for the local agent (207.223.13.69):
*********************************************************
Before any attempt is made to configure tunneling, the
machine, with RedHat 5.1 startup scripts intact, reveals:
# ip link show
1: lo: <LOOPBACK,UP> mtu 3924 qdisc noqueue
link/LOOPBACK 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
link/ETHER 00:60:08:1e:ad:cf brd ff:ff:ff:ff:ff:ff
inet 207.223.13.69/27 brd 207.223.13.95 scope global eth0
3: tunl0@NONE: <NOARP> mtu 1480 qdisc noop
link/TUNNEL 00:00:00:00 brd 00:00:00:00
# ip route list
207.223.13.64/27 dev eth0 scope link
207.223.13.64/27 dev eth0 proto kernel scope link src 207.223.13.69
127.0.0.0/8 dev lo scope link
default via 207.223.13.65 dev eth0
FYI: The way the netmask is designated in the new iproute2
package is a little different. It is given as the 'masklen'
where the number of addresses in a group is 2^(32-masklen)
Example: 27 2^(32-27) = 2^5 = 32 This means each subnet has
32 addresses and the netmask is 255.255.255.224
Others: 24 => 255.255.255.0
25 => 255.255.255.128
26 => 255.255.255.64
0 => 0.0.0.0
8 => 255.0.0.0
16 => 255.255.0.0
It is interesting to note that the old "route -n" command
shows the first two entries as being duplicates when in fact
they are not! I thought this was a bug in the new kernel
until I compiled the kernel with the NETLINK stuff and got
the iproute2 package working.
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
207.223.13.64 0.0.0.0 255.255.255.224 U 0 0 0 eth0
207.223.13.64 0.0.0.0 255.255.255.224 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 207.223.13.65 0.0.0.0 UG 0 0 0 eth0
It is also interesting to note that the ifconfig command
suggests that my eth0 is having problems transmitting.
However, all application level stuff seems to be functioning
perfectly.
# ifconfig -a
lo Link encap:Local Loopback
inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:24 errors:0 dropped:0 overruns:0
TX packets:0 errors:1848 dropped:24 overruns:0
eth0 Link encap:Ethernet HWaddr 00:60:08:1E:AD:CF
inet addr:207.223.13.69 Bcast:207.223.13.95 Mask:255.255.255.224
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3284 errors:0 dropped:0 overruns:0
TX packets:0 errors:1477151 dropped:3317 overruns:0
Interrupt:11 Base address:0xf8c0
The following was done to enable tunneling:
The equivalent iproute2 commands to enable the eth0 interface would be:
#ip link set eth0 up
#ip addr add 207.223.13.69/27 broadcast 207.223.13.95 label eth0 dev eth0
This was not needed since the startup already did the base config using
ifconfig and route.
To initialize the tunnel I would have done:
#ip tunnel add tunl0 mode ipip remote 172.17.42.50 local 207.223.13.75
but this returns
ioctl: No buffer space available
So I did this:
#ifconfig tunl0 207.223.13.75 netmask 255.255.255.224 pointopoint \
> 172.17.42.50 netmask 255.255.255.0
And then tell the route table that all traffic for 207.223.13.75 needs
to be sent to 172.17.42.50 thru the tunnel:
#ip route add 207.223.13.75 via 172.17.42.50 table main dev tunl0
Then have the eth0 interface listen for 207.223.13.75 traffic:
#arp -s 207.223.13.75 00:60:08:1E:AD:CF pub
I then have:
# ip link show
1: lo: <LOOPBACK,UP> mtu 3924 qdisc noqueue
link/LOOPBACK 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
link/ETHER 00:60:08:1e:ad:cf brd ff:ff:ff:ff:ff:ff
inet 207.223.13.69/27 brd 207.223.13.95 scope global eth0
3: tunl0@NONE: <NOARP,UP> mtu 1480 qdisc noqueue
link/TUNNEL 00:00:00:00 brd 00:00:00:00
inet 172.17.42.50/24 local 207.223.13.75 scope global tunl0
and:
# ip route list
207.233.13.75 via 172.17.42.50 dev tunl0
207.223.13.64/27 dev eth0 scope link
207.223.13.64/27 dev eth0 proto kernel scope link src 207.223.13.69
172.17.42.0/24 dev tunl0 proto kernel scope link src 207.223.13.75
127.0.0.0/8 dev lo scope link
default via 207.223.13.65 dev eth0
and: # arp -vn Address HWtype HWaddress Flags Mask Iface 207.223.13.65
ether 08:00:20:87:69:53 C eth0 207.223.13.75 * * MP * Entries: 2
Skipped: 0 Found: 2
*********************************************************
Here is the setup for the remote agent (172.17.42.50):
*********************************************************
Before any attempt is made to configure tunneling, the
machine, with RedHat 5.1 startup scripts intact, reveals:
# ip link show
1: lo: <LOOPBACK,UP> mtu 3924 qdisc noqueue
link/LOOPBACK 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
link/ETHER 00:80:c8:55:66:fe brd ff:ff:ff:ff:ff:ff
inet 172.17.42.50/24 brd 172.17.42.255 scope global eth0
3: tunl0@NONE: <NOARP> mtu 1480 qdisc noop
link/TUNNEL 00:00:00:00 brd 00:00:00:00
# ip route list
172.17.42.0/24 dev eth0 scope link
172.17.42.0/24 dev eth0 proto kernel scope link src 172.17.42.50
127.0.0.0/8 dev lo scope link
default via 172.17.42.1 dev eth0
The same errors show up on the ifconfig on this box too.
The following was done to enable tunneling:
The idea of seperating the interface level IP address from
the application level IP address on this box is a bit
misleading. I figured that it would be easier to bind the
207.223.13.75 address to the eth0 interface and proxy-ARP for the
172.17.42.50 address then to figure out some way of modifying
the src address on packets before they are encapsulated.
Any packets that I may want to send to the 172.17.42.0 network
will not need to go through the tunnel. However, all replies
from other machines in this network will send to 207.223.13.75
sending packets out of the network to machine 207.223.13.69 and
back through the tunnel before getting to 172.17.42.50 or I
guess we can call it 207.223.13.75 in the 172.17.42.0 network.
First change the address on eth0:
# ip addr del 172.17.42.50/24 dev eth0
# ip addr add 207.223.13.75/27 broadcast 207.223.13.95 dev eth0
Set up the tunnel:
# ifconfig tunl0 172.17.42.50 netmask 255.255.255.0 pointopoint \
> 207.223.13.69 netmask 255.255.255.224
Set the default route to go thru the tunnel:
# ip route add 0/0 via 207.223.13.69 table main dev tunl0
Send local traffic straight out eth0:
# ip route add 172.17.42.0/24 via 207.223.13.75 table main dev eth0
I wonder if I can say instead:
# ip route add 172.17.42.0/24 via 172.17.42.50 table main dev eth0
and have the source address of outgoing packets be 172.17.42.50?
Then proxy-ARP for 172.17.42.50 on eth0:
# arp -s 172.17.42.50 00:80:c8:55:66:fe pub
I then have:
# ip link show
1: lo: <LOOPBACK,UP> mtu 3924 qdisc noqueue
link/LOOPBACK 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
link/ETHER 00:80:c8:55:66:fe brd ff:ff:ff:ff:ff:ff
inet 207.223.13.75/27 brd 207.223.13.95 scope global eth0
3: tunl0@NONE: <NOARP,UP> mtu 1480 qdisc noqueue
link/TUNNEL 00:00:00:00 brd 00:00:00:00
inet 207.223.13.69/27 local 172.17.42.50 scope global tunl0
# ip route list
207.223.13.64/27 dev eth0 proto kernel scope link src 207.223.13.75
207.223.13.64/27 dev tunl0 proto kernel scope link src 172.17.42.50
172.17.42.0/24 via 207.223.13.75 dev eth0
127.0.0.0/8 dev lo scope link
default via 207.223.13.69 dev tunl0
# arp -vn Address HWtype HWaddress Flags Mask Iface 207.223.13.69
(incomplete) eth0 172.17.42.50 * * MP * Entries: 2 Skipped: 0 Found: 2
And, well, it does not work. :(
Here are my questions:
Is my logic completely screwed up here or what?
What's wrong and where?
What kind of testing can I do to debug?
What do I look for in a TCPDUMP?
Any help would be greatly appriciated!
References:
* Advanced routing mini-HOWTO by Timur A. Bolokhov,
[EMAIL PROTECTED] September 29, 1998
This has the most complete documentation on the
iproute2 package that I have found.
* /usr/src/linux/drivers/net/README.tunnel found in
the 2.0.34 kernel files
* Mobile-IP for Linux (ver 1.00) by Abhijit Dixit and
Vipul Gupta May 23, 1996
* and assorted postings to fa.linux.net, fa.linux.kernel,
and comp.os.linux.networking
ON THE CREATION OF A HOWTO
It is my sincere desire to initiate the creation of a HOWTO
on IP tunneling. I found a "mini-mini" IP tunneling HOWTO that
was initiated in Feb. '97 but did not contain anything useful.
The author did not even put their name on it. I would like
to document a few different approaches to IP tunneling based
on different network configurations and then eventually apply
encryption to the encapsulated packet for a VPN style approach.
Would the creation of this HOWTO be stepping on anybody's toes
or is there anybody that would like to contribute?
Many thanks.
-Steve Maring
[EMAIL PROTECTED]
GTE Enterprise Solutions
Tampa, FL USA
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: [EMAIL PROTECTED] (Ralph W. Crane)
Subject: Re: compuserve dial-in script?
Reply-To: [EMAIL PROTECTED]
Date: Thu, 25 Feb 1999 13:53:23 -0500
On Wed, 24 Feb 1999 14:17:45 GMT,
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>Hi,
>
>I've been trying to make a ppp-on script to dial in Compuserve's system. So
>far I managed to get this done, buy dialing in (successfuly) manualy:
>
<snip>
Hello:
I've answered this one before in one or more of these newsgroups, but here it
is again. Below is the chat script I use to connect to compuserve:
REPORT CONNECT
ABORT 'NO'
ABORT 'BUSY'
ABORT 'ERROR'
'' AT
OK-AT-OK ATZ
OK-AT-OK ATDT<local CSI tel#>
CONNECT '\r'
ame: CIS
ID: <my CSI id>/GO:PPPCONNECT
word: <password>
PPP
The important part for you is the GO:PPPCONNECT on the ID line. This form
allows you to do something ( in this case, start PPP connection) immediately
on login without having to wait for the initial messages, etc. compuserve
usually gives. Of course you could use GO PPPCONNECT at the prompt after
getting logged in.
I orginally found out how to do this by reading some files in the UNIXFORUM
forum ( a little redundant huh :-) ). Do a search on PPP.
Ralph
PS I just did a search and found a recent file called RHCISPPP.TXT in
UNIXFORUM Library 4 which purports to tell exactly how to connect from
RedHat LINUX. I haven't read it myself, so I don't know what it says.
------------------------------
From: "Margus" <[EMAIL PROTECTED]>
Subject: Accounting the time for using the proxy server
Date: Thu, 25 Feb 1999 21:34:52 +0200
Hello!
Can anybody say, whether is under Linux a program, like a Wingate for
Windows, what can count up the time accessing a proxy server (firewall) and
restrict (close) a connection, if a quoted time is used?
I will build a proxy server in SUSE Linux box. Now is working access over
the Intranet and dial-up on-demand. But I can?t find a program for
accounting the used time.
Thanks for any help!
Margus Leoste
------------------------------
From: tommy <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: ifwadm
Date: Thu, 25 Feb 1999 21:54:30 +0100
you need ifwadm ,
------------------------------
From: David Heddle <[EMAIL PROTECTED]>
Crossposted-To:
comp.software.config-mgmt,comp.os.linux,comp.os.linux.admin,comp.os.linux.help,comp.os.linux.misc,comp.os.linux.redhat
Subject: Remote CVS Access Broke With RedHat 5.2 Linux Upgrade
Date: Sat, 27 Feb 1999 20:44:36 GMT
==============F71A46D8E98C5D0DE98D7D50
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hello,
I recently upgraded my home Linux box to Red Hat 5.2. This also upgraded
cvs to 1.10. I keep a cvs repository on the home linux box and use
password authentication from machines over the net for access. After
upgrading, if I try to access the repository remotely I get the
following error
>cvs update
cvs [update aborted]: unrecognized auth response from 137.155.x.x :
error 0 Server configuration missing --allow-root in inetd.conf
(I put int the x.x to protect the ip address)
All this worked beautifully before I upgraded (betcha never heard that
from a linux user before!) Any suggestions? It seems as if I need
"--allow-root" SOMEWHERE in my inetd.conf file, but I do not know where.
Thanks for any & all help.
David
email: [EMAIL PROTECTED]
==============F71A46D8E98C5D0DE98D7D50
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
Hello,
<P>I recently upgraded my home Linux box to Red Hat 5.2. This also upgraded
cvs to 1.10. I keep a cvs repository on the home linux box and use password
authentication from machines over the net for access. After upgrading,
if I try to access the repository remotely I get the following error
<P>>cvs update
<BR><FONT COLOR="#FF0000">cvs [update aborted]: unrecognized auth response
from 137.155.x.x : error 0 Server configuration missing --allow-root in
inetd.conf</FONT>
<P>(I put int the x.x to protect the ip address)
<P>All this worked beautifully before I upgraded (betcha never heard that
from a linux user before!) Any suggestions? It seems as if I need "--allow-root"
SOMEWHERE in my inetd.conf file, but I do not know where.
<P>Thanks for any & all help.
<P>David
<P>email: [EMAIL PROTECTED]
<BR> </HTML>
==============F71A46D8E98C5D0DE98D7D50==
------------------------------
From: Darren Ehmke <[EMAIL PROTECTED]>
Subject: IP Forwarding??
Date: Wed, 24 Feb 1999 12:02:07 -0800
Hi,
I am trying to setup 2 computers to be routers as the following:
Internet
\|/
|
Cisco Router (ISP)
|
Cisco Router (ours)
|
First Linux Box (router system)
|
Second Linux Box (router system)
|
/|\
Our Internal Network
The question is, do I have to setup the rules for ipfwadm?? It is
in the kernel,
but the rules are not setup. Or will the routing work properly with the
route daemon
without the use of ipfwadm?? Any information would be greatly
appreciated.
Darren
[EMAIL PROTECTED]
------------------------------
From: Carter Koch <[EMAIL PROTECTED]>
Subject: Named dies.
Date: Thu, 25 Feb 1999 15:52:52 -0500
Hi,
I want to check out named on Linux. I've always run it on Solaris. I
took named.boot as
well as db's from known good Solaris named server. Ran .pl conversion
script to
create named.conf. Named dies after starting. Turned on debugging and
I don't see
anything unusual. Any ideas?
Thanks,
Carter
------------------------------
From: "Rob" <[EMAIL PROTECTED]>
Subject: Netgear 310tx
Date: Fri, 26 Feb 1999 12:53:28 -0700
I've recently started learning Linux and have so far got RedHat 5.0
installed on my pc and xwindows working. Were I'm at now is trying to
figure out the best way to get my Network card setup in Linux. The latest
info from Netgear on my card has files for Linux, but I don't know how to
get them from w98 into Linux. I read their (brief) help on it and it just
made me more confused. They suggest 2 separete ways to add the files. One
was if I wanted to compile it into my kernal, and the other is if I want it
as a Module.
I have no idea which would be better or exactly what I have to do (other
than type the command that their help file says). I guess I'm trying to
figure out which way I should go with it and how to get the files into
Linux.
Any help would be appriciated.
Rob
------------------------------
** 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
******************************
