Anonymous | Login | 2024-12-22 00:10 MST |
Main | My View | View Issues | Change Log | Roadmap | Repositories |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0000733 | ClearOS | app-network - Network Settings | public | 2012-08-30 08:28 | 2012-09-18 21:01 | ||||
Reporter | user2 | ||||||||
Assigned To | user2 | ||||||||
Priority | normal | Severity | tweak | Reproducibility | always | ||||
Status | closed | Resolution | fixed | ||||||
Platform | OS | OS Version | |||||||
Product Version | |||||||||
Target Version | 6.3.0 Updates | Fixed in Version | 6.3.0 Updates | ||||||
Summary | 0000733: Improve route detection with point-to-point connections | ||||||||
Description | A typical default route looks like the following (using "ip route"): default via 192.168.55.1 dev ppp0 On point-to-point connections (e.g. PPPoE), the IP address is not default dev eth0 scope link In ClearOS PPPoE, the system is configured to provide the IP address as shown in the first example. However, this IP address is updated a few seconds (around 10 seconds in the lab environment) after the interface is up and running. There are some network scripts that do some post network up changes: - /etc/sysconfig/network-scripts/ifup-post - /etc/sysconfig/network-scripts/ifup-routes On two customer systems, we observed that the IP address was never added to the route. Given the long delay and potential missed IP, the route class should handle these scenarios. | ||||||||
Tags | No tags attached. | ||||||||
Attached Files | |||||||||
Notes | |
(0000557) user2 2012-09-05 15:46 |
SVN revision 4570 |