Bug 696946 - can set ip in non existing range into gateway field w/o any notification
Summary: can set ip in non existing range into gateway field w/o any notification
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: NetworkManager-openswan
Version: 6.1
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Avesh Agarwal
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-15 11:28 UTC by Vladimir Benes
Modified: 2012-06-20 14:24 UTC (History)
4 users (show)

Fixed In Version: NetworkManager-openswan-0.8.0-8.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 14:24:49 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0915 0 normal SHIPPED_LIVE NetworkManager-openswan bug fix update 2012-06-19 20:46:25 UTC

Description Vladimir Benes 2011-04-15 11:28:27 UTC 
Description of problem:
when editing vpn profile I can add 1.1.1.999 and I get timeout then, no notification that IP is not correctly entered.. is it taken as hostname then?


Version-Release number of selected component (if applicable):
NetworkManager-0.8.1-8.el6.i686

How reproducible:
always

Steps to Reproduce:
1.enter 192.168.268.399 into gateway field
2.fill other things and click apply.. 

  
Actual results:
it timeouts silently now

Expected results:
some info should be shown if it looks like IP address but is not valid

Additional info:
Comment 5 errata-xmlrpc 2012-06-20 14:24:49 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0915.html
Note You need to log in before you can comment on or make changes to this bug.