On 16.08.2012 16:19, Tommy Pham wrote: > On Wed, Aug 15, 2012 at 11:18 PM, Mateusz Marzantowicz > <mmarzantowicz@xxxxxxxxxxx> wrote: >> On 16.08.2012 06:05, Tommy Pham wrote: >>> Hi, >>> >>> According to this >>> https://fedoraproject.org/wiki/Features/NMEnterpriseNetworking, NM now >>> supports bridging in F17. However, I can't seem to get it working >>> properly. Do I need to have network enabled in chkconfig? >>> >>> TIA, >>> Tommy >> What is wrong with your connection? Could you past some more info and >> error messages? >> >> To my knowledge, bridging in F17 is supported in a way that it's >> recognized by NM but can't be changed. You must configure it manually. >> >> >> Mateusz Marzantowicz > Hi Mateusz, > > Thanks for the reply. My bad! Forgot that info. I used the doc [1] > to configured below: > > [root@host network-scripts]# cat ifcfg-br9 > #HWADDR="ae:ed:9a:6a:e0:78" > BOOTPROTO="dhcp" > DEVICE="br9" > NM_CONTROLLED="yes" > ONBOOT="yes" > TYPE="Bridge" > STP="on" > DELAY="0" > #IPADDR="" > #NETMASK="" > #GATEWAY="" > #DNS1="" > #DNS2="" > > [root@host network-scripts]# cat ifcfg-p9p1 > UUID="b227ea83-c7be-4df1-b9d3-f9ff9381c56d" > #HWADDR="00:25:90:4C:E0:98" > BOOTPROTO="none" > BRIDGE="br9" > DEVICE="p9p1" > NM_CONTROLLED="yes" > ONBOOT="yes" > > [root@host network-scripts]# cat ifcfg-br10 > #HWADDR="c2:ee:cb:b3:65:04" > BOOTPROTO="none" > DEVICE="br10" > NM_CONTROLLED="yes" > ONBOOT="yes" > TYPE="Bridge" > STP="on" > DELAY="0" > IPADDR="192.168.0.254" > NETMASK="255.255.255.0" > GATEWAY="192.168.0.1" > DNS1="192.168.0.1" > > [root@host network-scripts]# cat ifcfg-p10p1 > UUID="b227ea83-c7be-4df1-b9d3-f9ff9381c56d" > #HWADDR="00:25:90:4C:E0:99" > BOOTPROTO="none" > BRIDGE="br10" > DEVICE="p10p1" > NM_CONTROLLED="yes" > ONBOOT="yes" > > [root@host ~]# ifconfig > lo: flags=73<UP,LOOPBACK,RUNNING> mtu 16436 > inet 127.0.0.1 netmask 255.0.0.0 > inet6 ::1 prefixlen 128 scopeid 0x10<host> > loop txqueuelen 0 (Local Loopback) > RX packets 4 bytes 420 (420.0 B) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 4 bytes 420 (420.0 B) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > p10p1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 > ether 00:25:90:4c:e0:99 txqueuelen 1000 (Ethernet) > RX packets 0 bytes 0 (0.0 B) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 0 bytes 0 (0.0 B) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > device interrupt 18 memory 0xfeae0000-feb00000 > > p9p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > inet 10.0.0.124 netmask 255.255.254.0 broadcast 10.0.0.255 > inet6 fe80::225:90ff:fe4c:e098 prefixlen 64 scopeid 0x20<link> > ether 00:25:90:4c:e0:98 txqueuelen 1000 (Ethernet) > RX packets 970 bytes 123838 (120.9 KiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 119 bytes 17099 (16.6 KiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > device interrupt 17 memory 0xfe9e0000-fea00000 > > > [root@host network-scripts]# chkconfig|grep -i network > > Note: This output shows SysV services only and does not include native > systemd services. SysV configuration data might be overridden by native > systemd configuration. > > network 0:off 1:off 2:off 3:off 4:off 5:off 6:off > > > [root@host network-scripts]# /etc/init.d/network status > Configured devices: > lo br9 br10 p9p1 p10p1 > Currently active devices: > lo p9p1 p10p1 > > [root@host network-scripts]# systemctl status NetworkManager.service > NetworkManager.service - Network Manager > Loaded: loaded > (/usr/lib/systemd/system/NetworkManager.service; enabled) > Active: active (running) since Thu, 16 Aug 2012 07:01:16 > -0700; 8min ago > Main PID: 603 (NetworkManager) > CGroup: name=systemd:/system/NetworkManager.service > â 603 /usr/sbin/NetworkManager --no-daemon > â 898 /sbin/dhclient -d -4 -sf > /usr/libexec/nm-dhcp-client.action -pf /var/run/dhclient-p9p1.pid -lf > /var/lib/dhclient/dhclient-ee1e0578-545b-4efd-b472-69820d17fe22-p9p1.lease > -cf /va... > > Aug 16 07:01:20 host.domain.local NetworkManager[603]: <info> > Activation (p9p1) Stage 5 of 5 (IPv4 Configure Commit) scheduled... > Aug 16 07:01:20 host.domain.local NetworkManager[603]: <info> > Activation (p9p1) Stage 5 of 5 (IPv4 Commit) started... > Aug 16 07:01:21 host.domain.local NetworkManager[603]: <info> (p9p1): > device state change: ip-config -> activated (reason 'none') [70 100 0] > Aug 16 07:01:21 host.domain.local NetworkManager[603]: <info> Policy > set 'Wired connection 1' (p9p1) as default for IPv4 routing and DNS. > Aug 16 07:01:21 host.domain.local NetworkManager[603]: <info> > Activation (p9p1) successful, device activated. > Aug 16 07:01:21 host.domain.local NetworkManager[603]: <info> > Activation (p9p1) Stage 5 of 5 (IPv4 Commit) complete. > Aug 16 07:01:39 host.domain.local NetworkManager[603]: <info> (p9p1): > IP6 addrconf timed out or failed. > Aug 16 07:01:39 host.domain.local NetworkManager[603]: <info> > Activation (p9p1) Stage 4 of 5 (IPv6 Configure Timeout) scheduled... > Aug 16 07:01:39 host.domain.local NetworkManager[603]: <info> > Activation (p9p1) Stage 4 of 5 (IPv6 Configure Timeout) started... > Aug 16 07:01:39 host.domain.local NetworkManager[603]: <info> > Activation (p9p1) Stage 4 of 5 (IPv6 Configure Timeout) complete. > > > When I have /etc/init.d/network enabled and running, I got this for ifconfig > > br9: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 > ether 56:27:4b:59:5b:4a txqueuelen 0 (Ethernet) > RX packets 0 bytes 0 (0.0 B) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 0 bytes 0 (0.0 B) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > br10: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 > inet 192.168.0.254 netmask 255.255.255.0 broadcast 192.168.0.255 > ether 46:4e:5f:50:1f:03 txqueuelen 0 (Ethernet) > RX packets 0 bytes 0 (0.0 B) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 0 bytes 0 (0.0 B) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > lo: flags=73<UP,LOOPBACK,RUNNING> mtu 16436 > inet 127.0.0.1 netmask 255.0.0.0 > inet6 ::1 prefixlen 128 scopeid 0x10<host> > loop txqueuelen 0 (Local Loopback) > RX packets 85 bytes 8935 (8.7 KiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 85 bytes 8935 (8.7 KiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > p10p1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 > ether 00:25:90:4c:e0:99 txqueuelen 1000 (Ethernet) > RX packets 0 bytes 0 (0.0 B) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 0 bytes 0 (0.0 B) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > device interrupt 18 memory 0xfeae0000-feb00000 > > p9p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > inet 10.0.0.124 netmask 255.255.254.0 broadcast 10.0.0.255 > inet6 fe80::225:90ff:fe4c:e098 prefixlen 64 scopeid 0x20<link> > ether 00:25:90:4c:e0:98 txqueuelen 1000 (Ethernet) > RX packets 395 bytes 53556 (52.3 KiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 43 bytes 8757 (8.5 KiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > device interrupt 17 memory 0xfe9e0000-fea00000 > > > However, when I access the system via ssh, it doesn't go beyond the > initial "login as:". > > Thanks, > Tommy > > [1] http://docs.fedoraproject.org/en-US/Fedora/15/html/Deployment_Guide/s1-networkscripts-interfaces.html Two possible problems came to my mind: 1) route configuration (check route -n command) 2) ssh configuration But first why do you need two bridges (br9 and br10? Maybe one is enough? (this is only a side question) I think that you should also uncomment HWADDR in one of your bridges configuration file. Mateusz Marzantowicz -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
