Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - VitRom

Pages: [1] 2 3
1
Thanks for a table tip!

Samba must listen only through internal interfaces...
Definitely it must! :)
Quote
So I think if you reach from the internal address, you should get to it.
JFYI (and possible debugging):

"Samba inaccessible from a lan" means that I'm able to see eBox Samba server but can't open it nor shares for browsing when subnets are equal. But eBox Samba still in the computers list and eBox replies on ping. Looks like resources listing and opening didn't works but smb advertizing still working. And immediately after second iface moved into a different subnet or simply swithed off then shares browsing fully restores and resources start opens. And within a pair of seconds after 2nd iface moved into the same subnet and changes are saved any attempts to browse share list ends with "address (or path?) not found" Windows err msg but eBox still replies on ping. I've repeated this a few dozens of times.

IMHO it looks like a wrong generation of FW rules or Samba bindings.

2
Is this a clean install of 1.4, so that the console GUI is installed?
Wow! :) I'm on 1.4-1 without X. Where this funny thing is?

Upd
Or did U mean not "console" but a Xwindow-based GUI with Firefox?

3
you have to set the route rule manually by using ip rule command
Excuse me but I misunderstood how exactly this command should b said (for example what "table" should it refers to) and where is the best place for it (to avoid rewrites by eBox).

Damn! When both ifaces are in one net then samba completely inacessible from lan! So one more (related) question:
- Where is samba bindings should b placed best (to avoid b rewriten like route rule too) -- in a .conf or somewhere in templates?


this configuration is out of a normal eBox configuration
It seems almost everything exept exact copying of "Best setup" config from docs (and 99% of what can b done in a "plain" system without any dances) are "out of a normal" :)

4
Hi sixstone,

I've reached this point a long time ago but there is one small troublem:

regardless of gateway "binding" on a Network/Gateways page all non-local traffic goes through the "main", "internal" iface :(

As I've said above both ifaces are in one subnet.
If I didn't mark one of them as "ext" then I can't use many of a features that I need just because eBox claims abt "no ext... etc".
If I do a "generic" setup -- one static int, one static ext, nat disabled -- and manually binds an one and only default gate onto ext then it didn't work as expected and all(!) traffic routes through int.

Just a picture:

interfaces
eth0 192.168.1.200/24
eth1 192.168.1.100/24
gateways
192.168.1.1 on eth1 [v]default

then I run ping to web and unplug eth1 cable but a ping still flows w/o any interruptions

5
Up!

This wasn't a joke question. I'm not completely new in a xNIXes but eBox makes me stuck on a simplest things.

Seems only devels knows what result from a chain of Linux configs wrapped with Debian scripts wrapped with Perl objects wrapped with eBox scripts can b :) And I don't wanna reinstall everything again after a few dozens reinstalls (not counting "small") already done :(

6
Installation and Upgrades / Re: eBox and mgetty -- is this possible?
« on: April 29, 2010, 04:44:26 pm »
Up!

This wasn't a joke question. I'm not completely new in a xNIXes but eBox makes me stuck on a simplest things.

Seems only devels knows what result from a chain of Linux configs wrapped with Debian scripts wrapped with Perl objects wrapped with eBox scripts can b :) And I don't wanna reinstall everything again after a few dozens reinstalls (not counting "small") already done :(

7
Up!

This wasn't a joke question. I'm not completely new in a xNIXes but eBox makes me stuck on a simplest things.

Seems only devels knows what result from a chain of Linux configs wrapped with Debian scripts wrapped with Perl objects wrapped with eBox scripts can b :) And I don't wanna reinstall everything again after a few dozens reinstalls (not counting "small") already done :(

8
sixstone, thank U 4 answer and sorry I'm late.

Am I right that U mean something aka "static lease"?

9
Installation and Upgrades / Re: MANUAL config tuning -- how 2 do?
« on: April 29, 2010, 03:17:00 pm »
Quote
eBox will overwrite the manual changes in files managed by eBox without asking the user again
And how this "asking the user" should look like?

10
Subj?

How to access to samba shares (or eBox samba itself for shares list) without creation of users, anonymously?

How to use a built-in user(s) -- eboxadmin, root or setup-time-created admin user -- for a samba access?

How to read a mail that's created by a non-eBox (standard or 3rd-party) daemons (not an ebox monitors) and addressed to a root and/or admin user?

11
I have to tell you again that our first aim with ebox-asterisk is integrating VoIP with eBox
Well, well, all right, OK.

So what U've said abt a reason to use something instead another something that can do the same things and also do more and require less resources? ;)

12
Installation and Upgrades / eBox and mgetty -- is this possible?
« on: April 21, 2010, 04:59:24 pm »
I need a simplest fax "receiver" that only recieves faxes and places them into one dir. Previously it was done with mgetty-fax and some simple scripts for bitmap conversions and datetime-based naming.

Is this possible in eBox (1.4-1)? Did eBox plays with (and overwrites) tty configs an related things?

13
Installation and Upgrades / Re: eBox 1.4 not seeing system updates?
« on: April 21, 2010, 04:48:49 pm »
Seems fix above works, but eBox makes me fear everything :(

I've grabbed a zip from changeset/17209 above, stopped ebox and replaced files then rebooted and after ebox-software was finished (apt sources still untouched from setup time) on the Software/System Updates page I can see a bunch of updates. Wow! Cool! Yahoo!

Btw when I've said init.d/ebox stop from ssh(!) my ssh(!) -- "core" component -- session hangs and ebox drops out from net. WTF?!

Well, seems all right and I've got updates list. But one of the updates is a
Quote
linux-server | Complete Linux kernel on Server Equipment. | 2.6.24.27.29
At the same time more then once on this forum I've seen notes like
Quote
pls be sure that u are uses the ...kernel-ebox (or ...server-ebox, or something like that) version and not a generic one

So here is very simple question:
will installing all updates from this page kills my eBox?

14
Subj?

I mean a full set of gateway/proxy/filter/shaper/etc features on a box with two interfaces, one of them marked "external", but both in a one ip subnet with a standalone adsl gateway. This way clients can access to Inet even without eBox, but via eBox by default.

In the other words: 192.168.1.0/24 net, 192.168.1.1 adsl gateway with own nat, eBox with 192.168.1.2 and 192.168.1.22 ifaces, eBox dhcp gives to clients .22 as "default gate", also all clients set up with a manual gateway .1 with very high metric

When both ifaces are "internal" then a proto filter and many other things claims for "impossible! no ext iface" and a similar trash. When one iface marked as "ext" then at least samba networking goes into shit because a firewall DROPs netbios packets on both ifaces :(

How to make a thing that's "generic" for many other distros works?

15
well, I have 1.4-1 with all above 0.95.3...hardy2.3 too (updated manually via aptitude, mark manual, update) and GUI shows "updated at (some hours ago) succesfully" everytime I look on it and everyday. But I still see a LibClam warning "*** Engine is outdated ***" on every boot. What's wrong at this time?

Pages: [1] 2 3