mmay149q
join:2009-03-05
Dallas, TX
| reply to x51
Re: U-Verse Static IP's: Not Working, Can't figure out problem
Well you are right on that, it only see's one mac, but if you hook it up to multiple NIC's then that takes care of the issue. Also if you are going through a switch/firewall, you can just static assign it to the machine, it works that was as well.
--
"Technological progress is like an axe in the hands of a pathological criminal." -Albert Einstein |
|
Darron
@sbcglobal.net
| I've got static IPs, and I'm trying to get more than one IP actually assigned to something.
I -want- to send multiple IPs to the same machine (firewall), but from reading enough posts the 2wire appears to be something of a joke as far as an internet router goes and can't do that. So...
I've got several machines behind a switch, which is connected to the 2wire. The machines are all running linux with static IPs configured.
The 2wire shows two machines (not a third) on the interface. On the "Edit Address Allocations Settings" page, two machines show as "Static IP" on the left side, but the right side shows machine #1 with the correct static IP, but machine #2 is set to WAN IP. If I try to change it to the correct static IP, then I get an error "For the public routed subinterface only WAN IP mapping is allowed.".
How can I get a few more of my static IPs actually attached to something? |
|
bclbob
join:2000-06-23
Oak Park, IL
clubs:
| Did you configure the "Public Routed Subinterface" section on this page?
»192.168.1.254/xslt?PAGE=J09&THIS···PAGE=J09
If so, you might have the wrong netmask, for a 5 public IP block you need 255.255.255.248 |
|
Darron
@sbcglobal.net
| Weird. Okay, By going to 192.168.1.254/ instead of your direct link, I get a different set of configuration pages. The pages I was looking at (C06) shows the pubic routed interface enabled and configured. The page you gave (J09) shows the public interface as blank.
When I enter the public interface on the J09 page, it refreshes to the status page, but does not show any public interface on that page. When I go back to J09, the public interface is blank again.
Any ideas? |
|
Darron
@sbcglobal.net
| The public interface on page J09 never shows, but the detailed log shows something is happening. Here, I changed the route from .6 to .5, cleared the log, then set it back.
INF 2009-06-05T20:27:58-05:00 lmd: ipnet2: DOWN on bridge0:2 with 75.63.108.5
INF 2009-06-05T20:27:58-05:00 lmd: ipnet2: UP on bridge0:2 with 75.63.108.6/29
INF 2009-06-05T20:27:59-05:00 lmd: ipnet2: dns change on bridge0:2 DNS1: 75.63.108.6 DNS2: 0.0.0.0 |
|
Darron
@sbcglobal.net
| reply to bclbob
The netmask does show 248, I forgot to mention that.
It's working for one computer, but never more than that. Do they have to be plugged in to different ethernet jacks on the 2wire? they're all on a switch, which is connected to the 2wire on one jack.
I see a weird "Display alert when another router is connected to this router" checkbox on the J09 page... what's that about?
On the C06 page, there is an "Auto firewall open" checkbox, which is cleared. What does that do? ... or should I always use the J pages and not the C pages? |
|
x51
join:2009-05-27
Stratford, CT | reply to Darron
Darron,
I had a lot of trouble with machines not being seen when I statically assigned my ips. Your best bet might to use DHCP, then sticky the publics on the machines you want to have them. |
|
x51
join:2009-05-27
Stratford, CT
| reply to Darron
quote:
It's working for one computer, but never more than that. Do they have to be plugged in to different ethernet jacks on the 2wire? they're all on a switch, which is connected to the 2wire on one jack.
When you say switch... do you mean a regular switch or a router like a linksys or netgear with a built in switch or something?
If you are using a router, this is your issue.. it wont happen. The router has one public interface and that's all the 2wire will see.
If it's a regular (non routing) switch... then forget all that stuff i just said  |
|
Darron
@sbcglobal.net
| I finally got it (so far, anyway, it works) After connecting and booting up an old laptop off an Ubuntu LiveCD, I disproved my "must be on seperate jacks on the 2wire" theory, and in the process figured out what it really was.
Sorry, I was a little boneheaded. The new NICs were in static IP mode, not DHCP. The 2wire will never 'see' a NIC card in the device list until it requests a DHCP address. That kind of makes sense. It's crappy, but no crappier than the rest of it, really. It works, so for that at least I'm thankful.
The problem was, the second NIC that half-works was once on DHCP, so the 2wire knew about it... but it was no longer, and the 2wire was ignoring it. So, I could try to configure it, but the 2wire wasn't going to let me. (The error message is NO help there) The third and fourth NIC cards that 2wire never saw as DHCP clients of course never showed up at all.
So, I set all 4 (yeah 4 now) of the new NICs to DHCP mode, and then went to the address allocation page and switched them to the IP addresses I wanted them to use.
Here's my question. I'm worried about leaving them as 'fixed' DHCP entries, because the computers may be off for extended periods. Will the 2wire "forget" static IP settings for a computer it hasn't seen in a while?
By the way, they're not physical machines... the new 4 are all in a single VMWare virtual machine in bridge mode. They all have dedicated MAC addresses, and a tcpdump trace on the ethernet wire shows they are talking with unique MACs, so I knew that wasn't it. I didn't want to mention that because I was sure that would throw off the assistance. Once a devices (virtual or otherwise) is talking with a different MAC address, there's absolutely no difference on the physical ethernet layer between that and a physical box. In bridged adapter mode, VMWare acts like a network switch (not router).
Why 4 NICs on a single virtual machine? Because now that PC can route them to where they really need to go. It's an ugly solution for an almost-broken 2wire system.
bclbob and x51, thanks for your help and your time. |
|
x51
join:2009-05-27
Stratford, CT
1 edit | said by Darron :
Sorry, I was a little boneheaded. The new NICs were in static IP mode, not DHCP. The 2wire will never 'see' a NIC card in the device list until it requests a DHCP address.
It will usually see it eventually if the static is on the same subnet and you generate a lot of taffic. But I've had it take up to 48 hours that way. So DHCP is the ony really usable solution.
said by Darron :
Here's my question. I'm worried about leaving them as 'fixed' DHCP entries, because the computers may be off for extended periods. Will the 2wire "forget" static IP settings for a computer it hasn't seen in a while?
It shouldnt be a problem. With regualar DHCP the lease will expire, but with the Fixed option selected it's not "supposed" to expire. |
|
bclbob
join:2000-06-23
Oak Park, IL
clubs:
1 edit | reply to Darron
said by Darron :
Here's my question. I'm worried about leaving them as 'fixed' DHCP entries, because the computers may be off for extended periods. Will the 2wire "forget" static IP settings for a computer it hasn't seen in a while?
I only have the DMZplus mode which assigns the single router static IP to a chosen device via DHCP and yes, it does forget if the assigned computer doesn't DHCP in a while. the 2wire hands out a 10 minute lease and I seem to reember thats how long it took for the traffic to stop flowing when I configured my router with the static IP and to block DHCP from the Internet (and hence the 2wire).
It might be different for true statics, but I wouldn't bet on it. |
|
