Topic: Wrong External IP Reports 192.168.65.17

[bean666]

I have been running SME Server on my @home cable modem for a long time now.  When @home changed over from Excite to there @home network my computer stopped update my dydns.org address.  I checked server manager and for my external ip it was reporting the old ip address of 24.xyz.xyz when it really was 68.xyz.xyz now.  I am able to connect to the internet with it like this.  I then changed the network cards.  This made no changes it still report the wrong ip.  Then I reinstalled everything.  When I got it back up and connected again it reported 192.168.65.17 wrong again.  It is setup to update my ip to dydns.org but it hasn't in a long time even after a reboot.  I think it is supposed to do this when the server obtains a new ip and update the 192.168.65.17 witch I think is the default ip of a fresh install.  So the only thing I can think is that for some reason my server is not registering obtaining a new ip.

When I do ifconfig:

eth0      Link encap:Ethernet  HWaddr 00:50:04:CE:7A:D5  
          inet addr:192.168.43.1  Bcast:192.168.43.255  Mask:255.255.255.0
          EtherTalk Phase 2 addr:65280/92
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:538 errors:0 dropped:0 overruns:0 frame:0
          TX packets:567 errors:0 dropped:0 overruns:0 carrier:0
          collisions:12 txqueuelen:100
          Interrupt:15 Base address:0xfc00

eth1      Link encap:Ethernet  HWaddr 00:50:DA:D9:72:C2  
          inet addr:68.39.131.101  Bcast:68.39.135.255  Mask:255.255.248.0
          UP BROADCAST NOTRAILERS RUNNING  MTU:1500  Metric:1
          RX packets:2483 errors:0 dropped:0 overruns:0 frame:0
          TX packets:244 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          Interrupt:11 Base address:0xf480

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          EtherTalk Phase 2 addr:0/0
          UP LOOPBACK RUNNING  MTU:3924  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0


When I do /sbin/ipchains -n -L input

target     prot opt     source                destination           ports
icmpIn     icmp ------  0.0.0.0/0            0.0.0.0/0             * ->   *
ACCEPT     all  ------  0.0.0.0/0            0.0.0.0/0             n/a
denylog    tcp  ------  0.0.0.0/0            0.0.0.0/0             0:19 ->   *
denylog    udp  ------  0.0.0.0/0            0.0.0.0/0             0:19 ->   *
denylog    tcp  ------  0.0.0.0/0            0.0.0.0/0             * ->   0:19
denylog    udp  ------  0.0.0.0/0            0.0.0.0/0             * ->   0:19
DENY       all  ------  224.0.0.0/4          0.0.0.0/0             n/a
DENY       all  ------  0.0.0.0/0            224.0.0.0/4           n/a
ACCEPT     tcp  ------  0.0.0.0/0            127.0.0.1             * ->   80
ACCEPT     tcp  ------  0.0.0.0/0            192.168.43.1          * ->   80
ACCEPT     tcp  ------  0.0.0.0/0            192.168.65.17         * ->   80
REDIRECT   tcp  ------  192.168.43.0/24      0.0.0.0/0             * ->   80 => 3128
ACCEPT     all  ------  192.168.43.0/24      0.0.0.0/0             n/a
ACCEPT     tcp  !y----  0.0.0.0/0            0.0.0.0/0             * ->   *
ACCEPT     tcp  ------  0.0.0.0/0            192.168.65.17         * ->   113
ACCEPT     udp  ------  0.0.0.0/0            192.168.65.17         * ->   113
ACCEPT     udp  ------  0.0.0.0/0            0.0.0.0/0             * ->   67:68
ACCEPT     udp  ------  0.0.0.0/0            0.0.0.0/0             67:68 ->   *
ACCEPT     tcp  ------  0.0.0.0/0            192.168.65.17         * ->   80
ACCEPT     tcp  ------  0.0.0.0/0            192.168.65.17         * ->   443
ACCEPT     ipv6-crypt------  0.0.0.0/0            192.168.65.17         n/a
ACCEPT     udp  ------  0.0.0.0/0            192.168.65.17         500 ->   500
ACCEPT     gre  ------  0.0.0.0/0            192.168.65.17         n/a
ACCEPT     tcp  ------  0.0.0.0/0            192.168.65.17         * ->   25
ACCEPT     tcp  ------  0.0.0.0/0            192.168.65.17         * ->   22
denylog    tcp  -y----  0.0.0.0/0            192.168.65.17         * ->   3306
DENY       udp  ------  0.0.0.0/0            0.0.0.0/0             * ->   520
DENY       tcp  ------  0.0.0.0/0            0.0.0.0/0             * ->   137:139
DENY       udp  ------  0.0.0.0/0            0.0.0.0/0             * ->   137:139
denylog    tcp  -y----  0.0.0.0/0            192.168.65.17         * ->   3128
ACCEPT     tcp  -y----  0.0.0.0/0            192.168.65.17         20 ->   1024:65535
ACCEPT     tcp  ------  0.0.0.0/0            0.0.0.0/0             * ->   1024:65535
ACCEPT     udp  ------  0.0.0.0/0            0.0.0.0/0             * ->   1024:65535
denylog    all  ------  0.0.0.0/0            0.0.0.0/0             n/a


Oh well?

[Alexander Ziemann]

Some providers seem to block DynIP adresses. Maybe that?

Alex

[bean6666]

I wish that was true but in server manager and in ipchains output it is reporting  192.168.65.17.

[JonB]

These are known bugs.

Check out

http://www.e-smith.org/bugs/index.php3?op=showBug&bugID=50
http://www.e-smith.org/bugs/index.php3?op=showBug&bugID=53

Jon

[bean666]

Thanks allot this makes me feel allot better I thought I was going crazy for a minute.  I guess I am out of luck considering that there is no fix or workaround for this.  I like the workaround "it is safe to ignore this bug "  I can't contact my computer from the outside on any ports.  Witch makes SME Server useless to me!!!  I wonder why this is happing to me is this an incompatibly with SME server and my ISP @home.

Review configuration panel reports incorrect gateway details
Applies to version: 5.0
Fixed in version:  
Problem: The 'Review configuration' panel in the server-manager is not displaying the correct Gateway IP information.  
Workaround: Until a fix is released, it is safe to ignore this bug.  
Final Solution:  
Comments: The gateway IP being displayed is the default static gateway IP address and is not actually used.

[bean666]

192.168.65.17 is the ip givin by e-smith to an ethernet card when the DHCP
request fails (ie: no DHCP servers are found).  But I am on the internet.  Does anyone know of a better workaround I like E-smith and would like to contuine to use it.  I have seen this question asked her before and they said changing ethernet cards fixed the problem but I have tryied many different cards.  Any suggestions are welcome.

[Quade]

See my post at http://forums.contribs.org/index.php?topic=12640.msg47434#msg47434 for a fix and explanation.

Basically, all you need to do for an interim fix is to pull a dynamic IP, copy the IP and gateway info, and then change the SME server to use a static IP using the IP that the DHCP server assigned you. I've been doing this for awhile now, and it has worked.

The only real caveat is when/if the IP lease is up, you may have to pull a new IP. I have yet to do this, and I have had uninterrupted service.

HTH,
Quade