Undo bridged connection and IPv6

linuxdave · November 20, 2009, 3:42am

When I installed 11.2 I allowed the installer to auto configure hardware and obviously had the ‘enable IPv6’ checkbox checked so I have /dev/br0 and /dev/eth0 where eth0 gets the IPv6 address and br0 gets the IPv4 address.

My machine is behind a router so it’s local subnet of a 192.168.xxx.xxx. Is there really a need to have IPv6 enabled on a LAN and how can I disable it and remove the bridged connection?

Also, the YaST manager says that the network card isn’t configured, but it’s only reading from eth0 and br0 is nowhere to be found in YaST.

Thanks

buckesfeld · November 20, 2009, 2:35pm

linuxdave,

Yast, Network Devices, Network Settings.
Global Options, uncheck IPV6. The bonding device should be under “Overview”.

HTH
Uwe

linuxdave · November 21, 2009, 2:59pm

Ok so I went into YaST. Curiously the ethernet device was listed as ‘Not Configured’. So after adding some basic config options the Global Options tab appeared and I unchecked IPv6.

This did NOT remove the bridged connection which is listed as br0.

After making the changes YaST said I needed to reboot, and so I did. After rebooting I lost all Internet connectivity and have the following:
suse:~ # ifconfig
br0 Link encap:Ethernet HWaddr 00:19:21:C1:66:46
inet addr:192.168.2.32 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::219:21ff:fec1:6646/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:17 errors:0 dropped:0 overruns:0 frame:0
TX packets:30 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1348 (1.3 Kb) TX bytes:7587 (7.4 Kb)

eth0 Link encap:Ethernet HWaddr 00:19:21:C1:66:46
inet addr:192.168.2.32 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::219:21ff:fec1:6646/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:375 errors:0 dropped:0 overruns:0 frame:0
TX packets:628 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:37307 (36.4 Kb) TX bytes:85495 (83.4 Kb)
Interrupt:20 Base address:0x8c00

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:329 errors:0 dropped:0 overruns:0 frame:0
TX packets:329 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:28587 (27.9 Kb) TX bytes:28587 (27.9 Kb)

So I took down br0 (which also took down eth0) and then brought only eth0 back up using:
suse:~ # ifdown br0
br0
suse:~ # ifup eth0
eth0 device: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
DHCP4 client is already running on eth0
IP address: 192.168.2.32/24

The message said that eth0 was already running but I could not get any Internet connectivity until I used ifup.

So I’m still back to asking the same question:

How can I get rid of the bridged connection (/dev/br0)?

Thanks

linuxdave · November 22, 2009, 5:26pm

Does anyone have any ideas on this? I really don’t want to have to manually take down br0 (the bridged connection) and ifup eth0 every time I boot the machine.

Maybe I should just wipe the drive and start over and not allow the installer to automagically configure?

Should this post go in networking maybe?

buckesfeld · November 22, 2009, 5:51pm

linuxdave wrote, On 11/21/2009 03:06 PM:
> This did NOT remove the bridged connection which is listed as br0.

I find this rather odd.
Do you have a configuration device for the bodning device under /etc/sysconfig/network?
If so, move it away and restart the network.

Uwe

linuxdave · November 23, 2009, 2:44am

Odd or not it is what it is and yes there was still a config file for the bridged connection:


ls -l
-rw-r--r-- 1 root root 10811 2009-11-21 08:50 config
-rw-r--r-- 1 root root  6267 2009-11-15 02:08 dhcp
-rw-r--r-- 1 root root   213 2009-11-21 08:29 ifcfg-br0
-rw-r--r-- 1 root root   169 2009-11-21 08:29 ifcfg-eth0
-rw-r--r-- 1 root root   174 2009-10-23 20:50 ifcfg-lo
-rw-r--r-- 1 root root 27402 2009-10-23 20:50 ifcfg.template
drwxr-xr-x 2 root root  4096 2009-11-15 01:53 if-down.d
-rw-r--r-- 1 root root   239 2009-10-23 20:50 ifroute-lo
drwxr-xr-x 2 root root  4096 2009-11-15 01:53 if-up.d
drwx------ 2 root root  4096 2009-10-23 20:47 providers
-rw-r--r-- 1 root root    28 2009-11-21 08:49 routes
drwxr-xr-x 2 root root  4096 2009-11-22 19:01 scripts

Moved to ifcfg-br0.original and moved it out of /etc/sysconfig/network
I think that will fix it. Possibly a bug in the gui applet to configure network devices?

I’m still trying to get used to the new gui apps to manage all this stuff, and coming from Red Hat/Fedora and Ubuntu they seem quite foreign and (honestly) don’t appear to work quite as well. YaST has left me unimpressed so far. I had an issue with it not being able to retrieve info from one of the repositories (and thereby bombing out), and just now noticed yet another repository is causing it grief, but that’s another topic and thread.

I have other issues too, but not yet sure if they’re related to KDE 4 or if it’s an openSUSE issue. Still I’m not going to revert back to Fedora or Ubuntu just yet.

Thank you Mr. Buckesfeld for your help!

mtbarr64 · November 24, 2009, 5:07pm

You can ping your router, right? Ping 192.168.0.1 or ping 192.168.1.1.

I found I could get to my router but not the internet. I had to add the DNS server IP addresses in the Yast Network configuration screen to access the internet.

You can get these values from your router. In my case the Qwest DSL modem allows me to connect to 192.168.0.1 as admin with a password and the DNS values were there.

Once I plugged them into the configuration the internet access AND the repository issue were resolved.