update to 4.10 via ssh

2004-06-17 Thread Nicolás de Bari Embríz G . R .
Hi all, right now I am using freebsd 4.9 but I would like to update to
4.10-STABLE but I have a problem, I want to do this on a dedicated server
the one is in  another country and miles away from me, so I am planing to
do this over ssh.

what I plan to do is a cvsup to get the latest release then:

 1.  `cd /usr/src'
 2.  `make buildworld'
 3.  `make buildkernel KERNCONF=MY_KERNEL'
 4.  `make installkernel KERNCONF=MY_KERNEL'
 6.  `mergemaster -p'
 7.  `make installworld'
 8.  `mergemaster'
 9.  `reboot'


Also I have Perl installed from ports so I have commented the #NOPERL=   
true on /etc/make.conf

I will appreciate some help, tips or recommendations for doing this so I
can update my system.



thanks in advance



-- 
[EMAIL PROTECTED]
key ID 1EF56FDC
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


ftp Redirect problems using RDR

2004-02-23 Thread Nicolás de Bari Embríz G . R .
Hi all.

I am having some problems redirecting a ftp using rrd, i am using ipfilter
and ipnat

my ipnat.rules on Server 1 file has some thing like:

map fxp0 192.168.50.1/24 - 148.243.246.2/32 portmap tcp/udp auto
map fxp0 192.168.50.1/24 - 148.243.246.2/32
rdr fxp0 148.243.246.2/32 port 21 - 192.168.60.1/32 port 21024

My net is something like:


  server 1  server 2
148.243.246.2 200.50.59.30
  - ---
 | FreBSD  | IPSEC tunnel--- |  FTP (pureftp port 11021) |
  - ---
 192.168.50.1192.168.60.1
 | |
 | |
   - -
  | NAT |   | NAT |
   - -
 | |
192.168.50.0/24192.168.60.0/24



I want to redirect ftp connections on server 1 (port 21) to server 2 (port
11021) so when a user, ftp to 148.243.246.2 he gets redirected to server
200.50.59.30, but using the IPSEC tunnel.

ftp 148.243.246.2 port 21  redirect to 192.168.60.1 port 11021

right now the IPSEC tunnel works fine i can ping an see machines from
192.168.50.0/24 to 192.168.60.0/24

Any idea on how could i fix this ?

both servers are using FreeBSD 4.9-STABLE



___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Routing Networks

2004-01-14 Thread Nicolás de Bari Embríz G . R .

Hi all, I need some help routing or making Nat on a LAN.

I have something like this:


  I N T E R N E T
 -
^ ^
| |
fxp0  public IP   public IP
| |
 FreeBSD server  LINUX server
| |
dc0   192.168.10.1|
dc1   192.168.1.1 ^   192.168.1.3
^ |   ^
| |   |
| |   |
   
  |   Switch/Hub   |
   
   |   |
-- -
   |  LAN  A  |   | LAN  B  |
   | 192.168.10.2-254 |   | 192.168.1.4-100 |
-- -

I have running a FreeBSD server as a gateway and DHCP, the server share
the Internet to all the computers on LAN A (192.168.10.0/24).

The server have 3 network cards:

fxp0 is public IP.
dc0  is the gateway for the LAN A 192.168.10.1.
dc1  has IP 192.168.1.1 ( need help with this ).


Right now i am just using fxp0 and dc0 so any computer on the LAN A
192.168.10.2-254 can have Internet, my ipnat.rules file looks like this:

--
map fxp0 192.168.10.1/24 - 0/32 portmap tcp/udp auto
map fxp0 192.168.10.1/24 - 0/32
--

until that point everything just work OK.

There is another network, I will call it LAN B, this LAN make the same
thing that i am doing with the FreeBSD Server, but instead it uses LINUX,
the m achine have 2 network cars.

eth0 has a public IP.
eth1 is the gateway for the LAN B 192.168.1.3


Both networks are connected to the same switch/hub, but now i need that
the computers of LAN A can see ping computers on LAN B.

