Bug 249179
Summary: | With 2.6.22.1-27.fc7 pppoe does not work correct | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Michael Weidner <micha> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 7 | CC: | chris.brown |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 2.6.22.5-76.fc7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-09-20 13:05:14 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Michael Weidner
2007-07-22 08:25:51 UTC
Can you try it without the bridge, in other words run pppoe directly over eth0 or eth1? This could help narrow down the problem. I have tried it direktly over eth0 (only eth0 activated), seems to work without bridging (no errors in /var/log/message and browsing the web is ok) The config of eth0 was: /etc/sysconfig/network-scripts/ifcfg-eth0: # VIA Technologies, Inc. VT6102 [Rhine-II] DEVICE=eth0 ONBOOT=yes TYPE=Ethernet IPADDR=192.168.0.99 NETMASK=255.255.255.0 IPV6INIT=no BOOTPROTO=none USERCTL=no PEERDNS=no NOZEROCONF=no ppp0 was the same configuartion as above, only change "ETH=eth0" Sorry, I have to switch back because I need the bridge for my LAN to work. Hello Michael, I'm reviewing this bug as part of the kernel bug triage project, an attempt to isolate current bugs in the fedora kernel. http://fedoraproject.org/wiki/KernelBugTriage I am CC'ing myself to this bug and will try and assist you in resolving it if I can. There hasn't been much activity on this bug for a while. Could you tell me if you are still having problems with the latest kernel? If the problem no longer exists then please close this bug or I'll do so in a few days if there is no additional information lodged. Cheers Chris |