Booting Error with Mondo While Restoring : kernel 2.4.19 + XFS

2002-09-25 Thread axacheng

Hello there, 

  I got some booting errors while trying to restore a system with Mondo
1.41.1-1 which consists of Debian Woody, kernel 2.4.19 and SGI Official XFS
kernel patch. On my Woody, the system works fine with these components
and no error occurred while mondoarchiving. But when I try to restore
it, the booting process says like this:

snip
NET4: Unix Domain Socket1.0/SMP for Linux NET4.0
ds: no socket drivers loaded!
RAMDISK: Compressed image found at block 0
Freeing inited memory: 273K freed
VFS: Monted root (ext2 filesystem) readonly
Freeing unused kernel memory: 124K freed
Monting /tmp/tmpfs...mkdir: Cannot create directory 'tmp/tmpfs': Read-only filesystem
/sbin/init: cannot create /tmp/mondo-restore.log: Read-only file system
Fatal error! Failed. UPGRADE YOUT RAM! Please! Dude, your computer is dying of thirst 
over here...
/sbin/logIt: cannot create /tmp/mondo-restore.log: Read-only file system

  I'm sure that I have my kernel 2.4.19 compiled with all necessary
functions for Mondo. Then I tried another archive, 2.4.18 + Debian official
XFS patch, everything goes well.
  I doubt it's a matter of the kernel, but I cannot find any suitable
answer for my situation, thus I come for a kind help. Any feedback or
comment is appreciated.

Thanks, 
Anderson
-- 

--
Anderson-1.0 is now available!

Email   : [EMAIL PROTECTED]
ICQ : 161984362
PGP Key : http://www.ezplay.tv/~anderson.fang/AndersonEZplay.gpg
--



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




DNS PROBLEMS

2002-09-25 Thread Ángel Carrasco



Hi all:

I have three dns server. They are bind compiling 
with ldap support. 


They are compiled with the same configuration and 
uses the same file configuration.

In my office, I can resolve with the three without 
problem. But Out my office, I can resolve only with two of them.
I think the problem was the firewall but I remove 
firewall and the problems continuous.


;  DiG 9.2.1  @IP 
domain.es
;; global options: printcmd
;; connection timed out; no servers could be 
reached


I type in named.conf allow-query {any;};. 



Can you help me please?


Thanks



Ángel


mod_auth_ldap and Umlaute

2002-09-25 Thread Andreas Rabus


Hi,

the Version 1.4-3 of libapache-mod-ldap seems to have some Problems with
umlauts üöä and so on.
It cuts the login names at the postion of the first umlaut...

Are there any workarounds or packages with do ldap auth for apache with
umlauts?

Thanks in advance,

ar




Andreas Rabus
entity38 AG

Isartalstr. 44a/Rgb.
80469 München

Tel +49 (89) 286772-27
Fax +49 (89) 286772-21
ISDN +49 (89) 286772-30
ICQ #132675697
GPG 3A0F 7E46 5286 E365 E102 0DB6 FCA9 6E6F 361B F7B3  

[EMAIL PROTECTED]
www.entity38.de
 


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




understanding Routing Cisco vs. Linux

2002-09-25 Thread Thedore Knab

Currently, I am creating a simple Linux Router with CQB and Iptables. 

The machine I have only has 2 interfaces.

We have the following devices on our network:

1 Cisco Catalyst connecting 16 Class C Networks 
1 Cisco Router Routing packets to the inside

The Catalyst uses VLans for our entire network.

It appears that the Catalyst is doing routing for the virtual networks
as it should. But, I am scratching my head over how the Catalyst 
handles incoming and outgoing connections. 

Traffic seems to flow differently depending on
its direction. 

Do I need to worry about how the VLAN handles packets
when I install the Linux Router ?

Also does the following diagram look like it will work  ?

Currently the route is - 

Trunk
  |
209.243.32.65 
  |
  |
  | 192.146.226.1 (Catalyst Routing of Vlans)
  [Catalyst] ---209.243.32.0/20 
 ---192.146.226.0/24


I figure that this may work it is my first attempt at using iproute:

Trunk
|
209.243.32.65
|
[Linux Router] 209.243.32.66 eth0
   209.243.32.67 eth1

ip route add 209.243.32.65 dev eth0  
ip route add 192.146.226.1 dev eth1
ip route add 192.146.226.0/24 dev eth1
ip route add 209.243.33.0/24 dev eth1
ip route add 209.243.34.0/24 dev eth1
...


| 
| 192.146.226.1 (Catalyst Internal Routing)
[Catalyst] 
---209.243.32.0/20
---192.146.226.0/24