If I configure the third nick dc1  on the FreeBSD server to have an IP
on the range of LAN B for example with ip 192.168.1.1, then I can see all
the computers from both LAN's, I can ping, telnet, ssh etc. to both
192.168.10.X and 192.168.1.X. networks standing on the FreeBSD server.


What i want to do is that a computer on LAN A with an IP on the range of 
192.168.10.2-254 can ping, telnet, ssh, etc. to a computer on LAN B
192.168.1.X.

How can i solve this problem, is this is a route or Nat problem ?

There is one more issue, I can't touch the LINUX SERVER I can just be a
client or join the LAN by configure a nic with a IP on the range of
192.168.1.0/24.


I have been trying to fix this with static routes but i am not having luck.


Any help will be apreciated.


regards.


-- 
[EMAIL PROTECTED]
key ID 1EF56FDC
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Solution to Routing Networks

2004-01-14 Thread Nicolás de Bari Embríz G . R .

Hi all thanks for all your answers.

The solution that i found was to add to my ipnat.rules this lines:

map dc1 192.168.10.0/24 - 0/32 portmap tcp/udp auto
map dc1 192.168.10.0/24 - 0/32

and to my rc.conf this :

static_routes=linux
route_linux=192.168.0.0/16 192.168.1.3



regards.



Hi all, I need some help routing or making Nat on a LAN.

I have something like this:


  I N T E R N E T
 -
^ ^
| |
fxp0  public IP   public IP
| |
 FreeBSD server  LINUX server
| |
dc0   192.168.10.1|
dc1   192.168.1.1 ^   192.168.1.3
^ |   ^
| |   |
| |   |
   
  |   Switch/Hub   |
   
   |   |
-- -
   |  LAN  A  |   | LAN  B  |
   | 192.168.10.2-254 |   | 192.168.1.4-100 |
-- -

I have running a FreeBSD server as a gateway and DHCP, the server share
the Internet to all the computers on LAN A (192.168.10.0/24).

The server have 3 network cards:

fxp0 is public IP.
dc0  is the gateway for the LAN A 192.168.10.1.
dc1  has IP 192.168.1.1 ( need help with this ).


Right now i am just using fxp0 and dc0 so any computer on the LAN A
192.168.10.2-254 can have Internet, my ipnat.rules file looks like this:

--
map fxp0 192.168.10.1/24 - 0/32 portmap tcp/udp auto
map fxp0 192.168.10.1/24 - 0/32
--

until that point everything just work OK.

There is another network, I will call it LAN B, this LAN make the same
thing that i am doing with the FreeBSD Server, but instead it uses LINUX,
the m achine have 2 network cars.

eth0 has a public IP.
eth1 is the gateway for the LAN B 192.168.1.3


Both networks are connected to the same switch/hub, but now i need that
the computers of LAN A can see ping computers on LAN B.

If I configure the third nick dc1  on the FreeBSD server to have an IP
on the range of LAN B for example with ip 192.168.1.1, then I can see all
the computers from both LAN's, I can ping, telnet, ssh etc. to both
192.168.10.X and 192.168.1.X. networks standing on the FreeBSD server.


What i want to do is that a computer on LAN A with an IP on the range of 
192.168.10.2-254 can ping, telnet, ssh, etc. to a computer on LAN B
192.168.1.X.

How can i solve this problem, is this is a route or Nat problem ?

There is one more issue, I can't touch the LINUX SERVER I can just be a
client or join the LAN by configure a nic with a IP on the range of
192.168.1.0/24.


I have been trying to fix this with static routes but i am not having luck.


Any help will be apreciated.


regards.


-- 
[EMAIL PROTECTED]
key ID 1EF56FDC


-- 
[EMAIL PROTECTED]
key ID 1EF56FDC


-- 
[EMAIL PROTECTED]
key ID 1EF56FDC


-- 
[EMAIL PROTECTED]
key ID 1EF56FDC
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Secure MSN and ICQ chat

