Connecting a Linux EEEPC to a Telecom Thomson Modem

Forums › Spark New Zealand (including Skinny and BigPipe) › Connecting a Linux EEEPC to a Telecom Thomson Modem - no luck?

lissie

495 posts

Ultimate Geek

#66149 13-Aug-2010 11:19

Hi,
I am on Telecom using their supplied Thomson router. It works generally fine with my XP laptop and mostly my partner's Vista laptop is OK with it too (the mostly is that he's on and then it disconnects and then we have to reboot the modem- I put this down to vista problems)

But now Iwant to connect my little EEEPC netbook its a 4 G running linux - so in verbose mode I can at least see the problem.

It connects fine to the neighbours unsecured wireless
It connects to the thomson fine with a direct cable

But when I try to connect to the thomson I select WPA and enter the network key - I leave the "key index" blank and then get the following as it trys to connect

sending on socket/fallback
dhcpdiscover on arth0 to 255.255.255.255 port 67 interval 5
dhcpdiscover on arth0 to 255.255.255.255 port 67 interval 5
dhcpdiscover on arth0 to 255.255.255.255 port 67 interval 13
dhcpdiscover on arth0 to 255.255.255.255 port 67 interval 8
NO DHCPOFFERS received

I have also had no luck getting my skype phone to connect to the thomson - and I am starting to wonder if Telecom just doesn't support linux???

I help authors publish their books - DIYPublishing.co.nz

BlakJak

1275 posts

Uber Geek

Trusted

#367233 13-Aug-2010 15:58

Do you have the DHCP server on your router running?

'NO DHCPOFFERS received' is pretty self explanitory; your computer needs an IP address and to know where the default gateway (the router) is, either you configure this manually or automatically via DHCP.

The Thomson routers are pretty basic but they should all do DHCP.
You should also be able to find out the routers IP address and the range of its DHCP server. Knowing that, you can manually set up your EeePC with IP (outside of the range), gateway (ip of the router), and DNS servers (ip of the router will probably work fine) and see what happens?

This is networking basics, it has little to do with the operating system you're using.
You could use your windows machines as a guide - get the IP/Subnet Mask/Gateway/DNS servers that they are issued, and then manually configure them into your EeePC and see what happens.

Telecom (I assume you mean Xtra) probably don't support Linux because they don't know how it works and don't care to support a 'minority' operating system. There are ISPs out there willing to give it a go, heck maybe even Xtra would if you got the right CSR.

You could also consider joining something like NZLUG (via www.linux.net.nz) whos mailing list would be able to advise you on linux-specific troubleshooting.

BJ.
PS: I assume you mean the EeePC 700 series ("4 G"). I found the Xandros-based default Linux OS a little limiting, you could try something like http://www.geteasypeasy.com/ as an alternative if you want some more power. It has the advantage of being Ubuntu based, and Ubuntu is one of the mature desktop-oriented distros with a larger support base in the community.

No signature to see here, move along...

cyril7

9058 posts

Uber Geek

ID Verified

Trusted

Subscriber

#367323 13-Aug-2010 19:07

I think I would want to take Wap encryption off the wireless, and see if it connects, then go from there. You have indicated that it connects via a wired connection so DHCP I doubt is an issue (and really these are pretty basic ICMP activities which just work, gear does not often get in the wild with these basics not working), but WAP there can be lots of issues.

Cyril

BlakJak

1275 posts

Uber Geek

Trusted

#367393 13-Aug-2010 22:11

That's good advice, start with no encryption and prove that works.
Then go up to the highest encryption that both ends support (WPA, if you can). Then work backwards....

No signature to see here, move along...