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?

[Randall]

Remember, that just because you are running DHCP does not mean that your Linux box will pickup the new IP address automatically. These systems are tuned for a Windoze networking environment... This is what I did. I  hooked  my laptop up to the Cable modem and using Windows' ipconfig /all to obtain all the necessary information and to check if the ip address changed.  I then setup my external network to use that static IP address.  This should work until your IP address expires and changes again.  Do not turn off your modem during this procedure!

If Cox is your ISP as they are here in Phoenix, they started blocking all smtp ports as well as port 80 on their internal network.  This is according to Cox here.  It seems a number of people were hosting which is against the service agreement.  Now who would do such a thing???  

If you are running a firewall off this same machine, would you -be so kind as to let me know if the connection between your firewall and cable modem stops responding to the point the firewall has to be reset.  This was the problem I had with Linux firwall  near the end.  I thought the server was going deaf periodically.  I was wrong, I still have the problem with my $200 Linksys firewall.

Randy Koth

[Bill Talcott]

bean666 wrote:
>
> 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

I'm no expert, but it looks like eth1 is getting the external address correctly. Did your settings just get messed up (maybe when you swapped NICs?) and the cards are reversed now? 192.168.x.x is a private IP, which your computer would get if it couldn't reach a DHCP server (Well, it would in Windows, I'm not sure how this is setup...).  It sounds to me like it's looking at the wrong NIC for the external info...  According your your ifconfig, it looks like it does have the correct external info...

[robert]

What you could do is manually run an ip-change event with the external ip from ifconfig as an argument, like so:
/sbin/e-smith/signal-event ip-change 68.39.131.101

That should make all the servers on the system that need it aware of the new external ip, but of course it's no real solution to your problem (though it may work until the next reboot). There appear to be some pretty serious DHCP issues with SME lately, most of them have to do with the DHCP server, but maybe there's a problem on the client side as well. Which release version are you running?

[bean666]

Cool that did not trick /sbin/e-smith/signal-event ip-change 68.39.131.101

Thanks allot this will do for now.  Until I can figure something else out that's more permanent.  I am running V5.  Before I reinstalled to fix the problem I was running the version before that.  It had the same problem with this new Comcast.net network.