https://bugzilla.novell.com/show_bug.cgi?id=383083
User mt@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=383083#c70
Marius Tomaschewski changed:
What |Removed |Added
----------------------------------------------------------------------------
Info Provider|mt@novell.com |quentin.jackson@exclamation.co.nz
--- Comment #70 from Marius Tomaschewski 2008-07-14 05:42:04 MDT ---
Quentin,
when I take a look to the attachment #215829 (comment #23), it looks like
a strange configuration. It seems, you've connected both the eth0 and
wlan0 interfaces to the wireless router and both interfaces are on the
same network:
SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC= SRC=192.168.1.101 DST=224.0.0.251
LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.1.151 DST=224.0.0.251
LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44
martian source 192.168.1.255 from 192.168.1.102, on dev wlan0
ll header: ff:ff:ff:ff:ff:ff:00:1f:3b:70:4d:77:08:00
Your routing table contains two routes to the same network (ip route show)
using both interfaces:
[...]
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.101
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.151
or like this (route -n):
Ziel Router Genmask Flags Metric Ref Use Iface
[...]
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0
[...]
correct?
Well this can not work, because the kernel will always use the first
eth0 interface, never wlan0 (except you specify a program to bind to
the interface, e.g. using "ping -I wlan0 192.168.1.102").
Further, I'd say there are some problems with the wireless driver:
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
iwl4965: Microcode SW error detected. Restarting 0x2000000.
^^^^^^^^^^^^^^^^^^^^^^^^^^^
iwl4965: Error sending REPLY_TX_LINK_QUALITY_CMD: time out after 500ms.
iwl4965: Error sending REPLY_PHY_CALIBRATION_CMD: time out after 500ms.
iwl4965: Error sending REPLY_QOS_PARAM: time out after 500ms.
wlan0: No ProbeResp from current AP 00:1d:7e:aa:1d:4a - assume out of range
iwl4965: Error sending REPLY_RXON_ASSOC: time out after 500ms.
iwl4965: Error sending REPLY_RXON_ASSOC: time out after 500ms.
^^^^^^^^^^^^^^^^^^^^
== About dhcp:
First of all, there are _two_ _different_ dhcp clients & packages,
both in version 3.x. But it are completely different clients.
- package dhcpcd-3.2.3-*, binary /sbin/dhcpcd, no config (command
line arguments).
This client is used by "ifup" by default, supports multiple
interfaces -- but not on same network :-)
The DHCLIENT_BIN variable in /etc/sysconfig/network/dhcp
defines which client is used by "ifup".
kinternet can (must not!) be used, when the USERCONTROL variable
is set to "yes" in /etc/sysconfig/network/ifcfg-*.
- package dhcp-client-3.0.6-*, binary /sbin/dhclient, config
file /etc/dhclient.conf.
When used in "ifup", setup script is /sbin/dhclient-script.
This client is used by NetworkManager with a different script
(/usr/lib/NetworkManager/nm-dhcp-client.action).
The NetworkManager may fail, when the /etc/dhclient.conf
contains a active script line (because of an update).
NetworkManager is started by rcnetwork when the
NETWORKMANAGER="yes" is set in /etc/sysconfig/network/config.
== How to continue.
- Stop & Disable SuSEfirewall2 using
SuSEfirewall2 stop
insserv -r /etc/init.d/SuSEfirewall2_setup
insserv -r /etc/init.d/SuSEfirewall2_init
You can enable it later by
insserv /etc/init.d/SuSEfirewall2_init
insserv /etc/init.d/SuSEfirewall2_setup
_and_ configure it using "yast2 firewall" when you've an
working network.
- Verify that the MAC filter on your router does not break
the configuration.
* Using ifup:
- rcnetwork stop
- Set NETWORKMANAGER="no" in /etc/sysconfig/network/config.
- Set DHCLIENT_BIN="" (or dhcpcd) in /etc/sysconfig/network/dhcp.
- Delete both, eth0 and wlan0 configurations in yast2, that is
all /etc/sysconfig/network/ifcfg-* files _except_ ifcfg-lo.
- Configure wlan0 interface with dhcp in YaST2
- rcnetwork restart
- test it.
When it does not work:
- rcnetwork stop
- Configure wlan0 interface with static IP in YaST2
- rcnetwork restart
- test, if you can ping the IP of the wireless router
and another IP's on the network.
- test, if you can ping IPs outside of your network, e.g.
195.135.220.3 (www.suse.de) when you add a default route
using "ip route add default via IP_OF_YOUR_ROUTER".
- delete the default route ("ip route del default") and
call "dhcpcd-test wlan0". When this works, change to
"dhcp" in yast2 (or set BOOTPROTO="dhcp" in ifcfg-wlan0)
and test again.
When this all does not work, please provide "iwconfig wlan0",
"ip addr show", "ip route show" and "dhcpcd-test wlan0"
outputs and the messages from /var/log/message since the
last boot.
* Using NetworkManager:
- rcnetwork stop
- Make sure there is no script line in /etc/dhclient.conf
- Set NETWORKMANAGER="yes" in /etc/sysconfig/network/config.
- Delete both, eth0 and wlan0 configurations in yast2, that is
all /etc/sysconfig/network/ifcfg-* files _except_ ifcfg-lo.
- rcnetwork start (starts network manager)
- Use network manager applet in your desktop to configure
the interfaces.
== Using two interfaces:
Using two interfaces almost always needs special configuration,
especially when they're (may be) connected to the same network.
The ifup script tries to handle the case where you are connected
to two different networks, by disabling setting of default route
etc. on the second interface.
What you can do is to use "ifplugd" to configure only the connected
interface, that is:
- Configure both interfaces with YaST2
- Set STARTMODE="ifplugd" in the ifcfg-* file of both interfaces
- Set IFPLUGD_PRIORITY="10" for one interface
- Set IFPLUGD_PRIORITY="20" for another interface
Quentin, can you try out to set up and test as described above
with one interface and static IPs first?
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.