Sagem router and VPN

audioslim · 10-01-08, 01:54 PM

Well I suppsecdly have a netgear router on it's way to me.

Phoned up support, got India (or wherever), got put on hold, got taken off hold and sat a listended to generasl office chat for 10 mins in the background.
Phoned back, expained situation to now Scottish lady, got passed to second line support (I think), explained situation and they are sending out a Netgear (I'm assured).

Heres hoping.

Slim

mossywell · 12-01-08, 08:52 PM

Just a thought, but the VPN passthrough v NAT-T applies only to IPSec based VPNs. I see that the Nortel VPN servers also support SSL VPNs, so your company might also have that available as a connectivity solution? (No mention of PPTP anywhere in the documentation that I can see [cough]; that would have worked as well, but most security / networking people take the phrase "PPTP" to be an expletive.

)

barnjp · 15-01-08, 04:48 PM

I am in exactly the same position - see other posts. They said they'd send a Netgear router. Another Sagem turned up. Tried again and they said once you have a Sagem, always a Sagem (me = v. angry). Asked to "complain", because these days sounding displeased on the phone gets you nowhere. Spoke to someone who "might be able to get me a Netgear router", but have not heard back from them...

Now the v2 Netgear has been hacked, I vote we concentrate on hacking the Sagem. After all, I have a spare one.

In terms of firmware etc how does the Sagem differ from the Netgear?

mossywell · 15-01-08, 05:34 PM

Quote:

Originally Posted by barnjp

In terms of firmware etc how does the Sagem differ from the Netgear?

Very similar. I don't have one but what I can deduce from what I've read (and filling in the gaps with a goodly dose of guesswork)...
- It's running the same kernel version but in 64-bit mode. (Maybe minor version differences.)
- Almost certainly based on the same GPL code / Busybox and all that.
- It's running telnet, but the telnet is inaccessible. (Guesswork: probably no accounts for login to authenticate so telnet login attempts will always fail. If so, why load it? Hmmm...)
- It's running all the other junk that these firmwares run, aimrc and so on.
- If I'm right, parts of the firmware source should be publically available. However, I couldn't locate them and my guess is (and this doesn't constitute a formal accusation that I can be sued for - it's just speculation!) that Sagem are not playing by the book.
- Brush up on your French if you don't speak it! There's lots of useful stuff around but in French (given that it's an off-the-shelf router en France).

Er, that's all I can say about it. Sorry.

James67 · 15-01-08, 07:04 PM

The Sagem router has a 64-bit processor? I thought it used the Broadcom BCM6348 which has a MIPS32 core.

mossywell · 15-01-08, 07:44 PM

Yes, odd that the OS signature is for x86_64 SMP. Could a duff signature, but I won't know until I get one.

mossywell · 15-01-08, 07:48 PM

Oh - hang on a bit - doesn't 32-bit MIPS need x86_64? [racks brains]. If so, I'll get my coat.

barnjp · 15-01-08, 08:10 PM

I know this may have been covered, but does anyone know the differences between our 2504 and the 2400 on sale in France then?

James67 · 15-01-08, 08:37 PM

Quote:

Originally Posted by mossywell

Oh - hang on a bit - doesn't 32-bit MIPS need x86_64? [racks brains]. If so, I'll get my coat.

A MIPS core needs MIPS code. I'm not sure what signature you're referring to, but I'm guessing that it's the build system signature, not the target system. So all it's saying is that it was compiled on a x86_64 machine.