On Tue, 2008-12-09 at 15:48 +, Eric Weidner wrote:
Address (IP subnet on the other side of the VPN): 192.168.1.0
Prefix: 32 (32 gives you access to the entire range of IP's)
Gateway: 0.0.0.0
Metric: 0 (not sure what this does)
Well, that'd surprise me if 32 was correct.
Using 32 as
If you create/edit a new VPN connection in nm-applet's Edit
Connections, there is the IPv4 Settings tab, at the bottom of which
you see a Routes... button.
Here, you just enter your subnets, the prefix length and 0.0.0.0 as
Gateway to that subnet.
The option has not been removed, it's called
In answer to what Balaij describes in his use case 3
(inhttps://bugs.launchpad.net/ubuntu/+source/vpnc/+bug/124663/comments/23):
That is precisely what enterprise networks don't want to happen, because
it's a security nightmare. If I had a user trying this on my employer's
remote access VPN, I'd
Matthias, thanks for a dpd-less vpnc version.
It might not actually needed anymore - I just upgraded to 8.10 and I am
successfully running the vpnc version from the normal repos now. I am
making use of the Disable DPD checkbox that was implemented according
to
I suffered a similar problem, see my question linked to this Bug or
https://answers.launchpad.net/ubuntu/+question/42403
On ubuntuforums.org (http://ubuntuforums.org/redirect.php?t=772107), had
found suggestions that dmraid was somehow conflicting with initrd
accessing drives via
Installing Chris' .debs
(https://bugs.launchpad.net/ubuntu/+source/vpnc/+bug/206673/comments/4 ,
see above) did help with Hardy on my HP Compaq 6910p.
I am now running network-manager-vpnc with his version of vpnc
underneath, and the VPN connection to my PIX501 (which does not support
DPD) stays
See comment No. 4 in Bug #206673
https://bugs.launchpad.net/ubuntu/+source/vpnc/+bug/206673/comments/4
Chris has made .debs available here on launchpad for a version of vpnc
that has the DPD timeout defaulted to 0 (i.e. disabled). I could add
them easily on the 8.04 install on my HP Compaq
Both my 7.04 and 7.10 installations suffered from this same problem:
stuck on the Jamendo Splash screen. To implement the patch as outlined
above, I had to:
- delete /usr/lib/rhythmbox/plugins/jamendo/JamendoSource.pyc
- patch JamendoSpurce.py as outlined above (the line numer on 7.04 was
** Description changed:
WIth gutsy (live CD as well as on upgraded install from Feisty),
rhythmbox does not load the UPnP sharing plugin.
python-louie is installed (Bug #132992), but running rhythmbox -d from
commandline reveals this:
(19:05:15) [0x80fb408]
Public bug reported:
WIth gutsy (live CD as well as on upgraded install from Feisty),
rhythmbox does not load the UPnP sharing plugin.
python-louie is installed (Bug #132992), but running rhythmbox -d from
commandline reveals this:
(19:05:15) [0x80fb408] [rb_plugins_engine_load]
** Description changed:
WIth gutsy (live CD as well as on upgraded install from Feisty),
rhythmbox does not load the UPnP sharing plugin.
python-louie is installed (Bug #132992), but running rhythmbox -d from
commandline reveals this:
(19:05:15) [0x80fb408]
This bug may be closed. PEBKAC!
After a lot of testing, and kismet'ing my own connection attempts, I
discovered that macchanger did no longer successfully overwrite ath0's
MAC address. Therefore it kep being refused by the AP which has a MAC
access list.
regards
Marc
** Changed in:
Sounds similar to bug #56427:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
ati/+bug/56427
Does using the x.org executable binary from Debain help?
best regards
Marc
--
PCI video card not addressed correctly for X
https://bugs.launchpad.net/bugs/103605
You received this bug
There's a workaround:
Replacing /usr/bin/Xorg with the one from Debian Testing's package
xserver-xorg-core makes X.org work without further changes to any other
file.
--
Fatal crash on X startup on Ultra 10
https://launchpad.net/bugs/56427
--
ubuntu-bugs mailing list
Similar on my U5, it's just that X.org won't start.
See Thread from Ubuntu Forums:
http://www.ubuntuforums.org/showthread.php?t=307406
This might be related to
Bug #392312 on bugs.debian.org: http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=392312
respectively
Bug #8020 of
Public bug reported:
Binary package hint: network-manager
Since upgrading to Ubuntu 6.10, NetworkManager does no longer fallback
to zerconf addressing (self-assigned IP addressing from the
169.254.0.0/16 range, as per RFC3330 and RFC3927) for the WLAN NIC. This
although package zeroconf is
** Description changed:
Binary package hint: network-manager
+
+ [Edit: preparing more detailed information with syslog excerpts etc]
Since upgrading to Ubuntu 6.10, NetworkManager does no longer fallback
to zerconf addressing (self-assigned IP addressing from the
169.254.0.0/16
** Description changed:
Binary package hint: network-manager
- [Edit: preparing more detailed information with syslog excerpts etc]
+ Since upgrading to Ubuntu 6.10, NetworkManager does no longer fallback
+ to zerconf addressing (self-assigned IP addressing from the
+ 169.254.0.0/16 range,
** Attachment added: Syslog excerpt of a failing fallback to zeroconf on a
wlan interface
http://librarian.launchpad.net/5068594/syslog%20ath0
--
can't join non-DHCP WLANs, no fallback to zeroconf addressing
https://launchpad.net/bugs/71748
--
ubuntu-bugs mailing list
19 matches
Mail list logo
