Our website would like to use cookies to store information on your computer. You may delete and block all cookies from this site, but parts of the site will not work as a result. Find out more about how we use cookies.

Login or Register

Powered by
Powered by Novacaster
 
Linux devices & BT Routers
by Simon Giles at 17:35 11/04/11 (Forum::Technical Advice::General)
One of our artists (we provide studios) is having the following problem:

Re. internet, I'm having real problems connecting _any_ linux device to
the router (I've tried 8 different ones!). I think this is a BT hardware problem. I can advise with tech logs if need be.

The Router is a BT Business Hub 2700HGV
Can anyone help?


--
billycan
<< - Ameol revisited >>
View Comments (Threaded Mode) Printer Version
Linux devices & BT Routers Simon Giles - 17:35 11/04/11
Re: Linux devices & BT Routers Simon - 19:17 11/04/11
If the router's handing out IP addresses over DHCP, he needs to make sure his Linux box is expecting to get its address that way.

What's the IP range that the router's giving out over DHCP (assuming that's what it's trying to do), and what's the IP address of the Linux box when it's been connected to the router with an Ethernet cable and booted up?
--
simon

Re: Linux devices & BT Routers Simon Giles - 21:53 11/04/11
Thanks Simon - I'll check the IP range and IP address when back in the office tomorrow...
--
billycan
- Deleted User Account - 23:52 11/04/11
-
Re: Linux devices & BT Routers Simon Giles - 11:16 12/04/11
Ans: wireless, and here's his log from this morning:

Network Manager log
===================

Hi Simon,

Here's the log.

I have the DNS servers set to 8.8.8.8,8.8.4.4h

Apr 12 09:32:06 faversham NetworkManager[926]: (wlan0): DHCPv4 request timed out.
Apr 12 09:32:06 faversham NetworkManager[926]: (wlan0): canceled DHCP transaction, DHCP client pid 1934
Apr 12 09:32:06 faversham NetworkManager[926]: Activation (wlan0) Stage 4 of 5 (IP4 Configure Timeout) scheduled...
Apr 12 09:32:06 faversham NetworkManager[926]: Activation (wlan0) Stage 4 of 5 (IP4 Configure Timeout) started...
Apr 12 09:32:06 faversham NetworkManager[926]: (wlan0): device state change: 7 -> 9 (reason 5)
Apr 12 09:32:06 faversham NetworkManager[926]: Activation (wlan0) failed for access point (TheWorkhouse0410)
Apr 12 09:32:06 faversham NetworkManager[926]: Marking connection 'Auto TheWorkhouse0410' invalid.
Apr 12 09:32:06 faversham NetworkManager[926]: Activation (wlan0) failed.
Apr 12 09:32:06 faversham NetworkManager[926]: Activation (wlan0) Stage 4 of 5 (IP4 Configure Timeout) complete.
Apr 12 09:32:06 faversham NetworkManager[926]: (wlan0): device state change: 9 -> 3 (reason 0)
Apr 12 09:32:06 faversham NetworkManager[926]: (wlan0): deactivating device (reason: 0).
Apr 12 09:32:06 faversham kernel: [ 149.348088] wlan0: deauthenticating from 34:ef:44:dc:80:31 by local choice (reason=3)

will now check for router IP info...
--
billycan

- Deleted User Account - 12:32 12/04/11
-
Re: Linux devices & BT Routers Simon Giles - 14:05 12/04/11
Thanks James. Just ran out of time to experiment - the guy (Jake) in question is back Thursday. Meanwhile, is manually assigning an IP at the Router the way of getting round this IPv4 incompatibility?
--
billycan
Re: Linux devices & BT Routers Simon - 14:39 12/04/11
James means give the Linux device a manually assigned IP on the same subnet, not to give the Router one.

What we're trying to do is work around the problem James has mentioned of the Linux box asking for an address from the router using DHCP and then failing to cope with being told to use IPv4 in the response.
--
simon

- Deleted User Account - 14:59 12/04/11
-
Re: Linux devices & BT Routers Simon Giles - 15:47 12/04/11
Cheers guys :-) - we'll see later this week...
--
billycan