remote access

[drdos2006]

Ok, looks like some people have issues and some don't with this model. ( F90-610025-06 ) I am assuming it the single port modem and you need to port forward 22/TCP in your router.

regards
[edit]
More information

http://forums.att.com/t5/Routers-and...r/td-p/2027807
This section here may help you to put the modem into bridged mode to the router.

Re: Bridge Mode for F90 Modem to Linsys Router
Options

* Mark as New
* Bookmark
* Subscribe
*
* Subscribe to RSS Feed
*
* Highlight
* Print
* Email to a Friend
*
* Report Inappropriate Content

03-29-2010 03:11:47 PM

Hello marhar,



Thank you for the reply.

If you are not getting the same options, please try to steps for Westell F90 modem.To bridge the Westell F90 modem, do the following:

1. Open a web browser.
2. Type 192.168.1.254 in the address bar.
3. Click the Go button or press the enter key on the keyboard.
4. Click the Advanced link.

There may be a prompt for a Modem Access Code. If so, do the following:
5. Locate the yellow sticker on the bottom of the Westell F90 modem.

6. Type the code in the Modem Access Code field.
7. Click the Continue button.

8. Click on the PPP Location link.
9. Choose PPP is on the computer, gateway or router radio button.
10. Click the Save Changes button.

[/edit]

regards

[amalafrida]

placing machine in 'bridged mode' as per instructions cuts all internet connectivity. I am forced to reset the modem in order to regain connectivity.

thanks, but just did not work.

I can successfully ping public ip from LAN, but not from a remote site. Any thoughts? Any further suggestions?

I certainly appreciate your attention to this matter. Quite a tough nut to crack.

traceroute from LAN to public IP (successful):
traceroute my.public.ip.address
traceroute to 74.181.252.241 (my.public.ip.address), 30 hops max, 60 byte packets
1 10.0.0.1 (10.0.0.1) 1.021 ms 1.264 ms 1.879 ms ... bing, hits the router
2 adsl-074-181-252-241.sip.mem.bellsouth.net (my.public.ip.address) 10.651 ms 18.783 ms 19.076 ms ... bing, hits the modem NIC

traceroute from remote site to public ip address:
traceroute my.public.ip.address (fails)
traceroute to my.public.ip.address (my.public.ip.address), 30 hops max, 60 byte packets
1 hdo127lab190.reggie.first.lib.ms.us (172.31.127.33) 4.746 ms 4.885 ms 87.057 ms
2 172.31.127.1 (172.31.127.1) 8.326 ms 23.399 ms *
3 172.17.209.1 (172.17.209.1) 87.437 ms 89.156 ms 89.788 ms
4 12.81.52.26 (12.81.52.26) 187.721 ms 187.847 ms 188.341 ms
5 12.81.104.92 (12.81.104.92) 89.834 ms 187.219 ms 187.450 ms
6 * * *
7 172.17.209.227 (172.17.209.227) 20.305 ms 86.711 ms 86.825 ms
8 * 74.231.173.5 (74.231.173.5) 89.997 ms 90.101 ms
9 12.81.48.6 (12.81.48.6) 21.835 ms 87.577 ms 88.676 ms
10 ixc00mem-7-0-1.bellsouth.net (65.83.237.77) 37.160 ms 110.459 ms 110.608 ms
11 * 12.81.52.47 (12.81.52.47) 95.265 ms 95.369 ms
12 * 12.81.52.24 (12.81.52.24) 18.241 ms 18.387 ms
13 12.81.52.21 (12.81.52.21) 17.503 ms 103.237 ms 103.410 ms
14 70.159.236.104 (70.159.236.104) 18.666 ms 103.542 ms 103.727 ms
15 70.159.236.35 (70.159.236.35) 18.296 ms 102.205 ms 102.707 ms
16 * * *
17 * * *
29 * * *
30 * * *
never reaches destination

Robert

[drdos2006]

From the link I gave you, it appears that this modem is full of problems. Have a look at the last post from dggriffin.

My suggestion at this time would be to replace the modem and router with a modem/router that will allow you to port forward. See if you can beg, borrow one from a friend to test with.

regards

[amalafrida]

yep. i think you're on to something. I did read the post. currently on line with ATT tech support, trying patiently to walk them through a simple ping to my public ip to establish that likely the problem is on their end.

we'll see.

will get back with you directly.

Robert

[amalafrida]

Ok. Long conversation with ATT. After much ado, they say that they can ping my public IP. I've tried it twice offsite today with no success. I wonder if I might get you to give it a try.

At least, if now the public IP is visible, as it has not been heretofore, I'll be able to move forward to establishing an ssh session.

If you cannot ping it, then I'll begin searching for a replacement modem

Thanks in advance,

Robert

[amalafrida]

so, just trying to get things in order here.
am i correct in assuming that pinging that public address is the sine qua non of setting up this connection?

if that does not work, then nothing can move forward?

kind of like a telephone analogy ... if no one answers the number you dial, then conversation is impossible. am I seeing this correctly?

robert

[drdos2006]

Hi Robert

I tried to ping your public address but cannot get a response. Some modem allow the ping to be received in the settings section. If ATT have said they can ping your modem then they might be using different terminology to say they can connect to your modem.

Yes, you are correct using the telephone analogy.

My advice would be to get a modem/router where you can tweak the settings.

regards

[amalafrida]

yes, thanks for the response. i've located a combo modem/router in Memphis and will run up tomorrow and snag it. Leaving town soon and will probably not be able to get back on this for 5 or 6 days.

the seller is an ex-ATT tech/installer. he seems to think this will work. and has offered to take it back if it does not.

AT&T 2Wire Modem 2701HG-B - $35 (Bartlett)
Up for sale is one AT&T 2Wire 2701HG-B Modem with ac adapter & ethernet cable, not included cdrom, telephone cables, or manual.

And once again thanks for you help. I don't really understand why ubuntu people lock in on an issue like this and make an effort to get it taken care of, but that's just another reason why I turned away from Microflaccid 7 years ago and have never looked back. I must confess that I've taken far more from the Ubuntu community than I have returned. But after this, I'm gonna change my ways.

All the best.

[drdos2006]

No problem.
I have bookmarked your topic and will check back in 5 or 6 days (unless you want to PM me when you are ready ).

regards

[stephenbbb]

Robert was unable to ping my IP.
when I go in advanced settings I have:
ATM Circuit Identifier: VPI: 0

VCI: 35
ATM Encapsulation: bridged LLC
ATM PVC Search: Disabled

in application support/advanced I discovered that there was 'block ping' checked. it is now unchecked.
Robert, please, try pinging again.

BTW ssh will not work as my Ubuntu is totally frozen and I am posting this from windows, which does not have an ssh server.
drdos,
pls advise if I need to change some of the settings above.
thank you all. I really wish Bell could hire smb who understands networking.