Re: 2nd ethernet ports and Routing....

2000-06-05 Thread Warren Brown


Hello
Using the standard Solaris file /etc/netmasks
would have solved this problem also.

WB

The solution was very simple.
Only on COGEN I did the following:
Add to /etc/hosts
152.153.16.50   ROUTER

Add to /etc/defaultrouter
ROUTER

But this didn't work.
FOXBORO networks are configured as class B network.
So I added a script to /etc/fox/userapps.dat called 'routing.scr' which 
looked like this:

#!/bin/sh
#
# We have to force the netmask like this because at boot time
# FOXBORO is resetting it to class B subnet
# This is ok for the NODE BUS but not for the second ethernet card.
#
# There are two 152.153.x.x networks separated by 10.202.x.x
# who need to be able to talk to each other
# 152.153.16.x on the foxboro side of the router and
# 152.153.the.rest on the other side of 10.202.x.x
#
# This script is called from /etc/fox/user_apps.dat
#
# 17-April-2000 F.Schouten.
#
ifconfig le1 netmask 255.255.255.0




---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with unsubscribe foxboro in the Subject. Or, send any mail to
[EMAIL PROTECTED]




RE: 2nd ethernet ports and Routing....

2000-06-05 Thread Schouten, Frits JF

Unfortunately not Warren.
I did put the netmask in etc/netmasks but at boot time the FOXBORO software 
is overwriting it, resulting to what is was before I made my changes.
Regards,
Frits.

 -Original Message-
 From: Warren Brown [SMTP:[EMAIL PROTECTED]]
 Sent: Tuesday, June 06, 2000 1:01 AM
 To:   [EMAIL PROTECTED]
 Subject:  Re: 2nd ethernet ports and Routing
 
 
 Hello
 Using the standard Solaris file /etc/netmasks
 would have solved this problem also.
 
 WB
 
 
 

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with unsubscribe foxboro in the Subject. Or, send any mail to
[EMAIL PROTECTED]




2nd ethernet ports and Routing....

2000-06-03 Thread Schouten, Frits JF

Well, I might as well put in my 5cts worth.

Here we are with a sold off co-generation plant. The decision was make to retain the 
IP addresses of the second ethernet ports on the Foxboro systems.
No problem so far. But for accounting and control purposes it was necessary to 
maintain production/control information to come to us. Now here we have a challenge.

COGEN FOXBORO 152.153.16.x   --  NEW COGEN NETWORK 10.202.x.x  -- OUR INTRANET 
152.153.x.x -- MELTERS FOXBORO 152.153.11.x

To add to the challenge the owners of 10.202.x.x installed a firewall between them and 
OUR INTRANET and we had placed routers between the FOXBOROs and the rest of the world 
to keep them isolated from network storms. They do happen, you know :-)

The solution was very simple.
Only on COGEN I did the following:
Add to /etc/hosts 
152.153.16.50   ROUTER

Add to /etc/defaultrouter
ROUTER

But this didn't work.
FOXBORO networks are configured as class B network.
So I added a script to /etc/fox/userapps.dat called 'routing.scr' which looked like 
this:

#!/bin/sh
#
# We have to force the netmask like this because at boot time
# FOXBORO is resetting it to class B subnet
# This is ok for the NODE BUS but not for the second ethernet card.
#
# There are two 152.153.x.x networks separated by 10.202.x.x
# who need to be able to talk to each other
# 152.153.16.x on the foxboro side of the router and
# 152.153.the.rest on the other side of 10.202.x.x
#
# This script is called from /etc/fox/user_apps.dat
#
# 17-April-2000 F.Schouten.
#
ifconfig le1 netmask 255.255.255.0

And they lived happy ever after..

G0AP01# netstat -r
 
Routing Table:
  Destination   Gateway   Flags  Ref   Use   Interface
  - - -- -
localhostlocalhost UH   0117  lo0
152.153.16.0 G0AP01E2  U2   1787  le1
151.128.0.0  G0AP01U3 96  le0
224.0.0.0G0AP01U3  0  le0
default  ROUTERUG   0   6135

G0AP01# ifconfig -a
lo0: flags=849UP,LOOPBACK,RUNNING,MULTICAST mtu 8232
inet 127.0.0.1 netmask ff00
le0: flags=863UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST mtu 1500
inet 151.128.16.65 netmask  broadcast 151.128.255.255
ether 8:0:20:7e:97:fc
le1: flags=863UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST mtu 1500
inet 152.153.16.1 netmask ff00 broadcast 152.153.255.255
ether 8:0:20:7e:97:fc

Cheers,

Frits Schouten
BHP-NZSteel

p.s A bit more that 5cts worth, I suppose :-))


EOM 

NOTICE - This message contains information intended only for the use of the addressee 
named above.  It may also be confidential and/or privileged.  If you are not the 
intended recipient of this message you are hereby notified that you must not 
disseminate, copy or take any action in reliance on it.  If you have received this 
message in error please notify [EMAIL PROTECTED]

---
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with unsubscribe foxboro in the Subject. Or, send any mail to
[EMAIL PROTECTED]