IPX works via wired network, not via wireless
IPX works via wired network, not via wireless
Hi All,
I have installed Atomic Bomberman as described here:
https://wiki.archlinux.org/index.php/Atomic_bomberman
When I connect 2 PC's running linux via networkcables and a switch, IPX works perfectly. I start the game on both PC's, set PC A to "Start Network game" via IPX, and PC B to "Join network game". Now PC B can see the game of PC A, connect to it, and then play a game of bomberman. No Problems.
When one of the 2 PC's is connected via wireless LAN, PC B can't see the game of PC A.
Both PC's run arch linux, and the same version of wine and kernel
wine-1.3.7
Linux laptop 2.6.35-ARCH #1 SMP PREEMPT Sat Oct 30 19:57:05 UTC 2010 i686 Intel(R) Core(TM)2 Duo CPU T5670 @ 1.80GHz GenuineIntel GNU/Linux
I see the following messages on the console:
$ wine BM.EXE
fixme:win:EnumDisplayDevicesW ((null),0,0x33f2a8,0x00000000), stub!
fixme:dinput:SysMouseAImpl_Acquire Clipping cursor to (0,0)-(640,480)
fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x13bbb8,0x13bb28): stub
fixme:winsock:is_sockaddr_bound don't know how to tell if IPX socket is bound, assuming it is!
Best regards,
Cedric
I have installed Atomic Bomberman as described here:
https://wiki.archlinux.org/index.php/Atomic_bomberman
When I connect 2 PC's running linux via networkcables and a switch, IPX works perfectly. I start the game on both PC's, set PC A to "Start Network game" via IPX, and PC B to "Join network game". Now PC B can see the game of PC A, connect to it, and then play a game of bomberman. No Problems.
When one of the 2 PC's is connected via wireless LAN, PC B can't see the game of PC A.
Both PC's run arch linux, and the same version of wine and kernel
wine-1.3.7
Linux laptop 2.6.35-ARCH #1 SMP PREEMPT Sat Oct 30 19:57:05 UTC 2010 i686 Intel(R) Core(TM)2 Duo CPU T5670 @ 1.80GHz GenuineIntel GNU/Linux
I see the following messages on the console:
$ wine BM.EXE
fixme:win:EnumDisplayDevicesW ((null),0,0x33f2a8,0x00000000), stub!
fixme:dinput:SysMouseAImpl_Acquire Clipping cursor to (0,0)-(640,480)
fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x13bbb8,0x13bb28): stub
fixme:winsock:is_sockaddr_bound don't know how to tell if IPX socket is bound, assuming it is!
Best regards,
Cedric
Ok ifconfig on both machines wireless cards showing IPX support?eth0 Link encap:Ethernet HWaddr 00:21:70:BE:44:EA
inet addr:10.12.21.104 Bcast:10.12.21.255 Mask:255.255.255.0
inet6 addr: fe80::221:70ff:febe:44ea/64 Scope:Link
IPX/Ethernet 802.2 addr:12345678:002170BE44EA
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:19768 errors:0 dropped:0 overruns:0 frame:0
TX packets:16693 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:22185092 (21.1 Mb) TX bytes:2131056 (2.0 Mb)
Interrupt:46 Base address:0x6000
ifconfig on PC A, PC A is connected via wired lan:
ifconfig on PC B, connected via wireless lan:
PC A is hosting the game, PC B tries to connect. PC B can't see the game.
Now I change PC B, so it is connected via wired lan:
ifconfig PC B, now on wireless lan:
PC A is hosting the game, PC B tries to connect. Now everything works without problems.
Is it usefull to enable the winsock debug channel and post the result?
Best regards,
Cedric
Code: Select all
# ipx_interface add -p eth0 802.2 0x12345678
[root@laptop bomber]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:21:70:BE:44:EA
inet addr:192.168.31.101 Bcast:192.168.31.255 Mask:255.255.255.0
inet6 addr: fe80::221:70ff:febe:44ea/64 Scope:Link
IPX/Ethernet 802.2 addr:12345678:002170BE44EA
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:17909 errors:0 dropped:0 overruns:0 frame:0
TX packets:7134 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3301751 (3.1 Mb) TX bytes:1093295 (1.0 Mb)
Interrupt:46 Base address:0xe000
eth1 Link encap:Ethernet HWaddr 00:23:4D:95:C9:97
inet6 addr: fe80::223:4dff:fe95:c997/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1030501 errors:0 dropped:0 overruns:0 frame:37193
TX packets:559036 errors:79 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1522594154 (1452.0 Mb) TX bytes:42565037 (40.5 Mb)
Interrupt:19
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:1032 errors:0 dropped:0 overruns:0 frame:0
TX packets:1032 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:36751 (35.8 Kb) TX bytes:36751 (35.8 Kb)
Code: Select all
# ipx_interface add -p eth0 802.2 0x12345678
[root@laptop bomber]# ifconfig
eth0 Link encap:Ethernet HWaddr C4:17:FE:46:43:24
inet addr:192.168.31.202 Bcast:192.168.31.255 Mask:255.255.255.0
inet6 addr: fe80::c617:feff:fe46:4324/64 Scope:Link
IPX/Ethernet 802.2 addr:12345678:C417FE464324
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5657742 errors:0 dropped:0 overruns:0 frame:331357
TX packets:4467510 errors:103 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1605887829 (1531.4 Mb) TX bytes:1216873005 (1160.5 Mb)
Interrupt:18
eth1 Link encap:Ethernet HWaddr 00:26:B9:A3:EB:35
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:687817 errors:0 dropped:0 overruns:0 frame:0
TX packets:475011 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:824193696 (786.0 Mb) TX bytes:115025239 (109.6 Mb)
Interrupt:47 Base address:0xe000
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:361865 errors:0 dropped:0 overruns:0 frame:0
TX packets:361865 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:10565136 (10.0 Mb) TX bytes:10565136 (10.0 Mb)
Now I change PC B, so it is connected via wired lan:
ifconfig PC B, now on wireless lan:
Code: Select all
# ipx_interface add -p eth1 802.2 0x12345678
[root@laptop bomber]# ifconfig
eth0 Link encap:Ethernet HWaddr C4:17:FE:46:43:24
inet6 addr: fe80::c617:feff:fe46:4324/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5674396 errors:0 dropped:0 overruns:0 frame:333531
TX packets:4481678 errors:103 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1623060722 (1547.8 Mb) TX bytes:1220017520 (1163.4 Mb)
Interrupt:18
eth1 Link encap:Ethernet HWaddr 00:26:B9:A3:EB:35
inet addr:192.168.31.202 Bcast:192.168.31.255 Mask:255.255.255.0
inet6 addr: fe80::226:b9ff:fea3:eb35/64 Scope:Link
IPX/Ethernet 802.2 addr:12345678:0026B9A3EB35
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:690213 errors:0 dropped:0 overruns:0 frame:0
TX packets:477091 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:826594805 (788.3 Mb) TX bytes:115479390 (110.1 Mb)
Interrupt:47 Base address:0xe000
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:361865 errors:0 dropped:0 overruns:0 frame:0
TX packets:361865 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:10565136 (10.0 Mb) TX bytes:10565136 (10.0 Mb)
Is it usefull to enable the winsock debug channel and post the result?
Best regards,
Cedric
PCA is a dell vostro 1710 with the following networkcards:
06:00.0 Network controller: Broadcom Corporation BCM4328 802.11a/b/g/n (rev 03)
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)
PC B is a dell vostro 1720 with the following networkcards:
08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
0e:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01)
The above wireless cards are not supported by the kernel, so I have to use the driver from broadcom. This is described here:
http://aur.archlinux.org/packages.php?ID=19514
Could somebody please test this with a wireless card that is supported by the linux kernel?
Best regards,
Cedric
06:00.0 Network controller: Broadcom Corporation BCM4328 802.11a/b/g/n (rev 03)
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)
PC B is a dell vostro 1720 with the following networkcards:
08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
0e:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01)
The above wireless cards are not supported by the kernel, so I have to use the driver from broadcom. This is described here:
http://aur.archlinux.org/packages.php?ID=19514
Could somebody please test this with a wireless card that is supported by the linux kernel?
Best regards,
Cedric
Come to think of it, I also run windows XP on the above 2 laptops. Windows XP shows the same problem. IPX works fine on the wired LAN, and does not work via wireless.
Therefore I wonder, is this a hardware problem? Could this be a broadcom driver problem? The wireless cards work fine for IP traffic
Where in the following stacks is the problem?
-Atomic Bomberman
-Wine
-Linux kernel
-Broadcom linux Driver
-Broadcom Wireless card
-Atomic Bomberman
-Windows kernel
-Broadcom windows driver
-Broadcom wireless card
Best regards,
Cedric
Therefore I wonder, is this a hardware problem? Could this be a broadcom driver problem? The wireless cards work fine for IP traffic
Where in the following stacks is the problem?
-Atomic Bomberman
-Wine
-Linux kernel
-Broadcom linux Driver
-Broadcom Wireless card
-Atomic Bomberman
-Windows kernel
-Broadcom windows driver
-Broadcom wireless card
Best regards,
Cedric
I have tested with a laptop with an intel wireless card. (I call this laptop PC C) This works perfectly. PC A is connected via wired network, and serving the game. PC C is connected via wireless. Now I can play the game without any problem.
PC C is running knoppix 6.2, wine-1.0.1-174-gc4039bd ,kernel 2.6.31.6
The wireless card: Network controller: Intel Corporation Wireless WiFi Link 5100
I think this is not a problem of wine, but rather a problem of the broadcom wireless card, or the broadcom driver.
Best regards,
Cedric
PC C is running knoppix 6.2, wine-1.0.1-174-gc4039bd ,kernel 2.6.31.6
The wireless card: Network controller: Intel Corporation Wireless WiFi Link 5100
I think this is not a problem of wine, but rather a problem of the broadcom wireless card, or the broadcom driver.
Best regards,
Cedric
Atomic Bomberman on internet
Hi, if you want play atomic bomberman over the internet, let me know on icq 649933647 or read this tutorial http://jakkajak.blog.cz/1009/how-to-pla ... ternet-eng
Or you can visit Atomic Bomberman Online chat here http://static.99widgets.com/chats/swf/c ... r=120965&l
kaja
Or you can visit Atomic Bomberman Online chat here http://static.99widgets.com/chats/swf/c ... r=120965&l
kaja