[Linux-Discussion] Re: [Fwd: network problems using RayLink wireless and Linux 2.4 firewall]

  • From: Carol Horwitz <chorwitz@xxxxxxxxxxx>
  • To: linux-discussion@xxxxxxxxxxxxx
  • Date: Mon, 17 Jun 2002 23:05:34 -0500

Done. The firewall now has 192.168.1.1 as ihostWireless and 192.168.0.1 
as ihostLan. The laptop (bigbird) is 192.168.1.3, both on the Windows 
and Linux OS. The desktop (Windows98, wired) is 192.168.0.2. Everything 
works (or not, as the case may be) as before. No more or less.The routes 
on the firewall now are:

Kernel IP routing table
Destination     Gateway    Genmask         Flags Metric Ref    Use Iface
192.168.1.0     *          255.255.255.0   U     0      0        0 eth2
192.168.0.0     *          255.255.255.0   U     0      0        0 eth1
66.69.80.0      *          255.255.240.0   U     0      0        0 eth0
127.0.0.0       *          255.0.0.0       U     0      0        0 lo
default       66.69.80.1   0.0.0.0         UG    0      0        0 eth0

ifconfig gives:

eth0      Link encap:Ethernet  HWaddr 00:E0:29:46:C2:66
           inet addr:66.69.86.2  Bcast:255.255.255.255 Mask:255.255.240.0
           UP BROADCAST NOTRAILERS RUNNING  MTU:1500  Metric:1
           RX packets:6712 errors:0 dropped:0 overruns:0 frame:0
           TX packets:726 errors:0 dropped:0 overruns:0 carrier:0
           collisions:23 txqueuelen:100
           RX bytes:1108767 (1.0 Mb)  TX bytes:91508 (89.3 Kb)
           Interrupt:9 Base address:0xf880

eth1      Link encap:Ethernet  HWaddr 00:80:C6:E7:2B:7C
           inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:1110 errors:0 dropped:0 overruns:0 frame:0
           TX packets:1269 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:100
           RX bytes:116557 (113.8 Kb)  TX bytes:782544 (764.2 Kb)
           Interrupt:5 Base address:0xf400

eth2      Link encap:Ethernet  HWaddr 00:00:F1:11:1C:11
           inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
           TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:100
           RX bytes:0 (0.0 b)  TX bytes:480 (480.0 b)
           Interrupt:3

lo        Link encap:Local Loopback
           inet addr:127.0.0.1  Mask:255.0.0.0
           UP LOOPBACK RUNNING  MTU:16436  Metric:1
           RX packets:116 errors:0 dropped:0 overruns:0 frame:0
           TX packets:116 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:0
           RX bytes:8120 (7.9 Kb)  TX bytes:8120 (7.9 Kb)

Is it possible that the pcmcia card is using a different interrupt on 
the Windows and Linux side and that makes a difference? I'm not sure I'd 
even know where to look.

cdh

Paul Anderson wrote:

> On Mon, 17 Jun 2002, Carol Horwitz wrote:
> 
> 
>>The "spaghetti" reference is definitely true, but remember that this
>>very same inelegant structure works when I use the laptop under Windows
>>2000.
>>
>>
> It shouldn't:)
> 
> 
>>I'd like to clean this up anyway, and see if it can possibly help. I
>>assume you mean that I should have two subnets, one for the "wired"
>>portion of my home network and one for the "wireless" portion.
>>
>>
> Precisely.
> 
> 
>>I don't
>>know what the subnet mask would be for the 192.168.1.0 portion.
>>
>>
> 192.168.1.0 and 192.168.0.0 would both have a netmask of 255.255.255.0.
> 
> 
>>Also, do
>>I map different hostnames to the different IPs on my firewall, one for
>>the wired side and one for the wireless?
>>
>>
> Should do the trick.
> 
> 
> 
> ---
> Paul Anderson
> geeky1!paul
> "Nature has been kinder to us than we had any right to expect.
>       --- Freeman Dyson
> 
> 
> 
> 



Other related posts: