Topic: DHCP problem on WAN side of gateway

[n1546660]

Hi all,

I have a problem with my SME v6.01 server.  For some reason it has a problem getting an IP address from my ISP.  I use a cable modem and my ISP is the Australian "Optus" cable internet provider.  I know DHCP works because if I plug the network cable coming from tbe cable modem to any other windows PC in the house, everything works fine, they get the IP, and everything works as usual, however, e-smith doesn't seem to want to work because it never manages to get a lease on an IP address from the modem/ISP (ifconfig shows no IP address on wan link)

I have read that sometimes the ISP requires a username or hostname to be passed, but I don't think that is the case because none of the windows PC's need to send any information via DHCP (other than ethernet address), and there are no clients installed on them either.  

So it seems that e-smith is not talking the right protocol or something to Optus.  

Can anyone suggest what I am doing wrong here?  Or what can I do to fix it or at least investigate further?

Thanks in advance for any help/suggestions/comments.

- Andrew Gray

[Reinhold]

Hi Andrew,

Check your SME setup first,
- Have you setup as Gateway&Server ?
- Have you setup dhcp with ethernet access
- Is the server operating dhcp internally or at least in the same subdomain ?

IF this seems OK, go to log files ...
Open server-manager / Administration View log Files / Choose a log file to view: messages NEXT / ...


In the log file look for a typcial dhcpd request:

Sep 15 14:54:13 myserver dhcpd: DHCPDISCOVER from 01:02:03:04:05:06 via eth0
Sep 15 14:54:14 myserver dhcpd: DHCPOFFER on 162.xxx.xxx.01 to 01:02:03:04:05:06 via eth0
Sep 15 14:54:14 myserver dhcpd: DHCPREQUEST for 162.xxx.xxx.01 from 01:02:03:04:05:06 via eth0

Sep 15 14:54:14 myserver dhcpd: DHCPACK on 162.xxx.xxx.01 to 01:02:03:04:05:06 via eth0

Note: myserver is you SME
01:02:03:04:05:06 (the MAC of your wan eth-card) is trying to discover, 162.xxx.xxx.01 was offered then requested finally acknowledged

If you find nothing like that there you might
- post what you find & deem relevant...
- call 1 800 501 283 ... <eg> seems they are running Linux too
One possible explanation (out of too many) could be they accept only 1 or 2 MACs now already taken by your Win-Box (es)

Regards
Reinhold

[Reinhold]

Actually it might be worthwhile reading their pamphlet...

http://www.optus.com.au/AST_File_Management/ACQ/optusnet_connection_657.pdf