http://www.shorewall.net/traffic_shaping.htm


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Booting Error with Mondo While Restoring : kernel 2.4.19 + XFS

2002-09-25 Thread axacheng
Hello there, 

  I got some booting errors while trying to restore a system with Mondo
1.41.1-1 which consists of Debian Woody, kernel 2.4.19 and SGI Official XFS
kernel patch. On my Woody, the system works fine with these components
and no error occurred while mondoarchiving. But when I try to restore
it, the booting process says like this:

snip
NET4: Unix Domain Socket1.0/SMP for Linux NET4.0
ds: no socket drivers loaded!
RAMDISK: Compressed image found at block 0
Freeing inited memory: 273K freed
VFS: Monted root (ext2 filesystem) readonly
Freeing unused kernel memory: 124K freed
Monting /tmp/tmpfs...mkdir: Cannot create directory 'tmp/tmpfs': Read-only 
filesystem
/sbin/init: cannot create /tmp/mondo-restore.log: Read-only file system
Fatal error! Failed. UPGRADE YOUT RAM! Please! Dude, your computer is dying of 
thirst over here...
/sbin/logIt: cannot create /tmp/mondo-restore.log: Read-only file system

  I'm sure that I have my kernel 2.4.19 compiled with all necessary
functions for Mondo. Then I tried another archive, 2.4.18 + Debian official
XFS patch, everything goes well.
  I doubt it's a matter of the kernel, but I cannot find any suitable
answer for my situation, thus I come for a kind help. Any feedback or
comment is appreciated.

Thanks, 
Anderson
-- 

--
Anderson-1.0 is now available!

Email   : [EMAIL PROTECTED]
ICQ : 161984362
PGP Key : http://www.ezplay.tv/~anderson.fang/AndersonEZplay.gpg
--





DNS PROBLEMS

2002-09-25 Thread Ángel Carrasco



Hi all:

I have three dns server. They are bind compiling 
with ldap support. 


They are compiled with the same configuration and 
uses the same file configuration.

In my office, I can resolve with the three without 
problem. But Out my office, I can resolve only with two of them.
I think the problem was the firewall but I remove 
firewall and the problems continuous.


;  DiG 9.2.1  @IP 
domain.es
;; global options: printcmd
;; connection timed out; no servers could be 
reached


I type in named.conf allow-query {any;};. 



Can you help me please?


Thanks



Ángel


mod_auth_ldap and Umlaute

2002-09-25 Thread Andreas Rabus

Hi,

the Version 1.4-3 of libapache-mod-ldap seems to have some Problems with
umlauts üöä and so on.
It cuts the login names at the postion of the first umlaut...

Are there any workarounds or packages with do ldap auth for apache with
umlauts?

Thanks in advance,

ar




Andreas Rabus
entity38 AG

Isartalstr. 44a/Rgb.
80469 München

Tel +49 (89) 286772-27
Fax +49 (89) 286772-21
ISDN +49 (89) 286772-30
ICQ #132675697
GPG 3A0F 7E46 5286 E365 E102 0DB6 FCA9 6E6F 361B F7B3  

[EMAIL PROTECTED]
www.entity38.de
 




understanding Routing Cisco vs. Linux

2002-09-25 Thread Thedore Knab
Currently, I am creating a simple Linux Router with CQB and Iptables. 

The machine I have only has 2 interfaces.

We have the following devices on our network:

1 Cisco Catalyst connecting 16 Class C Networks 
1 Cisco Router Routing packets to the inside

The Catalyst uses VLans for our entire network.

It appears that the Catalyst is doing routing for the virtual networks
as it should. But, I am scratching my head over how the Catalyst 
handles incoming and outgoing connections. 

Traffic seems to flow differently depending on
its direction. 

Do I need to worry about how the VLAN handles packets
when I install the Linux Router ?

Also does the following diagram look like it will work  ?

Currently the route is - 

Trunk
  |
209.243.32.65 
  |
  |
  | 192.146.226.1 (Catalyst Routing of Vlans)
  [Catalyst] ---209.243.32.0/20 
 ---192.146.226.0/24


I figure that this may work it is my first attempt at using iproute:

Trunk
|
209.243.32.65
|
[Linux Router] 209.243.32.66 eth0
   209.243.32.67 eth1

ip route add 209.243.32.65 dev eth0  
ip route add 192.146.226.1 dev eth1
ip route add 192.146.226.0/24 dev eth1
ip route add 209.243.33.0/24 dev eth1
ip route add 209.243.34.0/24 dev eth1
...


| 
| 192.146.226.1 (Catalyst Internal Routing)
[Catalyst] 
---209.243.32.0/20
---192.146.226.0/24

http://www.shorewall.net/traffic_shaping.htm