dslreports logo
 
    All Forums Hot Topics Gallery
spc
uniqs
5
tprince
join:2008-06-26
Edmonton, AB

tprince to TSI Gabe

Member

to TSI Gabe

Re: IPv6 beta

Is it possible to have our static IPv4 attached to an IPv6 account.
34764170 (banned)
join:2007-09-06
Etobicoke, ON

34764170 (banned)

Member

said by tprince:

Is it possible to have our static IPv4 attached to an IPv6 account.

I have prodded about this a number of times. TSI is slacking off.
dandin1
join:2008-05-27

dandin1 to tprince

Member

to tprince
Not yet, but you can work around that with an extra PPPoE tunnel that uses your static-IP account.


  1. First, add a line to pppd's pap-secrets with your @hsiservice.net account info.

  2. Modify your IPv6 ppp peer file to prevent it from acquiring an IPv4 address. You can do this by remove "defaultroute".

  3. Connect both ppp sessions! I don't think the order matters, but I start with the IPv4 one.



On Tomato, things are a bit more fragile because of its rigid environment. Modifying files will not do! You will have to configure scripts to run when the WAN connects. Scripts can be modified from the "Administration" sub-menu. Something like:

echo \"USERNAME@hsiservice.net\" \* \"PASSWORD\" \* >> /etc/ppp/pap-secrets

cat > /etc/ppp/peers/spppoe EOF
user 'USERNAME@hsiservice.net'
hide-password
nobsdcomp
nodeflate
lock
noauth
plugin rp-pppoe.so
br1
mtu 1492
mru 1492
noip
usepeerdns
lcp-echo-interval 5
lcp-echo-failure 12
maxfail 1
nodetach
holdoff '30'
EOF

redial spppoe &

=====

You would configure the tomato UI to connect with your static IPv4 account, then have it run that script when it connects. The peer file (in my example "spppoe") must start with an 's', which is a Tomato/MLPPP-specific hack to allow multiple PPPoE tunnels on the same interface.