Linux-Networking Digest #624, Volume #10 Thu, 25 Mar 99 03:13:39 EST
Contents:
Re: using linux box to console to cisco ([EMAIL PROTECTED])
Re: Windows 95/98 -> to linux Samba; diald problems (Carles Arjona)
Re: Bind 8.1.2 and MX records (Carles Arjona)
Redhat 5.1 upgrade to kernel 2.2.1 ("Ovidiu Dressler")
Re: IP Masqerading ("PEK")
IP Masquerading and FTP ("PEK")
Redhat 5.1 upgrade to kernel 2.2.1 ("Ovidiu Dressler")
How to configure 3 n/w cards on a single machine? (Kishore)
two computer network, 100% packet loss (Christopher)
chaos theory in network traffic ([EMAIL PROTECTED])
Is anyone usin ISDN modems? ("Bj�rn Ekstr�m")
Re: Can Linux Do This ??? (peter)
Re: Network unreachable or server down. ([EMAIL PROTECTED])
broken network (Mike Hammer)
Re: "Industrial" Ethernet (Ben Poole)
modem vs. mouse serial config ("liam toh")
----------------------------------------------------------------------------
From: [EMAIL PROTECTED]
Subject: Re: using linux box to console to cisco
Date: Thu, 25 Mar 1999 01:36:08 GMT
On Wed, 24 Mar 1999 04:31:21 GMT, [EMAIL PROTECTED] (Albert Mintz)
wrote:
>Hi all,
> I need help seeting up A serial port to console to A cisco router.I
>looked at the minicom setup options and don't really understand how to
>make it work as A null connection.If anyone is using linux As A
>console i'd really appreciate if you'd share with me how to set it up.
>
> Thanks
step 1.
connect the rj side of your cable that came with your router
labeled terminal into the console port one the back of the router.
step 2.
connect the db25 side of the cable labeled terminal to a RS232
serial port.
step3.
configure your terminal software ( in your case minicom ) to use
the serial port you plugged the db25 connector into. and set it to
9600,8,n,1 (once this is set in minicom, you need to restart minicom
for the changes to take effect [at least was nessecary for me])
step 4
press enter. you should now see a login prompt. if not then your
cable is not right or the router has the console disabled.
tng.
------------------------------
From: Carles Arjona <[EMAIL PROTECTED]>
Subject: Re: Windows 95/98 -> to linux Samba; diald problems
Date: Sun, 21 Mar 1999 12:40:32 +0100
Scott Harvey <[EMAIL PROTECTED]> wrote:
>
> What is happening, is that, every 15 minuets or so
> a request goes out to the ( named ) name server to resolve the name of
> my workgroup and that request fires up diald to call my ISP. Is there a
> way to filter this request out in standard.filter of diald ...
That's explained at the great web page:
http://personal1.iddeo.es/ret005lc/diald-win-e.html#netbios
Regards.
--
Carles Arjona [EMAIL PROTECTED]
-
Please, just remove the second NOSPAM for replies from newsgroups.
(Yes, NOSPAM is my real username)
[Don't send me e-mail copies of usenet postings, please]
------------------------------
From: Carles Arjona <[EMAIL PROTECTED]>
Subject: Re: Bind 8.1.2 and MX records
Date: Sun, 21 Mar 1999 12:23:15 +0100
Bill Dunn <[EMAIL PROTECTED]> wrote:
>
> I have always had the MX record set as mail.whatever.com, which is set
> as a CNAME to a previous A record.
That's wrong. From the http://www.sendmail.org/virtual-hosting.html web
page:
"3.Configure MX records for your domain (Note: CNAME records can not be
used; see � 5.2.2 of RFC 1123 for details.)"
http://www.sendmail.org/rfc/1123.html#Section5.2.2
Regards.
-
Carles Arjona [EMAIL PROTECTED]
-
Please, just remove the second NOSPAM for replies from newsgroups.
(Yes, NOSPAM is my real username)
[Don't send me e-mail copies of usenet postings, please]
------------------------------
From: "Ovidiu Dressler" <[EMAIL PROTECTED]>
Subject: Redhat 5.1 upgrade to kernel 2.2.1
Date: Tue, 16 Mar 1999 12:06:36 +0200
I tried to upgrade the kernel 2.0.35 to 2.2.1 on a Redhat 5.1 system.
I followed the instructions from the readme files and everything went
aparently ok.
I copied the old config file into the new linux directory and I added only
the ipportfw and the other ip_masquerading options. I also prepared and
installed the loadable modules.
After rebooting I received some weird error messages.
1. The machine doesn't recognize anymore one of the network cards (before
that it was recognized as a ne2000 compatible).
2. At boot time I see repeatedly the following message: unable to resolve
symlink for a big part of the modules.
Can anyone help me ? Where did I miss something ?
Fortunately I kept a copy of the old kernel and I'm able to boot 2.0.35
normaly.
I'm interested especially in the IPportforwarding option of the new kernel.
I tried to apply patches to the 2.0.35 one but patching failed from unknown
reasons.
Please help,
Ovidiu D.
------------------------------
From: "PEK" <[EMAIL PROTECTED]>
Subject: Re: IP Masqerading
Date: Thu, 25 Mar 1999 02:23:57 GMT
Greetings Jason
>I've got a problem setting up an IP masq system. Here's the situation.
>I think I've followed this as documented in the IP Masqerading Mini
>Howto at
>sunsite.unc.edu/pub/Linux/distributions/slackware/3.6/docs/howto/mini.
>
>My 2 '95 machines are both setup to use the LAN for internet access and
>have a gateway set for 192.168.1.1 and dns settings to look for my ISP's
>dns server. My machine (the one I'm using right now) is connected to
>the internet and is bound for the local network on eth0 to 192.168.1.1
>and internet access on ppp0 with a dynamic IP. My /etc/rc.d/rc.inet1
>sets up a route for the network (192.168.1.0) using the netmask
>255.255.255.0. I have ipfwadm setup an accept masq of 192.168.1.0/24
>and target it to 0.0.0.0/0 with the command ipfwadm -F -a m -S
>192.168.1.0/24 -D 0.0.0.0/0.
Make sure you're setting up a default route for your network over the ppp
connection with the 'defaultroute' command in pppd. It's a wise thing to
generally check over your routing table (just type 'route') and make sure
there's nothing that doesn't belong. The first time I set up two ethernet
adapters in one machine, all these routes appeared and half of them were
wrong.
Just a suggestion
Me
------------------------------
From: "PEK" <[EMAIL PROTECTED]>
Subject: IP Masquerading and FTP
Date: Thu, 25 Mar 1999 02:34:05 GMT
Greetings
I am sure this question has been posed before, but I cannot see it in any of
the past messages on this newsgroup. I'm running IP Masquerading with a
one-way cable modem for about a month now, and everything works dandy from
the client machines (Win98). I can http, write mail, browse newsgroups,
etc., but I cannot FTP with an FTP client. I expect this, because the FTP
client sends the data port command for the internal addresses of my network
(10.1.1.x) and obviously the FTP server won't send to these addresses.
I'd be desperately searching for a Linux-side solution to this problem, if
it weren't for the fact that FTP'ing within an http browser works just
fine...? Is there some sort of extra authorization performed by an FTP
client? Does the HTTP browser use an HTTP connection to the FTP server, and
thus forego the opening of an FTP port? I'm stumped.
The above situation makes me think there may be a client-side solution
and/or a linux-side solution. Either would be appreciated.
Thanks
[EMAIL PROTECTED]
------------------------------
From: "Ovidiu Dressler" <[EMAIL PROTECTED]>
Subject: Redhat 5.1 upgrade to kernel 2.2.1
Date: Mon, 15 Mar 1999 22:06:53 +0200
I tried to upgrade the kernel 2.0.35 to 2.2.1 on a Redhat 5.1 system.
I followed the instructions from the readme files and everything went
aparently ok.
I copied the old config file into the new linux directory and I added only
the ipportfw and the other ip_masquerading options. I also prepared and
installed the loadable modules.
After rebooting I received some weird error messages.
1. The machine doesn't recognize anymore one of the network cards (before
that it was recognized as a ne2000 compatible).
2. At boot time I see repeatedly the following message: unable to resolve
symlink for a big part of the modules.
Can anyone help me ? Where did I miss something ?
Fortunately I kept a copy of the old kernel and I'm able to boot 2.0.35
normaly.
I'm interested especially in the IPportforwarding option of the new kernel.
I tried to apply patches to the 2.0.35 one but patching failed from unknown
reasons.
Please help,
Ovidiu D.
------------------------------
From: Kishore <[EMAIL PROTECTED]>
Subject: How to configure 3 n/w cards on a single machine?
Date: 25 Mar 1999 02:31:52 GMT
I have a machine which has 3 network cards on it.
I gave it
10.1.1.1
10.1.2.1
10.1.3.1
as the ip addressses to it.
I have another machine which I gave 10.1.1.2 (IP addr)
10.1.1.1 as the gw.
I gave 255.255.255.0 as Subnet mask for this machine.
This machine(10.1.1.2) cannot ping the gw.
even the gateway cannot ping this.
Please give me a detailed approach how to do this.
Just establish two machines with network connection.
10.1.2.1 is to be connected to a separate machine with IP 10.1.2.2
But I have not tried yet!
Thanks for your suggestions in advance
Sincerely,
Kishore
================== Posted via SearchLinux ==================
http://www.searchlinux.com
------------------------------
From: [EMAIL PROTECTED] (Christopher )
Subject: two computer network, 100% packet loss
Date: Wed, 24 Mar 1999 23:57:30 GMT
Hello, I am trying to setup a mini network with two computers. I have
read the instructions from NET-3 and ORA's TCP/IP but I still can't
get the computers talking. I am using two DEC ethernet cards (DE200,
and DE205) that appear to be working with out conflicts. They
attached with thin net cable which is terminated at both ends.
I used ifconfig on the first and set the address to eth0 to 172.16.1.3
with netmask 255.255.0.0. The other computer is eth0 172.16.1.2.
On the first machine route -n gives
Dest Gateway Genmask Flags ... Iface
172.16.1.2 0.0.0.0 255.255.255.255 UH eth0
127.0.0.0 0.0.0.0 255.0.0.0 U lo
On the other:
Dest Gateway Genmask Flags ... Iface
172.16.1.3 0.0.0.0 255.255.255.255 UH eth0
127.0.0.0 0.0.0.0 255.0.0.0 U lo
When I ping from either machine with
ping 172.16.1.2 or ping 172.16.1.3
I get the following message:
PING 172.16.1.2 : 56 data bytes
After ctrl-c
--- 172.16.1.2 ping statistics ---
7 packets transmitted, 0 packets recieved, 100% packet loss
Both machines give the same messages.
Please give me some ideas as to what could be causing the problem.
Thanks.
------------------------------
From: [EMAIL PROTECTED]
Subject: chaos theory in network traffic
Date: Thu, 25 Mar 1999 06:30:56 GMT
hello!
I am exploring the application of CHAOS THEORY in NETWORK TRAFFIC.
Could anyone give me references to the research done in this
field?
Any help in this regard will be greatly appreciated.
Regards,
Piyush
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: "Bj�rn Ekstr�m" <[EMAIL PROTECTED]>
Subject: Is anyone usin ISDN modems?
Date: Tue, 16 Mar 1999 22:18:29 +0100
I have a zyxel omni.net plus ISDN modem. Has anyone used that modem with
linux? I have no problem to connect with a analog US robotics modem but with
the zyxel it seems to be difficult to make a connection.
Bjorn Ekstrom
------------------------------
From: [EMAIL PROTECTED] (peter)
Subject: Re: Can Linux Do This ???
Date: Thu, 25 Mar 1999 06:50:58 GMT
On Wed, 24 Mar 1999 11:37:55 -0800, "The Lone Scribe"
<[EMAIL PROTECTED]> wrote:
>peter wrote in message <[EMAIL PROTECTED]>...
>>1) Does linux support 56k v90 modems ???
>
>
>Yes. But to take advantage of v.90, your ISP has to have v.90 modems
>installed at their POP(s).
>
>>2) Now, linux also supports multiple modems, does my IP have to
>>support it as well???
>
>
>Yes, your ISP will need to sell you a 'shotgun' type of account (if
>available) so that you can use two phone lines/modem as a pair, not as two
>separate accounts. I've never tried this with Linux because it was more cost
>effective to get a xDSL account instead. Shotgun accounts were twice the
>cost of a standard dial-up ($40/mo.), and needed a second phone line
>($12/mo.), bringing the total cost to a bit higher than DSL ($49/mo.) at a
>fraction of the speed of DSL, and I saved even more because I eliminated my
>voice phone line (you can use both DSL and voice at the same time on the
>same line). But perhaps someone else has done this and will post a solution
>for you if you can't get affordable DSL in your area.
>
>
>
Wow, DSL sound great, what speed is your line?
My friend has DSL running something like; 192k download and 80k
upload. He pays a total of $59.
Can people call you on the DSL line?
peter
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Network unreachable or server down.
Date: Thu, 25 Mar 1999 06:57:15 GMT
In article <7dbfp7$h5j$[EMAIL PROTECTED]>,
"Georgios" <[EMAIL PROTECTED]> wrote:
> I 've just set-up my RedHat 5.2 ppp but..I have an access problem to my ISP
>
> After connecting to my ISP without any problem I get the "Network error
> Unable to connect to server TCP error Network unreachable or the server is
> down".
>
> Does anybody has an idea??
>
>
first: what do you do AFTER connecting to your isp, to elicit this response?
( which program do you start) second : look at ifconfig to see that ppp is
running, has the correct dns-servers, etc ... try to ping the proxy-server of
your isp, the dns-servers - see that that works after that , maybe THE
(which?) server is really down
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: [EMAIL PROTECTED] (Mike Hammer)
Subject: broken network
Reply-To: [EMAIL PROTECTED]
Date: Tue, 16 Mar 1999 22:47:50 GMT
Some how I managed to break my home network. My 3 machines originally
started with WD 8013 NICs and everything worked well. I acquired 3 SMC
8216s and decided to replace the WDs with the newer SMCs. The change
on the first machine went smoothly. I installed the new NIC and
changed modules with linuxconf. The new card was detected and
everything worked just fine.
Now on to the 2nd machine. Same procedure but once I rebooted the
new NIC was not being detected. The error message is:
smc-ultra.c: No SMC Ultra card found (i/o=0x118)
insmod: /lib/modules/2.0.36/net/smc-ultra.o: init_module:
Device or Resource busy
delaying eth0 initialization
First thought was an IRQ or I/O address conflict but this machine
is pretty bare and there isnt really anything to conflict with.
Changing addresses and/or IRQs didnt help.
I then attempted to put back in the old 8013 card that WAS working
just fine. However I now get the same error now with the old card and
the WD 80xx module.
I know these cards are OK as Ive tried them in the other machine.
And compiling a new kernel and modules didnt help either.
I hate to reinstall from scratch but at this point Ive run out of
ideas. Anybody got any ideas?
------------------------------
From: Ben Poole <[EMAIL PROTECTED]>
Subject: Re: "Industrial" Ethernet
Date: 25 Mar 1999 05:31:52 GMT
James Youngman wrote:
>
> [EMAIL PROTECTED] writes:
>
> > Install a backbone consisting of redundant fiber between platforms in a
Bus
> > configuration. Install a media converter and hub on each platform thus
> > converting to a Star configuration.
> >
> > My limited knowledge of Ethernet tells me that a Bus topology depends
on
> > being "terminated" at every end and will fail the entire network if a
cable
> > breaks, and that a Star topology will continue to operate if one
segment
> > fails as long as the hub continues to operate. My concern is (with this
given
> > topology) if the backbone is cut between the platforms, does the star
network
> > on the "stand- alone" platform continue to operate?
>
> Basically, this depends on the media converters themselves. Many
> Ethernet hubs have optical uplinks.
COST IS A FACTOR.
>
> Anyway, my experience of comms in industrial environments makes me
> very reluactant to use electrical connections of any kind. I would
> reccomend fiber instead, even *within* each platform. Things like
> welding really disable you, otherwise.
>
I basically agree completely. However, if the control room is, as I am
assuming by the description of the evironment, encased in steel, this will
protect the internal communications system from interference. Only those
nodes which are external to the communications hub need be connected by
fiber this will reduce cost and 100TX is much more duable - if moved - than
fiber.
VERY IMPORTANT: If you are using Linux it, is cost efficient plus wise to
load balance with a minimum of 2 servers for redundancy at each platform
point on your star topology.
I cannot imagine a situation where a $500 pc could not function perfectly
for each server plus NIC cards and monitor. I can only imagine what the
down time cost would be to a platform....probably less than the cost of the
equipment I mentioned for the added security of redundancy. That limits
your points of failure to the transmission equipment and switch. HOWEVER,
if these nodes are the only servers on the platform, I would certainly beef
that estimate up heavily with daily tape or DVD backups, redundant
hot-swapable drives and power supplies, etc. and use these units as mail,
http, ftp, etc. servers for each platform. Their redundancy will prove to
be uniterrupted (read less headaches for you) service to your users.
( if my job was on the line, I would recommend microwave in a triangle -
since there are three platforms - so that if one goes down the other two
will continue to communicate. The reason for microwave is for adequate
banwidth for the future and I assume direct line of sight over the water
for all platforms...for today 3MB is reasonable as was described earlier
for RF transmission....But then, this is a cost tradeoff.)
For the expense, internal connections should be 100TX full duplex with a
switch for each node. The price of these items and the NIC cards involved
really nullify any argument for using the 10TX connections except for fiber
- hence, switch. HP (and many others, I have used this and it works but
there are other vendors, cisco, baynetworks, etc) HP 4000 10/100 switch
with redundant power supplies come with 48+ 10/100TX connections plus
expansion modules for fiber and is SMNP manageable for about $1500 street.
For the network administrator, SMNP managed via a web browser or java
console is a life send. HINT: use all SNMP controlable via browser devices.
Just pop in 2 Fiber 10FX modules and connect to two microwave or RF com
units for each platform with expansion capabilities for other FX modules
that would communicate outside the communications room. This allows the 10
mb transmission segment talk to the 200mb (full duplex) platform network.
You will have bandwidth to spare on the 200mb side which may be utilized by
engineers on site and the small extra expense will be more than justified
in reduced headaches in a very few years due to increased bandwidth usage
of future OS and application demands.
> ACTUALLY reachable as @free-lunch.demon.(whitehouse)co.uk:james+usenet
================== Posted via SearchLinux ==================
http://www.searchlinux.com
------------------------------
From: "liam toh" <[EMAIL PROTECTED]>
Subject: modem vs. mouse serial config
Date: Tue, 16 Mar 1999 14:34:18 -0800
new to linux, using redhat 5.2 kernel 2.0.36
Im trying to set up my modem, I have a serial mouse connected. Can anyone
point me to a doc that will describe how to configure each of these devices
on their own port.
With the modem connected (Ive tried an old intel 144/144e and a USR
sportster 33.6 #00083907, both external) Im not getting any device info on
any port except cua0
When I run:
statserial /dev/cua0
I get a device print out, but
0 clear to send
0 data set ready
all of the other ports give TIOCMGET failed: Input/output error
How can I find what port my mouse is using, and where can I find info on
configuring these devices to their own ports?
------------------------------
** 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
******************************
