Koozali.org: home of the SME Server

ifconfig strangeness

Charlie Hartill

ifconfig strangeness
« on: August 10, 2003, 12:31:58 AM »
Hello wise people,

Running ifconfig on my SME 5.6U4 I get the following:


eth0      Link encap:Ethernet  HWaddr 00:50:04:06:2E:20
          inet addr:10.33.100.52  Bcast:10.33.100.255  Mask:255.255.255.0
          EtherTalk Phase 2 addr:65280/143
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:21516 errors:0 dropped:0 overruns:0 carrier:21516
          collisions:0
          RX bytes:0 (0.0 b)  TX bytes:2801728 (2.6 Mb)

eth1      Link encap:Ethernet  HWaddr 00:C0:4F:B1:AC:74
          inet addr:10.33.100.53  Bcast:10.33.100.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6419336 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4481279 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0
          RX bytes:3193802812 (3045.8 Mb)  TX bytes:1340014038 (1277.9 Mb)

eth0 is the internal & eth1 the external.

These are 3Com 905bTx cards using the standard driver. I also feel the performance is rather under par.

Any thoughts?

Charlie

Guck Puppy

Re: ifconfig strangeness
« Reply #1 on: August 10, 2003, 03:21:34 AM »
Charlie Hartill wrote:
> eth0      Link encap:Ethernet  HWaddr 00:50:04:06:2E:20
>           inet addr:10.33.100.52  Bcast:10.33.100.255

> eth1      Link encap:Ethernet  HWaddr 00:C0:4F:B1:AC:74
>           inet addr:10.33.100.53  Bcast:10.33.100.255

> eth0 is the internal & eth1 the external.

I'm curious... aren't those IP addresses a bit odd for a gateway machine? what subnet are you using inside the eth0 network?

G

Charlie Hartill

Re: ifconfig strangeness
« Reply #2 on: August 10, 2003, 07:23:33 PM »
Well the network has to be portable & adaptable so sometimes the machine is a gateway & others it talks to another router, all on the 10.33.100.0/255.255.255.0 network.

When it is the only gateway eth1 gets set to DHCP & gets a public facing 62.x.x.x address.

Is this a problem?