: silvertip257
To: Marat Nepomnyashy ; vyatta-users@mailman.vyatta.com
Sent: Sunday, January 13, 2008 6:54 PM
Subject: Re: [Vyatta-users] DHCP pool questions
Why cannot I take addresses out of the beginning of the block like I'd rather
it do? How can I (without rewriting/modifying source code
Yep,
Here's more info on this problem:
https://bugzilla.vyatta.com/show_bug.cgi?id=2411
These are the actual lines that changed:
http://suva.vyatta.com/git/?p=ofr.git;a=commitdiff;h=fc524cf7d59981669cb4400192707d4135c6ff49
The 'if' block on lines 377 to 385 that does the VPN clustering IP
Hi Jesse,
If the system is pingable, then you should be able to access the WebGUI if you
enabled 'service webgui'. Have you tried enabling 'service ssh', and ssh-ing
to the system? For which IPs did that work?
Thanks,
Marat
- Original Message -
From: Jesse Robertson
To:
Hi Todd,
Thanks for the feedback. Two new enhancement requests have been open in the
Vyatta Bugzilla.
1. Display hostname of router when user logs into GUI
Bug 2562 http://bugzilla.vyatta.com/show_bug.cgi?id=2562
2. Add firewall-rule-specific enable/disable configuration parameters
Hi Sergio,
There is a limitation in the VC3 release in that only 'ethX' values can be
specified for DHCP relay interfaces. This is due to overly stringent
validation checks. I just opened a new bug on this:
https://bugzilla.vyatta.com/show_bug.cgi?id=2473
A temporary work-around can be
For more info on this problem, take a look at Bug 2366.
http://bugzilla.vyatta.com/show_bug.cgi?id=2366
The 2.3 release will no longer have this problem.
Now, the problem that Jeff has been experiencing has similar symptoms, but
is actually due to different causes, as Jeff did not install with
Hi Mike,
The vyatta user login credentials are initialized by rtrmgr based on the
information in the configuration file. The rtrmgr may have crashed before it
would have initialized the login credentials. To test this hypothesis, login
as root/vyatta, and do 'ps - ef | grep rtrmgr'.
If the
Hi Egbert,
It sounds like after the package update, lighttpd got restarted with the
default settings in '/etc/lighttpd/lighttpd.conf', and the default
'document-root' settings are pointed to '/var/www' instead of
'/var/www/pages'. The reason why you saw the general login page layout but
not