| Anonymous | Login | 2024-12-22 00:08 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 | ||||
| 0000204 | ClearOS | app-multiwan - Multi-WAN | public | 2010-10-24 09:00 | 2010-12-22 08:55 | ||||
| Reporter | Vejlefjordskolen | ||||||||
| Assigned To | |||||||||
| Priority | normal | Severity | minor | Reproducibility | always | ||||
| Status | closed | Resolution | no change required | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | 5.2-SP1 | ||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0000204: One interface is reported as down, even though it is fine | ||||||||
| Description | Hi, We've had some problems in the past with our multi-WAN setup, but have managed to work around them so far. Now we've come across another one though. We have 4 external interfaces: eth0, eth1, eth2 and eth3. We did a completely clean installation of ClearOS 5.2-SP1 this weekend, but now eth1 won't report as up on the multi-WAN page. It works fine until syswatch brings it down, i.e. it can be pinged from the Internet, but syswatch doesn't seem to be able to ping out through it for some reason. It's not a problem with out ISP on that line, as we tried moving the cables around, and eth2 can connect just fine with the line, while eth1 then has the same problem with eth2's line, so it's something specific to eth1. I hope you can understand me, as I'm having a hard time explaining the problem. Thanks a lot, - Marcus | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
 Relationships |
|
 Relationships |
|
Notes |
|
|
(0000308) Vejlefjordskolen (reporter) 2010-10-29 00:04 |
I just thought I'd give an overview of what we've tried so far. Deleting the interface and recreating it in webconfig. Comparing all mentions of eth1 with eth0 and eth2 in /etc. Comparing /etc from our old 5.1 install with the new one. Bringing interface down and up manually using ifconfig, which allowed the interface to be pinged from the Internet. None of these things helped us change the interface status on the Multi-WAN page from Offline. We still haven't been able to find any reason why eth1 shouldn't work. |
|
(0000322) Vejlefjordskolen (reporter) 2010-12-21 03:44 |
Please remove this issue. It is based on false information that I had at the time. I've just been able to physically get to the box and what people haven't told me is that the DSL light is not showing in the modem, so ClearOS is doing its job. I'm very sorry for this, but I don't actually have physical access to the box very often, so I rely on the information other people give me. I hope you haven't spent any time researching this issue. |
|
(0000324) timb80 (developer) 2010-12-22 08:54 |
Glad you found the problem! - i'll mark the issue as closed |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2010-10-24 09:00 | Vejlefjordskolen | New Issue | |
| 2010-10-25 13:11 | user2 | Severity | major => minor |
| 2010-10-25 13:11 | user2 | Status | new => acknowledged |
| 2010-10-29 00:04 | Vejlefjordskolen | Note Added: 0000308 | |
| 2010-12-21 03:44 | Vejlefjordskolen | Note Added: 0000322 | |
| 2010-12-22 08:54 | timb80 | Note Added: 0000324 | |
| 2010-12-22 08:55 | timb80 | Status | acknowledged => closed |
| 2010-12-22 08:55 | timb80 | Resolution | open => no change required |
|
Issue History |