...this is where I got their phone no.
(I'm in EU not AU ... so this is where I "got to know them"

Regards
Reinhold

[n1546660]

Hello, thank you for your response.  

I have set this server up as gateway and server, with ethernet dhcp access, and it is operating a DHCP service on the local lan.

The log files say (with a "dhcp" filter):
Oct 25 08:42:03 andygw dhcpcd[1230]: broadcasting DHCP_REQUEST for 192.168.1.1
Oct 25 08:43:03 andygw dhcpcd[1230]: timed out waiting for DHCP_ACK response
Oct 25 08:43:03 andygw dhcpcd[1230]: broadcasting DHCP_DISCOVER
Oct 25 08:44:03 andygw dhcpcd[1230]: timed out waiting for a valid DHCP server response
Oct 25 08:44:03 andygw ifup: dhcpcd: MAC address = 00:c0:4f:7a:08:b1
Oct 25 08:44:03 andygw network: Determining IP information for eth1...dhcpcd: MAC address = 00:c0:4f:7a:08:b1
Oct 25 08:44:05 andygw dhcpcd: Starting dhcpcd:
Oct 25 08:44:06 andygw dhcpcd: Starting dhcpcd succeeded
Oct 25 08:44:06 andygw dhcpcd:
Oct 25 08:44:06 andygw rc: Starting dhcpcd:  succeeded
Oct 25 08:44:07 andygw dhcpcd[1348]: broadcasting DHCP_REQUEST for 192.168.1.1
Oct 25 08:44:24 andygw dhcpd: Starting dhcpd:
Oct 25 08:44:25 andygw dhcpd: Starting dhcpd succeeded
Oct 25 08:44:25 andygw dhcpd:
Oct 25 08:44:25 andygw rc: Starting dhcpd:  succeeded
Oct 25 08:44:28 andygw dhcpd: Internet Software Consortium DHCP Server 2.0pl5
Oct 25 08:44:28 andygw dhcpd: Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
Oct 25 08:44:28 andygw dhcpd: All rights reserved.
Oct 25 08:44:28 andygw dhcpd:
Oct 25 08:44:28 andygw dhcpd: Please contribute if you find this software useful.
Oct 25 08:44:28 andygw dhcpd: For info, please visit http://www.isc.org/dhcp-contrib.html
Oct 25 08:44:28 andygw dhcpd:
Oct 25 08:44:29 andygw dhcpd: Listening on Socket/eth0/192.168.1.0
Oct 25 08:44:29 andygw dhcpd: Sending on   Socket/eth0/192.168.1.0
Oct 25 08:45:07 andygw dhcpcd[1348]: timed out waiting for DHCP_ACK response
Oct 25 08:45:07 andygw dhcpcd[1348]: broadcasting DHCP_DISCOVER
Oct 25 08:46:08 andygw dhcpcd[1348]: timed out waiting for a valid DHCP server response
Oct 25 08:46:48 andygw dhcpcd[2782]: broadcasting DHCP_REQUEST for 192.168.1.1
Oct 25 08:47:48 andygw dhcpcd[2782]: timed out waiting for DHCP_ACK response
Oct 25 08:47:48 andygw dhcpcd[2782]: broadcasting DHCP_DISCOVER
Oct 25 08:48:48 andygw dhcpcd[2782]: timed out waiting for a valid DHCP server response
Oct 25 08:49:27 andygw dhcpcd[3070]: broadcasting DHCP_REQUEST for 192.168.1.1

I don't know where it gets 192.168.1.1, since it's internal lan IP is 192.168.1.254, and has nothing to do with the external interface.  But the MAC address mentioned in the ifup part is the correct external interface MAC.

[root@andygw root]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:10:5A:74:44:F6
          inet addr:192.168.1.254  Bcast:192.168.1.255  Mask:255.255.255.0
          EtherTalk Phase 2 addr:65280/78
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:83 errors:0 dropped:0 overruns:0 frame:0
          TX packets:160 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0
          RX bytes:9634 (9.4 Kb)  TX bytes:77518 (75.7 Kb)

eth1      Link encap:Ethernet  HWaddr 00:C0:4F:7A:08:B1
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2135 errors:0 dropped:0 overruns:0 frame:0
          TX packets:21 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0
          RX bytes:131140 (128.0 Kb)  TX bytes:12390 (12.0 Kb)

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:16436  Metric:1
          RX packets:1355 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1355 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0
          RX bytes:144632 (141.2 Kb)  TX bytes:144632 (141.2 Kb)


I didn't think linux would be anything like a supported OS by Optus, I'm quite certain that if I tell them I'm using linux, they'll tell me it's not supported.  But I'll give it a shot.  

Also, you are right in that it only accepts one mac address at a time.  But I didn't think it would matter what the ethernet address would be since they didn't supply the network cards.  The cable modem is connected to my server via a cross-over cable (direct connect).  

Let me know what you think.  Thank you!!!

- Andrew Gray

[Reinhold]

Hi

Solution is hopefully simple:
 Reset Cable Modem - then connect with SME first...
It seems the modem remembers the last MAC address
and refuses to talk to someone else.
You could fake that from Linux but real is better!

To be sure:
- What is your (real) external Interface ?
- Your message log is a bit inconsistent... be sure about the dhcp with ethernet access setting !
- Most current equipment finds out about x- or straight cabling and takes what it needs - nevertheless usually you'd want a straight for the modem cabling !? (It works so no need to change anyway .-)

Note:
- dhcpd isn't Windows or Linux dependend ...it's a Network protocol
- the MAC address doesn't need to be known to your ISP since your 1st connection is directly with him. This is why most of them accept only a limited no. of MACs on that line (else you could just put all your PCs on a hub/switch and connect them directly (dangerous no Firewall).

Regards
Reinhold

[n1546660]

Hi,

oh man, do I feel stupid!  Here I thought it was some sort of problem, and the solution was as simple as resetting the cable modem just prior to a reboot of the SME server!  grrr, why didn't I think of that?

Well thank you very much for having the insight to see that the solution was so simple, and for sharing it with me.  All is working fine now, and I am even sending this message out through the internet connection that is coming from my SME server.

Thanks again!

- Andy Gray

[Reinhold]

Andy,

No need to feel stupid - solution wasn't that obvious at first and nothing's happened that a bottle of Fosters couldn't erase...
Next time I'm in down under I will bring that cable and well' have a

Regards
Reinhold

[n1546660]

haha!  Hey, sounds good mate!  

Thanks again!  

- Andy