|
Bugzilla – Full Text Bug Listing |
| Summary: | cannot "unblock" ssh port in firewall proposal during installation; firewall gets reactivated automatically | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Forgotten User ZhJd0F0L3x <forgotten_ZhJd0F0L3x> |
| Component: | Installation | Assignee: | Lukas Ocilka <locilka> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | mvidner |
| Version: | Alpha 4 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Component Test | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Bug Depends on: | |||
| Bug Blocks: | 140732 | ||
| Attachments: | /var/log/YaST2 | ||
|
Description
Forgotten User ZhJd0F0L3x
2006-01-04 13:23:32 UTC
Created attachment 61948 [details]
/var/log/YaST2
from log: Proposal based on configuration: Dial-up interfaces: [], Other: [] It seems that you are using a Network Manager which caused that problem. I've done the Network Manager support just today, so you could find it in the next alpha-beta version. Network Manager doesn't report network interfaces, non-existent interface couldn't have been mentioned in the firewall configuration. So, all in all it was impossible to enable SSH port on non-existent interface. So, this is already fixed ... I hope so :) IIRC, i first disabled the firewall (after trying to unblock ssh), then disabled the network manager and then configured the interfaces. After that the firewall was enabled again. Short: i'll retry once the next snapshot is ready and if it does not work, i'll bug you again :) Thanks Ups, I'm afraid that playing with firewall (enable/disable) plus the same with ssh and also network manager together might be a bit buggy. I have to think about it more tomorrow and test it again. This issue tend to be a bit bothering and confusing :( *** Bug 141239 has been marked as a duplicate of this bug. *** *** Bug 197933 has been marked as a duplicate of this bug. *** Ignore comment #6. There was a typo in the bug number. It is NOT a duplicate of 197933. |