2004-01-14 Thread Nicolás de Bari Embríz G . R .
Hello all.

I want to secure the network traffic of the users on my LAN, I want to
secure the MSN and ICQ data so people on the building can't use a sniffer
and watch the conversations.

I have something like this:


InternetInternet
  ^   ^
  |   |
router ( sniffer in here )|
  |   |
  |   |
  |   |
FBSD server   -- VPN/IPSEC  --   FBSD server on a secure network
  |
  |
  Swith/hub
  |
  |
-
   | LAN |
-

Right now i have an tunnel with IPSEC to another FreeBSD Server the one is
on a secure network and on a different building, what i was thinking to
do, was to install a proxy on the Secure FreeBSD server and configure the
MSN/ICQ clients to use that proxy so only that traffic could go out using
the secure network.

I would like to know if there is a better option for securing this
communications, or if this idea is fine and what proxy software do you
recommend to install for doing this.

regards
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Solution to Routing Networks

2004-01-14 Thread Nicolás de Bari Embríz G . R .
Hi all thanks for all your answers.

The solution that i found was to add to my ipnat.rules this lines:

map dc1 192.168.10.0/24 - 0/32 portmap tcp/udp auto
map dc1 192.168.10.0/24 - 0/32

and to my rc.conf this :

static_routes=linux
route_linux=192.168.0.0/16 192.168.1.3



regards.



Hi all, I need some help routing or making Nat on a LAN.

I have something like this:


  I N T E R N E T
 -
^ ^
| |
fxp0  public IP   public IP
| |
 FreeBSD server  LINUX server
| |
dc0   192.168.10.1|
dc1   192.168.1.1 ^   192.168.1.3
^ |   ^
| |   |
| |   |
   
  |   Switch/Hub   |
   
   |   |
-- -
   |  LAN  A  |   | LAN  B  |
   | 192.168.10.2-254 |   | 192.168.1.4-100 |
-- -

I have running a FreeBSD server as a gateway and DHCP, the server share
the Internet to all the computers on LAN A (192.168.10.0/24).

The server have 3 network cards:

fxp0 is public IP.
dc0  is the gateway for the LAN A 192.168.10.1.
dc1  has IP 192.168.1.1 ( need help with this ).


Right now i am just using fxp0 and dc0 so any computer on the LAN A
192.168.10.2-254 can have Internet, my ipnat.rules file looks like this:

--
map fxp0 192.168.10.1/24 - 0/32 portmap tcp/udp auto
map fxp0 192.168.10.1/24 - 0/32
--

until that point everything just work OK.

There is another network, I will call it LAN B, this LAN make the same
thing that i am doing with the FreeBSD Server, but instead it uses LINUX,
the m achine have 2 network cars.

eth0 has a public IP.
eth1 is the gateway for the LAN B 192.168.1.3


Both networks are connected to the same switch/hub, but now i need that
the computers of LAN A can see ping computers on LAN B.

If I configure the third nick dc1  on the FreeBSD server to have an IP
on the range of LAN B for example with ip 192.168.1.1, then I can see all
the computers from both LAN's, I can ping, telnet, ssh etc. to both
192.168.10.X and 192.168.1.X. networks standing on the FreeBSD server.


What i want to do is that a computer on LAN A with an IP on the range of 
192.168.10.2-254 can ping, telnet, ssh, etc. to a computer on LAN B
192.168.1.X.

How can i solve this problem, is this is a route or Nat problem ?

There is one more issue, I can't touch the LINUX SERVER I can just be a
client or join the LAN by configure a nic with a IP on the range of
192.168.1.0/24.


I have been trying to fix this with static routes but i am not having luck.


Any help will be apreciated.


regards.


-- 
[EMAIL PROTECTED]
key ID 1EF56FDC


-- 
[EMAIL PROTECTED]
key ID 1EF56FDC


-- 
[EMAIL PROTECTED]
key ID 1EF56FDC
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]